Messages in this thread | | | Date | Tue, 27 Nov 2007 15:12:42 +0100 | From | Andi Kleen <> | Subject | Re: [PATCH RFC] [1/9] Core module symbol namespaces code and intro. |
| |
> OK, short of making IPv4 a module (which would be a worthy task :)
At some point there were patches, it is probably not very difficult. But DaveM resisted at some point because he didn't want people to replace the network stack (although I personally don't have a problem with that)
> do you have an example where a symbol is used by more than one module > but needs to be put into a namespace?
For SCSI: SD,SR,SG etc. For Networking: e.g. symbols i put into inet, which are only used by protocols (sctp, dccp, udplite, ipv6) I already caught someone doing something wrong with that BTW -- wanrouter clearly does some things it shouldn't be doing. Or the fib namespace, where all the fib functions should be only used by the two fib_* modules and ipv6/decnet. For KVM: the exports used by kvm_amd/intel For arch/x86: e.g. e820_*, IO_APIC_get_PCI_irq_vector, swiotlb, a lot of stuff only used by acpi processor.c, pcibios*, etc.etc. Roland gave another example for Infiniband.
Also in general it allows flexibility later if modules get split.
-Andi - 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/
| |