From: yamamoto-jCdQPDEk3idL9jVzuh4AOg@public.gmane.org (YAMAMOTO Takashi)
To: balbir-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org
Cc: containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org,
minoura-jCdQPDEk3idL9jVzuh4AOg@public.gmane.org
Subject: Re: [RFC] [PATCH] memory controller background reclamation
Date: Tue, 27 Nov 2007 07:43:58 +0900 (JST) [thread overview]
Message-ID: <20071126224359.2268C1CF696@siro.lan> (raw)
In-Reply-To: Your message of "Mon, 26 Nov 2007 09:26:05 +0530" <474A43D5.8020600-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
> Balbir Singh wrote:
> > YAMAMOTO Takashi wrote:
> >>>> + int batch_count = 128; /* XXX arbitrary */
> >>> Could we define and use something like MEM_CGROUP_BATCH_COUNT for now?
> >>> Later we could consider and see if it needs to be tunable. numbers are
> >>> hard to read in code.
> >> although i don't think it makes sense, i can do so if you prefer.
> >>
> >
> > Using numbers like 128 make the code unreadable. I prefer something
> > like MEM_CGROUP_BATCH_COUNT since its more readable than 128. If we ever
> > propagate batch_count to other dependent functions, I'd much rather do
> > it with a well defined name.
> >
>
> I just checked we already have FORCE_UNCHARGE_BATCH, we could just
> rename and re-use it.
i don't think it's a good idea to use a single constant for
completely different things.
YAMAMOTO Takashi
next prev parent reply other threads:[~2007-11-26 22:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-22 9:43 [RFC] [PATCH] memory controller background reclamation YAMAMOTO Takashi
[not found] ` <20071022094349.60B351C1015-Pcsii4f/SVk@public.gmane.org>
2007-10-22 16:10 ` Balbir Singh
[not found] ` <471CCB85.3040905-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2007-10-22 23:44 ` YAMAMOTO Takashi
[not found] ` <20071022234430.EE6B11C1231-Pcsii4f/SVk@public.gmane.org>
2007-11-15 6:16 ` YAMAMOTO Takashi
[not found] ` <20071115061602.856171CD9BF-Pcsii4f/SVk@public.gmane.org>
2007-11-22 8:57 ` YAMAMOTO Takashi
[not found] ` <20071122085733.758AD1CEE9F-Pcsii4f/SVk@public.gmane.org>
2007-11-22 13:33 ` kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A
2007-11-23 3:46 ` Balbir Singh
[not found] ` <47464D04.2030906-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2007-11-26 2:47 ` YAMAMOTO Takashi
[not found] ` <20071126024710.8F4ED1CF411-Pcsii4f/SVk@public.gmane.org>
2007-11-26 3:00 ` Balbir Singh
[not found] ` <474A36C3.80509-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2007-11-26 3:12 ` YAMAMOTO Takashi
2007-11-26 3:56 ` Balbir Singh
[not found] ` <474A43D5.8020600-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2007-11-26 22:43 ` YAMAMOTO Takashi [this message]
2007-11-26 23:46 ` YAMAMOTO Takashi
2007-11-26 4:09 ` Balbir Singh
2007-10-22 17:10 ` Vaidyanathan Srinivasan
[not found] ` <471CD987.5030800-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2007-10-22 23:45 ` YAMAMOTO Takashi
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=20071126224359.2268C1CF696@siro.lan \
--to=yamamoto-jcdqpdek3idl9jvzuh4aog@public.gmane.org \
--cc=balbir-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org \
--cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
--cc=minoura-jCdQPDEk3idL9jVzuh4AOg@public.gmane.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.