[lkml]   [2004]   [Mar]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [Swsusp-devel] Re: Dropping CONFIG_PM_DISK?
On Mon, 01 Mar 2004 14:47:23 +0100, Arjan van de Ven <> wrote:

>> Then one could just drop in a driver from 2.4 and use it.
>> People having time to make new "pretty" drivers could
>> also use this facility for cross checking.
> I'm sorry but this is a load of bull ;)

Thank you, I do fully concur with you from an ideal scientific perspective
where resources are not constrained. Applying the same perspective I might
like to craft lots of drivers in assembler or even reinvent whatever...,
but I do not live an ideal world.

> New kernel revisions come with a new API. If we keep the old one around
> forever that achieves two things
> 1) The kernel bloats up

By a few %, only when old API is used, the benefits far outweighs the cost.

The old API should be an independent glue layer where incompatible.
Performance is not a concern here, functionality is.

> 2) Nobody puts effort into using the new (better) API

Could be fixed by the simple policy that drivers which did not exist before
must use new API.

> A proof of 2 is the scsi error handling; the old one was kept around as
> compat for the last 5 years and only 2 or 3 drivers bothered to use the
> new one.

I am not around here that long, but if those drivers were added after the
API was finalized, it would have been a policy issue which does not have to
be repeated.

At least, (hopefully not from an ideal perspective), the new API is good
enough to last and will not have to be trown away in 2.7 or even 2.9 :)

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 14:01    [W:0.062 / U:41.120 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site