From: Jamie Lokier <jamie@shareable.org>
To: Shaya Potter <spotter@cs.columbia.edu>
Cc: Christoph Hellwig <hch@infradead.org>, linux-fsdevel@vger.kernel.org
Subject: Re: which dentry a page belongs to
Date: Fri, 23 Apr 2004 23:49:47 +0100 [thread overview]
Message-ID: <20040423224947.GC8915@mail.shareable.org> (raw)
In-Reply-To: <1082759212.1854.6.camel@zaphod>
Shaya Potter wrote:
> OK, great example, now I see the problem which can't be easily solved.
>
> update-data
> ioctl
> update-data
> writepage()
>
> writepage can't differentiate b/w data b4 and data after, so only way to
> do it would be to force a sync b4 ioctl is called, which I would think
> (perhaps wrong) should write out all the data to disk. But unsure if
> prorgramatically able to really test to see if it worked or not.
"sync" doesn't do anything to help.
Read up on msync() until you understand what is intended here.
In general, first "update-data" in your example doesn't count as a
"write" and it wouldn't be logical for a program to expect it to be
snapshotted. It counts as the program queuing up data which it does
not expect to be visible in the file until the next msync, munmap or
exit (although it is visible to other concurrent mmaps, and it _might_
be visible in the file, of parts of it might).
-- Jamie
next prev parent reply other threads:[~2004-04-23 22:49 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 [this message]
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
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=20040423224947.GC8915@mail.shareable.org \
--to=jamie@shareable.org \
--cc=hch@infradead.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