From: Andi Kleen <ak@linux.intel.com>
To: Jerome Glisse <jglisse@redhat.com>
Cc: lsf-pc@lists.linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [LSF/MM TOPIC] Page flags, can we free up space ?
Date: Tue, 22 Jan 2019 13:44:15 -0800 [thread overview]
Message-ID: <87tvi074gg.fsf@linux.intel.com> (raw)
Message-ID: <20190122214415.iWizBunTWe7pg9VQwJ8u15R0TEnThblVlFyR7MxLUE0@z> (raw)
In-Reply-To: <20190122201744.GA3939@redhat.com> (Jerome Glisse's message of "Tue, 22 Jan 2019 15:17:44 -0500")
Jerome Glisse <jglisse@redhat.com> writes:
>
> Right now this is more a temptative ie i do not know if i will succeed,
> in any case i can report on failure or success and discuss my finding to
> get people opinions on the matter.
I would just stop putting node/zone number into the flags. These
could be all handled with a small perfect hash table, like the original
x86_64 port did, which should be quite cheap to look up.
Then there should be enough bits for everyone again.
-Andi
next prev parent reply other threads:[~2019-01-22 21:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-22 20:17 Jerome Glisse
2019-01-22 21:44 ` Andi Kleen [this message]
2019-01-22 21:44 ` Andi Kleen
2019-01-22 23:52 ` Jerome Glisse
2019-01-23 1:56 ` Mike Kravetz
2019-01-30 11:51 ` David Hildenbrand
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=87tvi074gg.fsf@linux.intel.com \
--to=ak@linux.intel.com \
--cc=jglisse@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox