> A class number is an excellent idea, and could have potential
> performance gains. I thought of making such a patch, but expected it
> would be rejected since it is necessarily required and would require
> changes to significant sections of the kernel (to add the class to each
> object type).
>
> Have any better ideas for an implementation that doesn't touch so many
> sections of the kernel?
It should be trivial - we can use the subsystem name that the kobject
belongs to for the class ID. And, struct subsystem can gain a sequence
number, instead of having a global one in lib/kobject.c.
-pat
-
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/
This archive was generated by hypermail 2b29 : Mon Jun 23 2003 - 22:00:33 EST