qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Bin Meng <bmeng.cn@gmail.com>
To: "Jason Wang" <jasowang@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>,
	"Peter Maydell" <peter.maydell@linaro.org>,
	qemu-devel@nongnu.org
Cc: Bin Meng <bmeng.cn@gmail.com>
Subject: [PATCH v4 02/12] net: Add a 'do_not_pad" to NetClientState
Date: Tue, 16 Mar 2021 20:04:10 +0800	[thread overview]
Message-ID: <20210316120420.19658-3-bmeng.cn@gmail.com> (raw)
In-Reply-To: <20210316120420.19658-1-bmeng.cn@gmail.com>

This adds a flag in NetClientState, so that a net client can tell
its peer that the packets do not need to be padded to the minimum
size of an Ethernet frame (60 bytes) before sending to it.

Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>

---

(no changes since v3)

Changes in v3:
- add a comment to 'do_not_pad'

 include/net/net.h | 1 +
 1 file changed, 1 insertion(+)

diff --git a/include/net/net.h b/include/net/net.h
index 919facaad2..f944731c18 100644
--- a/include/net/net.h
+++ b/include/net/net.h
@@ -100,6 +100,7 @@ struct NetClientState {
     int vring_enable;
     int vnet_hdr_len;
     bool is_netdev;
+    bool do_not_pad; /* do not pad to the minimum ethernet frame length */
     QTAILQ_HEAD(, NetFilterState) filters;
 };
 
-- 
2.25.1



  parent reply	other threads:[~2021-03-16 12:06 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-16 12:04 [PATCH v4 00/12] net: Pad short frames for network backends Bin Meng
2021-03-16 12:04 ` [PATCH v4 01/12] net: eth: Add a helper to pad a short Ethernet frame Bin Meng
2021-03-16 15:09   ` Philippe Mathieu-Daudé
2021-03-17  6:22     ` Bin Meng
2021-03-16 12:04 ` Bin Meng [this message]
2021-03-16 12:04 ` [PATCH v4 03/12] net: Pad short frames to minimum size before sending from SLiRP/TAP Bin Meng
2021-03-16 15:10   ` Philippe Mathieu-Daudé
2021-03-16 12:04 ` [PATCH v4 04/12] hw/net: virtio-net: Initialize nc->do_not_pad to true Bin Meng
2021-03-16 12:04 ` [PATCH v4 05/12] hw/net: e1000: Remove the logic of padding short frames in the receive path Bin Meng
2021-03-16 12:04 ` [PATCH v4 06/12] hw/net: vmxnet3: " Bin Meng
2021-03-16 12:04 ` [PATCH v4 07/12] hw/net: i82596: " Bin Meng
2021-03-16 12:04 ` [PATCH v4 08/12] hw/net: ne2000: " Bin Meng
2021-03-16 12:04 ` [PATCH v4 09/12] hw/net: pcnet: " Bin Meng
2021-03-16 12:04 ` [PATCH v4 10/12] hw/net: rtl8139: " Bin Meng
2021-03-16 12:04 ` [PATCH v4 11/12] hw/net: sungem: " Bin Meng
2021-03-16 12:04 ` [PATCH v4 12/12] hw/net: sunhme: " Bin Meng

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=20210316120420.19658-3-bmeng.cn@gmail.com \
    --to=bmeng.cn@gmail.com \
    --cc=jasowang@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.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 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).