public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Bryan Shumsky" <bzs@via.com>
To: "Perez-Gonzalez, Inaky" <inaky.perez-gonzalez@intel.com>,
	<linux-kernel@vger.kernel.org>
Subject: Re: Memory mapped files question
Date: Mon, 14 Apr 2003 12:42:01 -0700	[thread overview]
Message-ID: <004301c302bd$ed548680$fe64a8c0@webserver> (raw)
In-Reply-To: A46BBDB345A7D5118EC90002A5072C780BEBAD8D@orsmsx116.jf.intel.com

Hi, everyone.  Thanks for all your responses.  Our confusion is that in Unix
environments, when we modify memory in memory-mapped files the underlying
system flusher manages to flush the files for us before the files are
munmap'ed or msysnc'ed.

Rewriting all of our code to manually handle the flushing is a MAJOR
undertaking, so I was hoping there might be some sneaky solution you could
come up with.  Any ideas?

Thanks again,

-- Bryan Shumsky
Director of Engineering
Via Systems, Inc.

----- Original Message -----
From: "Perez-Gonzalez, Inaky" <inaky.perez-gonzalez@intel.com>
To: "'Bryan Shumsky'" <bzs@via.com>; <linux-kernel@vger.kernel.org>
Sent: Monday, April 14, 2003 12:31 PM
Subject: RE: Memory mapped files question


>
> > From: Bryan Shumsky [mailto:bzs@via.com]
>
> > Hi, everyone.  I'm running into a problem that I hope someone else has
> seen,
> > and maybe can help solve.  We're using the mmap system function for
memory
> > mapped files, but our updates never get flushed until we munmap or
msysnc.
>
> I thought that was the way it was supposed to work.
>
> Iñaky Pérez-González -- Not speaking for Intel -- all opinions are my own
> (and my fault)
>
>



  reply	other threads:[~2003-04-14 19:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-14 19:31 Memory mapped files question Perez-Gonzalez, Inaky
2003-04-14 19:42 ` Bryan Shumsky [this message]
2003-04-14 19:53   ` Alan Cox
2003-04-14 21:24     ` Chris Friesen
2003-04-14 20:13   ` Richard B. Johnson
2003-04-14 20:27     ` Frank van Maarseveen
2003-04-14 20:52       ` Richard B. Johnson
2003-04-14 22:08   ` H. Peter Anvin
2003-04-15  4:56     ` Jamie Lokier
2003-04-15  5:30       ` H. Peter Anvin
  -- strict thread matches above, loose matches on Subject: below --
2003-04-14 19:50 Perez-Gonzalez, Inaky
2003-04-14  3:57 Bryan Shumsky
2003-04-14 14:36 ` Martin J. Bligh
2003-04-14 15:07   ` Antonio Vargas
2003-04-14 15:04     ` Martin J. Bligh
2003-04-14 18:07       ` H. Peter Anvin
2003-04-14 20:39         ` Chris Friesen
2003-04-14 21:12           ` H. Peter Anvin

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='004301c302bd$ed548680$fe64a8c0@webserver' \
    --to=bzs@via.com \
    --cc=inaky.perez-gonzalez@intel.com \
    --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