From: KOSAKI Motohiro <kosaki.motohiro@gmail.com>
To: Hugh Dickins <hughd@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Konstantin Khlebnikov <khlebnikov@openvz.org>,
linux-mm@kvack.org
Subject: Re: [PATCH 3/3] mm: take pagevecs off reclaim stack
Date: Thu, 29 Dec 2011 19:24:18 -0500 [thread overview]
Message-ID: <4EFD04B2.7050407@gmail.com> (raw)
In-Reply-To: <alpine.LSU.2.00.1112291510390.4888@eggly.anvils>
(12/29/11 6:27 PM), Hugh Dickins wrote:
> On Thu, 29 Dec 2011, Andrew Morton wrote:
>> On Wed, 28 Dec 2011 20:39:36 -0800 (PST)
>> Hugh Dickins<hughd@google.com> wrote:
>>
>>> Replace pagevecs in putback_lru_pages() and move_active_pages_to_lru()
>>> by lists of pages_to_free
>>
>> One effect of the pagevec handling was to limit lru_lock hold times and
>> interrupt-disabled times.
>>
>> This patch removes that upper bound and has the potential to cause
>> various latency problems when processing large numbers of pages.
>>
>> The affected functions have rather a lot of callers. I don't think
>> that auditing all these callers and convincing ourselves that none of
>> them pass in 10,000 pages is sufficient, because that doesn't prevent us
>> from introducing such latency problems as the MM code evolves.
>
> That's an interesting slant on it, that hadn't crossed my mind;
> but it looks like intervening changes have answered that concern.
>
> putback_lru_pages() has one caller, shrink_inactive_list();
> move_active_pages_to_lru() has one caller, shrink_active_list().
> Following those back, they're in all cases capped to SWAP_CLUSTER_MAX
> pages per call. That's 32 pages, not so very much more than the 14
> page limit the pagevecs were imposing.
>
> And both shrink_inactive_list() and shrink_active_list() gather these
> pages with isolate_lru_pages(), which does not drop lock or enable
> interrupts at all - probably why the SWAP_CLUSTER_MAX cap got imposed.
When lumpy reclaim occur, isolate_lru_pages() gather much pages than
SWAP_CLUSTER_MAX. However, at that time, I think this patch behave
better than old. If we release and retake zone lock per 14 pages,
other tasks can easily steal a part of lumpy reclaimed pages. and then
long latency wrongness will be happen when system is under large page
memory allocation pressure. That's the reason why I posted very similar
patch a long time ago.
--
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-12-30 0:24 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-29 4:32 [PATCH 0/3] mm: three minor vmscan improvements Hugh Dickins
2011-12-29 4:35 ` [PATCH 1/3] mm: test PageSwapBacked in lumpy reclaim Hugh Dickins
2011-12-29 5:06 ` KOSAKI Motohiro
2012-01-04 1:23 ` Minchan Kim
2012-01-05 6:03 ` KAMEZAWA Hiroyuki
2011-12-29 4:36 ` [PATCH 2/3] mm: cond_resched in scan_mapping_unevictable_pages Hugh Dickins
2011-12-29 5:14 ` KOSAKI Motohiro
2011-12-29 5:48 ` Hugh Dickins
2011-12-29 22:46 ` Hugh Dickins
2011-12-29 4:39 ` [PATCH 3/3] mm: take pagevecs off reclaim stack Hugh Dickins
2011-12-29 5:42 ` KOSAKI Motohiro
2011-12-29 11:18 ` Konstantin Khlebnikov
2011-12-29 22:20 ` Hugh Dickins
2011-12-29 22:55 ` Andrew Morton
2011-12-29 23:27 ` Hugh Dickins
2011-12-30 0:24 ` KOSAKI Motohiro [this message]
2011-12-30 1:55 ` Hugh Dickins
2011-12-30 3:59 ` Andrew Morton
2011-12-30 15:51 ` Mel Gorman
2012-01-01 7:18 ` Hugh Dickins
2012-01-03 23:12 ` Andrew Morton
2012-01-03 23:17 ` KOSAKI Motohiro
2012-01-03 23:29 ` Andrew Morton
2012-01-04 0:03 ` KOSAKI Motohiro
2012-01-04 3:22 ` Hugh Dickins
2012-01-04 20:20 ` 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=4EFD04B2.7050407@gmail.com \
--to=kosaki.motohiro@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=khlebnikov@openvz.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).