From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: khlebnikov@openvz.org
Cc: linux-mm@kvack.org, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC] mm: reverse lru scanning order
Date: Tue, 02 Aug 2011 08:45:04 +0900 [thread overview]
Message-ID: <4E373A80.3090206@jp.fujitsu.com> (raw)
In-Reply-To: <4E36D110.30407@openvz.org>
(2011/08/02 1:15), Konstantin Khlebnikov wrote:
> sorry, this patch is broken.
If you resend a _tested_ patch, I'll ack this one.
Thanks.
>
> Konstantin Khlebnikov wrote:
>> LRU scanning order was accidentially changed in commit v2.6.27-5584-gb69408e:
>> "vmscan: Use an indexed array for LRU variables".
>> Before that commit reclaimer always scan active lists first.
>>
>> This patch just reverse it back.
>> This is just notice and question: "Does it affect something?"
WARNING: multiple messages have this Message-ID (diff)
From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: khlebnikov@openvz.org
Cc: linux-mm@kvack.org, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC] mm: reverse lru scanning order
Date: Tue, 02 Aug 2011 08:45:04 +0900 [thread overview]
Message-ID: <4E373A80.3090206@jp.fujitsu.com> (raw)
In-Reply-To: <4E36D110.30407@openvz.org>
(2011/08/02 1:15), Konstantin Khlebnikov wrote:
> sorry, this patch is broken.
If you resend a _tested_ patch, I'll ack this one.
Thanks.
>
> Konstantin Khlebnikov wrote:
>> LRU scanning order was accidentially changed in commit v2.6.27-5584-gb69408e:
>> "vmscan: Use an indexed array for LRU variables".
>> Before that commit reclaimer always scan active lists first.
>>
>> This patch just reverse it back.
>> This is just notice and question: "Does it affect something?"
--
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-08-01 23:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-27 11:10 [PATCH RFC] mm: reverse lru scanning order Konstantin Khlebnikov
2011-07-27 11:10 ` Konstantin Khlebnikov
2011-08-01 16:15 ` Konstantin Khlebnikov
2011-08-01 16:15 ` Konstantin Khlebnikov
2011-08-01 23:45 ` KOSAKI Motohiro [this message]
2011-08-01 23:45 ` KOSAKI Motohiro
2011-08-08 11:02 ` [PATCH v2] vmscan: " Konstantin Khlebnikov
2011-08-08 11:02 ` Konstantin Khlebnikov
2011-08-08 12:22 ` Michal Hocko
2011-08-08 12:22 ` Michal Hocko
2011-08-08 22:30 ` Minchan Kim
2011-08-08 22:30 ` Minchan Kim
2011-08-08 23:48 ` KAMEZAWA Hiroyuki
2011-08-08 23:48 ` KAMEZAWA Hiroyuki
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=4E373A80.3090206@jp.fujitsu.com \
--to=kosaki.motohiro@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=khlebnikov@openvz.org \
--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 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.