On Fri, 15 Apr 2011 22:34:53 +0100 Tony Ibbs <tibs@xxxxxxxxxxxxxx> wrote: > This patch provides mechanisms for setting an absolute maximum message > size at compile time, and a per-device maximum at runtime. It seems like a good step in the right direction. Do you really need to add a bunch more configuration options, though? It seems like a reasonable default and a way to change it (sysfs file, maybe) might be better. Is there a way to cap the total memory used by the kbus subsystem? The kzalloc() fixes seem like a good idea too, BUT: I honestly think that the item at the top of your list, if you want to merge this code, must be to get the user-space API more widely reviewed and accepted. It could, I think, be a big sticking point, and it's something you want to try to address sooner rather than later. That means getting more people to look at the patch, which could be hard. The problem is that, if you wait, they'll only squeal when the code is close to going in, and you could find yourself set back a long way. A good first step might be to CC Andrew Morton on your next posting. Thanks, jon -- To unsubscribe from this list: send the line "unsubscribe linux-embedded" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
