From: Paul Mackerras <paulus@samba.org>
To: "David S. Miller" <davem@redhat.com>
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: Make 2.5.17 TLB even more friendlier
Date: Tue, 21 May 2002 22:53:31 +1000 (EST) [thread overview]
Message-ID: <15594.17227.311046.740703@argo.ozlabs.ibm.com> (raw)
In-Reply-To: <20020521.051031.56144279.davem@redhat.com>
David S. Miller writes:
> You get called via pte_free_tlb() and pmd_free_tlb() for every
> operation performed by clear_page_tables(). The PTEs themselves are
> all cleared out at the point that clear_page_tables, so you can't
> possibly need the PTE contents. I am assuming therefore you just
> need to get at the linkage, and those two pte/pmd hooks give you
> that.
I have a bit in the PTE that tells me if there is an MMU hash table
entry for the virtual address represented by the PTE. This bit is not
affected by set_pte or ptep_get_and_clear etc. and it is not part of
the swap-entry fields of the PTE. Thus I need to have the PTE page
still around at the point where I flush stuff from the MMU hash
table, even though all the PTEs in it have been cleared, so that I can
avoid searching the hash table for PTEs for virtual addresses for
which I have not put a PTE in the hash table.
Now I could of course try to come up with some other way to store this
information, such as a bitmap associated with the mmu context. The
bitmap would be 96kB in size for a 3GB userspace, though. It could be
allocated on a page-by-page basis, I guess. But all the schemes I
have thought of so far end up being more complex than using a special
bit in the PTE.
Regards,
Paul.
next prev parent reply other threads:[~2002-05-21 12:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-21 6:07 David S. Miller
2002-05-21 12:18 ` Paul Mackerras
2002-05-21 12:10 ` David S. Miller
2002-05-21 12:53 ` Paul Mackerras [this message]
2002-05-21 18:42 ` Linus Torvalds
2002-05-21 23:05 ` Paul Mackerras
2002-05-21 23:13 ` Linus Torvalds
2002-05-22 3:57 ` Paul Mackerras
2002-05-22 4:04 ` Linus Torvalds
2002-05-22 8:40 ` Paul Mackerras
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=15594.17227.311046.740703@argo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=davem@redhat.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®