From: Jakub Kicinski <kuba@kernel.org>
To: Kuniyuki Iwashima <kuniyu@amazon.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Ivan Babrou <ivan@cloudflare.com>,
Kuniyuki Iwashima <kuni1840@gmail.com>, <netdev@vger.kernel.org>
Subject: Re: [PATCH v4 net-next 0/4] af_unix: Random improvements for GC.
Date: Tue, 2 Jan 2024 15:29:11 -0800 [thread overview]
Message-ID: <20240102152911.20171dee@kernel.org> (raw)
In-Reply-To: <20231219030102.27509-1-kuniyu@amazon.com>
On Tue, 19 Dec 2023 12:00:58 +0900 Kuniyuki Iwashima wrote:
> If more than 16000 inflight AF_UNIX sockets exist on a host, each
> sendmsg() will be forced to wait for unix_gc() even if a process
> is not sending any FD.
>
> This series tries not to impose such a penalty on sane users who
> do not send AF_UNIX FDs or do not have inflight sockets more than
> SCM_MAX_FD * 8.
>
> Cleanup patches for commit 69db702c8387 ("io_uring/af_unix: disable
> sending io_uring over sockets") will be posted later as noted in [0].
Could you repost? I tried to revive it in patchwork but I think
it keeps getting Archived because it's more than 2 weeks old :(
next prev parent reply other threads:[~2024-01-02 23:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 3:00 [PATCH v4 net-next 0/4] af_unix: Random improvements for GC Kuniyuki Iwashima
2023-12-19 3:00 ` [PATCH v4 net-next 1/4] af_unix: Do not use atomic ops for unix_sk(sk)->inflight Kuniyuki Iwashima
2023-12-19 3:01 ` [PATCH v4 net-next 2/4] af_unix: Return struct unix_sock from unix_get_socket() Kuniyuki Iwashima
2023-12-19 3:01 ` [PATCH v4 net-next 3/4] af_unix: Run GC on only one CPU Kuniyuki Iwashima
2023-12-19 3:01 ` [PATCH v4 net-next 4/4] af_unix: Try to run GC async Kuniyuki Iwashima
2024-01-02 23:29 ` Jakub Kicinski [this message]
2024-01-09 2:01 ` [PATCH v4 net-next 0/4] af_unix: Random improvements for GC Kuniyuki Iwashima
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240102152911.20171dee@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=ivan@cloudflare.com \
--cc=kuni1840@gmail.com \
--cc=kuniyu@amazon.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.