From: Zach Brown <zach.brown@oracle.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Patch] invalidate range of pages after direct IO write
Date: Mon, 07 Feb 2005 13:19:36 -0800 [thread overview]
Message-ID: <4207DB68.2050406@oracle.com> (raw)
In-Reply-To: <20050204153530.0409744b.akpm@osdl.org>
>> But this won't happen if next
>>started as 0 and we didn't update it. I don't know if retrying is the
>>intended behaviour or if we care that the start == 0 case doesn't do it.
>
>
> Good point. Let's make it explicit?
Looks great. I briefly had visions of some bitfield to pack the three
boolean ints we have and then quickly came to my senses. :)
I threw together those other two patches that work with ranges around
direct IO. (unmaping before r/w and writing and waiting before reads).
rc3-mm1 is angry with my test machine so they're actually against
current -bk with this first invalidation patch applied. I hope that
doesn't make life harder than it needs to be. I'll send them under
seperate cover.
- z
prev parent reply other threads:[~2005-02-07 21:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-29 2:16 [Patch] invalidate range of pages after direct IO write Zach Brown
2005-02-04 0:19 ` Andrew Morton
2005-02-04 1:52 ` Zach Brown
2005-02-04 2:28 ` Andrew Morton
2005-02-04 23:12 ` Zach Brown
2005-02-04 23:35 ` Andrew Morton
2005-02-07 21:19 ` Zach Brown [this message]
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=4207DB68.2050406@oracle.com \
--to=zach.brown@oracle.com \
--cc=akpm@osdl.org \
--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).