linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Phillips <phillips@arcor.de>
To: Andrew Morton <akpm@zip.com.au>
Cc: Rik van Riel <riel@conectiva.com.br>,
	Matti Aarnio <matti.aarnio@zmailer.org>,
	Dave McCracken <dmccr@us.ibm.com>,
	Linux Memory Management <linux-mm@kvack.org>
Subject: Re: [PATCH] Optimize away pte_chains for single mappings
Date: Tue, 16 Jul 2002 06:50:56 +0200	[thread overview]
Message-ID: <E17UKIa-0003hA-00@starship> (raw)
In-Reply-To: <3D33371D.6003AAAE@zip.com.au>

On Monday 15 July 2002 22:57, Andrew Morton wrote:
> Daniel Phillips wrote:
> > On Monday 15 July 2002 18:34, Rik van Riel wrote:
> > > On Mon, 15 Jul 2002, Daniel Phillips wrote:
> > >
> > > > None of these cases apply, the low bit is always masked off before being
> > > > used as a pointer.
> > >
> > > Too ugly to live.
> > 
> > That's a nonargument.  I presume you weren't able to think of a
> > substantive reason.
> 
> How about "Linus will roast our nuts if we do that"?

Unless someone can come up with a rational argument, I'd be forced to conclude
that Linus is superstitious.

> Plus accessing the same storage with both atomic and non-atomic
> ops may be a problem on some hardware.

Qu'est-ce que ca veux dire?  We're protected under the pte_chain lock are we
not?

> Let's wait until we run out of page flags first...

Sure, I intend to lay claim to six of them in due course, that would leave a
mere eight for posterity.

Then there is the method I proposed for saving 8 bytes per pte_chain with
the help of an overloaded pointer.  In what way does that not turn the ugly
duckling into a beautiful swan?

-- 
Daniel
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/

  reply	other threads:[~2002-07-16  4:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-09 18:35 Dave McCracken
2002-07-13 13:13 ` Daniel Phillips
2002-07-15 14:02   ` Dave McCracken
2002-07-15 14:56     ` Daniel Phillips
2002-07-15 15:40       ` Matti Aarnio
2002-07-15 16:10         ` Daniel Phillips
2002-07-15 16:34           ` Rik van Riel
2002-07-15 16:42             ` Daniel Phillips
2002-07-15 20:57               ` Andrew Morton
2002-07-16  4:50                 ` Daniel Phillips [this message]
2002-07-15 16:30         ` Daniel Phillips
2002-07-15 16:55           ` Matti Aarnio
2002-07-15 17:50             ` Daniel Phillips

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=E17UKIa-0003hA-00@starship \
    --to=phillips@arcor.de \
    --cc=akpm@zip.com.au \
    --cc=dmccr@us.ibm.com \
    --cc=linux-mm@kvack.org \
    --cc=matti.aarnio@zmailer.org \
    --cc=riel@conectiva.com.br \
    /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