Hello!
> Why not using fully dynamical loadable kernel modules as done with Solaris
> since 1992? Since that time nobody cares because what you need is auto-loaded
> on demand and there is absolutely no need for a manual configuration.
Yes, but it still eats the memory if loaded.
> BTW: Introducing an orthogonal SCSI based implementation would save a lot of
> code. The model currently used on Linux is duplicating a lot of unneeded code
> in target drivers and the SCSI glue code is only a few KB (less than 30k on
> Solaris).
Please stop beating a dead horse and diverting this discussion to irrelevant
implementation details.
What we were (and should be) discussing are the interfaces. If you have
any sound arguments against the current interface, speak up.
Whether the interface leads to code duplication is neither yours nor
mine to judge -- the only people who should care are the maintainers
of the drivers and they seem to be happy with the current approach
and they are willing to improve it to simplify scanning.
Have a nice fortnight
--
Martin `MJ' Mares <[email protected]> http://atrey.karlin.mff.cuni.cz/~mj/
Faculty of Math and Physics, Charles University, Prague, Czech Rep., Earth
"Beware of bugs in the above code; I have only proved it correct, not tried it." -- D.E.K.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
