From: Nikita Danilov <Nikita@Namesys.COM>
To: Andrew Morton <akpm@osdl.org>
Cc: Linux-Kernel@vger.kernel.org
Subject: Re: [PATCH] 2/5 VM changes: skip-writepage.patch
Date: Wed, 9 Jul 2003 14:41:40 +0400 [thread overview]
Message-ID: <16139.61796.951198.414088@laputa.namesys.com> (raw)
In-Reply-To: <20030709031242.14e89af6.akpm@osdl.org>
Andrew Morton writes:
> Nikita Danilov <Nikita@Namesys.COM> wrote:
> >
> > Don't call ->writepage from VM scanner when page is met for the first time
> > during scan.
>
>
> I don't think we need all the code reorganisation. Something like this:
I separated call to ->writepage into special function because of some
other patch that I didn't send yet.
>
>
> include/linux/page-flags.h | 7 +++++++
> mm/page_alloc.c | 1 +
> mm/truncate.c | 2 ++
[...]
> @@ -328,6 +328,8 @@ shrink_list(struct list_head *page_list,
> * See swapfile.c:page_queue_congested().
> */
> if (PageDirty(page)) {
> + if (!TestSetPageSkipped(page))
> + goto keep_locked;
> if (!is_page_cache_freeable(page))
> goto keep_locked;
> if (!mapping)
> @@ -351,6 +353,7 @@ shrink_list(struct list_head *page_list,
> list_move(&page->list, &mapping->locked_pages);
> spin_unlock(&mapping->page_lock);
>
> + ClearPageSkipped(page);
Good idea.
By the way, have you noted that patch changes wbc.nonblocking to be 0,
if called from kswapd or pdflush, what do you think?
> SetPageReclaim(page);
> res = mapping->a_ops->writepage(page, &wbc);
>
Nikita.
next prev parent reply other threads:[~2003-07-09 10:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-09 8:47 Nikita Danilov
2003-07-09 10:12 ` Andrew Morton
2003-07-09 10:12 ` Andrew Morton
2003-07-09 10:41 ` Nikita Danilov [this message]
2003-07-09 10:46 ` Andrew Morton
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=16139.61796.951198.414088@laputa.namesys.com \
--to=nikita@namesys.com \
--cc=Linux-Kernel@vger.kernel.org \
--cc=akpm@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®