From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Julien Grall <julien.grall@citrix.com>
Cc: "Ian Campbell" <Ian.Campbell@citrix.com>,
"Stefano Stabellini" <Stefano.Stabellini@eu.citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
"David Vrabel" <david.vrabel@citrix.com>,
"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: [RFC] Support of non-indirect grant backend on 64KB guest
Date: Fri, 21 Aug 2015 12:07:52 -0400 [thread overview]
Message-ID: <20150821160752.GF26663@l.oracle.com> (raw)
In-Reply-To: <55D67F29.4050107@citrix.com>
On Thu, Aug 20, 2015 at 06:30:17PM -0700, Julien Grall wrote:
>
>
> On 20/08/2015 10:42, David Vrabel wrote:
> >>When using 64KB page, a Linux block request (struct *request) may
> >>contain up to 64KB of data. This is because the block segment size
> >>must at least be the size of a Linux page.
> >
> >You should ensure you configure the request queue with the limits that
> >are currently supported. In particular:
> >
> > /* Each segment in a request is up to an aligned page in
> > size. */
> > blk_queue_segment_boundary(rq, PAGE_SIZE - 1);
> > blk_queue_max_segment_size(rq, PAGE_SIZE);
> >
> >Is obviously wrong with PAGE_SIZE > 44 KiB.
> >
> >Get the block later to split requests and don't do it in blkfront.
>
> I may not have been enough clear in the paragraph you quoted. I said that
> the minimum size supported by the block framework is a linux page size. It
> means that if you pass a value smaller than that it will replace with the
> page linux granularity.
>
> It would have been handy that the block framework supports smaller size but
> it's not the case, give a look to the implementation of both function.
>From a block API size one can argue that the driver is doing something
wrong by requiring < PAGE_SIZE requests. It is kind of implied that all
the drivers are able to manage this and break up an 'struct request'
in multiple IO commands if it needs to.
>
> Cheers,
>
> --
> Julien Grall
prev parent reply other threads:[~2015-08-21 16:07 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-18 6:29 [RFC] Support of non-indirect grant backend on 64KB guest Julien Grall
2015-08-18 7:09 ` Roger Pau Monné
2015-08-18 7:26 ` Jan Beulich
2015-08-18 18:45 ` Julien Grall
2015-08-19 8:50 ` Roger Pau Monné
2015-08-19 14:54 ` Julien Grall
2015-08-19 15:17 ` Roger Pau Monné
2015-08-19 15:52 ` Julien Grall
2015-08-19 23:44 ` Stefano Stabellini
2015-08-20 8:31 ` Roger Pau Monné
2015-08-20 9:43 ` David Vrabel
2015-08-20 16:16 ` Julien Grall
2015-08-20 17:23 ` Stefano Stabellini
2015-08-21 16:05 ` Konrad Rzeszutek Wilk
2015-08-21 16:08 ` David Vrabel
2015-08-21 16:49 ` Stefano Stabellini
2015-08-21 17:10 ` PAGE_SIZE (64KB), while block driver 'struct request' deals with < PAGE_SIZE (up to 44Kb). Was:Re: " Konrad Rzeszutek Wilk
2015-08-27 17:51 ` Julien Grall
2015-09-04 14:04 ` Stefano Stabellini
2015-09-04 15:41 ` Konrad Rzeszutek Wilk
2015-09-04 16:15 ` Julien Grall
2015-09-04 17:32 ` Konrad Rzeszutek Wilk
2015-09-04 22:05 ` Julien Grall
2015-08-20 9:37 ` Jan Beulich
2015-08-19 8:58 ` Jan Beulich
2015-08-19 15:25 ` Julien Grall
2015-08-20 17:42 ` David Vrabel
2015-08-21 1:30 ` Julien Grall
2015-08-21 16:07 ` Konrad Rzeszutek Wilk [this message]
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=20150821160752.GF26663@l.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Campbell@citrix.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=david.vrabel@citrix.com \
--cc=julien.grall@citrix.com \
--cc=roger.pau@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 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).