From: Dipankar Sarma <dipankar@in.ibm.com>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.5.69-mm3
Date: Fri, 9 May 2003 19:40:12 +0530 [thread overview]
Message-ID: <20030509141012.GD2059@in.ibm.com> (raw)
In-Reply-To: <20030508013958.157b27b7.akpm@digeo.com>
On Thu, May 08, 2003 at 08:41:12AM +0000, Andrew Morton wrote:
> http://www.zip.com.au/~akpm/linux/patches/2.5/2.5.69-mm3.gz
>
> Will appear sometime at
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.5/2.5.69/2.5.69-mm3/
>
>
> Small things. Mainly a resync for various people...
>
> rcu-stats.patch
> RCU statistics reporting
I am wondering what we should do with this patch. The RCU stats display
the #s of RCU requests and actual updates on each CPU. On a normal system
they don't mean much to a sysadmin, so I am not sure if it is the right
thing to include this feature. OTOH, it is extremely useful to detect
potential memory leaks happening due to, say a CPU looping in
kernel (and RCU not happening consequently). Will a CONFIG_RCU_DEBUG
make it more palatable for mainline ?
Thanks
Dipankar
WARNING: multiple messages have this Message-ID (diff)
From: Dipankar Sarma <dipankar@in.ibm.com>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.5.69-mm3
Date: Fri, 9 May 2003 19:40:12 +0530 [thread overview]
Message-ID: <20030509141012.GD2059@in.ibm.com> (raw)
In-Reply-To: <20030508013958.157b27b7.akpm@digeo.com>
On Thu, May 08, 2003 at 08:41:12AM +0000, Andrew Morton wrote:
> http://www.zip.com.au/~akpm/linux/patches/2.5/2.5.69-mm3.gz
>
> Will appear sometime at
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.5/2.5.69/2.5.69-mm3/
>
>
> Small things. Mainly a resync for various people...
>
> rcu-stats.patch
> RCU statistics reporting
I am wondering what we should do with this patch. The RCU stats display
the #s of RCU requests and actual updates on each CPU. On a normal system
they don't mean much to a sysadmin, so I am not sure if it is the right
thing to include this feature. OTOH, it is extremely useful to detect
potential memory leaks happening due to, say a CPU looping in
kernel (and RCU not happening consequently). Will a CONFIG_RCU_DEBUG
make it more palatable for mainline ?
Thanks
Dipankar
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2003-05-09 13:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-08 8:39 2.5.69-mm3 Andrew Morton
2003-05-08 8:39 ` 2.5.69-mm3 Andrew Morton
2003-05-09 14:10 ` Dipankar Sarma [this message]
2003-05-09 14:10 ` 2.5.69-mm3 Dipankar Sarma
2003-05-09 19:49 ` 2.5.69-mm3 Martin J. Bligh
2003-05-09 19:49 ` 2.5.69-mm3 Martin J. Bligh
2003-05-09 21:18 ` 2.5.69-mm3 Andrew Morton
2003-05-09 21:18 ` 2.5.69-mm3 Andrew Morton
2003-05-13 20:13 ` 2.5.69-mm3 Bill Davidsen
2003-05-13 20:13 ` 2.5.69-mm3 Bill Davidsen
2003-05-09 14:53 ` 2.5.69-mm3 William Lee Irwin III
2003-05-09 14:53 ` 2.5.69-mm3 William Lee Irwin III
2003-05-09 15:37 ` 2.5.69-mm3 William Lee Irwin III
2003-05-09 15:37 ` 2.5.69-mm3 William Lee Irwin III
2003-05-09 17:55 ` 2.5.69-mm3 William Lee Irwin III
2003-05-09 17:55 ` 2.5.69-mm3 William Lee Irwin III
2003-05-09 18:12 ` 2.5.69-mm3 William Lee Irwin III
2003-05-09 18:12 ` 2.5.69-mm3 William Lee Irwin III
2003-05-09 18:15 ` 2.5.69-mm3 William Lee Irwin III
2003-05-09 18:15 ` 2.5.69-mm3 William Lee Irwin III
2003-05-09 18:54 ` 2.5.69-mm3 William Lee Irwin III
2003-05-09 18:54 ` 2.5.69-mm3 William Lee Irwin III
2003-05-13 18:21 ` 2.5.69-mm3 bug Szonyi Calin
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=20030509141012.GD2059@in.ibm.com \
--to=dipankar@in.ibm.com \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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 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.