public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Brian Gerst <bgerst@didntduck.org>
To: Andrew Morton <akpm@zip.com.au>
Cc: Linus Torvalds <torvalds@transmeta.com>,
	Dave Jones <davej@suse.de>,
	Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] percpu updates
Date: Wed, 01 May 2002 18:54:01 -0400	[thread overview]
Message-ID: <3CD07209.5060301@didntduck.org> (raw)
In-Reply-To: <3CD06ACE.1090402@didntduck.org> <3CD06FD1.2E75F5F2@zip.com.au>

Andrew Morton wrote:
> Brian Gerst wrote:
> 
>>These patches convert some of the existing arrays based on NR_CPUS to
>>use the new per cpu code.
>>
>>...
>>-extern struct page_state {
>>+struct page_state {
>>        unsigned long nr_dirty;
>>        unsigned long nr_locked;
>>        unsigned long nr_pagecache;
>>-} ____cacheline_aligned_in_smp page_states[NR_CPUS];
>>+};
>>+
>>+extern struct page_state __per_cpu_data page_states;
> 
> 
> When I did this a couple of weeks back it failed in
> mysterious ways and I ended up parking it.  Failure
> symptoms included negative numbers being reported in
> /proc/meminfo for "Locked" and "Dirty".
> 
> How well has this been tested?  (If the answer
> is "not very" then please wait until I've tested
> it out...)
> 
> -
> 

Well, the answer is not very.  I don't have an SMP machine to do 
thorough testing on.  The best I can do is boot an SMP kernel on a UP 
machine.  I did check the disassembly of vmlinux, and it looked like it 
would work as advertised.

-- 

						Brian Gerst


  reply	other threads:[~2002-05-01 22:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-01 22:23 [PATCH] percpu updates Brian Gerst
2002-05-01 22:44 ` Andrew Morton
2002-05-01 22:54   ` Brian Gerst [this message]
2002-05-01 23:05     ` Randy.Dunlap
2002-05-01 23:35       ` Alan Cox
2002-05-03 14:59         ` Timothy D. Witham
2002-05-05  4:08 ` Andrew Morton
2002-05-05 16:38   ` Brian Gerst
2002-05-06  8:57     ` Andrew Morton
2002-05-06 12:44       ` Brian Gerst
2002-05-06  7:27   ` Rusty Russell

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=3CD07209.5060301@didntduck.org \
    --to=bgerst@didntduck.org \
    --cc=akpm@zip.com.au \
    --cc=davej@suse.de \
    --cc=linux-kernel@vger.kernel.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