From: John Levon <levon@movementarian.org>
To: Mikael Pettersson <mikpe@user.it.uu.se>
Cc: Rusty Russell <rusty@rustcorp.com.au>, linux-kernel@vger.kernel.org
Subject: Re: module changes
Date: Tue, 18 Feb 2003 16:05:04 +0000 [thread overview]
Message-ID: <20030218160504.GA97537@compsoc.man.ac.uk> (raw)
In-Reply-To: <15954.22427.557293.353363@gargle.gargle.HOWL>
On Tue, Feb 18, 2003 at 04:56:11PM +0100, Mikael Pettersson wrote:
> Does the implementation have to be perfect? The per_cpu API can easily
> be simulated using good old NR_CPUS arrays:
I agree, the main advantage of having per-cpu API available to modules
is that code can just use it and not worry about module vs. monolithic.
Some obscure limitation doesn't sound like a good idea in that respect
:)
regards
john
next prev parent reply other threads:[~2003-02-18 15:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030217213221.3103.qmail@eklektix.com>
2003-02-18 7:19 ` module changes Rusty Russell
2003-02-18 15:56 ` Mikael Pettersson
2003-02-18 16:05 ` John Levon [this message]
2003-02-18 22:24 ` Rusty Russell
2003-02-19 3:51 ` Andrew Morton
2003-02-19 4:28 ` Rusty Russell
2003-02-19 12:52 ` Mikael Pettersson
2003-02-20 0:15 ` 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=20030218160504.GA97537@compsoc.man.ac.uk \
--to=levon@movementarian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@user.it.uu.se \
--cc=rusty@rustcorp.com.au \
/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