From: Pavel Emelyanov <xemul@parallels•com>
To: David Miller <davem@davemloft•net>,
Linux Netdev List <netdev@vger•kernel.org>
Subject: [PATCH net-next 0/4] tun: Some bits required for tun's checkpoint-restore (v2)
Date: Wed, 21 Aug 2013 14:31:11 +0400 [thread overview]
Message-ID: <521496EF.8090909@parallels.com> (raw)
Hi,
After taking a closer look on tun checkpoint-restore I've found several
issues with the tun's API that make it impossible to dump and restore
the state of tun device and attached tun-files.
The proposed API changes are all about extending the existing ioctl-based
stuff. Patches fit today's net-next.
This v2 has David's comments about patch #1 fixed. All the rest is the same.
Signed-off-by: Pavel Emelyanov <xemul@parallels•com>
next reply other threads:[~2013-08-21 10:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-21 10:31 Pavel Emelyanov [this message]
2013-08-21 10:31 ` [PATCH 1/4] tun: Add ability to create tun device with given index Pavel Emelyanov
2013-08-21 10:32 ` [PATCH 2/4] tun: Report whether the queue is attached or not Pavel Emelyanov
2013-08-21 10:32 ` [PATCH 3/4] tun: Allow to skip filter on attach Pavel Emelyanov
2013-08-21 10:32 ` [PATCH 4/4] tun: Get skfilter layout Pavel Emelyanov
2013-08-21 19:22 ` [PATCH net-next 0/4] tun: Some bits required for tun's checkpoint-restore (v2) 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=521496EF.8090909@parallels.com \
--to=xemul@parallels$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox