Re: A Layered Kernel: Proposal

From: Rik van Riel (riel_at_redhat.com)
Date: 02/25/04

  • Next message: Matthew Wilcox: "Re: [SUBJECT CHANGE]: megaraid unified driver version 2.20.0.0-alpha1" 
    Date:	Wed, 25 Feb 2004 07:52:32 -0500 (EST)
To: Grigor Gatchev <grigor@zadnik.org>

    On Wed, 25 Feb 2004, Grigor Gatchev wrote:

    > > I'm all for cleaning up the badly written code so it fits
    > > in better with the rest of the kernel ;)
    >
    > Unhappily, cleaning up would not be enough. A separation of the kernel
    > layers, to the extent that one may be able to use them independently,
    > and to plug modules between them (having the appropriate access) may be
    > better.

    Some parts of the kernel (eg. the VFS or the device driver
    layers) can already do that, while others still have layering
    violations.

    I suspect that the least destabilising way of moving to a
    more modular model would be to gradually clean up the layering
    violations in the rest of the code, until things are modular.

    Yes, I know it's a lot of work ... 

    -- 
"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it." - Brian W. Kernighan
-
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/
  • Next message: Matthew Wilcox: "Re: [SUBJECT CHANGE]: megaraid unified driver version 2.20.0.0-alpha1"