mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Gregory Giguashvili <Gregoryg@ParadigmGeo.com>
To: "'Dr. Michael Weller'" <eowmob@exp-math.uni-essen.de>
Cc: "Linux Kernel (E-mail)" <linux-kernel@vger.kernel.org>
Subject: RE: Problem with msync system call
Date: Tue, 23 Jul 2002 20:00:55 +0200	[thread overview]
Message-ID: <EE83E551E08D1D43AD52D50B9F511092E114A3@ntserver2> (raw)

Thanks a lot for your comments.

>I must say I have a very uneasy feeling about such a usage and 
>don't know how it is covered by standards (although you claim it works for
non
>linux). Experience shows that such a construct is very 
>fragile. Note also that NFS file locking is not mandatory, only advisory
(read: 
>user level) and it is unclear how that will interact with mmap.

I agree that the construction is very fragile, but...

- It's been working on a variety of OSes for years... There is no reason for
Linux not to support it as a mature operating system.
- This works for read/write system calls if the file is open with O_SYNC
flag and NFS is mounted using "sync" option.
- There has to be something in the OS that users can do to unconditionally
reread mapped files (no matter if this is NFS or not)
- Even mandatory locking should be sufficient for mmap interaction if one
cares to flush information to the disk before the file is unlocked.
Suprisingly, locking is not the problem here :)

Best,
Giga


             reply	other threads:[~2002-07-23 17:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-23 18:00 Gregory Giguashvili [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-07-23 19:36 Gregory Giguashvili
2002-07-23 19:04 Gregory Giguashvili
2002-07-23 18:45 Gregory Giguashvili
2002-07-23 18:06 ` Andi Kleen
     [not found] <EE83E551E08D1D43AD52D50B9F511092E1149F@ntserver2.suse.lists.linux.kernel>
2002-07-23 17:07 ` Andi Kleen
2002-07-23 18:01   ` Trond Myklebust
2002-07-23 16:58 Gregory Giguashvili
2002-07-23 16:31 ` Dr. Michael Weller

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=EE83E551E08D1D43AD52D50B9F511092E114A3@ntserver2 \
    --to=gregoryg@paradigmgeo.com \
    --cc=eowmob@exp-math.uni-essen.de \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®