stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Jiri Slaby <jslaby@suse.cz>,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org,
	xen-devel@lists.xenproject.org, felipe.franciosi@citrix.com,
	roger.pau@citrix.com, jerry.snitselaar@oracle.com,
	axboe@kernel.dk, vkuznets@redhat.com
Subject: Re: Backport request to stable of two performance related fixes for xen-blkfront (3.13 fixes to earlier trees)
Date: Fri, 6 Jun 2014 10:02:08 -0400	[thread overview]
Message-ID: <20140606140207.GA9426@localhost.localdomain> (raw)
In-Reply-To: <20140606135657.GB11781@kroah.com>

On Fri, Jun 06, 2014 at 06:56:57AM -0700, Greg KH wrote:
> On Fri, Jun 06, 2014 at 12:47:07PM +0200, Jiri Slaby wrote:
> > On 06/04/2014 07:48 AM, Greg KH wrote:
> > > On Wed, May 14, 2014 at 03:11:22PM -0400, Konrad Rzeszutek Wilk wrote:
> > >> Hey Greg
> > >>
> > >> This email is in regards to backporting two patches to stable that
> > >> fall under the 'performance' rule:
> > >>
> > >>  bfe11d6de1c416cea4f3f0f35f864162063ce3fa
> > >>  fbe363c476afe8ec992d3baf682670a4bd1b6ce6
> > > 
> > > Now queued up, thanks.
> > 
> > AFAIU, they introduce a performance regression.
> 
> That "regression" is also in mainline, right?  As Konrad doesn't seem to
> think it matters, I'm deferring to the maintainer here.

Hehe.

Greg is correct - the performance regression with tmpfs/ramfs does exist
upstream and once a fix has been established will be dealt with. Right now we
are fousing on the 99% usage models which is solid state, rotational,
and flash (just got one of those) and the two patches outlined above are
needed for the stable trees.

Thank you.

Hopefully I haven't confused the issue here.
> 
> thanks,
> 
> greg k-h

  reply	other threads:[~2014-06-06 14:02 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
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 [this message]
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=20140606140207.GA9426@localhost.localdomain \
    --to=konrad.wilk@oracle.com \
    --cc=axboe@kernel.dk \
    --cc=felipe.franciosi@citrix.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jerry.snitselaar@oracle.com \
    --cc=jslaby@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roger.pau@citrix.com \
    --cc=stable@vger.kernel.org \
    --cc=vkuznets@redhat.com \
    --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;
as well as URLs for NNTP newsgroup(s).