From: Andi Kleen <ak@suse.de>
To: Zachary Amsden <zach@vmware.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Pratap Subrahmanyam <pratap@vmware.com>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] x86_64 Avoid some atomic operations during address space destruction
Date: Thu, 25 Aug 2005 19:26:09 +0200 [thread overview]
Message-ID: <200508251926.11219.ak@suse.de> (raw)
In-Reply-To: <430DFC14.50906@vmware.com>
On Thursday 25 August 2005 19:12, Zachary Amsden wrote:
> Andi Kleen wrote:
> >On Sunday 07 August 2005 14:16, Zachary Amsden wrote:
> >
> >
> >FYI I have queued it, but cannot apply it because the necessary generic
> >code support is still not in mainline.
>
> Here's the patch for generic / i386 support; it's already in the -mm tree.
I'll probably not put that into my tree because I try to avoid generic
patches of other people - i assume it's queued for mainline.
If you want you can include the x86-64 patch with that submission too
(it's fine for me), alternatively I'll submit it later when I do the next
merge from i386 (that might take some time though) or remember about it
for some other reason.
>
> >Do you have any other optimizations pending for x86-64?
> >
> >There is still the iopl optimization that you did that is on my TODO list
> > to add. Anything else.
>
> I started porting the IOPL work, but got confused in my tree and end up
> patching asm-i386 with x86-64 code. The joy of unenforced source control!
Ok. When you don't get around to it I'll eventually.
>
> I have some other MMU optimizations pending that will hopefully be a win
> for all architectures; still measuring which alternative is best there.
Ok. Thanks. Please keep me updated on that.
-Andi
prev parent reply other threads:[~2005-08-25 17:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-07 12:16 Zachary Amsden
2005-08-25 16:54 ` Andi Kleen
2005-08-25 17:12 ` Zachary Amsden
2005-08-25 17:26 ` Andi Kleen [this message]
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=200508251926.11219.ak@suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pratap@vmware.com \
--cc=zach@vmware.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 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®