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 <bin.meng@windriver.com>
Subject: [RFC PATCH v2 7/9] hw/net: rtl8139: Remove the logic of padding short frames in the receive path
Date: Wed, 3 Mar 2021 17:21:44 +0800 [thread overview]
Message-ID: <1614763306-18026-8-git-send-email-bmeng.cn@gmail.com> (raw)
In-Reply-To: <1614763306-18026-1-git-send-email-bmeng.cn@gmail.com>
From: Bin Meng <bin.meng@windriver.com>
Now that we have implemented unified short frames padding in the
QEMU networking codes, remove the same logic in the NIC codes.
Signed-off-by: Bin Meng <bin.meng@windriver.com>
---
(no changes since v1)
hw/net/rtl8139.c | 12 ------------
1 file changed, 12 deletions(-)
diff --git a/hw/net/rtl8139.c b/hw/net/rtl8139.c
index 4675ac8..cbfe29a 100644
--- a/hw/net/rtl8139.c
+++ b/hw/net/rtl8139.c
@@ -827,7 +827,6 @@ static ssize_t rtl8139_do_receive(NetClientState *nc, const uint8_t *buf, size_t
uint32_t packet_header = 0;
- uint8_t buf1[MIN_BUF_SIZE + VLAN_HLEN];
static const uint8_t broadcast_macaddr[6] =
{ 0xff, 0xff, 0xff, 0xff, 0xff, 0xff };
@@ -939,17 +938,6 @@ static ssize_t rtl8139_do_receive(NetClientState *nc, const uint8_t *buf, size_t
}
}
- /* if too small buffer, then expand it
- * Include some tailroom in case a vlan tag is later removed. */
- if (size < MIN_BUF_SIZE + VLAN_HLEN) {
- memcpy(buf1, buf, size);
- memset(buf1 + size, 0, MIN_BUF_SIZE + VLAN_HLEN - size);
- buf = buf1;
- if (size < MIN_BUF_SIZE) {
- size = MIN_BUF_SIZE;
- }
- }
-
if (rtl8139_cp_receiver_enabled(s))
{
if (!rtl8139_cp_rx_valid(s)) {
--
2.7.4
next prev parent reply other threads:[~2021-03-03 9:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 9:21 [RFC PATCH v2 0/9] net: Handle short frames for SLiRP/TAP interfaces Bin Meng
2021-03-03 9:21 ` [RFC PATCH v2 1/9] net: Pad short frames to minimum size before send from SLiRP/TAP Bin Meng
2021-03-03 10:15 ` Philippe Mathieu-Daudé
2021-03-03 10:31 ` Bin Meng
2021-03-03 9:21 ` [RFC PATCH v2 2/9] hw/net: e1000: Remove the logic of padding short frames in the receive path Bin Meng
2021-03-03 9:21 ` [RFC PATCH v2 3/9] hw/net: vmxnet3: " Bin Meng
2021-03-03 9:21 ` [RFC PATCH v2 4/9] hw/net: i82596: " Bin Meng
2021-03-03 9:21 ` [RFC PATCH v2 5/9] hw/net: ne2000: " Bin Meng
2021-03-03 9:21 ` [RFC PATCH v2 6/9] hw/net: pcnet: " Bin Meng
2021-03-03 9:21 ` Bin Meng [this message]
2021-03-03 9:21 ` [RFC PATCH v2 8/9] hw/net: sungem: " Bin Meng
2021-03-03 9:21 ` [RFC PATCH v2 9/9] 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=1614763306-18026-8-git-send-email-bmeng.cn@gmail.com \
--to=bmeng.cn@gmail.com \
--cc=bin.meng@windriver.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).