From: Christoph Hellwig <hch@infradead.org>
To: Jan Hudec <bulb@ucw.cz>
Cc: Shaya Potter <spotter@cs.columbia.edu>,
Jamie Lokier <jamie@shareable.org>,
linux-fsdevel@vger.kernel.org
Subject: Re: which dentry a page belongs to
Date: Sat, 24 Apr 2004 10:20:56 +0100 [thread overview]
Message-ID: <20040424102056.A10932@infradead.org> (raw)
In-Reply-To: <20040424084445.GB7119@vagabond>; from bulb@ucw.cz on Sat, Apr 24, 2004 at 10:44:46AM +0200
On Sat, Apr 24, 2004 at 10:44:46AM +0200, Jan Hudec wrote:
> On Fri, Apr 23, 2004 at 17:37:38 +0100, Christoph Hellwig wrote:
> > in 2.4 writepage is always the result of data dirtied by mmap. In 2.6 it's
> > also for use for data dirtied by write. Even in 2.4 there's no gurantee
> > the mapping that dirtied the page still exists when the page is written out
> > by the VM.
>
> No, It's the same in 2.4 and 2.6 -- both may use writepage for write
> (depends on how you implement your commit_write).
Well, okay. At least xfs uses writepage and some network filesystems do
aswell. The filesystems using generic fs/buffer.c routines don't use
writepage at least..
next prev parent reply other threads:[~2004-04-24 9:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-23 14:57 which dentry a page belongs to Shaya Potter
2004-04-23 15:14 ` Jamie Lokier
2004-04-23 15:42 ` Shaya Potter
2004-04-23 16:37 ` Christoph Hellwig
2004-04-23 16:52 ` Shaya Potter
2004-04-23 17:01 ` Christoph Hellwig
2004-04-23 17:18 ` Shaya Potter
2004-04-23 17:22 ` Christoph Hellwig
2004-04-23 17:32 ` Shaya Potter
2004-04-23 17:37 ` Jamie Lokier
2004-04-23 17:59 ` Shaya Potter
2004-04-23 22:13 ` Jamie Lokier
2004-04-23 18:05 ` Shaya Potter
2004-04-23 21:37 ` Jamie Lokier
2004-04-23 22:26 ` Shaya Potter
2004-04-23 22:49 ` Jamie Lokier
2004-04-25 5:23 ` Shaya Potter
2004-04-25 23:22 ` Erez Zadok
2004-04-24 8:53 ` Jan Hudec
2004-04-24 8:44 ` Jan Hudec
2004-04-24 9:20 ` Christoph Hellwig [this message]
2004-04-24 9:32 ` Jan Hudec
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=20040424102056.A10932@infradead.org \
--to=hch@infradead.org \
--cc=bulb@ucw.cz \
--cc=jamie@shareable.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=spotter@cs.columbia.edu \
/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