All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Benjamin S." <sbenni@gmx.de>
Subject: Re: [git patch] atang tree: fix 2.6.32 SSD performance regression
Date: Tue, 23 Feb 2010 13:17:01 +0100	[thread overview]
Message-ID: <201002231317.01128.bzolnier@gmail.com> (raw)
In-Reply-To: <20100223062324.GI1025@kernel.dk>

On Tuesday 23 February 2010 07:23:24 am Jens Axboe wrote:
> On Mon, Feb 22 2010, Bartlomiej Zolnierkiewicz wrote:
> > DISCLAIMER: the fact of getting patches merged into atang tree means
> > that from now on they will be getting updates for changes happening
> > in atang tree and it should not be treated as an indication regarding
> > decisions taken by 'upstream' kernel trees
> > 
> > 
> > Fix 2.6.32 regression bringing back the desired SSD performance.
> > 
> > [ 'upstream' may want to wait for a proper resolution, for atang tree
> >   performance of big non-ATA boxes owned by a very few people is not
> >   of such a big concern as a major regression on a commodity hardware ]
> 
> What is the point of this, other than continuing your past history of
> political tirades?

I worry that you may be reading too much into it -- I don't use Linus'
tree or linux-next tree any longer so the next kernel I would see fix
for the issue is most likely 2.6.34 and there is a little point from my
personal perspective in waiting for such long time..

--
Bartlomiej Zolnierkiewicz

  reply	other threads:[~2010-02-23 12:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-22 21:24 [git patch] atang tree: fix 2.6.32 SSD performance regression Bartlomiej Zolnierkiewicz
2010-02-23  6:23 ` Jens Axboe
2010-02-23 12:17   ` Bartlomiej Zolnierkiewicz [this message]
2010-02-23 12:23     ` Jens Axboe
2010-02-23 12:36       ` Bartlomiej Zolnierkiewicz

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=201002231317.01128.bzolnier@gmail.com \
    --to=bzolnier@gmail.com \
    --cc=jens.axboe@oracle.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sbenni@gmx.de \
    /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.