From: Rob Gardner <rob.gardner@hp.com>
To: Andi Kleen <ak@suse.de>
Cc: xen-devel@lists.xensource.com, John L Griffin <jlg@us.ibm.com>
Subject: Re: Re: Fine-grained proxy resource charging
Date: Mon, 22 Aug 2005 09:08:51 -0600 [thread overview]
Message-ID: <4309EA83.1050001@hp.com> (raw)
In-Reply-To: <p73br3qm7o4.fsf@verdi.suse.de>
Andi Kleen wrote:
> John L Griffin <jlg@us.ibm.com> writes:
>
> > I am looking into how to charge a domain (say, domain "A") for the
> > resources consumed by other service domains (say, B) on behalf of
> > A. For example, charging A for the CPU cycles consumed by the
> > network I/O domain (B) as it processes packets produced or consumed
> > by A.
>
>
> Consider a xenblk request from different domains that gets merged
> into a single request by the elevator. Would you charge the time the
> driver spends processing that one to the one domain or the other? Or
> a xenblk write the is done in the background by the pdflushd daemons?
> There are lots of other cases where IO from different processes gets
> "mixed" like this. And in case of Xen you would even need to track IO
> from the same process.
>
> Not even standard linux attempts finegrained IO resource tracking and
> it would be probably quite complicated and require changes all over
> in the host kernel. I don't think it's a particularly good idea.
It's not a bad idea just because it's a hard problem.
As demonstrated in the Usenix paper that John refers to
(http://www.usenix.org/publications/library/proceedings/usenix05/tech/general/cherkasova.html),
the overhead in a driver domain can be very high under certain
circumstances. If you have "customers" sharing domains in a virtual
environment, you have to have some way of charging them fairly for
resource usage. I think the Xen I/O architecture needs to account for
this somehow.
Rob
next prev parent reply other threads:[~2005-08-22 15:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-22 5:25 Fine-grained proxy resource charging John L Griffin
2005-08-22 13:18 ` Andi Kleen
2005-08-22 15:08 ` Rob Gardner [this message]
2005-08-22 15:15 ` Andi Kleen
2005-08-22 15:28 ` Rob Gardner
2005-08-22 15:25 ` John L Griffin
2005-08-22 15:39 ` Andi Kleen
[not found] <200508231916.MAA09719@viola.hpl.hp.com>
2005-08-23 20:36 ` John L Griffin
-- strict thread matches above, loose matches on Subject: below --
2005-08-24 16:35 Lucy Cherkasova
2005-08-24 17:13 ` Mark Williamson
2005-08-25 4:56 ` John L Griffin
2005-08-24 17:34 Lucy Cherkasova
2005-08-24 17:34 ` Mark Williamson
2005-08-25 22:02 Lucy Cherkasova
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=4309EA83.1050001@hp.com \
--to=rob.gardner@hp.com \
--cc=ak@suse.de \
--cc=jlg@us.ibm.com \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.