Date: Sat, 16 Jun 2001 19:41:55 -0400 From: Alfred Perlstein <bright@rush.net> To: Sascha Schumann <sascha@schumann.cx> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: poll(2)'s arbitrary limit Message-ID: <20010616194155.L1832@superconductor.rush.net> In-Reply-To: <Pine.LNX.4.33.0106170013280.3244-100000@rossini.schumann.cx>; from sascha@schumann.cx on Sun, Jun 17, 2001 at 12:30:47AM %2B0200 References: <Pine.LNX.4.33.0106170013280.3244-100000@rossini.schumann.cx>
next in thread | previous in thread | raw e-mail | index | archive | help
* Sascha Schumann <sascha@schumann.cx> [010616 19:03] wrote: > Hi, > > one of my applications uses the SGI State Threads Library > (I/O multiplexing scheduler). At its heart is a function > which concatenates the pollfd arrays of all threads and calls > poll(2). As sockets are shared between threads, the size of > the final pollfd array can easily be greater than > RLIMIT_NOFILE. Are you sure? #define RLIMIT_NOFILE 8 /* number of open files */ That would mean that the pollfd array is larger than the amount of open files you're allowed. I think it may be a good idea to actually allow double RLIMIT_NOFILE and FD_SETSIZE for flexibility. Anyone object? -- -Alfred Perlstein [alfred@freebsd.org] Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010616194155.L1832>