From: Doug Alcorn <doug@lathi.net>
To: linux-kernel@vger.kernel.org
Subject: FAQ followup: changes in open fd/proc in 2.4.x?
Date: 17 Nov 2000 10:58:12 -0500 [thread overview]
Message-ID: <m38zqitwtn.fsf@balder.seapine.com> (raw)
I am working on a project to port a commercial app to Linux. Our app
is essentially a dataserver with approximately two files per database
table. I did a search of this mailing lists archive on the subject
and found a discussion back in the 2.0.x days when the limit was 256.
Basically the discussion went like this:
guy who wanted more: I really need more fds
list: redesign your app
guy who wanted more: But my app is really mature
list: no response
I couldn't find any of the discussion from when the limit was
increased.
With the 2.2.x kernel, our choices are basically to live with the
limitation or redesign. We certainly don't like the limitation and
are talking about a redesign.
Now we get to the reason for this post. Has anything changed for
2.4.x? With release eminent, we don't really want to go through the
redesign and implementation if the architecture is different for
2.4.x. I don't closely follow linux-kernel (except through periodic
catch-ups on the kernel cousin). It seems like the VFS changes might
affect this, I don't know.
So basically, before we begin the arduous task of redesign is there
anything in the 2.4.x kernel that will affect our decisions?
PS, please CC: me on replies.
--
(__) Doug Alcorn (mailto:doug@lathi.net http://www.lathi.net)
oo /
|_/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2000-11-17 16:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-17 15:58 Doug Alcorn [this message]
2000-11-17 16:13 ` FAQ followup: changes in open fd/proc in 2.4.x? Richard B. Johnson
2000-11-17 16:21 ` Vasil Kolev
2000-11-17 16:21 ` Andi Kleen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m38zqitwtn.fsf@balder.seapine.com \
--to=doug@lathi.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.