From: Daniel Phillips <phillips@arcor.de>
To: Dave McCracken <dmccr@us.ibm.com>,
Linux Memory Management <linux-mm@kvack.org>
Cc: Andrew Morton <akpm@zip.com.au>
Subject: Re: [PATCH] Optimize away pte_chains for single mappings
Date: Sat, 13 Jul 2002 15:13:35 +0200 [thread overview]
Message-ID: <E17TMiO-0003IR-00@starship> (raw)
In-Reply-To: <55160000.1026239746@baldur.austin.ibm.com>
On Tuesday 09 July 2002 20:35, Dave McCracken wrote:
>
> Here's a patch that optimizes out using a struct pte_chain when there's
> only one mapping for that page. It re-uses the pte_chain pointer in struct
> page, with an appropriate flag. The patch is based on Rik's latest 2.5.25
> rmap patch.
>
> I've done basic testing on it (it boots and runs simple commands).
>
> This version of the patch uses an anonymous union, so it only builds with
> gcc 3.x. I'm working on an alternate version of the patch, but wanted to
> get this one out for people to look at.
Why are we using up valuable real estate in page->flags when the low bit
of page->pte_chain is available?
--
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/
next prev parent reply other threads:[~2002-07-13 13:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-09 18:35 [PATCH] Optimize away pte_chains for single mappings Dave McCracken
2002-07-13 13:13 ` Daniel Phillips [this message]
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
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=E17TMiO-0003IR-00@starship \
--to=phillips@arcor.de \
--cc=akpm@zip.com.au \
--cc=dmccr@us.ibm.com \
--cc=linux-mm@kvack.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 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.