The proposal from GGI folk looks fine but it is a SAASTDWDIOAI (TM).
StillAnotherAbstractionsSetIntendedToDealWithBrainDamagedInOutArchitectureImplementations.
The PCI recommendation is to have a flat model with unified memory/BUS
physical addressing from all parts (I mean CPUs and BUSes). It seems
that when it is easy to make things simple and hard to make them complex,
architecture designers did prefer the latter.
Just a question:
If I choose a system that has a simple IO system design, how much will be
the bloat and the overhead due to this proposal?
Regards,
Gerard.
PS: my prefered way to make things portable is to use '#if' (preprocessed)
contructs and not 'if' (run time) contructs. Any bloat or overhead due to
portability issues is poor design in my opinion. I would prefer to use non
portable code rather than to have code that checks at run time if my
system is something different from what it actually is. BTW, I understand
portability issues since my official work is to develop such kind of
applications.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/