From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: linux-mm@kvack.org, yinghan@google.com, linux-kernel@vger.kernel.org
Cc: kosaki.motohiro@jp.fujitsu.com
Subject: Re: [PATCH V2 2/2] change shrinker API by passing shrink_control struct
Date: Fri, 20 May 2011 11:59:55 +0900 [thread overview]
Message-ID: <4DD5D92B.8030209@jp.fujitsu.com> (raw)
> Hmm, got Nick's email wrong.
>
> --Ying
Ping.
Can you please explain current status? When I can see your answer?
>
> On Tue, Apr 26, 2011 at 6:15 PM, Ying Han <yinghan@google.com> wrote:
>> On Tue, Apr 26, 2011 at 5:47 PM, KOSAKI Motohiro
>> <kosaki.motohiro@jp.fujitsu.com> wrote:
>>>> > > \x1a{
>>>> > > \x1a \x1a \x1a struct xfs_mount *mp;
>>>> > > \x1a \x1a \x1a struct xfs_perag *pag;
>>>> > > \x1a \x1a \x1a xfs_agnumber_t \x1aag;
>>>> > > \x1a \x1a \x1a int \x1a \x1a \x1a \x1a \x1a \x1a reclaimable;
>>>> > > + \x1a \x1a int nr_to_scan = sc->nr_slab_to_reclaim;
>>>> > > + \x1a \x1a gfp_t gfp_mask = sc->gfp_mask;
>>>> >
>>>> > And, this very near meaning field .nr_scanned and .nr_slab_to_reclaim
>>>> > poped up new question.
>>>> > Why don't we pass more clever slab shrinker target? Why do we need pass
>>>> > similar two argument?
>>>> >
>>>>
>>>> I renamed the nr_slab_to_reclaim and nr_scanned in shrink struct.
>>>
>>> Oh no. that's not naming issue. example, Nick's previous similar patch pass
>>> zone-total-pages and how-much-scanned-pages. (ie shrink_slab don't calculate
>>> current magical target scanning objects anymore)
>>> \x1a \x1a \x1a \x1aie, \x1a"4 * \x1amax_pass \x1a* (scanned / nr- lru_pages-in-zones)"
>>>
>>> Instead, individual shrink_slab callback calculate this one.
>>> see git://git.kernel.org/pub/scm/linux/kernel/git/npiggin/linux-npiggin.git
>>>
>>> I'm curious why you change the design from another guy's previous very similar effort and
>>> We have to be convinced which is better.
>>
>> Thank you for the pointer. My patch is intended to consolidate all
>> existing parameters passed from reclaim code
>> to the shrinker.
>>
>> Talked w/ Nick and Andrew from last LSF, \x1awe agree that this patch
>> will be useful for other extensions later which allows us easily
>> adding extensions to the shrinkers without shrinker files. Nick and I
>> talked about the effort later to pass the nodemask down to the
>> shrinker. He is cc-ed in the thread. Another thing I would like to
>> repost is to add the reclaim priority down to the shrinker, which we
>> won't throw tons of page caches pages by reclaiming one inode slab
>> object.
>>
>> --Ying
WARNING: multiple messages have this Message-ID (diff)
From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: linux-mm@kvack.org, yinghan@google.com, linux-kernel@vger.kernel.org
Cc: kosaki.motohiro@jp.fujitsu.com
Subject: Re: [PATCH V2 2/2] change shrinker API by passing shrink_control struct
Date: Fri, 20 May 2011 11:59:55 +0900 [thread overview]
Message-ID: <4DD5D92B.8030209@jp.fujitsu.com> (raw)
> Hmm, got Nick's email wrong.
>
> --Ying
Ping.
Can you please explain current status? When I can see your answer?
>
> On Tue, Apr 26, 2011 at 6:15 PM, Ying Han <yinghan@google.com> wrote:
>> On Tue, Apr 26, 2011 at 5:47 PM, KOSAKI Motohiro
>> <kosaki.motohiro@jp.fujitsu.com> wrote:
>>>> > > \x1a{
>>>> > > \x1a \x1a \x1a struct xfs_mount *mp;
>>>> > > \x1a \x1a \x1a struct xfs_perag *pag;
>>>> > > \x1a \x1a \x1a xfs_agnumber_t \x1aag;
>>>> > > \x1a \x1a \x1a int \x1a \x1a \x1a \x1a \x1a \x1a reclaimable;
>>>> > > + \x1a \x1a int nr_to_scan = sc->nr_slab_to_reclaim;
>>>> > > + \x1a \x1a gfp_t gfp_mask = sc->gfp_mask;
>>>> >
>>>> > And, this very near meaning field .nr_scanned and .nr_slab_to_reclaim
>>>> > poped up new question.
>>>> > Why don't we pass more clever slab shrinker target? Why do we need pass
>>>> > similar two argument?
>>>> >
>>>>
>>>> I renamed the nr_slab_to_reclaim and nr_scanned in shrink struct.
>>>
>>> Oh no. that's not naming issue. example, Nick's previous similar patch pass
>>> zone-total-pages and how-much-scanned-pages. (ie shrink_slab don't calculate
>>> current magical target scanning objects anymore)
>>> \x1a \x1a \x1a \x1aie, \x1a"4 * \x1amax_pass \x1a* (scanned / nr- lru_pages-in-zones)"
>>>
>>> Instead, individual shrink_slab callback calculate this one.
>>> see git://git.kernel.org/pub/scm/linux/kernel/git/npiggin/linux-npiggin.git
>>>
>>> I'm curious why you change the design from another guy's previous very similar effort and
>>> We have to be convinced which is better.
>>
>> Thank you for the pointer. My patch is intended to consolidate all
>> existing parameters passed from reclaim code
>> to the shrinker.
>>
>> Talked w/ Nick and Andrew from last LSF, \x1awe agree that this patch
>> will be useful for other extensions later which allows us easily
>> adding extensions to the shrinkers without shrinker files. Nick and I
>> talked about the effort later to pass the nodemask down to the
>> shrinker. He is cc-ed in the thread. Another thing I would like to
>> repost is to add the reclaim priority down to the shrinker, which we
>> won't throw tons of page caches pages by reclaiming one inode slab
>> object.
>>
>> --Ying
--
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 reply other threads:[~2011-05-20 3:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-20 2:59 KOSAKI Motohiro [this message]
2011-05-20 2:59 ` [PATCH V2 2/2] change shrinker API by passing shrink_control struct KOSAKI Motohiro
2011-05-20 3:23 ` Ying Han
2011-05-20 12:30 ` KOSAKI Motohiro
2011-05-20 12:30 ` KOSAKI Motohiro
-- strict thread matches above, loose matches on Subject: below --
2011-04-25 17:22 [PATCH V2 0/2] pass the scan_control into shrinkers Ying Han
2011-04-25 17:22 ` [PATCH V2 2/2] change shrinker API by passing shrink_control struct Ying Han
2011-04-25 18:34 ` Rik van Riel
2011-04-25 18:47 ` Pavel Emelyanov
2011-04-26 1:15 ` KOSAKI Motohiro
2011-04-27 0:21 ` Ying Han
2011-04-27 0:47 ` KOSAKI Motohiro
2011-04-27 1:15 ` Ying Han
2011-04-27 1:18 ` Ying Han
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=4DD5D92B.8030209@jp.fujitsu.com \
--to=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=yinghan@google.com \
/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.