All of lore.kernel.org
 help / color / mirror / Atom feed
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>
Subject: Re: [PATCH] x86_64 Avoid some atomic operations during address space destruction
Date: Thu, 25 Aug 2005 18:54:09 +0200	[thread overview]
Message-ID: <200508251854.10060.ak@suse.de> (raw)
In-Reply-To: <42F5FB9A.5000708@vmware.com>

On Sunday 07 August 2005 14:16, Zachary Amsden wrote:
> This turned out to be a huge win on 32-bit i386 in PAE mode, but it is
> likely not as significant on x86_64; I don't know because I haven't
> actually measured the cost.  I don't have 64-bit hardware that I have
> the luxury of rebooting right now, so this patch is untested, but if
> someone wants to try this out, it might actually show a measurable win
> on fork/exit.  I lost my cycle count measurement diffs, but I don't
> think they would apply cleanly to x86_64 anyways.  This patch at least
> looks good, and compiles cleanly on 2.6.13-rc5-mm1, thus passing some
> level of testing.

FYI I have queued it, but cannot apply it because the necessary generic
code support is still not in mainline.

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.

-Andi

  reply	other threads:[~2005-08-25 16:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-07 12:16 [PATCH] x86_64 Avoid some atomic operations during address space destruction Zachary Amsden
2005-08-25 16:54 ` Andi Kleen [this message]
2005-08-25 17:12   ` Zachary Amsden
2005-08-25 17:26     ` Andi Kleen

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=200508251854.10060.ak@suse.de \
    --to=ak@suse.de \
    --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 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.