From: YAMAMOTO Takashi <yamamoto@valinux.co.jp>
To: taka@valinux.co.jp
Cc: ckrm-tech@lists.sourceforge.net, linux-mm@kvack.org
Subject: Re: [ckrm-tech] Virtual NUMA machine and CKRM
Date: Wed, 01 Jun 2005 14:28:19 +0900 [thread overview]
Message-ID: <1117603699.326265.4138.nullmailer@yamt.dyndns.org> (raw)
In-Reply-To: Your message of "Fri, 27 May 2005 22:16:13 +0900 (JST)" <20050527.221613.78716667.taka@valinux.co.jp>
hi,
> Why don't you implement CKRM memory controller as virtual NUMA
> node.
i think that you need to describe what's a "virtual NUMA node" before
soliciting comments.
> 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.
because resource restrictions from numa and ckrm are very different,
i don't think there is a single effective structure for both of them.
YAMAMOTO Takashi
--
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>
prev parent reply other threads:[~2005-06-01 5:28 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
2005-05-31 19:10 ` Chandra Seetharaman
2005-06-01 5:28 ` YAMAMOTO Takashi [this message]
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=1117603699.326265.4138.nullmailer@yamt.dyndns.org \
--to=yamamoto@valinux.co.jp \
--cc=ckrm-tech@lists.sourceforge.net \
--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