From: Chandra Seetharaman <sekharan@us.ibm.com>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: ckrm-tech@lists.sourceforge.net, linux-mm <linux-mm@kvack.org>
Subject: Re: [ckrm-tech] [Patch 5/6] CKRM: Add config support for mem controller
Date: Thu, 19 May 2005 09:26:53 -0700 [thread overview]
Message-ID: <20050519162653.GB27270@chandralinux.beaverton.ibm.com> (raw)
In-Reply-To: <1116466010.26955.102.camel@localhost>
On Wed, May 18, 2005 at 06:26:50PM -0700, Dave Hansen wrote:
> There appears to still be some serious issues in the patch with respect
> to per-zone accounting. There is only accounting in each ckrm_mem_res
> for each *kind* of zone, not each zone.
In the absense of NUMA/DISCONTIGMEM, isn't 'kind of zone' and 'zone'
the same ? Correct me if this assumption is wrong.
>
> For instance, the accounting for a page appears to be the same no matter
> which zone it came from, just which kind of zone
>
> Then, when it comes to actually use some of the information, the kswapd
> wakeup just throws a completely unrelated number into wakeup_kswapd().
> ZONE_DMA (zone 0) tends to be *MUCH* smaller than ZONE_HIGHMEM, for
> instance. It doesn't make a whole lot of logical sense to me to be
> waking up kswapd for a possibly 16GB zone with data from a 16MB zone.
When control goes into wakeup_kswapd(), it looks for the over_limit list and
works only on the classes, and completely ignores the arguments to
wakeup_kswapd().
I did it this way(instead of having my own logic) to use existing code.
>
> + for_each_zone(zone) {
> + /* This is just a number to get to wakeup kswapd */
> + order = cls->pg_total[0] -
> + ((ckrm_mem_shrink_to * cls->pg_limit) / 100);
> + wakeup_kswapd(zone, order);
> + break; /* only once is enough */
> + }
>
> If the number doesn't matter, why not just pass 0 into it?
Yes, i could. will do it.
>
> Could you explain what advantages keeping a per-zone-type count has over
> actually doing one count for each zone? Also, why bother tracking it
> per-zone-type anyway? Would a single count work the same way
fits the NUMA/DISCONTIGMEM issue discussed above.
>
> -- Dave
>
--
----------------------------------------------------------------------
Chandra Seetharaman | Be careful what you choose....
- sekharan@us.ibm.com | .......you may get it.
----------------------------------------------------------------------
--
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:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2005-05-19 16:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 0:33 Chandra Seetharaman
2005-05-19 1:26 ` [ckrm-tech] " Dave Hansen
2005-05-19 16:26 ` Chandra Seetharaman [this message]
2005-05-19 16:43 ` Dave Hansen
2005-05-19 16:49 ` Chandra Seetharaman
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=20050519162653.GB27270@chandralinux.beaverton.ibm.com \
--to=sekharan@us.ibm.com \
--cc=ckrm-tech@lists.sourceforge.net \
--cc=haveblue@us.ibm.com \
--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