From: Minchan Kim <minchan.kim@gmail.com>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Ben Gamari <bgamari.foss@gmail.com>,
linux-kernel@vger.kernel.org, rsync@lists.samba.org,
linux-mm@kvack.org, Peter Zijlstra <peterz@infradead.org>,
Wu Fengguang <fengguang.wu@intel.com>
Subject: Re: fadvise DONTNEED implementation (or lack thereof)
Date: Mon, 15 Nov 2010 16:19:48 +0900 [thread overview]
Message-ID: <AANLkTim0vCJkMoH5P0wCN9J6340rDsscyNBQ+R+_ph8m@mail.gmail.com> (raw)
In-Reply-To: <20101115160413.BF0F.A69D9226@jp.fujitsu.com>
On Mon, Nov 15, 2010 at 4:09 PM, KOSAKI Motohiro
<kosaki.motohiro@jp.fujitsu.com> wrote:
>> > Because we have an alternative solution already. please try memcgroup :)
>>
>> I think memcg could be a solution of them but fundamental solution is
>> that we have to cure it in VM itself.
>> I feel it's absolutely absurd to enable and use memcg for amending it.
>>
>> I wonder what's the problem in Peter's patch 'drop behind'.
>> http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg179576.html
>>
>> Could anyone tell me why it can't accept upstream?
>
> I don't know the reason. And this one looks reasonable to me. I'm curious the above
> patch solve rsync issue or not.
> Minchan, have you tested it yourself?
Still yet. :)
If we all think it's reasonable, it would be valuable to adjust it
with current mmotm and see the effect.
>
>
>
--
Kind regards,
Minchan Kim
next prev parent reply other threads:[~2010-11-15 7:19 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-04 5:58 fadvise DONTNEED implementation (or lack thereof) Ben Gamari
2010-11-09 7:28 ` KOSAKI Motohiro
2010-11-09 8:03 ` KOSAKI Motohiro
2010-11-09 12:54 ` Ben Gamari
2010-11-14 5:09 ` KOSAKI Motohiro
2010-11-14 5:20 ` Ben Gamari
2010-11-14 21:33 ` Brian K. White
2010-11-15 6:07 ` Minchan Kim
2010-11-15 7:09 ` KOSAKI Motohiro
2010-11-15 7:19 ` Minchan Kim [this message]
2010-11-15 7:28 ` KOSAKI Motohiro
2010-11-15 7:46 ` Minchan Kim
2010-11-15 12:46 ` Ben Gamari
2010-11-15 8:47 ` Peter Zijlstra
2010-11-15 9:05 ` Minchan Kim
2010-11-15 14:48 ` Rik van Riel
2010-11-17 10:16 ` Minchan Kim
2010-11-17 11:15 ` Minchan Kim
2010-11-17 16:22 ` Rik van Riel
2010-11-18 2:47 ` Minchan Kim
2010-11-18 3:24 ` Rik van Riel
2010-11-18 3:46 ` Minchan Kim
2010-11-15 9:10 ` KOSAKI Motohiro
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=AANLkTim0vCJkMoH5P0wCN9J6340rDsscyNBQ+R+_ph8m@mail.gmail.com \
--to=minchan.kim@gmail.com \
--cc=bgamari.foss@gmail.com \
--cc=fengguang.wu@intel.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=peterz@infradead.org \
--cc=rsync@lists.samba.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).