From: Christoph Lameter <clameter@sgi.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Hugh Dickins <hugh@veritas.com>, Nick Piggin <npiggin@suse.de>,
dgc@sgi.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] Optimize compound_head() by avoiding a shared page flag
Date: Mon, 9 Apr 2007 10:22:24 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0704091020310.4878@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <20070407184801.b6f3f549.akpm@linux-foundation.org>
On Sat, 7 Apr 2007, Andrew Morton wrote:
> andl $48, %eax #, tmp399
> cmpl $48, %eax #, tmp399
> je .L265 #,
>
> what's "yuck" about that?
>
> With the single page flag:
>
> movl (%ebx), %eax #* page.521, D.21940
> testb $32, %al #, D.21940
> jne .L265 #,
>
> So you're talking about saving one sole single silly solitary instruction.
We are also using another register. The bit instructions can just go in an
test. Ok. Will submit this patch. .... Maybe I can special case 64 bit.
next prev parent reply other threads:[~2007-04-09 17:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-05 22:36 [PATCH 1/2] Make page->private usable in compound pages V1 Christoph Lameter
2007-04-05 22:36 ` [PATCH 2/2] Optimize compound_head() by avoiding a shared page flag Christoph Lameter
2007-04-07 5:23 ` Andrew Morton
2007-04-07 22:16 ` Christoph Lameter
2007-04-07 22:51 ` Andrew Morton
2007-04-08 0:21 ` Christoph Lameter
2007-04-08 1:25 ` Andrew Morton
2007-04-08 1:32 ` Christoph Lameter
2007-04-08 1:48 ` Andrew Morton
2007-04-09 17:22 ` Christoph Lameter [this message]
2007-04-09 18:09 ` Christoph Lameter
2007-04-09 18:45 ` Andrew Morton
2007-04-09 18:49 ` Christoph Lameter
2007-04-09 22:05 ` Christoph Lameter
2007-04-05 23:43 ` [PATCH 1/2] Make page->private usable in compound pages V1 Andrew Morton
2007-04-06 17:01 ` Christoph Lameter
2007-04-06 20:04 ` Andrew Morton
2007-04-06 20:28 ` Christoph Lameter
2007-04-06 19:46 ` Christoph Lameter
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=Pine.LNX.4.64.0704091020310.4878@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=dgc@sgi.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@suse.de \
/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®