public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Gruenbacher <agruen@suse.de>
To: Neil Brown <neilb@cse.unsw.edu.au>,
	Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: linux-kernel@vger.kernel.org, Olaf Kirch <okir@suse.de>
Subject: [RFC] ACLs over NFS: Handling of large buffers
Date: Thu, 20 Feb 2003 14:11:42 +0100	[thread overview]
Message-ID: <200302201411.42714.agruen@suse.de> (raw)

Hello,

in the current kernel nfsd, a buffer of (8+1)k is allocated for each 
kernel nfsd thread. Since the NFS ACL protocol requests arrive at the 
same transport endpoint, in the short term (i.e., for the NFS ACL 
protocol) I need a limit of (24+1)k for each nfsd thread. While this 
wastes memory that will not be used most of the time, the amount of 
wasted memory is still not totally crazy.

However, the NFS ACL protocol still does not support Extended Attributes 
in general, so somebody will have to implement one of the EA NFS 
protocols in addition. (I'm leaning towards the one protocol extension 
from  SGI OB1). This will require a buffer of 64k. So I'm wondering how 
we could solve the problem of buffer space more flexibly. Any ideas?


Thanks,
Andreas.


                 reply	other threads:[~2003-02-20 13:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200302201411.42714.agruen@suse.de \
    --to=agruen@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@cse.unsw.edu.au \
    --cc=okir@suse.de \
    --cc=trond.myklebust@fys.uio.no \
    /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