From: Nathan Neulinger <nneul@umr.edu>
To: Christoph Hellwig <hch@infradead.org>
Cc: David Howells <dhowells@redhat.com>,
torvalds@transmeta.com, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org, openafs-devel@openafs.org
Subject: Re: [OpenAFS-devel] Re: [PATCH] PAG support only
Date: 13 May 2003 17:27:20 -0500 [thread overview]
Message-ID: <1052864839.20037.2.camel@nneul-laptop> (raw)
In-Reply-To: <20030513213759.A9244@infradead.org>
> > +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"?
I have machines that typically have 0 pags and tokens in kernel, and I
have machines that typically have a few hundred to a thousand.
Per pag on most clients will only have a single token, but number of
pags will depend totally on the nature of the machine.
I also have machines that have a few hundred pags around that don't have
any tokens in them, but could at any time.
-- Nathan
------------------------------------------------------------
Nathan Neulinger EMail: nneul@umr.edu
University of Missouri - Rolla Phone: (573) 341-4841
Computing Services Fax: (573) 341-4216
next prev parent reply other threads:[~2003-05-13 22:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-13 16:33 David Howells
2003-05-13 16:48 ` Jeff Garzik
2003-05-13 20:37 ` Christoph Hellwig
2003-05-13 22:27 ` Nathan Neulinger [this message]
2003-05-14 5:33 ` [OpenAFS-devel] " Christoph Hellwig
2003-05-16 15:24 ` 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=1052864839.20037.2.camel@nneul-laptop \
--to=nneul@umr.edu \
--cc=dhowells@redhat.com \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openafs-devel@openafs.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®