linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Robert Hancock <hancockr@shaw.ca>
Cc: Jens Axboe <jens.axboe@oracle.com>,
	linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/7] ide: locking improvements
Date: Sat, 11 Oct 2008 13:39:44 +0200	[thread overview]
Message-ID: <200810111339.44998.bzolnier@gmail.com> (raw)
In-Reply-To: <48F010AB.7010009@shaw.ca>

On Saturday 11 October 2008, Robert Hancock wrote:
> Bartlomiej Zolnierkiewicz wrote:
> >> Sorry, but I just have to ask 'why'? IDE is seeing a whole lot of churn
> >> for something that should essentially be a stable code base in
> >> maintenance mode, and now scalability improvements?
> > 
> > It is the stable code but being in "maintenance only mode" has never
> > been true and as long as there are active users & developers there is
> > really no reason to change it.
> 
> Are there really many active users at this point? I'm not aware of any 
> new distributions that are using it. The only people I can see that 
> might still want to be using it would be people with old setups or old 
> embedded devices.. many of those wouldn't be using newer kernels anyway.

Like I said before: as long as there are any active users/developers
there is no real reason to stop IDE improvements (especially since there
is no complete replacement available).

I also wouldn't worry that much about what some distros are doing.  They
are free to make their own decisions based on whatever criteria they like.

> These kinds of changes only will really help scalability on multi-core 
> machines which are unlikely to be using this code anyway.. They seem 

>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.

> rather like putting makeup on a corpse to me..

Please refrain from such comments.  Not only the metaphor is completely
bogus but it may sound disrespectful to some IDE developers.

Thanks,
Bart

  reply	other threads:[~2008-10-11 11:41 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 [this message]
2008-10-11 12:01         ` Borislav Petkov
2008-10-11 13:53           ` Jens Axboe
2008-10-11 14:45             ` Bartlomiej Zolnierkiewicz
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=200810111339.44998.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 \
    /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).