Дана Tue, 28 May 2013 15:49:45 +0200 Stanislav Meduna <stano@xxxxxxxxxx> написа: > On 28.05.2013 15:01, Nebojša Ćosić wrote: > > > If you are having several processes/threads with different priorities > > sending on same eth, combined with high cpu load on RT processes, than > > it sounds a lot like a problem I had: Check > > http://article.gmane.org/gmane.linux.rt.user/10163 for details > > Hm, interesting. However, there is just one thread sending on the > interface and all threads with higher priority generally only run for > brief intervals and do not do anything with ethernet. There are > lower-prio threads doing full TCP/IP but they communivate on another > interface (also a e100e one). > > Thanks Well, I think it still applies. Lock which is responsible for this problem is driver wise... Lower prio thread can take driver lock, and thus delay higher thread from accessing driver. It is enough that there are jobs with higher prio than lowest prio tcp/ip sending thread, even if they have nothing to do with network. -- Nebojša -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
