All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Leşe Doru Călin" <lesedorucalin01@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>,
	Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
	netdev@vger.kernel.org
Subject: Re: [PATCH] net: UDP repair mode for retrieving the send queue of corked UDP socket
Date: Thu, 9 Apr 2020 01:25:27 +0300	[thread overview]
Message-ID: <20200408222527.GA23620@white> (raw)
In-Reply-To: <20200408.142749.1712309028781080294.davem@davemloft.net>

On Wed, Apr 08, 2020 at 02:27:49PM -0700, David Miller wrote:
> From: Lese Doru Calin <lesedorucalin01@gmail.com>
> Date: Wed, 8 Apr 2020 23:59:54 +0300
> 
> > Hello everyone!
> > 
> > In this year's edition of GSoC, there is a project idea for CRIU to add support
> > for checkpoint/restore of cork-ed UDP sockets. But to add it, the kernel API needs
> > to be extended.
> > This is what this patch does. It adds UDP "repair mode" for UDP sockets in a similar
> > approach to the TCP "repair mode", but only the send queue is necessary to be retrieved.
> > So the patch extends the recv and setsockopt syscalls. Using UDP_REPAIR option in
> > setsockopt, caller can set the socket in repair mode. If it is setted, the
> > recv/recvfrom/recvmsg will receive the write queue and the destination of the data.
> > As in the TCP mode, to change the repair mode requires the CAP_NET_ADMIN capability
> > and to receive data the caller is obliged to use the MSG_PEEK flag.
> > 
> > Best regards,
> > Lese Doru
> > 
> > Signed-off-by: Lese Doru Calin <lesedorucalin01@gmail.com>
> 
> Why do I feel like I've seen this patch several times before?

Maybe others contestants in GSoC already sended a patch for this.
This is the my first time when try.

  reply	other threads:[~2020-04-08 22:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-08 20:59 [PATCH] net: UDP repair mode for retrieving the send queue of corked UDP socket Leşe Doru Călin
2020-04-08 21:27 ` David Miller
2020-04-08 22:25   ` Leşe Doru Călin [this message]
2020-04-13  3:56 ` David Miller
2020-04-13 20:09   ` Leşe Doru Călin
2020-04-13 20:33     ` David Miller

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=20200408222527.GA23620@white \
    --to=lesedorucalin01@gmail.com \
    --cc=davem@davemloft.net \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=netdev@vger.kernel.org \
    --cc=yoshfuji@linux-ipv6.org \
    /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.