From: David Howells <dhowells@warthog.cambridge.redhat.com>
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: [PATCH] PAG support only
Date: Wed, 14 May 2003 09:17:43 +0100 [thread overview]
Message-ID: <13536.1052900263@warthog.warthog> (raw)
In-Reply-To: <20030513213759.A9244@infradead.org>
Christoph Hellwig wrote:
> Please split this into 2 lines as per Documentation/CodingStyle. Even better
> make vfs_token_put handle a NULL argument.
Done the latter.
> Random whitespace change
Gone.
> - and even a wrong one..
I disagree, but no matter.
> > +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..
And then there's the people who said I shouldn't use kmalloc but should create
a slab instead...
> > + if (pag>0) {
> > + /* join existing PAG */
> > + if (tsk->vfspag->pag &&
> > + tsk->vfspag->pag==pag)
> > + return pag;
>
> Please try to get your code in conformance with Documentation/CodingStyle.
You are suggesting what changes exactly?
David
next prev parent reply other threads:[~2003-05-14 8:05 UTC|newest]
Thread overview: 17+ 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-14 5:33 ` Christoph Hellwig
2003-05-16 15:24 ` Derek Atkins
2003-05-14 8:17 ` David Howells [this message]
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
[not found] <20030513175240.6313ea92.akpm@digeo.com>
2003-05-14 9:44 ` David Howells
2003-05-14 10:00 ` Andrew Morton
2003-05-14 10:01 ` Miles Bader
-- strict thread matches above, loose matches on Subject: below --
2003-05-14 16:04 Chuck Ebbert
2003-05-14 16:20 ` William Lee Irwin III
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=13536.1052900263@warthog.warthog \
--to=dhowells@warthog.cambridge.redhat.com \
--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