Thread (9 messages) flat view 9 messages, 3 authors, 2018-10-10

Re: [PATCH net-next] tcp: forbid direct reclaim if MSG_DONTWAIT is set in send path

From: Eric Dumazet <edumazet@google.com>
Date: 2018-10-09 15:38:54
Also in: lkml

On Tue, Oct 9, 2018 at 7:58 AM Eric Dumazet [off-list ref] wrote:
We do not add bloat in the kernel if no application is ever going to
use it, especially in the TCP fast path.
BTW, are you willing to change all memory allocations in the kernel as well ?

Let say an application is using a system call providing a pathname
(open(), stat(), ...), how this system call
is going to ask the kernel for no direct reclaim ?

Even allocating a socket with socket() or accept() has no ability to
avoid direct reclaim.

So tcp_sendmsg() is only the tip of the iceberg.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help