[17112] in Kerberos_V5_Development

home help back first fref pref prev next nref lref last post

Re: [RFC][PATCH] krb5 => libverto main loop

daemon@ATHENA.MIT.EDU (Nathaniel McCallum)
Wed Aug 24 09:24:33 2011

From: Nathaniel McCallum <npmccallum@redhat.com>
To: Sam Hartman <hartmans@mit.edu>
Date: Wed, 24 Aug 2011 09:24:18 -0400
In-Reply-To: <tsl62lnepz8.fsf@mit.edu>
Message-ID: <1314192260.2440.8.camel@localhost>
Mime-Version: 1.0
Cc: Ken Raeburn <raeburn@mit.edu>, "krbdev@mit.edu" <krbdev@mit.edu>,
   Tom Yu <tlyu@mit.edu>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krbdev-bounces@mit.edu

On Tue, 2011-08-23 at 18:13 -0400, Sam Hartman wrote:
> >>>>> "Tom" == Tom Yu <tlyu@MIT.EDU> writes:
> 
>     Tom> Sam Hartman <hartmans@MIT.EDU> writes:
>     >> I agree with Simo.  Please bundle something, do not create your
>     >> own.  Supporting things beyond select is quite important; you
>     >> need something that does more than 1024 fds at a minimum.
> 
>     Tom> But is needing more than 1024 file descriptors realistic for a
>     Tom> KDC or kadmind?
> 
> Yes, a KDC could have more than 1024 TCP connections.
> Rare but possible.

The risk for this increases once we began handling multiple requests
simultaneously. Before this, accept() would never execute until the
previous request had called close(). Async programming almost always
increases the number of fds used dramatically.

Nathaniel

_______________________________________________
krbdev mailing list             krbdev@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev

home help back first fref pref prev next nref lref last post