From: Antonio Vargas <wind@cocodriloo.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: Bryan Shumsky <bzs@via.com>, linux-kernel@vger.kernel.org
Subject: Re: Memory mapped files question
Date: Mon, 14 Apr 2003 17:07:59 +0200 [thread overview]
Message-ID: <20030414150759.GA14552@wind.cocodriloo.com> (raw)
In-Reply-To: <8180000.1050330998@[10.10.2.4]>
On Mon, Apr 14, 2003 at 07:36:39AM -0700, Martin J. Bligh wrote:
> > 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.
> > Are we missing something? Is there a tunable parameter in the kernel or
> > filing system that can be set to flag these updates as 'write required'?
>
> This was discussed about a week ago on either linux-kernel or linux-mm.
> The short answer is "yes, that's deliberate", but an archive search would
> probably be fruitful.
>
> M.
Martin, something which was not mentioned last week (I've just checked).
It's OK if we never write to disk unless explicitely told, but will we writeback
when we munmap?
Greets, Antonio.
next prev parent reply other threads:[~2003-04-14 14:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-14 3:57 Memory mapped files question Bryan Shumsky
2003-04-14 14:36 ` Martin J. Bligh
2003-04-14 15:07 ` Antonio Vargas [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2003-04-14 19:31 Perez-Gonzalez, Inaky
2003-04-14 19:42 ` Bryan Shumsky
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
2003-04-14 19:50 Perez-Gonzalez, Inaky
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=20030414150759.GA14552@wind.cocodriloo.com \
--to=wind@cocodriloo.com \
--cc=bzs@via.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox