From: Konstantin Khlebnikov <khlebnikov@openvz.org>
To: Dave Chinner <david@fromorbit.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm: remove struct reclaim_state
Date: Fri, 18 Nov 2011 14:07:02 +0400 [thread overview]
Message-ID: <4EC62E46.6080503@openvz.org> (raw)
In-Reply-To: <20111118095644.GJ7046@dastard>
Dave Chinner wrote:
> On Fri, Nov 18, 2011 at 01:28:06PM +0300, Konstantin Khlebnikov wrote:
>> Memory reclaimer want to know how much pages was reclaimed during shrinking slabs.
>> Currently there is special struct reclaim_state with single counter and pointer from
>> task-struct. Let's store counter direcly on task struct and account freed pages
>> unconditionally. This will reduce stack usage and simplify code in reclaimer and slab.
>>
>> Logic in do_try_to_free_pages() is slightly changed, but this is ok.
>> Nobody calls shrink_slab() explicitly before do_try_to_free_pages(),
>
> Except for drop_slab() and shake_page()....
Indeed, but they do not care about accounting reclaimed pages and
they do not call do_try_to_free_pages() after all.
>
> Cheers,
>
> Dave.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-11-18 10:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-18 10:28 [PATCH] mm: remove struct reclaim_state Konstantin Khlebnikov
2011-11-18 9:56 ` Dave Chinner
2011-11-18 10:07 ` Konstantin Khlebnikov [this message]
2011-11-18 21:09 ` Dave Chinner
2011-11-19 9:55 ` [PATCH v2] " Konstantin Khlebnikov
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=4EC62E46.6080503@openvz.org \
--to=khlebnikov@openvz.org \
--cc=akpm@linux-foundation.org \
--cc=david@fromorbit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).