From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: roger.pau@citrix.com, xen-devel@lists.xensource.com
Cc: james.harper@bendigoit.com.au, martin.petersen@oracle.com,
koverstreet@google.com, ronghui.duan@intel.com,
justing@spectralogic.com, JBeulich@suse.com,
joseph.glanville@orionvm.com.au
Subject: Xen-blkback bugs/features
Date: Tue, 13 Nov 2012 14:14:28 -0500 [thread overview]
Message-ID: <20121113191428.GA12691@localhost.localdomain> (raw)
Hey Roger,
Since you are taking a look at blkback and continuing the work
that Oliver did with persistent grants (and btw, thanks for doing
that!) I was wondering if you were also looking at some of the
"todos" that were circulating around.
One of them was the 4KB issue. If one hooks up bcache as backend
into blkback, the I/Os don't seem to go anywhere. Both James Harper
and .. I think the author of bcache were talking about this but
it never got anywhere.
The other one is expanding the segment limit. We have hard-coded
it to be 11 but with existing use-cases (say SSDs) that is not
enough. Intel had posted an RFC patchset that created a new ring
for segments. SpectraLogic (Justin) did it by expanding the ring.
Then there is the prototype work that Martin Peterson (really really
prototype) to get DIF/DIX plumbed in xen-blkback/xen-blkfront. He
needed 8 bytes per bio so he ended up creating a new ring to track that.
I think those are the outstanding use-cases that I know off.
So was wondering if you had thought/looked at some of this and
had ideas - and were thinking to do something in the future?
Thanks!
P.S.
I hope I have CC-ed everybody here.
reply other threads:[~2012-11-13 19:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20121113191428.GA12691@localhost.localdomain \
--to=konrad.wilk@oracle.com \
--cc=JBeulich@suse.com \
--cc=james.harper@bendigoit.com.au \
--cc=joseph.glanville@orionvm.com.au \
--cc=justing@spectralogic.com \
--cc=koverstreet@google.com \
--cc=martin.petersen@oracle.com \
--cc=roger.pau@citrix.com \
--cc=ronghui.duan@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).