From: Yuri Benditovich <yuri.benditovich@daynix.com>
To: davem@davemloft.net, kuba@kernel.org, mst@redhat.com,
jasowang@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org
Cc: yan@daynix.com
Subject: [PATCH 3/4] tun: define feature bit for USO support
Date: Tue, 11 May 2021 07:42:52 +0300 [thread overview]
Message-ID: <20210511044253.469034-4-yuri.benditovich@daynix.com> (raw)
In-Reply-To: <20210511044253.469034-1-yuri.benditovich@daynix.com>
User mode software can probe this bit to check whether the
USO feature is supported by TUN/TAP device.
Signed-off-by: Yuri Benditovich <yuri.benditovich@daynix.com>
---
include/uapi/linux/if_tun.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/uapi/linux/if_tun.h b/include/uapi/linux/if_tun.h
index 454ae31b93c7..24f246920dd5 100644
--- a/include/uapi/linux/if_tun.h
+++ b/include/uapi/linux/if_tun.h
@@ -88,6 +88,7 @@
#define TUN_F_TSO6 0x04 /* I can handle TSO for IPv6 packets */
#define TUN_F_TSO_ECN 0x08 /* I can handle TSO with ECN bits. */
#define TUN_F_UFO 0x10 /* I can handle UFO packets */
+#define TUN_F_USO 0x20 /* I can handle USO packets */
/* Protocol info prepended to the packets (when IFF_NO_PI is not set) */
#define TUN_PKT_STRIP 0x0001
--
2.26.3
next prev parent reply other threads:[~2021-05-11 4:43 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-11 4:42 [PATCH 0/4] Add host USO support to TUN device Yuri Benditovich
2021-05-11 4:42 ` [PATCH 1/4] virtio-net: add definitions for host USO feature Yuri Benditovich
2021-05-11 6:47 ` Jason Wang
2021-05-11 8:12 ` Yuri Benditovich
2021-05-11 8:24 ` Jason Wang
2021-05-11 9:21 ` Yuri Benditovich
2021-05-12 1:21 ` Jason Wang
2021-05-11 4:42 ` [PATCH 2/4] virtio-net: add support of UDP segmentation (USO) on the host Yuri Benditovich
2021-05-11 6:47 ` Jason Wang
2021-05-11 8:23 ` Yuri Benditovich
2021-05-11 8:31 ` Jason Wang
2021-05-11 17:47 ` Willem de Bruijn
2021-05-12 6:09 ` Yuri Benditovich
2021-05-12 14:32 ` Willem de Bruijn
2021-05-12 18:56 ` Yuri Benditovich
2021-05-12 19:53 ` Willem de Bruijn
2021-05-11 4:42 ` Yuri Benditovich [this message]
2021-05-11 4:42 ` [PATCH 4/4] tun: indicate support for USO feature Yuri Benditovich
2021-05-11 6:50 ` Jason Wang
2021-05-11 8:33 ` Yuri Benditovich
2021-05-11 19:06 ` Yuri Benditovich
2021-05-12 1:33 ` Jason Wang
2021-05-12 5:24 ` Yuri Benditovich
[not found] ` <CACGkMEsZBCzV+d_eLj1aYT+pkS5m1QAy7q8rUkNsdV0C8aL8tQ@mail.gmail.com>
[not found] ` <CAOEp5OeSankfA6urXLW_fquSMrZ+WYXDtKNacort1UwR=WgxqA@mail.gmail.com>
[not found] ` <CACGkMEt3bZrdqbWtWjSkXvv5v8iCHiN8hkD3T602RZnb6nPd9A@mail.gmail.com>
[not found] ` <CAOEp5Odw=eaQWZCXr+U8PipPtO1Avjw-t3gEdKyvNYxuNa5TfQ@mail.gmail.com>
[not found] ` <CACGkMEuqXaJxGqC+CLoq7k4XDu+W3E3Kk3WvG-D6tnn2K4ZPNA@mail.gmail.com>
[not found] ` <CAOEp5OfB62SQzxMj_GkVD4EM=Z+xf43TPoTZwMbPPa3BsX2ooA@mail.gmail.com>
2021-05-13 7:04 ` Jason Wang
2021-05-13 8:14 ` Yuri Benditovich
2021-05-13 20:43 ` Willem de Bruijn
2021-05-14 5:48 ` Yuri Benditovich
2021-05-13 20:34 ` Willem de Bruijn
2021-05-14 7:16 ` Jason Wang
2021-05-14 7:38 ` Yuri Benditovich
2021-05-14 12:41 ` Willem de Bruijn
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=20210511044253.469034-4-yuri.benditovich@daynix.com \
--to=yuri.benditovich@daynix.com \
--cc=davem@davemloft.net \
--cc=jasowang@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=yan@daynix.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 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).