From: Christoph Hellwig <hch@infradead.org>
To: Nathan Scott <nathans@sgi.com>
Cc: linux-xfs@oss.sgi.com, linux-fsdevel@vger.kernel.org
Subject: Re: TAKE 949916 - direct read vs delalloc
Date: Fri, 17 Mar 2006 17:57:19 +0000 [thread overview]
Message-ID: <20060317175719.GA6619@infradead.org> (raw)
In-Reply-To: <20060317053019.C44EF49F168A@chook.melbourne.sgi.com>
On Fri, Mar 17, 2006 at 04:30:19PM +1100, Nathan Scott wrote:
> Flush and invalidate dirty pages at the start of a direct read also,
> else we can hit a delalloc-extents-via-direct-io BUG.
If this is needed it should be done in the filemap.c code.
>
> Date: Fri Mar 17 16:29:59 AEDT 2006
> Workarea: chook.melbourne.sgi.com:/build/nathans/xfs-linux
> Inspected by: tes
>
> The following file(s) were checked into:
> longdrop.melbourne.sgi.com:/isms/xfs-kern/xfs-linux-melb
>
>
> Modid: xfs-linux-melb:xfs-kern:25483a
> linux-2.6/xfs_lrw.c - 1.237 - changed
> http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/linux-2.6/xfs_lrw.c.diff?r1=text&tr1=1.237&r2=text&tr2=1.236&f=h
>
>
---end quoted text---
next parent reply other threads:[~2006-03-17 17:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060317053019.C44EF49F168A@chook.melbourne.sgi.com>
2006-03-17 17:57 ` Christoph Hellwig [this message]
2006-03-18 3:27 ` TAKE 949916 - direct read vs delalloc Nathan Scott
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=20060317175719.GA6619@infradead.org \
--to=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.com \
--cc=nathans@sgi.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