From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: petkovbb@gmail.com, Robert Hancock <hancockr@shaw.ca>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/7] ide: locking improvements
Date: Sat, 11 Oct 2008 16:45:27 +0200 [thread overview]
Message-ID: <200810111645.27847.bzolnier@gmail.com> (raw)
In-Reply-To: <20081011135300.GP19428@kernel.dk>
On Saturday 11 October 2008, Jens Axboe wrote:
> On Sat, Oct 11 2008, Borislav Petkov wrote:
> > > >From my perspective the main gain of these patches is the increased
> > > maintainability and sanity of the code, scalability improvements are
> > > just an added bonus.
> >
> > and better code/improved scalability is a bad thing because... ?!
>
> It's a bad thing because nobody on earth cares about IDE scalability,
JFYI: just yesterday I got mail proving otherwise. ;)
> from a performance POV a modern SATA controller is just better on
> several levels. I don't think anybody cares about IDE scaling on 8-16
> cores or more, simply because NOBODY is using IDE on such systems.
>
> As such, trying to improve locking is a pointless exercise. And that is
> a bad thing, because code change invariably brings in code bugs. Then
> see previous mail on lack of coverage testing, and it can naturally be
> harmful.
Your concerns were already addressed in my reply but I worry that having
a discussion based on technical arguments is not your goal.
Just to repeat: these patches are not hardware specific and obviously
they are not going to be merged today, tomorrow or in a week (they are
2.6.29 material after months of time in pata tree / linux-next).
> > > > rather like putting makeup on a corpse to me..
> >
> > so _NOT_ true.
>
> Depends on what you think is the corpse. Since IDE is essentially dead
> and frozen, it IS a corpse and the phrase is then very appropriate. This
> is not a personal jab at the IDE guys and does not reflect on the
> (mostly) good work they do, just a reflection on the state of IDE in
> general.
Interesting statement given that i.e. diffstat-wise pata tree has more
than twice as much stuff queued up for 2.6.28 than "some other" trees
(and we have history of being a _very_ conservative w.r.t. to needlessly
moving code around in drivers/ide/).
Please stop being silly and pushing your view/idea on what other people
should be doing (not to mention ignoring real facts).
Thanks,
Bart
next prev parent reply other threads:[~2008-10-11 14:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.Ke90oacfRjgiI4x5LejzjssRBEg@ifi.uio.no>
[not found] ` <fa.5sGSpBgVBoMAsIwwLABWnjDzM38@ifi.uio.no>
[not found] ` <fa.8TkQ+xA96EhlNKL9gIbVTxVrcUE@ifi.uio.no>
2008-10-11 2:34 ` [PATCH 0/7] ide: locking improvements Robert Hancock
2008-10-11 11:39 ` Bartlomiej Zolnierkiewicz
2008-10-11 12:01 ` Borislav Petkov
2008-10-11 13:53 ` Jens Axboe
2008-10-11 14:45 ` Bartlomiej Zolnierkiewicz [this message]
2008-10-11 15:05 ` Jens Axboe
2008-10-11 15:56 ` Bartlomiej Zolnierkiewicz
2008-10-11 17:06 ` Borislav Petkov
2008-10-11 17:56 ` Jens Axboe
2008-10-11 17:56 ` Jens Axboe
2008-10-11 18:34 ` Borislav Petkov
2008-10-11 18:46 ` Bartlomiej Zolnierkiewicz
2008-10-12 1:38 ` Robert Hancock
2008-10-12 9:05 ` Bartlomiej Zolnierkiewicz
2008-10-08 20:29 Bartlomiej Zolnierkiewicz
2008-10-09 6:51 ` Jens Axboe
2008-10-09 8:36 ` Bartlomiej Zolnierkiewicz
2008-10-09 8:40 ` Jens Axboe
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=200810111645.27847.bzolnier@gmail.com \
--to=bzolnier@gmail.com \
--cc=hancockr@shaw.ca \
--cc=jens.axboe@oracle.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=petkovbb@gmail.com \
/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).