public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	axboe@kernel.dk, felipe.franciosi@citrix.com,
	gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org, jerry.snitselaar@oracle.com,
	xen-devel@lists.xenproject.org
Subject: Re: [Xen-devel] Backport request to stable of two performance related fixes for xen-blkfront (3.13 fixes to earlier trees)
Date: Tue, 20 May 2014 13:41:10 +0200	[thread overview]
Message-ID: <87lhtwznhl.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <537B2F2C.4080905@citrix.com> ("Roger Pau \=\?utf-8\?Q\?Monn\?\= \=\?utf-8\?Q\?\=C3\=A9\=22's\?\= message of "Tue, 20 May 2014 12:32:12 +0200")

Roger Pau Monné <roger.pau@citrix.com> writes:

> On 20/05/14 11:54, Vitaly Kuznetsov wrote:
>> Vitaly Kuznetsov <vkuznets@redhat.com> writes:
>> 
>>> 1) ramdisks (/dev/ram*) (persistent grants and indirect descriptors
>>> disabled)
>> 
>> sorry, there was a typo. persistent grants and indirect descriptors are
>> enabled with ramdisks, otherwise such testing won't make any sense.
>
> I'm not sure how is that possible, from your description I get that you
> are using 3.11 on the Dom0, which means blkback has support for
> persistent grants and indirect descriptors, but the guest is RHEL7,
> that's using the 3.10 kernel AFAICT, and this kernel only has persistent
> grants implemented.

RHEL7 kernel is mostly merged with 3.11 in its Xen part, we have
indirect descriptors backported.

Actually I tried my tests with upstream (Fedora) kernel and results were
similar. I can try comparing e.g. 3.11.10 with 3.12.0 and provide exact
measurements.

-- 
  Vitaly

  reply	other threads:[~2014-05-20 11:41 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-14 19:11 Backport request to stable of two performance related fixes for xen-blkfront (3.13 fixes to earlier trees) Konrad Rzeszutek Wilk
2014-05-14 19:21 ` Josh Boyer
2014-05-20  3:19 ` Greg KH
2014-05-22 12:54   ` Roger Pau Monné
2014-05-20  9:32 ` [Xen-devel] " Vitaly Kuznetsov
2014-05-20  9:54   ` Vitaly Kuznetsov
2014-05-20 10:32     ` Roger Pau Monné
2014-05-20 11:41       ` Vitaly Kuznetsov [this message]
2014-05-20 13:59         ` Felipe Franciosi
2014-05-22  8:52           ` Vitaly Kuznetsov
2014-06-04  5:48 ` Greg KH
2014-06-06 10:47   ` Jiri Slaby
2014-06-06 10:58     ` Vitaly Kuznetsov
2014-06-10 13:19       ` [Xen-devel] " Vitaly Kuznetsov
2014-06-10 16:55         ` Roger Pau Monné
2014-06-12 12:00           ` Vitaly Kuznetsov
2014-06-12 12:32             ` Felipe Franciosi
2014-06-12 15:32               ` Vitaly Kuznetsov
2014-06-20 17:06                 ` Felipe Franciosi
2014-06-10 17:26         ` Felipe Franciosi
2014-06-06 13:56     ` Greg KH
2014-06-06 14:02       ` Konrad Rzeszutek Wilk
2014-06-06 14:03         ` Jiri Slaby

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=87lhtwznhl.fsf@vitty.brq.redhat.com \
    --to=vkuznets@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=felipe.franciosi@citrix.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jerry.snitselaar@oracle.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roger.pau@citrix.com \
    --cc=stable@vger.kernel.org \
    --cc=xen-devel@lists.xenproject.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