From: Neil Brown <neilb@suse.de>
To: Steve Dickson <steved@redhat.com>
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH 0/3] Make size of gssd_proc fd array a little more dynamic
Date: Wed, 28 Nov 2012 12:11:22 +1100 [thread overview]
Message-ID: <20121128010939.2475.13123.stgit@notabene.brown> (raw)
We recently had a request to raise the number of fds that gssd can
work with - again.
Rather than just change the hard-coded number I seemed to make sense
to have it depend on RLIMIT_NOFILE - as poll won't work with more than
that anyway.
So the default becomes 1024, but it is easily raised further without
code change.
These patches implement that.
NeilBrown
---
Neil Brown (3):
gssd_proc: use pollsize, not FD_ALLOC_BLOCK, in get_poll_index().
gssd_proc: remove pointless test against FD_ALLOC_BLOCK in process_pipedir
gssd: base the size of the fd array on the RLIMIT_NOFILE limit.
utils/gssd/gssd_proc.c | 14 +++++++++-----
1 file changed, 9 insertions(+), 5 deletions(-)
--
Signature
next reply other threads:[~2012-11-28 1:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-28 1:11 Neil Brown [this message]
2012-11-28 1:11 ` [PATCH 2/3] gssd_proc: remove pointless test against FD_ALLOC_BLOCK in process_pipedir Neil Brown
2012-11-28 1:11 ` [PATCH 1/3] gssd_proc: use pollsize, not FD_ALLOC_BLOCK, in get_poll_index() Neil Brown
2012-11-28 1:11 ` [PATCH 3/3] gssd: base the size of the fd array on the RLIMIT_NOFILE limit Neil Brown
2012-11-28 13:10 ` J. Bruce Fields
2012-11-29 0:30 ` NeilBrown
2012-12-11 0:02 ` NeilBrown
2012-12-11 16:16 ` J. Bruce Fields
2012-12-13 6:03 ` NeilBrown
2012-12-13 19:21 ` J. Bruce Fields
2012-11-28 19:54 ` [PATCH 0/3] Make size of gssd_proc fd array a little more dynamic Steve Dickson
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=20121128010939.2475.13123.stgit@notabene.brown \
--to=neilb@suse.de \
--cc=linux-nfs@vger.kernel.org \
--cc=steved@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).