From: "David S. Miller" <davem@redhat.com>
To: grundler@dsl2.external.hp.com
Cc: jsm@udlkern.fc.hp.com, parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Re: RFC: mmap patch
Date: Fri, 07 Mar 2003 22:29:45 -0800 (PST) [thread overview]
Message-ID: <20030307.222945.32673395.davem@redhat.com> (raw)
In-Reply-To: <20030308063043.GB27859@dsl2.external.hp.com>
From: grundler@dsl2.external.hp.com (Grant Grundler)
Date: Fri, 7 Mar 2003 23:30:43 -0700
I don't pretend to understand the issues with virtual tags and
linux VM design, I just want to encourage the discussion since
I'd really like to see SMP work right on parisc.
If you flush caches exactly what sparc64 does in 2.5.x, and you do
have a virtually indexed, physically tagged cache, you should have no
correctness. I've stressed that port to no end (in particular the LTP
suite has a great mmap/read/write coherency tester), and if there are
holes I'd like to know about them :-)
The sparc64 port only flushes when absolutely necessary.
The most crucial area to get efficient flushing is the
{copy,clear}_user_page implementation. If you use temporary kernel
mappings mapped at virtual addresses matching the virtual color that
the user's mappings will have, this avoids virtually ALL of the
flushing for anonymous pages. I haven't noticed too many ports pick
up this trick even though I mention it in cachetlb.txt.
On sparc64 I even save the original TLB entries before the flush
and restore them afterwards, so there is no TLB traffic as a result
of doing these temp mappings.
next prev parent reply other threads:[~2003-03-08 6:51 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-06 14:14 [parisc-linux] Re: RFC: mmap patch John Marvin
2003-03-06 14:31 ` Matthew Wilcox
2003-03-06 15:31 ` Randolph Chung
2003-03-08 6:30 ` Grant Grundler
2003-03-08 6:29 ` David S. Miller [this message]
2003-03-08 17:24 ` Grant Grundler
2003-03-08 19:04 ` David S. Miller
2003-03-08 20:42 ` Grant Grundler
2003-03-08 22:45 ` Matthew Wilcox
2003-03-08 23:00 ` David S. Miller
2003-03-08 23:27 ` Matthew Wilcox
2003-03-08 23:14 ` David S. Miller
2003-03-08 23:31 ` Randolph Chung
2003-03-08 23:15 ` David S. Miller
2003-03-09 2:15 ` Grant Grundler
2003-03-08 23:11 ` Matthew Wilcox
2003-03-08 23:02 ` David S. Miller
2003-03-09 14:42 ` Matthew Wilcox
2003-03-09 21:38 ` David S. Miller
2003-03-10 1:50 ` Matthew Wilcox
2003-03-10 5:18 ` David S. Miller
2003-03-14 13:04 ` Jochen Friedrich
2003-03-14 16:23 ` Grant Grundler
-- strict thread matches above, loose matches on Subject: below --
2003-03-09 3:42 John Marvin
2003-03-09 21:29 ` David S. Miller
2003-03-09 3:51 John Marvin
2003-03-09 21:31 ` David S. Miller
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=20030307.222945.32673395.davem@redhat.com \
--to=davem@redhat.com \
--cc=grundler@dsl2.external.hp.com \
--cc=jsm@udlkern.fc.hp.com \
--cc=parisc-linux@lists.parisc-linux.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