Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Randolph Chung <tausq@debian.org>
To: "David S. Miller" <davem@redhat.com>
Cc: willy@debian.org, grundler@dsl2.external.hp.com,
	jsm@udlkern.fc.hp.com, parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Re: RFC: mmap patch
Date: Sat, 8 Mar 2003 15:31:41 -0800	[thread overview]
Message-ID: <20030308233141.GC11363@tausq.org> (raw)
In-Reply-To: <20030308.150023.97153009.davem@redhat.com>

> You need merely 9MB of address space (2 * 4MB) if you implement
> my {copy,clear}_user_page() dynamic mapping hack, that will be
> tons more cheaper than any kmap based scheme and also be nicer
> on the TLB as there will be zero TLB changes occurring around
> the copy/clear.

i hope i'm not missing something obvious, but from what i understand
from this discussion, {copy,user}_user_page helps with the initial
syncing up of new mappings that are created for a process... but how
does this deal with syncing up changes afterwards? for that we still
need the flush_dcache_page to walk the user mappings right?

randolph
-- 
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/

  parent reply	other threads:[~2003-03-08 23:32 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
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 [this message]
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=20030308233141.GC11363@tausq.org \
    --to=tausq@debian.org \
    --cc=davem@redhat.com \
    --cc=grundler@dsl2.external.hp.com \
    --cc=jsm@udlkern.fc.hp.com \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=willy@debian.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