From: bmeng.cn@gmail.com
To: Jason Wang <jasowang@redhat.com>, qemu-devel@nongnu.org
Cc: Bin Meng <bmeng.cn@gmail.com>, Bin Meng <bmeng@tinylab.org>
Subject: [PATCH v6 7/8] hw/net: sungem: Remove the logic of padding short frames in the receive path
Date: Wed, 1 Mar 2023 17:02:02 +0800 [thread overview]
Message-ID: <20230301090203.1601925-8-bmeng.cn@gmail.com> (raw)
In-Reply-To: <20230301090203.1601925-1-bmeng.cn@gmail.com>
From: Bin Meng <bmeng.cn@gmail.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 <bmeng.cn@gmail.com>
Signed-off-by: Bin Meng <bmeng@tinylab.org>
---
hw/net/sungem.c | 14 --------------
1 file changed, 14 deletions(-)
diff --git a/hw/net/sungem.c b/hw/net/sungem.c
index eb01520790..103376c133 100644
--- a/hw/net/sungem.c
+++ b/hw/net/sungem.c
@@ -550,7 +550,6 @@ static ssize_t sungem_receive(NetClientState *nc, const uint8_t *buf,
PCIDevice *d = PCI_DEVICE(s);
uint32_t mac_crc, done, kick, max_fsize;
uint32_t fcs_size, ints, rxdma_cfg, rxmac_cfg, csum, coff;
- uint8_t smallbuf[60];
struct gem_rxd desc;
uint64_t dbase, baddr;
unsigned int rx_cond;
@@ -584,19 +583,6 @@ static ssize_t sungem_receive(NetClientState *nc, const uint8_t *buf,
return size;
}
- /* We don't drop too small frames since we get them in qemu, we pad
- * them instead. We should probably use the min frame size register
- * but I don't want to use a variable size staging buffer and I
- * know both MacOS and Linux use the default 64 anyway. We use 60
- * here to account for the non-existent FCS.
- */
- if (size < 60) {
- memcpy(smallbuf, buf, size);
- memset(&smallbuf[size], 0, 60 - size);
- buf = smallbuf;
- size = 60;
- }
-
/* Get MAC crc */
mac_crc = net_crc32_le(buf, ETH_ALEN);
--
2.34.1
next prev parent reply other threads:[~2023-03-01 9:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 9:01 [PATCH v6 0/8] net: Pad short frames for network backends bmeng.cn
2023-03-01 9:01 ` [PATCH v6 1/8] hw/net: e1000: Remove the logic of padding short frames in the receive path bmeng.cn
2023-03-01 9:01 ` [PATCH v6 2/8] hw/net: vmxnet3: " bmeng.cn
2023-03-01 9:01 ` [PATCH v6 3/8] hw/net: i82596: " bmeng.cn
2023-03-01 9:01 ` [PATCH v6 4/8] hw/net: ne2000: " bmeng.cn
2023-03-01 9:02 ` [PATCH v6 5/8] hw/net: pcnet: " bmeng.cn
2023-03-01 9:02 ` [PATCH v6 6/8] hw/net: rtl8139: " bmeng.cn
2023-03-01 9:02 ` bmeng.cn [this message]
2023-03-01 9:02 ` [PATCH v6 8/8] hw/net: sunhme: " bmeng.cn
2023-03-01 9:12 ` [PATCH v6 0/8] net: Pad short frames for network backends Cédric Le Goater
2023-03-01 10:20 ` 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=20230301090203.1601925-8-bmeng.cn@gmail.com \
--to=bmeng.cn@gmail.com \
--cc=bmeng@tinylab.org \
--cc=jasowang@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).