From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Olaf Hering <olaf@aepfle.de>
Cc: Ian Campbell <Ian.Campbell@citrix.com>,
Li Dongyang <lidongyang@novell.com>,
xen-devel@lists.xen.org
Subject: Re: qdisk vs. file as vbd type
Date: Fri, 10 Jan 2014 10:15:51 -0500 [thread overview]
Message-ID: <20140110151551.GB20152@phenom.dumpdata.com> (raw)
In-Reply-To: <20140110150000.GA20287@aepfle.de>
On Fri, Jan 10, 2014 at 04:00:00PM +0100, Olaf Hering wrote:
> On Fri, Jan 10, Ian Campbell wrote:
>
> > On Fri, 2014-01-10 at 15:40 +0100, Olaf Hering wrote:
> > > What is the reason the backend 'type' property of a configured disk is
> > > now "qdisk" instead of "file"?
> >
> > Because qdisk is the backend instead of loop+blk (==file) I think this
> > just happens naturally.
> >
> > > Would the guest really care about that
> > > detail? For example block-front currently just checks for "phy" and
> > > "file" when deciding if discard should be enabled.
> >
> > That sounds entirely bogus, it should be checking for some sort of
> > feature-discard.
>
> It does that, then calls blkfront_setup_discard which in turn knows just
> about phy and file. And I wonder why it does that.
> Maybe this function should be simplified to assume that if its called
> feature_discard can be enabled. And if both
> discard-granularity/discard-alignment exist those properties should be
> assigned, similar for discard-secure.
>
> Now that I look at the history of blkfront_setup_discard:
>
> Li, Konrad, why does that function care at all about the 'type'?
> Shouldnt that check be removed?
You are looking at:
ed30bf317 (Li Dongyang 2011-09-01 18:39:09 +0800 1664) } else if (strncmp(type, "file", 4) == 0)
ed30bf317 (Li Dongyang 2011-09-01 18:39:09 +0800 1665) info->feature_discard = 1;
ed30bf317 (Li Dongyang 2011-09-01 18:39:09 +0800 1666)
ed30bf317 (Li Dongyang 2011-09-01 18:39:09 +0800 1667) kfree(type);
ed30bf317 (Li Dongyang 2011-09-01 18:39:09 +0800 1668)}
ed30bf317 (Li Dongyang 2011-09-01 18:39:09 +0800 1669)
My recollection is that at the time the patches were developed, loop
was not able to do discard operations. That has since changed and
loop can do it. Hence the force of =1 was added in.
But that assumes that 'file' is going through the 'loop' device.
If that assumption is incorrect then this needs to be fixed and
perhaps the underlaying device ('file'?) interogated as to whether
it can do discard or not.
>
> Olaf
next prev parent reply other threads:[~2014-01-10 15:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-10 14:40 qdisk vs. file as vbd type Olaf Hering
2014-01-10 14:47 ` Ian Campbell
2014-01-10 15:00 ` Olaf Hering
2014-01-10 15:15 ` Konrad Rzeszutek Wilk [this message]
2014-01-10 15:19 ` Olaf Hering
2014-01-10 15:29 ` Konrad Rzeszutek Wilk
2014-01-10 15:20 ` Ian Campbell
2014-01-10 15:32 ` Konrad Rzeszutek Wilk
2014-01-10 15:09 ` Roger Pau Monné
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=20140110151551.GB20152@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Campbell@citrix.com \
--cc=lidongyang@novell.com \
--cc=olaf@aepfle.de \
--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.