From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Wei Liu <wei.liu2@citrix.com>, Jan Beulich <JBeulich@suse.com>,
xen-devel <xen-devel@lists.xen.org>
Subject: Re: blkback global resources
Date: Mon, 26 Mar 2012 12:56:44 -0400 [thread overview]
Message-ID: <20120326165644.GA12494@phenom.dumpdata.com> (raw)
In-Reply-To: <1332778808.26550.23.camel@zakaz.uk.xensource.com>
On Mon, Mar 26, 2012 at 05:20:08PM +0100, Ian Campbell wrote:
> On Mon, 2012-03-26 at 16:56 +0100, Jan Beulich wrote:
> > All the resources allocated based on xen_blkif_reqs are global in
> > blkback. While (without having measured anything) I think that this
> > is bad from a QoS perspective (not the least implied from a warning
> > issued by Citrix'es multi-page-ring patches:
> >
> > if (blkif_reqs < BLK_RING_SIZE(order))
> > printk(KERN_WARNING "WARNING: "
> > "I/O request space (%d reqs) < ring order %ld, "
> > "consider increasing %s.reqs to >= %ld.",
> > blkif_reqs, order, KBUILD_MODNAME,
> > roundup_pow_of_two(BLK_RING_SIZE(order)));
> >
> > indicating that this _is_ a bottleneck), I'm otoh hesitant to convert
> > this to per-instance allocations, as the amount of memory taken
> > away from Dom0 for this may be not insignificant when there are
> > many devices.
> >
> > Does anyone have an opinion here, in particular regarding the
> > original authors' decision to make this global vs. the apparently
> > made observation (by Daniel Stodden, the author of said patch,
> > who I don't have any current email of to ask directly), but also
> > in the context of multi-page rings, the purpose of which is to
> > allow for larger amounts of in-flight I/O?
>
> Not really much to say other than we (well, mostly Wei Liu) have a
> similar issue with netback too. That used to have a global pool, then a
> pool-per-worker thread. When Wei added thread-per-vif support he solved
> this by adding a "page pool" which handles allocations. Possibly this
> could grow some sort of fairness etc nobs and be shared with blkback?
Yes! That is what I was hoping for - as it would hopefully also have
the shrinker API hooked up to combat excessive memory consumption.
>
> Ian.
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2012-03-26 16:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-26 15:56 blkback global resources Jan Beulich
2012-03-26 16:20 ` Ian Campbell
2012-03-26 16:56 ` Konrad Rzeszutek Wilk [this message]
2012-03-26 20:47 ` Matt Wilson
2012-03-27 8:45 ` Ian Campbell
2012-03-27 9:41 ` Wei Liu
2012-03-27 10:22 ` Jan Beulich
2012-03-27 12:34 ` Wei Liu
2012-03-27 12:45 ` Jan Beulich
2012-03-27 13:01 ` Wei Liu
[not found] <CB965278.2F50F%keir.xen@gmail.com>
[not found] ` <1332780797.30244.159.camel@espiritosanto>
2012-03-27 7:27 ` Jan Beulich
2012-03-27 9:21 ` Wei Liu
2012-03-27 10:11 ` Jan Beulich
2012-04-02 9:56 ` Andrei Lifchits
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=20120326165644.GA12494@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.org \
/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.