lkml.org 
[lkml]   [2005]   [Oct]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: ioctls, etc. (was Re: [PATCH 1/4] sas: add flag for locally attachedPHYs)
David Lang wrote:
> On Sat, 22 Oct 2005, Stefan Richter wrote:
>> I doubt that the desired cleanup of the SCSI core could be done
>> on-the-go, i.e. without temporary breakage of larger parts of the
>> subsystem (out of mainline). But then again, I don't know much of the
>> subsystem, so what am I talking about here?
>>
>> Also, long-term breakage of smaller parts of the SCSI subsystem in
>> mainline is to be expected; breakage which is to be announced and
>> scheduled.
>
> Stefan, what you and Luben are missing is that big-bang changes like you
> are proposing are simply not acceptable anymore.

I agree with you that big-bang changes are not acceptable. This wasn't
however what I had in mind.

> a few years ago when the 2.5 kernel series opened a similar big-bang
> approach was attempted for the IDE drivers. the instability that
> resulted (and rumors of the instability being worse then it was)
> eliminated a lot of people from testing things. things finally got bad
> enough that the entire system was reverted, and then a developer (one
> who had previously stated that such drastic changes were impossible) sat
> down and produced a long series of patches, each of which did a small
> amount of changes, each of which left the kernel in a working state (and
> each of which provided an advantage that could be identified at the time
> of the patch, either a better abstraction or a code cleanup). over a
> very few months (especially relative to the time spent working on the
> big-bang patches) the entire system was re-written.

What I proposed was to "renovate" a _part_ of the SCSI subsystem (the
core and the interfaces of the rest of the subsystem to the core) with
the 2.6 kernel as a basis. This is a huge difference to 2.5. Changes
took place everywhere in 2.5, many of them drastic.

I agree with you that the incremental approach is preferrable whenever
possible. I even believe that this method could be applied to the SCSI
core cleanup. However, concerns were voiced that this method would
effectively lead to a double SCSI core: The old one, and a new one in
parallel to it which doesn't share much code with the old one. (At least
for some time, perhaps for a too long time.)

It has been said multiple times that this would not be desirable for
reasons of /a/ more kernel bloat (while the goal was to remove existing
bloat and lay foundations to avoid future bloat), and /b/ massive
maintenance burden of two parallel infrastructures.

So that's why I said that *short-term* breakage right on top and right
below the core should be accepted.

Again, the huge difference to the 2.5 times would be that all this would
happen on top of a relatively stable kernel. (Stable in two senses.)

> This is what Jeff is trying to tell you. you can't just produce an
> entirely new SCSI subsystem and drop it into the kernel one day, you can

What I was referring to was to clean up a _part_ of the subsystem (the
core), not to replace the subsystem. I admit though that my wording left
much room for misunderstanding.

Furthermore, note that the "scsi-cleanup tree" which I referred to is
not meant to be a fork. It should merely be another working stage before
the -mm stage. And let me add that this stage should be left as soon as
possible.

> all agree on a goal (this has almost been done, but nto quite), but
> that's only the first step. After you have some idea of the goal you
> then have to look at how to move to that goal without breaking things in
> the meantime. This requires that each step along the way keeps things
> working and is relativly straightforward in and of itself.
>
> this definantly sounds a LOT harder then the 'throw it out and replace
> it all' approach, and it is (from the point of view of the programmer),
> however the result ends up being far more reliable as the process forces
> better examination of all the details,

I agree with you on that. Again, although my post may have sounded like
it, I did not want to advocate the "throw it out and replace it all"
approach.

> and allows more people to
> understand what's happening each step of the way.

Absolutely.

However I don't agree with you that _every_ little step must keep
everything working. I believe that this may actually make the transition
less easy to follow.

> And since there are no
> releases that are made unuseable for people deliberatly, you also get

I did not suggest to make unuseable releases.

> extensive testing of all the steps along the way. This not only finds
> bugs sooner, it also makes it far more obvious where performance issues
> show up

I agree with you on these advantages of the "(try to) keep everything
working after each patch". Although the monitoring of performance is
less important during the initial stage of the cleanup of the core.

> so please accept that you aren't going to be able to replace any
> significant system in one massive change

Agreed. This is absolutely not what should be done.

> and instead start looking for
> ways to move the existing design towards where you want it to be and you
> will receive a lot of assistance in the process instead of banging heads
> with everyone.

OK.
--
Stefan Richter
-=====-=-=-= =-=- =-==-
http://arcgraph.de/sr/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-10-22 19:44    [W:0.338 / U:0.340 seconds]
©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site