From: Ravikiran G Thirumalai <kiran@in.ibm.com>
To: akpm@digeo.com
Cc: linux-kernel@vger.kernel.org, dipankar@in.ibm.com
Subject: Re: [patch] kstat cleanup
Date: Wed, 23 Oct 2002 20:01:53 +0530 [thread overview]
Message-ID: <20021023200153.B32662@in.ibm.com> (raw)
In-Reply-To: <20021022194111.A27878@in.ibm.com>; from kiran@in.ibm.com on Tue, Oct 22, 2002 at 07:41:11PM +0530
Hi Andrew,
Here is the kstat cleanup patch set with all the arch changes.
Applies neatly on mm-3. I am mailing the url since both the patches
exceed 40k limit by 900 bytes :). The first patch is for
generic+i386 changes, the second patch is for arch specific changes
for all other archs. Tested well on a PIII 4 way.
Patches can be found at:
http://osdn.dl.sourceforge.net/sourceforge/lse/kstat-2.5.44-mm3-2.patch
and
http://osdn.dl.sourceforge.net/sourceforge/lse/kstat-arch-2.5.44-mm3.patch
Thanks,
Kiran
On Tue, Oct 22, 2002 at 07:41:11PM +0530, Ravikiran G Thirumalai wrote:
> Hi Andrew,
> Here's the kstat cleanup you'd suggested sometime ago.
> I have used Rusty's per_cpu infrastructure for the stats now.
> Here're the changes in short.
>
> 1. Break out disk stats from kernel_stat and move disk stat to blkdev.h
> 2. Group cpu stat in kernel_stat and make them "per_cpu" instead of
> the NR_CPUS array
> 3. Remove EXPORT_SYMBOL(kstat) from ksyms.c (as I noticed that no module is
> using kstat)
>
> The foll patch is tested on a 4 way PIII xeon. This patch has changes
> for i386 files (+ arch independent changes)(.. it'll break other archs).
> I am in the process of changing other archs. Patch for the same to follow
> soon. In the meanwhile, do let me know if the patch is ok by you. Patch
> applies neatly on 2.5..44-mm2
prev parent reply other threads:[~2002-10-23 14:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-22 14:11 Ravikiran G Thirumalai
2002-10-23 14:31 ` Ravikiran G Thirumalai [this message]
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=20021023200153.B32662@in.ibm.com \
--to=kiran@in.ibm.com \
--cc=akpm@digeo.com \
--cc=dipankar@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
/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
Powered by JetHome