From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: Valdis.Kletnieks@vt.edu
Cc: Andrea Righi <righiandr@users.sourceforge.net>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC][PATCH] per-uid/gid I/O throttling (was Re: [RFC][PATCH] per-task I/O throttling)
Date: Wed, 16 Jan 2008 17:35:33 +0530 [thread overview]
Message-ID: <20080116120533.GB7166@balbir.in.ibm.com> (raw)
In-Reply-To: <13594.1200483031@turing-police.cc.vt.edu>
* Valdis.Kletnieks@vt.edu <Valdis.Kletnieks@vt.edu> [2008-01-16 06:30:31]:
> On Wed, 16 Jan 2008 16:15:41 +0530, Balbir Singh said:
>
> > Thanks for doing this. I am going to review the patches in greater
> > detail and also test them. Why do you use configfs when we have a
> > control group filesystem available for grouping tasks and providing a
> > file system based interface for control and accounting?
>
> And here I thought "There's more than one way to do it" was the Perl slogan. :)
>
Yes, there are several ways to do it, but the discussion over the last
year or so has been centered around control groups. We've discussed
all approaches on lkml on there was consensus on using control groups.
Please read the lkml archives for the discussion details.
> An equally valid question would be: "Why are we carrying around a control
> group filesystem when we have configfs?" (Honestly, I didn't know we *were*
> carrying around such a filesystem - and quite likely Andrea Righi didn't
> either...)
Control groups is derived from cpusets and for those interested in
grouping tasks for control, is the preferred method of providing
control.
--
Warm Regards,
Balbir Singh
Linux Technology Center
IBM, ISTL
next prev parent reply other threads:[~2008-01-16 12:06 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-10 22:45 [RFC][PATCH] per-task I/O throttling Andrea Righi
2008-01-11 1:50 ` Bill Davidsen
2008-01-11 10:28 ` Andrea Righi
2008-01-11 14:20 ` Peter Zijlstra
2008-01-11 15:29 ` Andrea Righi
2008-01-11 14:05 ` David Newall
2008-01-11 15:44 ` Andrea Righi
2008-01-16 19:21 ` David Newall
2008-01-11 15:59 ` Balbir Singh
2008-01-11 16:32 ` Andrea Righi
2008-01-12 4:57 ` Valdis.Kletnieks
2008-01-12 9:46 ` Peter Zijlstra
2008-01-12 10:57 ` Balbir Singh
2008-01-12 11:10 ` Peter Zijlstra
2008-01-12 18:01 ` Andrea Righi
2008-01-13 4:46 ` Balbir Singh
2008-01-15 16:49 ` [RFC][PATCH] per-uid/gid I/O throttling (was Re: [RFC][PATCH] per-task I/O throttling) Andrea Righi
2008-01-11 17:58 ` Pavel Machek
2008-01-23 15:41 ` Andrea Righi
2008-01-16 10:45 ` Balbir Singh
2008-01-16 11:30 ` Valdis.Kletnieks
2008-01-16 12:05 ` Balbir Singh [this message]
2008-01-16 12:24 ` Valdis.Kletnieks
2008-01-16 12:58 ` Andrea Righi
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=20080116120533.GB7166@balbir.in.ibm.com \
--to=balbir@linux.vnet.ibm.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=righiandr@users.sourceforge.net \
/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
all inboxes | Powered by JetHome®