On Thu, Jan 22, 2015 at 09:49:00AM -0500, Austin S Hemmelgarn wrote: > While I agree that there should be a way for userspace to get the list of > supported operations, userspace apps will only actually care about that > once, when they begin talking to kdbus, because (ignoring the live kernel > patching that people have been working on recently) the list of supported > operations isn't going to change while the system is running. While a u64 > copy has relatively low overhead, it does have overhead, and that is very > significant when you consider part of the reason some people want kdbus is > for the performance gain. Especially for those automotive applications that > have been mentioned which fire off thousands of messages during start-up, > every little bit of performance is significant. A single u64 in a structure is not going to be measurable at all, processors just copy memory too fast these days for 4 extra bytes to be noticable. So let's make this as easy as possible for userspace, making it simpler logic there, which is much more important than saving theoretical time in the kernel. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-api" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
