From: "J. Bruce Fields" <bfields@fieldses.org>
To: Andreas Gruenbacher <agruen@suse.de>
Cc: Andrew Morton <akpm@osdl.org>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/11] nfsacl
Date: Tue, 27 Apr 2004 11:18:03 -0400 [thread overview]
Message-ID: <20040427151802.GA1490@fieldses.org> (raw)
In-Reply-To: <1082975143.3295.68.camel@winden.suse.de>
On Mon, Apr 26, 2004 at 12:28:47PM +0200, Andreas Gruenbacher wrote:
> nfsacl-lazy-alloc
> Allow to allocate pages in the receive buffers lazily. ACLs may have
> up to 1024 entries in nfsacl but usually are small, so allocating
> space for them on demand makes sense.
Is there any reason we couldn't set the maximum smaller than that? It
looks like the acl entries are pretty compact (12 bytes if I'm reading
the xdr code right?) so if we limited the length of an xdr-encoded acl
to a page that would still allow a few hundred entries. Are there
really people that need 1000-entry acls?
--Bruce Fields
next prev parent reply other threads:[~2004-04-27 15:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-26 10:28 [PATCH 0/11] nfsacl Andreas Gruenbacher
2004-04-27 15:18 ` J. Bruce Fields [this message]
2004-04-27 15:51 ` Andreas Gruenbacher
2004-04-27 16:12 ` J. Bruce Fields
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=20040427151802.GA1490@fieldses.org \
--to=bfields@fieldses.org \
--cc=agruen@suse.de \
--cc=akpm@osdl.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox