From: Eric Van Hensbergen <ericvh@gmail.com>
To: linux-fsdevel@vger.kernel.org
Subject: Re: mmap question
Date: Tue, 22 Mar 2005 15:05:47 -0600 [thread overview]
Message-ID: <a4e6962a05032213055e93983@mail.gmail.com> (raw)
In-Reply-To: <OFB9643933.64EB4A92-ON88256FCB.0080A040-88256FCB.0080B74B@us.ibm.com>
Just wanted to thank everybody for their help. I ended up backing off
the lofty goals and worked towards just passing fsx for now. The main
thing needed was an invalidate_inode_pages2(inode->i_mapping) when I
wrote the file through the uncached method (in order to invalidate any
read buffers). It turns out fsx was msync'ing the mmap writes so that
path was already clear.
I've got plenty of other fires to fight before I go after the more
extreme case, and perhaps direct I/O is the appropriate way to go
about it.
Thanks again.
-eric
next prev parent reply other threads:[~2005-03-22 21:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-21 17:59 mmap question Eric Van Hensbergen
2005-03-21 21:33 ` Bryan Henderson
2005-03-21 22:23 ` Matthew Wilcox
2005-03-21 23:18 ` Bryan Henderson
[not found] ` <a4e6962a05032114575776f94b@mail.gmail.com>
2005-03-21 22:57 ` Eric Van Hensbergen
2005-03-21 23:24 ` Bryan Henderson
2005-03-21 23:27 ` Bryan Henderson
2005-03-22 21:05 ` Eric Van Hensbergen [this message]
2005-03-21 23:56 ` Martin Jambor
-- strict thread matches above, loose matches on Subject: below --
2005-08-02 22:44 Ruslan Nikolaev
2002-09-24 7:26 Der Herr Hofrat
2002-09-24 8:54 ` Der Herr Hofrat
2002-09-24 9:37 ` Zhonghua Dai
2002-06-04 13:22 Frederic Gobry
2002-07-01 13:14 ` Frederic Gobry
2002-07-11 16:19 ` Frederic Gobry
2002-07-11 19:15 ` Jörn Engel
2002-07-12 7:57 ` Frederic Gobry
2002-07-12 15:08 ` Jörn Engel
2002-07-15 7:41 ` Frederic Gobry
2002-07-12 15:21 ` David Woodhouse
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=a4e6962a05032213055e93983@mail.gmail.com \
--to=ericvh@gmail.com \
--cc=linux-fsdevel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.