On Sun, 18 Jun 2006 16:11:18 +1000
Nick Piggin <[email protected]> wrote:
> If you want to *completely* isolate N groups of users, surely you
> have to use virtualisation,
I'd view this as a kludge. If one group of tasks is trashing the
performance of another group of tasks the user is forced to use hardware
virtualisation to work around it.
I mean, is this our answer to the updatedb problem? Instantiate a separate
copy of the kernel just to run updatedb?
> unless you are willing to isolate memory
> management, pagecache, slab caches, network and disk IO, etc.
Well yes. Ideally and ultimately. People have done this, and it's in
production. We need to see (and work upon) the patches before we can judge
whether we want to do this, and how far we want to go.
> Again, I don't care about the solutions at this stage. I want to know
> what the problem is. Please?
Isolation. To prevent one group of processes from damaging the performance
of other groups, by providing manageability of the resource consumption of
each group. There are plenty of applications of this, not just
server-consolidation-via-server-virtualisation.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
