From: William Lee Irwin III <wli@holomorphy.com>
To: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Cc: linux-kernel@vger.kernel.org, suparna@in.ibm.com, linux-aio@kvack.org
Subject: Re: aio on ramfs
Date: Sun, 7 Dec 2003 09:50:13 -0800 [thread overview]
Message-ID: <20031207175013.GF14258@holomorphy.com> (raw)
In-Reply-To: <87ptf0h6h8.fsf@devron.myhome.or.jp>
William Lee Irwin III <wli@holomorphy.com> writes:
>> +static int ramfs_writepage(struct page *page, struct writeback_control *wbc)
>> +{
>> + return 0;
>> +}
On Mon, Dec 08, 2003 at 02:40:03AM +0900, OGAWA Hirofumi wrote:
> Doesn't this break the magic of shrink_list()? I think it need the
> "return WRITEPAGE_ACTIVATE;" at least.
In truth these things shouldn't be on the LRU at all, though they're
probably blindly plopped down there. My handwavy argument was that it
makes no sense to do anything with it on the LRU and that I'd nopped
out ->set_page_dirty() anyhow (i.e. PG_dirty should never get set). Does
that hold enough water or should I still hand back WRITEPAGE_ACTIVATE?
-- wli
next prev parent reply other threads:[~2003-12-07 17:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-07 8:34 aio on ramfs William Lee Irwin III
2003-12-07 17:40 ` OGAWA Hirofumi
2003-12-07 17:50 ` William Lee Irwin III [this message]
2003-12-07 18:55 ` OGAWA Hirofumi
2003-12-07 21:50 ` Rob Landley
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=20031207175013.GF14258@holomorphy.com \
--to=wli@holomorphy.com \
--cc=hirofumi@mail.parknet.co.jp \
--cc=linux-aio@kvack.org \
--cc=linux-kernel@vger.kernel.org \
--cc=suparna@in.ibm.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