From: Christoph Hellwig <hch@infradead.org>
To: Christoph Lameter <christoph@lameter.com>
Cc: akpm@osdl.org, shai@scalex86.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Per cpu irq stat
Date: Tue, 15 Mar 2005 09:14:33 +0000 [thread overview]
Message-ID: <20050315091433.GA29079@infradead.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0503142230050.11651@server.graphe.net>
On Mon, Mar 14, 2005 at 10:32:34PM -0800, Christoph Lameter wrote:
> The definition of the irq_stat as an array means that the individual
> elements of the irq_stat array are located on one NUMA node requiring
> internode traffic to access irq_stat from other nodes. This patch makes
> irq_stat a per_cpu variable which allows most accesses to be local.
There's architectures accessing it from assemly.
But furthermore there's absolutely not point for the irq_stat structure
at all anymore now that we have the per_cpu infrastructure. so kill it
completely and let every architecture just provide a local_softirq_pending
macro.
next prev parent reply other threads:[~2005-03-15 9:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-15 6:32 Christoph Lameter
2005-03-15 6:48 ` Andrew Morton
2005-03-15 7:36 ` Christoph Lameter
2005-03-15 9:14 ` Christoph Hellwig [this message]
2005-03-15 16:51 ` 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=20050315091433.GA29079@infradead.org \
--to=hch@infradead.org \
--cc=akpm@osdl.org \
--cc=christoph@lameter.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shai@scalex86.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
all inboxes | Powered by JetHome®