From: "David S. Miller" <davem@redhat.com>
To: akpm@digeo.com
Cc: kiran@in.ibm.com, linux-kernel@vger.kernel.org,
netdev@oss.sgi.com, dipankar@in.ibm.com
Subject: Re: [patch] Make rt_cache_stat use kmalloc_percpu
Date: Fri, 20 Dec 2002 23:29:09 -0800 (PST) [thread overview]
Message-ID: <20021220.232909.88324816.davem@redhat.com> (raw)
In-Reply-To: <3E0418EC.B55941EE@digeo.com>
From: Andrew Morton <akpm@digeo.com>
Date: Fri, 20 Dec 2002 23:31:56 -0800
"David S. Miller" wrote:
> I can't consider this seriously until the kmalloc_percpu stuff
> actually makes it into Linus's tree. Last I checked, Andrew had
> a lot of legitimate gripes with the ideas.
Kiran's latest (vastly simpler) version looks fine to my eye.
Ok, so once that is in, he can feel free to resubmit the
rt_cache_state patch.
next prev parent reply other threads:[~2002-12-21 7:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-16 13:52 [patch] Make rt_cache_stat use kmalloc_percpu Ravikiran G Thirumalai
2002-12-21 7:05 ` David S. Miller
2002-12-21 7:31 ` Andrew Morton
2002-12-21 7:29 ` David S. Miller [this message]
2002-12-23 4:34 ` Ravikiran G Thirumalai
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=20021220.232909.88324816.davem@redhat.com \
--to=davem@redhat.com \
--cc=akpm@digeo.com \
--cc=dipankar@in.ibm.com \
--cc=kiran@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).