linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Christoph Lameter <clameter@sgi.com>
Cc: linux-mm@kvack.org, sparclinux@vger.kernel.org,
	"David S. Miller" <davem@davemloft.net>
Subject: Re: Vmstat: Small revisions to refresh_cpu_vm_stats()
Date: Tue, 13 Nov 2007 03:37:55 -0800	[thread overview]
Message-ID: <20071113033755.c2e64c09.akpm@linux-foundation.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0711091837390.18567@schroedinger.engr.sgi.com>

On Fri, 9 Nov 2007 18:39:03 -0800 (PST) Christoph Lameter <clameter@sgi.com> wrote:

> 1. Add comments explaining how the function can be called.
> 
> 2. Avoid interrupt enable / disable through the use of xchg.
> 
> 3. Collect global diffs in a local array and only spill
>    them once into the global counters when the zone scan
>    is finished. This means that we only touch each global
>    counter once instead of each time we fold cpu counters
>    into zone counters.

: undefined reference to `__xchg_called_with_bad_pointer'

This is sparc64's way of telling you that you can'd do xchg on an s8.

Dave, is that fixable?

I assume not, in which case we either go for some open-coded implementation
for 8- and 16-bits or we should ban (at compile time) 8- and 16-bit xchg on
all architectures.


--
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:[~2007-11-13 11:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-10  2:39 Christoph Lameter
2007-11-13 11:37 ` Andrew Morton [this message]
2007-11-13 11:47   ` David Miller, Andrew Morton
2007-11-13 11:55     ` Andrew Morton
2007-11-13 22:05       ` Christoph Lameter

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=20071113033755.c2e64c09.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=clameter@sgi.com \
    --cc=davem@davemloft.net \
    --cc=linux-mm@kvack.org \
    --cc=sparclinux@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