From: Christoph Hellwig <hch@infradead.org>
To: Nathan Neulinger <nneul@umr.edu>
Cc: David Howells <dhowells@redhat.com>,
torvalds@transmeta.com, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [OpenAFS-devel] Re: [PATCH] PAG support only
Date: Wed, 14 May 2003 06:33:46 +0100 [thread overview]
Message-ID: <20030514063345.A517@infradead.org> (raw)
In-Reply-To: <1052864839.20037.2.camel@nneul-laptop>; from nneul@umr.edu on Tue, May 13, 2003 at 05:27:20PM -0500
[openafs-devel dropped from the Cc-list due to stupid subscriber only policy]
On Tue, May 13, 2003 at 05:27:20PM -0500, Nathan Neulinger wrote:
> > > +static kmem_cache_t *vfs_token_cache;
> > > +static kmem_cache_t *vfs_pag_cache;
> >
> > How many of those will be around for a typical AFS client? I have the vague
> > feeling the slabs are overkill..
>
> What's a "typical client"?
The case we wan to optimize for. The question here is whether we really want
a separate slab or whether it makes more senze to just use the new kmalloc
slab (usually power of two sized).
next prev parent reply other threads:[~2003-05-14 5:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-13 16:33 [PATCH] PAG support only David Howells
2003-05-13 16:48 ` Jeff Garzik
2003-05-13 20:37 ` Christoph Hellwig
2003-05-13 22:27 ` [OpenAFS-devel] " Nathan Neulinger
2003-05-13 22:27 ` Nathan Neulinger
2003-05-14 5:33 ` Christoph Hellwig [this message]
2003-05-16 15:24 ` [OpenAFS-devel] " Derek Atkins
2003-05-14 8:17 ` David Howells
2003-05-14 8:39 ` Christoph Hellwig
2003-05-14 4:57 ` Muli Ben-Yehuda
2003-05-14 9:54 ` David Howells
2003-05-14 12:35 ` Muli Ben-Yehuda
2003-05-14 13:17 ` David Howells
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=20030514063345.A517@infradead.org \
--to=hch@infradead.org \
--cc=dhowells@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nneul@umr.edu \
--cc=torvalds@transmeta.com \
/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.