From: Dave McCracken <dmccr@us.ibm.com>
To: Daniel Phillips <phillips@arcor.de>
Cc: Linux Memory Management <linux-mm@kvack.org>
Subject: Re: [PATCH] Optimize away pte_chains for single mappings
Date: Mon, 15 Jul 2002 09:02:40 -0500 [thread overview]
Message-ID: <10930000.1026741760@baldur.austin.ibm.com> (raw)
In-Reply-To: <E17TMiO-0003IR-00@starship>
--On Saturday, July 13, 2002 03:13:35 PM +0200 Daniel Phillips
<phillips@arcor.de> wrote:
> Why are we using up valuable real estate in page->flags when the low bit
> of page->pte_chain is available?
Right now my flag is bit number 18 in page->flags out of 32. Mechanisms
already exist to manipulate this bit in a reasonable fashion. I don't see
any good reason for complicating things by putting a flag bit into a
pointer, where we'd have to repeatedly check and clear it before we
dereference the pointer. When I discussed this with Rik he said putting it
in flags was reasonable. We can always revisit it in the future if we run
out of bits.
Dave
======================================================================
Dave McCracken IBM Linux Base Kernel Team 1-512-838-3059
dmccr@us.ibm.com T/L 678-3059
--
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-15 14:02 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 [this message]
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=10930000.1026741760@baldur.austin.ibm.com \
--to=dmccr@us.ibm.com \
--cc=linux-mm@kvack.org \
--cc=phillips@arcor.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