All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Phillips <phillips@arcor.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>, Linus Torvalds <torvalds@osdl.org>
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
	Jamie Lokier <jamie@shareable.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] fix remap of shared read only mappings
Date: Fri, 5 Sep 2003 03:31:38 +0200	[thread overview]
Message-ID: <200309050331.38597.phillips@arcor.de> (raw)
In-Reply-To: <1062724028.23305.14.camel@dhcp23.swansea.linux.org.uk>

On Friday 05 September 2003 03:07, Alan Cox wrote:
> On Gwe, 2003-09-05 at 01:49, Linus Torvalds wrote:
> > What really matters is that mmap() under Linux is 100% coherent, as far
> > as the hardware just allows. We haven't taken the easy way out. We
> > shouldn't start now.
>
> NFS ?

NFS doesn't attempt to implement local Posix semantics, but a DFS should.  
Anyway, Linus has ruled we're being held to the higher standard of "Linux 
semantics".

> The problem with OpenGFS is that it is a network file system so
> implementing "perfect" shared mmap semantics might actually reduce it
> from handy to useless. Right now the worst we have to do is mark pages
> uncached in some weird shared map cases, with pages being bounced across
> firewire its a bit different.

Sistina has been doing it the "perfect" way for some time now, and it's worked 
out OK.  This relies on writes being rare.

Things will definitely slow to a crawl if several nodes keep writing little 
bits into the same mmap, but that's a case of "doctor it hurts" I think.  If 
there's a common application that does this, I'd appreciate knowing about it.

Regards,

Daniel


  reply	other threads:[~2003-09-05  1:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-04 14:49 [PATCH] fix remap of shared read only mappings James Bottomley
2003-09-04 21:48 ` Jamie Lokier
2003-09-04 22:33   ` James Bottomley
2003-09-04 22:56     ` Jamie Lokier
2003-09-04 23:23       ` James Bottomley
2003-09-04 23:40         ` Jamie Lokier
2003-09-05  0:49     ` Daniel Phillips
2003-09-05  0:49       ` Linus Torvalds
2003-09-05  1:07         ` Alan Cox
2003-09-05  1:31           ` Daniel Phillips [this message]
2003-09-05  4:35           ` Linus Torvalds
2003-09-05  0:52       ` James Bottomley
2003-09-05  1:21         ` Daniel Phillips

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=200309050331.38597.phillips@arcor.de \
    --to=phillips@arcor.de \
    --cc=James.Bottomley@SteelEye.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jamie@shareable.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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 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.