From: Arjan van de Ven <arjan@infradead.org>
To: Andi Kleen <ak@suse.de>
Cc: Benjamin LaHaise <bcrl@kvack.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/9] x86-64 put current in r10
Date: Wed, 30 Nov 2005 14:32:51 +0100 [thread overview]
Message-ID: <1133357572.2825.35.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <20051130130216.GL19515@wotan.suse.de>
On Wed, 2005-11-30 at 14:02 +0100, Andi Kleen wrote:
> On Tue, Nov 29, 2005 at 11:21:18PM -0500, Benjamin LaHaise wrote:
> > Hello Andi,
> >
> > The following emails contain the patches to convert x86-64 to store current
> > in r10 (also at http://www.kvack.org/~bcrl/patches/v2.6.15-rc3/). This
> > provides a significant amount of code savings (~43KB) over the current
> > use of the per cpu data area. I also tested using r15, but that generated
> > code that was larger than that generated with r10. This code seems to be
> > working well for me now (it stands up to 32 and 64 bit processes and ptrace
> > users) and would be a good candidate for further exposure.
>
> Looks good thanks. It will need longer testing though.
is it -mm ready?
next prev parent reply other threads:[~2005-11-30 13:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-30 4:21 Benjamin LaHaise
2005-11-30 6:39 ` Jari Ruusu
2005-11-30 7:56 ` Arjan van de Ven
2005-11-30 8:20 ` Nick Piggin
2005-11-30 17:29 ` Jari Ruusu
2005-11-30 17:32 ` Andi Kleen
2005-11-30 17:33 ` Christoph Hellwig
2005-11-30 12:45 ` Andi Kleen
2005-11-30 16:22 ` Randy.Dunlap
2005-11-30 16:39 ` Kyle Moffett
2005-12-01 9:06 ` Helge Hafting
2005-11-30 13:02 ` Andi Kleen
2005-11-30 13:32 ` Arjan van de Ven [this message]
2005-11-30 15:10 ` Benjamin LaHaise
2005-11-30 13:57 ` Andi Kleen
2005-11-30 15:18 ` Matti Aarnio
2005-11-30 15:24 ` Benjamin LaHaise
2005-11-30 15:29 ` Andi Kleen
2005-11-30 15:34 ` Arjan van de Ven
2005-11-30 16:13 ` Jesper Juhl
2005-12-01 14:30 ` Steven Rostedt
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=1133357572.2825.35.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=ak@suse.de \
--cc=bcrl@kvack.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®