LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: Bui Quang Minh <minhquangbui99@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Network Development <netdev@vger.kernel.org>,
David Miller <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
David Ahern <dsahern@kernel.org>,
Willem de Bruijn <willemb@google.com>,
Paolo Abeni <pabeni@redhat.com>, Andrei Vagin <avagin@gmail.com>,
alexander@mihalicyn.com,
Lese Doru Calin <lesedorucalin01@gmail.com>
Subject: Re: [PATCH v2 1/2] udp: UDP socket send queue repair
Date: Mon, 16 Aug 2021 07:38:40 -0700 [thread overview]
Message-ID: <CAF=yD-LnDSzFFz6B8o84B1OSxTQE9p=LyFoAe_7+-k7q_r0yog@mail.gmail.com> (raw)
In-Reply-To: <20210811154557.6935-1-minhquangbui99@gmail.com>
On Wed, Aug 11, 2021 at 8:48 AM Bui Quang Minh <minhquangbui99@gmail.com> wrote:
>
> In this patch, I implement UDP_REPAIR sockoption and a new path in
> udp_recvmsg for dumping the corked packet in UDP socket's send queue.
>
> A userspace program can use recvmsg syscall to get the packet's data and
> the msg_name information of the packet. Currently, other related
> information in inet_cork that are set in cmsg are not dumped.
[ intended to include in my previous response ]
What other related information? Fields like transmit_time and gso_size?
This would be another reason to prefer dropping the packet over trying
to restore it incompletely.
prev parent reply other threads:[~2021-08-16 14:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-11 15:45 Bui Quang Minh
2021-08-11 16:14 ` Eric Dumazet
2021-08-12 13:46 ` Bui Quang Minh
2021-08-12 15:51 ` Eric Dumazet
2021-08-13 11:08 ` Bui Quang Minh
2021-08-13 13:00 ` David Laight
2021-08-17 16:22 ` avagin
2021-08-16 14:35 ` Willem de Bruijn
2021-08-16 14:38 ` Willem de Bruijn [this message]
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='CAF=yD-LnDSzFFz6B8o84B1OSxTQE9p=LyFoAe_7+-k7q_r0yog@mail.gmail.com' \
--to=willemdebruijn.kernel@gmail.com \
--cc=alexander@mihalicyn.com \
--cc=avagin@gmail.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=kuba@kernel.org \
--cc=lesedorucalin01@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=minhquangbui99@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=willemb@google.com \
--cc=yoshfuji@linux-ipv6.org \
--subject='Re: [PATCH v2 1/2] udp: UDP socket send queue repair' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).