From: Andre Hedrick <andre@linux-ide.org>
To: Keith Ansell <keitha@edp.fastfreenet.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>, Jens Axboe <axboe@suse.de>
Subject: Re: bdflush flushing memory mapped pages.
Date: Wed, 9 Apr 2003 02:13:03 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.10.10304090209440.12558-100000@master.linux-ide.org> (raw)
In-Reply-To: <007601c2fecd$12209070$230110ac@kaws>
Funny you mention this point!
I just spent 30-45 minutes on the phone talking to Jens about this very
issue. Jens states he can map the model in to 2.5. and will give it a
fling in a bit. This issue is a must; however, I had given up on the idea
until 2.7. However, the issues he and I addressed, in combination to your
request jive in sync.
Cheers,
Andre Hedrick
LAD Storage Consulting Group
On Wed, 9 Apr 2003, Keith Ansell wrote:
> help
>
> My application uses SHARED memory mapping files for file I/O, and we have
> observed
> that Linux does not flush dirty pages to disk until munmap or msync are
> called.
>
> I would like to know are there any development plans which would address
> this issue or
> if there is a version of bdflush which flushes write required pages (dirty
> pages) to disk?
>
> Regards
> Keith Ansell.
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2003-04-09 9:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-09 19:20 bdflush flushing memory mapped pages Keith Ansell
2003-04-09 9:13 ` Andre Hedrick [this message]
2003-04-09 9:27 ` Andrew Morton
2003-04-09 9:33 ` Jens Axboe
2003-04-10 20:09 ` Keith Ansell
2003-04-10 8:16 ` Andre Hedrick
2003-04-10 9:02 ` Nick Piggin
2003-04-10 17:04 ` Alan Cox
2003-04-09 9:22 ` Arjan van de Ven
2003-04-09 10:39 ` Alan Cox
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=Pine.LNX.4.10.10304090209440.12558-100000@master.linux-ide.org \
--to=andre@linux-ide.org \
--cc=axboe@suse.de \
--cc=keitha@edp.fastfreenet.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;
as well as URLs for NNTP newsgroup(s).