All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@debian.org>
To: "David S. Miller" <davem@redhat.com>
Cc: Matthew Wilcox <willy@debian.org>,
	santosha@india.hp.com, sct@redhat.com, santosh.abraham@hp.com,
	randolph@tausq.org, parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Fwd:  Problems with raw interface.
Date: Fri, 26 Sep 2003 15:30:52 +0100	[thread overview]
Message-ID: <20030926143052.GL24824@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20030926070450.603c5c33.davem@redhat.com>

On Fri, Sep 26, 2003 at 07:04:50AM -0700, David S. Miller wrote:
> On Fri, 26 Sep 2003 15:09:48 +0100
> Matthew Wilcox <willy@debian.org> wrote:
> 
> > > You have to find a way to walk all the address spaces to figure out
> > > where the page is mapped.
> > 
> > That's ridiculous.  For a start, pages can't be mapped into multiple
> > address spaces without being in the page cache.
> 
> How in the world can anonymous pages work then?  Of course anonymous
> pages can be in multiple address spaces without being in the page
> cache.

How?  By fork()?  If so, that's not a problem -- the pages stay at the same
address in both processes, and flushing one will flush any inherited pages.
Otherwise you'll have to be more explicit.

-- 
"It's not Hollywood.  War is real, war is primarily not about defeat or
victory, it is about death.  I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk

  reply	other threads:[~2003-09-26 14:30 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-25 10:38 [parisc-linux] Fwd: Problems with raw interface Santosh Abraham
2003-09-25 10:50 ` Randolph Chung
2003-09-25 11:19   ` Santosh Abraham
2003-09-25 14:26     ` Matthew Wilcox
2003-09-26  1:08       ` David S. Miller
2003-09-26 11:24         ` Matthew Wilcox
2003-09-26 11:20           ` David S. Miller
2003-09-26 11:57             ` Stephen C. Tweedie
2003-09-26 11:48               ` David S. Miller
2003-09-26 12:20                 ` Matthew Wilcox
2003-09-26 12:38                   ` David S. Miller
2003-09-26 13:11                     ` SANTOSH ABRAHAM
2003-09-26 12:56                       ` David S. Miller
2003-09-26 13:29                         ` Matthew Wilcox
2003-09-26 13:21                           ` David S. Miller
2003-09-26 14:09                             ` Matthew Wilcox
2003-09-26 14:04                               ` David S. Miller
2003-09-26 14:30                                 ` Matthew Wilcox [this message]
2003-09-26 14:20                                   ` David S. Miller
2003-09-26 14:42                                     ` Stephen C. Tweedie
2003-09-26 14:26                               ` Stephen C. Tweedie
2003-09-26 11:47           ` Santosh Abraham
2003-09-26 10:42       ` Santosh Abraham
2003-09-26 10:34         ` David S. Miller
2003-09-26 12:12           ` Santosh Abraham

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=20030926143052.GL24824@parcelfarce.linux.theplanet.co.uk \
    --to=willy@debian.org \
    --cc=davem@redhat.com \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=randolph@tausq.org \
    --cc=santosh.abraham@hp.com \
    --cc=santosha@india.hp.com \
    --cc=sct@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.