linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	cl@linux-foundation.org, tokunaga.keiich@jp.fujitsu.com
Subject: Re: [RFC][PATCH 1/2] Show quicklist at meminfo
Date: Fri, 22 Aug 2008 10:05:45 +0900	[thread overview]
Message-ID: <20080822100049.F562.KOSAKI.MOTOHIRO@jp.fujitsu.com> (raw)
In-Reply-To: <2f11576a0808210036icd9b61eue58049f15381bcc8@mail.gmail.com>

> > quicklist_total_size() is racy against cpu hotplug.  That's OK for
> > /proc/meminfo purposes (occasional transient inaccuracy?), but will it
> > crash?  Not in the current implementation of per_cpu() afaict, but it
> > might crash if we ever teach cpu hotunplug to free up the percpu
> > resources.
> 
> First, Quicklist doesn't concern to cpu hotplug at all.
> it is another quicklist problem.
> 
> Next, I think it doesn't cause crash. but I haven't any test.
> So, I'll test cpu hotplug/unplug testing today.
> 
> I'll report result tommorow.

OK.
I ran cpu hotplug/unplug coutinuous workload over 12H.
then, system crash doesn't happend.

So, I believe my patch is cpu unplug safe.


test method
--------------------------------------------------------------
1. open 7 terminal and following script run on each console.

CPU=cpuXXX; while true; do echo 0 > /sys/devices/system/cpu/$CPU/online; echo 1 > /sys/devi
ces/system/cpu/$CPU/online;done

2. open another console, following command run.

watch -n 1 cat /proc/meminfo



--
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:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2008-08-22  1:05 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-20 11:05 [RFC][PATCH 0/2] Quicklist is slighly problematic KOSAKI Motohiro
2008-08-20 11:07 ` [RFC][PATCH 1/2] Show quicklist at meminfo KOSAKI Motohiro
2008-08-20 18:35   ` Andrew Morton
2008-08-21  7:36     ` KOSAKI Motohiro
2008-08-22  1:05       ` KOSAKI Motohiro [this message]
2008-08-22  4:28         ` Andrew Morton
2008-08-22 13:23           ` Robin Holt
2008-08-22 13:56             ` Christoph Lameter
2008-08-23  8:24           ` KOSAKI Motohiro
2008-08-24  5:29             ` Andrew Morton
2008-08-20 11:08 ` [RFC][PATCH 2/2] quicklist shouldn't be proportional to # of CPUs KOSAKI Motohiro
2008-08-20 15:27   ` Christoph Lameter
2008-08-21  6:46   ` Andrew Morton
2008-08-21  7:13     ` David Miller, Andrew Morton
2008-08-21  7:18       ` KOSAKI Motohiro
2008-08-21  7:27       ` Andrew Morton
2008-08-21  7:31         ` KOSAKI Motohiro
2008-08-21  9:32         ` Peter Zijlstra
2008-08-21 10:04           ` KOSAKI Motohiro
2008-08-21 10:09             ` David Miller, KOSAKI Motohiro
2008-08-21 10:13               ` KOSAKI Motohiro
2008-08-21 10:26                 ` David Miller, KOSAKI Motohiro
2008-08-21 10:22             ` KOSAKI Motohiro
2008-08-21 12:02               ` KOSAKI Motohiro
2008-08-25 18:48             ` Mike Travis
2008-08-25 23:33               ` KOSAKI Motohiro
2008-08-26 20:35                 ` Mike Travis
2008-08-25 18:44           ` Mike Travis
2008-08-25 18:40       ` Mike Travis
2008-08-25 23:31         ` KOSAKI Motohiro
2008-08-20 14:10 ` [RFC][PATCH 0/2] Quicklist is slighly problematic Christoph Lameter
2008-08-20 14:49   ` KOSAKI Motohiro
2008-08-20 15:26     ` Christoph Lameter
2008-08-21  2:13   ` Robin Holt
2008-08-21  2:16     ` Robin Holt
2008-08-21  3:08     ` David Miller, Robin Holt
2008-08-21 13:10       ` Christoph Lameter
2008-08-20 18:31 ` Andrew Morton
2008-08-21  2:42   ` Robin Holt
2008-08-21 13:07     ` Christoph Lameter
2008-08-21 13:14       ` Robin Holt
2008-08-21 13:18         ` Christoph Lameter
2008-08-21 13:45           ` Robin Holt

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=20080822100049.F562.KOSAKI.MOTOHIRO@jp.fujitsu.com \
    --to=kosaki.motohiro@jp.fujitsu.com \
    --cc=akpm@linux-foundation.org \
    --cc=cl@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=tokunaga.keiich@jp.fujitsu.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