From: Rusty Russell <rusty@rustcorp.com.au>
To: Eric Dumazet <dada1@cosmosbay.com>
Cc: Mike Travis <travis@sgi.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux kernel <linux-kernel@vger.kernel.org>,
Christoph Lameter <clameter@sgi.com>
Subject: Re: [PATCH] modules: Use a better scheme for refcounting
Date: Mon, 19 May 2008 00:31:44 +1000 [thread overview]
Message-ID: <200805190031.45136.rusty@rustcorp.com.au> (raw)
In-Reply-To: <482E8AF5.9050804@cosmosbay.com>
On Saturday 17 May 2008 17:36:21 Eric Dumazet wrote:
> Christoph Lameter made good work last year and apparently the path is to :
>
> 1) Put pda at the begining of percpu section.
Well, we killed the pda on i386: it's basically a limited arch-specific percpu
section. Unfortunately, ISTR that doing so kills -fstack-protector on x86-64
(gcc was explicitly patched to support the kernel doing this, but it nailed
us to a fixed offset off %fs). But the PDA is a redundant idea which should
be removed.
> 2) Relocate percpu variables to begin at zero
> 3) Use %gs (or %fs) register to address pda AND percpu section.
Thanks for the prod Eric. ISTR acking those patches; Christoph, what happened
to them?
Cheers,
Rusty.
next prev parent reply other threads:[~2008-05-18 14:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-15 20:40 [PATCH] modules: Use a better scheme for refcounting Eric Dumazet
2008-05-15 21:57 ` Andi Kleen
2008-05-16 4:44 ` Eric Dumazet
2008-05-16 0:09 ` Rusty Russell
2008-05-16 5:29 ` Eric Dumazet
2008-05-16 13:41 ` Mike Travis
2008-05-17 5:33 ` Rusty Russell
2008-05-17 7:36 ` Eric Dumazet
2008-05-18 14:31 ` Rusty Russell [this message]
2008-05-19 16:42 ` Christoph Lameter
2008-05-19 16:41 ` Christoph Lameter
2008-05-19 18:04 ` Mike Travis
2008-05-19 16:39 ` Christoph Lameter
-- strict thread matches above, loose matches on Subject: below --
2009-02-03 3:01 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=200805190031.45136.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=dada1@cosmosbay.com \
--cc=linux-kernel@vger.kernel.org \
--cc=travis@sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.