All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Steve Dickson <SteveD@redhat.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
	nfs@lists.sourceforge.net,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [NFS] Re: [PATCH v2] reduce NFS stack usage
Date: 25 Sep 2003 12:37:25 -0700	[thread overview]
Message-ID: <shsk77w3bii.fsf@charged.uio.no> (raw)
In-Reply-To: <3F7335B4.1070002@RedHat.com>

>>>>> " " == Steve Dickson <SteveD@redhat.com> writes:

     > Also, not like there much choice in matter, but I wonder what
     > type of performance hit (if any) there will be by making these
     > routines call kmalloc()... lookups and readdirs are pretty
     > popular ops...

There are always alternatives...

If really this is a problem, how about slabifying the structs
nfs_fattr and/or nfs_fh?

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?

Cheers,
  Trond

  reply	other threads:[~2003-09-25 19:37 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   ` Trond Myklebust [this message]
2003-09-30  1:55     ` [NFS] " 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
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=shsk77w3bii.fsf@charged.uio.no \
    --to=trond.myklebust@fys.uio.no \
    --cc=SteveD@redhat.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nfs@lists.sourceforge.net \
    /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.