xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.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>,
	axboe@fb.com, "David Vrabel" <david.vrabel@citrix.com>,
	"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: PAGE_SIZE (64KB), while block driver 'struct request' deals with < PAGE_SIZE (up to 44Kb). Was:Re: [RFC] Support of non-indirect grant backend on 64KB guest
Date: Fri, 4 Sep 2015 23:05:28 +0100	[thread overview]
Message-ID: <55EA15A8.3060805@citrix.com> (raw)
In-Reply-To: <20150904173211.GC2042@l.oracle.com>

Hi Konrad,

On 04/09/2015 18:32, Konrad Rzeszutek Wilk wrote:
> On Fri, Sep 04, 2015 at 05:15:13PM +0100, Julien Grall wrote:
>> On 04/09/15 16:41, Konrad Rzeszutek Wilk wrote:
>>>> Maybe we could fall back to the previous plan of modifying xen-blkfront
>>>> for the moment?
>>>
>>> Which afaic need to be reposted?
>>
>> Right. Although I didn't see any comment on the patch. All the comments
>> was about the problem. Does it mean that you and Roger are "happy" with
>> the way it's done?
>
> There were some #idef I think? And I recall seeing the segment limit being
> advertised as PAGE_SIZE / 2?

There is no ifdef but a PAGE_SIZE / 2. I know about the latter and plan 
to replace it. It was only to have a quick patch to expose my problem.

> I dug in the other block drivers to figure out what they
> do when the underlaying storage cannot handle < PAGE_SIZE data.
> And I couldn't find them. Which means this should be really dealt
> on the drivers side (xen-blkfront) as an quirk.
>
> Anyhow what I am going to do is - once it is reposted, force the
> driver under x86 to work under this condition. That is disable
> persistent support and only use 2048 .. and then drive some IO.
> If all goes well I will send it in a git pull to Jens.

It will also depends on 64KB series which I plan to repost next week. I 
will send as follow-up.

To test it properly on x86 it will be necessary to drop on BUG_ON in the 
code which ensure that the extra req is never use for 4KB
(see BUG_ON((XEN_PAGE_SIZE == PAGE_SIZE) && require_extra_req)).

Regards,

-- 
Julien Grall

  reply	other threads:[~2015-09-04 22:05 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 [this message]
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

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=55EA15A8.3060805@citrix.com \
    --to=julien.grall@citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=axboe@fb.com \
    --cc=david.vrabel@citrix.com \
    --cc=konrad.wilk@oracle.com \
    --cc=roger.pau@citrix.com \
    --cc=stefano.stabellini@eu.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).