All of lore.kernel.org
 help / color / mirror / Atom feed
From: Minchan Kim <minchan.kim@gmail.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-mm <linux-mm@kvack.org>,
	LKML <linux-kernel@vger.kernel.org>,
	KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
	Johannes Weiner <hannes@cmpxchg.org>,
	Rik van Riel <riel@redhat.com>,
	"M. Vefa Bicakci" <bicave@superonline.com>,
	stable@kernel.org
Subject: Re: [PATCH v2] vmscan: check all_unreclaimable in direct reclaim path
Date: Mon, 13 Sep 2010 09:47:02 +0900	[thread overview]
Message-ID: <AANLkTimzby23QO4w0o1vSHnin9AakoG+cp9zd6a8T6FA@mail.gmail.com> (raw)
In-Reply-To: <201009121942.53543.rjw@sisk.pl>

On Mon, Sep 13, 2010 at 2:42 AM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> On Sunday, September 12, 2010, Minchan Kim wrote:
>> Adnrew, Please drop my old version and merge this verstion.
>> (old : vmscan-check-all_unreclaimable-in-direct-reclaim-path.patch)
>>
>>  * Changelog from v2
>>    * remove inline - suggested by Andrew
>>    * add function desription - suggeseted by Adnrew
>>
>> == CUT HERE ==
>
> For the record, this commit:
>
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=6715045ddc7472a22be5e49d4047d2d89b391f45
>
> is reported to fix the problem without the $subject patch (see
> http://lkml.org/lkml/2010/9/11/129).  So, I'm not sure if it's still necessary
> to special case this particular situation?


I didn't follow your patch.
If your patch can fix the problem, We don't need new overhead direct
reclaim without big benefit. So I don't care of dropping this patch.

We need agreement of another author KOSAKI.

Thanks for the information, Rafael. :)
-- 
Kind regards,
Minchan Kim

WARNING: multiple messages have this Message-ID (diff)
From: Minchan Kim <minchan.kim@gmail.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-mm <linux-mm@kvack.org>,
	LKML <linux-kernel@vger.kernel.org>,
	KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
	Johannes Weiner <hannes@cmpxchg.org>,
	Rik van Riel <riel@redhat.com>,
	"M. Vefa Bicakci" <bicave@superonline.com>,
	stable@kernel.org
Subject: Re: [PATCH v2] vmscan: check all_unreclaimable in direct reclaim path
Date: Mon, 13 Sep 2010 09:47:02 +0900	[thread overview]
Message-ID: <AANLkTimzby23QO4w0o1vSHnin9AakoG+cp9zd6a8T6FA@mail.gmail.com> (raw)
In-Reply-To: <201009121942.53543.rjw@sisk.pl>

On Mon, Sep 13, 2010 at 2:42 AM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> On Sunday, September 12, 2010, Minchan Kim wrote:
>> Adnrew, Please drop my old version and merge this verstion.
>> (old : vmscan-check-all_unreclaimable-in-direct-reclaim-path.patch)
>>
>>  * Changelog from v2
>>    * remove inline - suggested by Andrew
>>    * add function desription - suggeseted by Adnrew
>>
>> == CUT HERE ==
>
> For the record, this commit:
>
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=6715045ddc7472a22be5e49d4047d2d89b391f45
>
> is reported to fix the problem without the $subject patch (see
> http://lkml.org/lkml/2010/9/11/129).  So, I'm not sure if it's still necessary
> to special case this particular situation?


I didn't follow your patch.
If your patch can fix the problem, We don't need new overhead direct
reclaim without big benefit. So I don't care of dropping this patch.

We need agreement of another author KOSAKI.

Thanks for the information, Rafael. :)
-- 
Kind regards,
Minchan Kim

--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2010-09-13  0:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-12 16:32 [PATCH v2] vmscan: check all_unreclaimable in direct reclaim path Minchan Kim
2010-09-12 16:32 ` Minchan Kim
2010-09-12 17:42 ` Rafael J. Wysocki
2010-09-12 17:42   ` Rafael J. Wysocki
2010-09-13  0:47   ` Minchan Kim [this message]
2010-09-13  0:47     ` Minchan Kim

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=AANLkTimzby23QO4w0o1vSHnin9AakoG+cp9zd6a8T6FA@mail.gmail.com \
    --to=minchan.kim@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=bicave@superonline.com \
    --cc=hannes@cmpxchg.org \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=riel@redhat.com \
    --cc=rjw@sisk.pl \
    --cc=stable@kernel.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.