From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Patch 1/3] Reclaim pmd and pte entries to quicklists.
Date: Tue, 01 Mar 2005 19:23:21 +0000 [thread overview]
Message-ID: <16932.49449.300899.778608@napali.hpl.hp.com> (raw)
In-Reply-To: <20050226142541.GE10965@lnx-holt.americas.sgi.com>
>>>>> On Sat, 26 Feb 2005 08:25:41 -0600, Robin Holt <holt@sgi.com> said:
Robin> Tony, This patch introduces using the quicklists for pgd,
Robin> pmd, and pte levels by combining the alloc and free functions
Robin> into a common set of routines. This greatly simplifies the
Robin> reading of this header file.
Agreed, but now you implicitly assume that the directories at all
levels are the same size. I think it would be better to pass the
desired size to the alloc routine such that you can at least fail
noisily if somebody ever tried to use different-size directories.
Robin> Before:
Robin> Process fork+exit: 255.0909 microseconds
Robin> After:
Robin> Process fork+exit: 184.2333 microseconds
Nice.
Robin> + ret = local_cpu_data->pgtable_quicklist;
Is there any reason pgtable_quicklist isn't a normal per-CPU variable?
We didn't use to have that facility, that's why we used to keep it in
local_cpu_data, but noadays, there should be no need for that ugly
hack.
Since this is performance-critical, it's probably worthwhile to use
__ia64_per_cpu_var() to access the quicklist. That way, the address
of pgtable_quicklist can be obtained with a single "addl" instruction.
--david
next prev parent reply other threads:[~2005-03-01 19:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-26 14:25 [Patch 1/3] Reclaim pmd and pte entries to quicklists Robin Holt
2005-03-01 19:23 ` David Mosberger [this message]
2005-03-01 21:10 ` Robin Holt
2005-03-02 17:36 ` David Mosberger
2005-03-02 18:33 ` Robin Holt
2005-03-02 18:43 ` David Mosberger
2005-03-02 20:44 ` Robin Holt
2005-03-02 21:21 ` David Mosberger
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=16932.49449.300899.778608@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@vger.kernel.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