On Thu, May 25, 2017 at 05:56:51PM -0700, Dmitry Torokhov wrote: > On Thu, May 25, 2017 at 05:16:29PM -0700, Luis R. Rodriguez wrote: > > This adds helpers for getting access to the kmod limit from > > userspace. This knob should help userspace more gracefully and > > deterministically handle module loading. > > I think more details is needed before we add a new ABI to the kernel. > Why can't userspace submit as much as it wants and the kernel decide how > much it will service at once? I suppose I should clarify on the commit log then, that without this heuristic of #ifdef get_kmod_umh_limit -- *iff* userspace today is allowing more than 50 threads it can mean userspace is allowing a modprobe to fail. Check the results of test 0008 and 0009 on dmesg, you can end up with really unexpected results. This knob enables userspace to gracefully send in as many requests as allowed. I guess this could just be a kernel revision check... given that once throttling go in it can be as crazy as it wants. Also I suppose one could argue that *since* this has not been a real issue *yet* (we assume), the old userspace of sending as many requests as it needs is fine. Will drop this! Luis -- To unsubscribe from this list: send the line "unsubscribe linux-kselftest" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
