All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benoit Depail <benoit.depail@nbs-system.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: Keith Busch <keith.busch@intel.com>,
	<linux-block@vger.kernel.org>, <xen-users@lists.xen.org>,
	WebDawg <webdawg@gmail.com>
Subject: Re: [Xen-users] File-based domU - Slow storage write since xen 4.8
Date: Wed, 2 Aug 2017 18:29:48 +0200	[thread overview]
Message-ID: <46b4bdb3-25c4-076e-3401-0506688e2d83@nbs-system.com> (raw)
In-Reply-To: <20170801094831.cr2brqudqubcinxt@dhcp-3-128.uk.xensource.com>

On 08/01/2017 11:48 AM, Roger Pau Monné wrote:
> On Fri, Jul 28, 2017 at 04:50:27PM +0200, Benoit Depail wrote:
>> On 07/26/17 00:25, Keith Busch wrote:
>>> On Fri, Jul 21, 2017 at 07:07:06PM +0200, Benoit Depail wrote:
>>>> On 07/21/17 18:07, Roger Pau Monné wrote:
>>>>>
>>>>> Hm, I'm not sure I follow either. AFAIK this problem came from
>>>>> changing the Linux version in the Dom0 (where the backend, blkback is
>>>>> running), rather than in the DomU right?
>>>>>
>>>>> Regarding the queue/sectors stuff, blkfront uses several blk_queue
>>>>> functions to set those parameters, maybe there's something wrong
>>>>> there, but I cannot really spot what it is:
>>>>>
>>>>> http://elixir.free-electrons.com/linux/latest/source/drivers/block/xen-blkfront.c#L929
>>>>>
>>>>> In the past the number of pages that could fit in a single ring
>>>>> request was limited to 11, but some time ago indirect descriptors
>>>>> where introduced in order to lift this limit, and now requests can
>>>>> have a much bigger number of pages.
>>>>>
>>>>> Could you check the max_sectors_kb of the underlying storage you are
>>>>> using in Dom0?
>>>>>
>>>>> Roger.
>>>>>
>>>> I checked the value for the loop device as well
>>>>
>>>> With 4.4.77 (bad write performance)
>>>> $ cat /sys/block/sda/queue/max_sectors_kb
>>>> 1280
>>>> $ cat /sys/block/loop1/queue/max_sectors_kb
>>>> 127
>>>>
>>>>
>>>> With 4.1.42 (normal write performance)
>>>> $ cat /sys/block/sda/queue/max_sectors_kb
>>>> 4096
>>>> $ cat /sys/block/loop1/queue/max_sectors_kb
>>>> 127
>>>
>>> Thank you for the confirmations so far. Could you confirm performance dom0
>>> running 4.4.77 with domU running 4.1.42, and the other way around? Would
>>> like to verify if this is just isolated to blkfront.
>>>
>> Hi,
>>
>> I've ran the tests, and I can tell that the domU kernel version have no
>> influence on the performance.
>>
>> Dom0 with 4.4.77 always shows bad performance, wether the domU runs
>> 4.1.42 or 4.4.77.
>>
>> Dom0 with 4.1.42 always shows good performance, wether the domU runs
>> 4.1.42 or 4.4.77.
> 
> Hello,
> 
> I haven't yet got time to look into this sadly. Can you please try to
> use fio [0] in order to run the tests against the loop device in Dom0?
> 
> If possible, could you test several combinations of block sizes, I/O
> sizes and I/O depths?
> 
> Thanks, Roger.
> 
> [0] http://git.kernel.dk/?p=fio.git;a=summary
> 

Ok I'll give a try later when I have more time. Probably next week.

Thanks,

-- 
Benoit Depail
Senior Infrastructures Architect
NBS System

  reply	other threads:[~2017-08-02 16:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5554bd39-6e0a-5c17-2b64-bb80d4a6502b@nbs-system.com>
     [not found] ` <CAKdd5H9f_=NCYMmhLcvHKFw7m_sKvygSVqz3+Z0YPAGiPMxKxQ@mail.gmail.com>
     [not found]   ` <5b562ef2-36e2-a08e-1683-6ffc7cfa54de@nbs-system.com>
     [not found]     ` <20170717124931.rsiqxkzzkmvfofd7@MacBook-Pro-de-Roger.local>
     [not found]       ` <5dd18982-cbcf-a675-1e07-5b4c4e4da50e@nbs-system.com>
     [not found]         ` <20170717164658.drliebetcnil3wjb@dhcp-3-128.uk.xensource.com>
     [not found]           ` <bba4e389-b975-fbb8-b680-c9c4039617ca@nbs-system.com>
2017-07-20  8:52             ` [Xen-users] File-based domU - Slow storage write since xen 4.8 Roger Pau Monné
2017-07-20 15:12               ` Benoit Depail
2017-07-20 15:33                 ` Keith Busch
2017-07-20 15:57                   ` Benoit Depail
2017-07-20 17:36                 ` Keith Busch
2017-07-21 10:19                   ` Benoit Depail
2017-07-21 15:53                     ` Keith Busch
2017-07-21 16:07                       ` Roger Pau Monné
2017-07-21 17:07                         ` Benoit Depail
2017-07-25 22:25                           ` Keith Busch
2017-07-28 14:50                             ` Benoit Depail
2017-08-01  9:48                               ` Roger Pau Monné
2017-08-02 16:29                                 ` Benoit Depail [this message]
2017-08-23 15:54                                   ` Benoit Depail

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=46b4bdb3-25c4-076e-3401-0506688e2d83@nbs-system.com \
    --to=benoit.depail@nbs-system.com \
    --cc=keith.busch@intel.com \
    --cc=linux-block@vger.kernel.org \
    --cc=roger.pau@citrix.com \
    --cc=webdawg@gmail.com \
    --cc=xen-users@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.