From: Chandra Seetharaman <sekharan@us.ibm.com>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: Hirokazu Takahashi <taka@valinux.co.jp>,
ckrm-tech@lists.sourceforge.net, linux-mm <linux-mm@kvack.org>
Subject: Re: [ckrm-tech] Virtual NUMA machine and CKRM
Date: Tue, 31 May 2005 12:13:03 -0700 [thread overview]
Message-ID: <20050531191303.GE29202@chandralinux.beaverton.ibm.com> (raw)
In-Reply-To: <1117203358.18725.12.camel@localhost>
On Fri, May 27, 2005 at 07:15:58AM -0700, Dave Hansen wrote:
> On Fri, 2005-05-27 at 22:16 +0900, Hirokazu Takahashi wrote:
> > Why don't you implement CKRM memory controller as virtual NUMA
> > node.
> >
> > I think what you want do is almost what NUMA code does, which
> > restricts resources to use. If you define virtual NUMA node with
> > some memory and some virtual CPUs, you can just assign target jobs
> > to them.
> >
> > What do you think of my idea?
>
> First of all, NUMA nodes don't have any balancing done on them, so I
> don't think they're an appropriate structure. But, NUMA nodes *do*
> contain zones, which are a slightly more appropriate structure.
>
> One thing I pointed out when he first posted this code was that a lot of
> the accounting gets shifted from the 'struct zone' to the ckrm class.
> It was appropriate to have a set of macros to set up and perform this
> indirection.
>
> However, a 'struct zone' currently has more than one job. It collects
> "like" pages together, it provides accounting for those pages, and it
> represents a contiguous area of memory.
>
> If you could collect just the accounting pieces out of 'struct zone',
> perhaps those could be used by both ckrm classes, and the old 'struct
> zone'.
will look into it.
Thanks
>
> -- 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-31 19:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 0:30 [PATCH 0/6] CKRM: Memory controller for CKRM Chandra Seetharaman
2005-05-19 1:43 ` Hirokazu Takahashi
2005-05-19 16:33 ` Chandra Seetharaman
2005-05-20 5:29 ` Hirokazu Takahashi
2005-05-21 0:07 ` Chandra Seetharaman
2005-05-23 11:31 ` Hirokazu Takahashi
2005-05-23 12:54 ` Hirokazu Takahashi
2005-05-20 9:26 ` Hirokazu Takahashi
2005-05-21 0:11 ` Chandra Seetharaman
2005-05-23 13:20 ` Hirokazu Takahashi
2005-05-27 13:16 ` Virtual NUMA machine and CKRM Hirokazu Takahashi
2005-05-27 14:09 ` Martin J. Bligh
2005-05-28 7:40 ` Hirokazu Takahashi
2005-05-27 14:15 ` [ckrm-tech] " Dave Hansen
2005-05-31 19:13 ` Chandra Seetharaman [this message]
2005-05-31 19:10 ` Chandra Seetharaman
2005-06-01 5:28 ` [ckrm-tech] " 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=20050531191303.GE29202@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 \
--cc=taka@valinux.co.jp \
/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