From: Robert Love <rml@tech9.net>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] New per-cpu patch v2.5.1
Date: 20 Dec 2001 01:24:45 -0500 [thread overview]
Message-ID: <1008829509.1213.8.camel@phantasy> (raw)
In-Reply-To: <E16GwUZ-0004xr-00@wagner.rustcorp.com.au>
In-Reply-To: <E16GwUZ-0004xr-00@wagner.rustcorp.com.au>
On Thu, 2001-12-20 at 01:15, Rusty Russell wrote:
> After some discussion, this may be a more sane (untested) per-cpu area
> patch. It dynamically allocated the sections (and discards the
> original), which would allow (future) NUMA people to make sure their
> CPU area is allocated near them.
>
> Comments welcome,
Would the next step be to find the various per-CPU data in the kernel
and convert it to your new form? I.e., is this a general purpose
interface for per-CPU data structures, or am I missing something?
If it is, this is a good idea. Other Unices have this (IRIX comes to
mind). One of the biggest advantages, IMO, is simply the readability --
data structures that are per-CPU have varying methods of creation and
referencing. The implicit locking (i.e., none) can be unclear.
Bring everything together can be a good thing.
Robert Love
next prev parent reply other threads:[~2001-12-20 6:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-20 6:15 [PATCH] New per-cpu patch v2.5.1 Rusty Russell
2001-12-20 6:24 ` Robert Love [this message]
2001-12-26 0:39 ` Rusty Russell
-- strict thread matches above, loose matches on Subject: below --
2001-12-20 12:13 Dipankar Sarma
2001-12-27 6:50 ` Rusty Russell
2002-01-13 5:52 ` 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=1008829509.1213.8.camel@phantasy \
--to=rml@tech9.net \
--cc=linux-kernel@vger.kernel.org \
--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