Messages in this thread | | | Date | Tue, 12 Sep 2006 14:24:25 +0400 | From | Pavel Emelianov <> | Subject | Re: [ckrm-tech] [PATCH] BC: resource beancounters (v4) (added user memory) |
| |
Srivatsa Vaddagiri wrote: > On Mon, Sep 11, 2006 at 11:02:06AM +0400, Pavel Emelianov wrote: > >> Sure. At the beginning I have one task with one BC. Then >> 1. A thread is spawned and new BC is created; >> > > Why do we have to create a BC for every new thread? A new BC is needed > for every new service level instead IMO. And typically there wont be > unlimited service levels. > That's the scenario we started from - each domain is served in a separate BC with *threaded* Apache. > >> 2. New thread touches a new page (e.g. maps a new file) which is charged >> to new BC >> (and this means that this BC's must stay in memory till page is >> uncharged); >> 3. Thread exits after serving the request, but since it's mm is shared >> with parent >> all the touched pages stay resident and, thus, the new BC is still >> pinned in memory. >> Steps 1-3 are done multiple times for new pages (new files). >> Remember that we're discussing the case when pages are not recharged. >> > > >
- 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/
| |