From: David Mosberger <davidm@napali.hpl.hp.com>
To: "David S. Miller" <davem@redhat.com>
Cc: davidm@hpl.hp.com, davidm@napali.hpl.hp.com, hugh@veritas.com,
linux-kernel@vger.kernel.org, andrea@suse.de,
torvalds@transmeta.com
Subject: Re: Q: PREFETCH_STRIDE/16
Date: Thu, 23 May 2002 10:02:33 -0700 [thread overview]
Message-ID: <15597.8361.533679.563624@napali.hpl.hp.com> (raw)
In-Reply-To: <20020523.093416.133929379.davem@redhat.com>
>>>>> On Thu, 23 May 2002 09:34:16 -0700 (PDT), "David S. Miller" <davem@redhat.com> said:
DaveM> I mentioned this 1 or 2 days ago in the TLB thread with
DaveM> Linus, you pessimistically maintain a tiny bitmap per
DaveM> mm_struct which keeps track of where mappings actually are.
DaveM> You use some hash function on the virtual address to
DaveM> determine the bit. You clear it when the mm_struct is new,
DaveM> and you just set bits when mappings are installed. Very
DaveM> simple.
DaveM> Then all of these "walk all valid page tables" loops that
DaveM> scan entire mostly empty pages of pgd/pmd/pte entries for no
DaveM> reason can just check the bitmap instead.
DaveM> Most of the exit overhead is in clear_page_tables walking
DaveM> over entire pages. It effectively flushes the cache unless
DaveM> all you are doing is fork/exit/fork/exit
Sounds like something worth experimenting with. I doubt you could
really avoid (effectively) flushing the caches, but even if there are
just a few zero bits in the bitmap at the time of the tear-down, a
fair amount of time could be saved.
--david
next prev parent reply other threads:[~2002-05-23 17:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-23 15:12 Hugh Dickins
2002-05-23 16:26 ` David Mosberger
2002-05-23 16:21 ` David S. Miller
2002-05-23 16:43 ` David Mosberger
2002-05-23 16:34 ` David S. Miller
2002-05-23 17:02 ` David Mosberger [this message]
2002-05-23 17:00 ` David S. Miller
2002-05-23 18:32 ` 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=15597.8361.533679.563624@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=andrea@suse.de \
--cc=davem@redhat.com \
--cc=davidm@hpl.hp.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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
all inboxes | Powered by JetHome®