From: Steve Dickson <SteveD@redhat.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: nfs@lists.sourceforge.net
Subject: Re: Re: [PATCH v2] reduce NFS stack usage
Date: Thu, 25 Sep 2003 17:10:52 -0400 [thread overview]
Message-ID: <3F7359DC.10301@RedHat.com> (raw)
In-Reply-To: <mailman.1064518981.2825.linux-kernel2news@redhat.com>
Trond Myklebust wrote:
>
> There are always alternatives...
>
> If really this is a problem, how about slabifying the structs
> nfs_fattr and/or nfs_fh?
Why is allocating memory from a "private" slab is faster than
using a general purpose one (i.e. GFP_KERNEL)?
Something to do with lock contention?
>
> Also, since nfs_entry is only large due to the fh and fattr fields
> which are unused unless you have READDIRPLUS (in which case they are
> converted to pointers anyhow), how about kicking them out of
> nfs_entry altogether?
That would take care of readdirs...
SteveD.
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-09-25 21:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1064420466.30286.linux-kernel2news@redhat.com>
2003-09-25 18:36 ` [PATCH v2] reduce NFS stack usage Steve Dickson
2003-09-25 19:37 ` [NFS] " Trond Myklebust
2003-09-30 1:55 ` Steve Dickson
2003-09-30 15:31 ` UPDATED: " Steve Dickson
[not found] ` <mailman.1064518981.2825.linux-kernel2news@redhat.com>
2003-09-25 21:10 ` Steve Dickson [this message]
2003-09-26 0:07 ` Jeff Garzik
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=3F7359DC.10301@RedHat.com \
--to=steved@redhat.com \
--cc=nfs@lists.sourceforge.net \
--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 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.