From: Nikita Danilov <Nikita@Namesys.COM>
To: David Woodhouse <dwmw2@infradead.org>
Cc: manningc2@actrix.gen.nz, linux-fsdevel@vger.kernel.org
Subject: Re: Implementing writepage
Date: Mon, 27 Oct 2003 11:43:29 +0300 [thread overview]
Message-ID: <16284.55985.863779.2130@laputa.namesys.com> (raw)
In-Reply-To: <1067243966.15551.256.camel@hades.cambridge.redhat.com>
David Woodhouse writes:
> On Mon, 2003-10-27 at 11:34 +0300, Nikita Danilov wrote:
> > Note that ->writepage() is used not only by mmap() (actually, it is only
> > used by mmap() is file system doesn't provide its on
> > ->writepages()). ->writepage() is used by VM to write pages in response
> > to the memory pressure (see mm/vmscan.c:shrink_list()). Every
> > well-behaving file system has to provide ->writepage() for this purpose.
>
> How do you get dirty but still file-backed pages if you don't get them
> by shared writable mmap?
By write(2)? May be I am missing something in this discussion, though.
>
> --
> dwmw2
>
Nikita.
next prev parent reply other threads:[~2003-10-27 8:43 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-07 4:11 fs test suite Pat LaVarre
2003-10-07 14:17 ` Randy.Dunlap
2003-10-07 14:59 ` Zachary Peterson
2003-10-07 17:16 ` Randy.Dunlap
2003-10-07 18:54 ` Pat LaVarre
2003-10-07 18:58 ` Randy.Dunlap
2003-10-07 19:26 ` Pat LaVarre
2003-10-20 9:12 ` srfs - a new file system Nir Tzachar
2003-10-20 21:00 ` Eric Sandall
2003-10-21 12:07 ` Nir Tzachar
2003-10-21 14:29 ` Brian Beattie
2003-10-21 16:59 ` Jan Harkes
2003-10-23 13:58 ` Pavel Machek
2003-10-24 9:28 ` Nir Tzachar
2003-10-23 17:46 ` Daniel Egger
2003-10-23 18:47 ` Eric Sandall
2003-10-23 23:15 ` Daniel Egger
2003-10-24 15:45 ` srfs - a new file system.--OT Gadgeteer
2003-10-24 9:26 ` srfs - a new file system Nir Tzachar
2003-10-22 4:57 ` Erik Andersen
2003-10-22 10:16 ` Nir Tzachar
2003-10-22 14:22 ` Jan Harkes
2003-10-23 7:50 ` Nir Tzachar
2003-10-23 12:33 ` Jan Hudec
2003-10-23 20:12 ` Pat LaVarre
2003-10-24 9:21 ` Nir Tzachar
2003-10-24 12:08 ` Matthew Wilcox
2003-10-24 19:14 ` Nir Tzachar
2003-10-24 14:38 ` Jan Harkes
2003-10-24 19:16 ` Nir Tzachar
2003-10-24 20:11 ` Andreas Dilger
2003-10-24 20:24 ` Pat LaVarre
2003-10-24 20:38 ` Andreas Dilger
2003-10-24 20:52 ` Pat LaVarre
2003-10-24 21:00 ` Nir Tzachar
2003-10-24 21:22 ` Pat LaVarre
2003-10-24 23:03 ` Nir Tzachar
2003-10-25 0:23 ` Bryan Henderson
2003-10-25 10:37 ` Nir Tzachar
2003-10-24 21:15 ` Andreas Dilger
2003-10-24 20:53 ` Nir Tzachar
2003-10-25 8:01 ` Jan Hudec
2003-10-22 10:21 ` Nir Tzachar
2003-10-22 16:05 ` Valdis.Kletnieks
2003-10-22 19:38 ` Erik Andersen
2003-10-23 5:20 ` Miles Bader
2003-10-23 5:37 ` Valdis.Kletnieks
2003-10-25 9:27 ` Implementing writepage Charles Manning
2003-10-25 16:18 ` David Woodhouse
2003-10-25 22:40 ` Charles Manning
2003-10-26 10:25 ` David Woodhouse
2003-10-26 15:28 ` Matthew Wilcox
2003-10-26 18:47 ` Mark B
2003-10-26 20:40 ` Charles Manning
2003-10-26 21:04 ` David Woodhouse
2003-10-26 20:54 ` Charles Manning
2003-10-27 8:34 ` Nikita Danilov
2003-10-27 8:39 ` David Woodhouse
2003-10-27 8:43 ` Nikita Danilov [this message]
2003-10-27 8:46 ` David Woodhouse
2003-10-27 8:52 ` Nikita Danilov
2003-10-27 9:06 ` David Woodhouse
2003-10-27 9:08 ` 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=16284.55985.863779.2130@laputa.namesys.com \
--to=nikita@namesys.com \
--cc=dwmw2@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=manningc2@actrix.gen.nz \
/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.