Messages in this thread | | | Subject | Re: [ckrm-tech] [RFC] [PATCH 00/12] CKRM after a major overhaul | From | Chandra Seetharaman <> | Date | Mon, 24 Apr 2006 18:42:46 -0700 |
| |
On Mon, 2006-04-24 at 14:18 +0900, Hirokazu Takahashi wrote: > Hi Chandra, <snip> > > Yes, it is effective, and the reclamation is O(1) too. It has couple of > > problems by design, (1) doesn't handle shared pages and (2) doesn't > > provide support for both min_shares and max_shares. > > I'm not sure all of them have to be managed under ckrm_core and rcfs > in kernel. > > These functions you mentioned can be implemented in user space > to minimize the overhead in usual VM operations because it isn't > expected quick response to resize it. It is a bit different from > that of CPU resource.
Agree, that is where the additional complexity arise from.
If the user can achieve the same results with user space solution that would be good too.
Thanks
chandra
> You don't need to invent everything. I think you can reuse what > NUMA team is doing instead. This approach may not fit in your rcfs, > though. > > > > This requirement is basically a glorified RLIMIT_RSS manager, isn't it? > > > Just that it covers a group of mm's and not just the one mm? > > > > Yes, that is the core object of ckrm, associate resources to a group of > > tasks. > > Thanks, > Hirokazu Takahahsi. --
---------------------------------------------------------------------- Chandra Seetharaman | Be careful what you choose.... - sekharan@us.ibm.com | .......you may get it. ----------------------------------------------------------------------
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |