On 31/07/20(Fri) 21:58, Vitaliy Makkoveev wrote: > [...] > What denies us to move pipex(4) under it's own lock?
Such question won't lead us anywhere. It assumes it makes sense to move pipex under its own lock. This assumption has many drawback which clearly haven't been studied and more importantly it doesn't explains what for. What is your goal? What are you trying to achieve? Improve latency? Improve performances? Of which subsystem? Where is the bottleneck? What is the architecture of the system? IMHO the KERNEL_LOCK() should be removed an anything else postponed at least until one has a clear understanding of the whole subsystem under the NET_LOCK().
