From: "J. Bruce Fields" <bfields@fieldses.org>
To: Andreas Gruenbacher <agruen@suse.de>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/11] nfsacl
Date: Tue, 27 Apr 2004 12:12:33 -0400 [thread overview]
Message-ID: <20040427161232.GC2086@fieldses.org> (raw)
In-Reply-To: <1083081107.19655.160.camel@winden.suse.de>
On Tue, Apr 27, 2004 at 05:51:47PM +0200, Andreas Gruenbacher wrote:
> On Tue, 2004-04-27 at 17:18, J. Bruce Fields wrote:
> > 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?
>
> Well, that's what the protocol allows so I don't see why we shouldn't
> implement it fully. Besides, nfsacl-lazy-alloc benefits the common case
> even more, because with small acls that fit into xdr_buf->head entirely,
> no page needs to be allocated.
Hm, so looks like xdr_buf->head would fit about 150 entries. Couldn't
that be enough?
--Bruce Fields
prev parent reply other threads:[~2004-04-27 16:12 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
2004-04-27 15:51 ` Andreas Gruenbacher
2004-04-27 16:12 ` J. Bruce Fields [this message]
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=20040427161232.GC2086@fieldses.org \
--to=bfields@fieldses.org \
--cc=agruen@suse.de \
--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