DPDK patches and discussions
 help / color / mirror / Atom feed
* [dpdk-dev] [PATCH v5] net/virtio: set offload flag for jumbo frames
@ 2019-02-05 11:17 Jens Freimann
  2019-02-08  9:51 ` Maxime Coquelin
  2019-02-08 18:05 ` Maxime Coquelin
  0 siblings, 2 replies; 3+ messages in thread
From: Jens Freimann @ 2019-02-05 11:17 UTC (permalink / raw)
  To: dev; +Cc: tiwei.bie, maxime.coquelin

Port configuration fails because offload flags don't match the expected
value when max-pkt-len is set to a value that should enable receive port
offloading but doesn't.

The .dev_infos_get callback can be called before the configure callback.
At that time we don't know the maximum packet size yet because it is
only set up when ports are started. So in virtio_dev_info_get() just
always set the jumbo packet offload flag.

Check the maximum packet length at device configure time, because then we
have access to the max-pkt-len value provided by the user. If the
max-pkt-len exceeds the maximum MTU supported by the device we remove
the VIRTIO_NET_F_MTU flag from requested features.

Fixes: a4996bd89c42 ("ethdev: new Rx/Tx offloads API")
Cc: stable@dpdk.org

Signed-off-by: Jens Freimann <jfreimann@redhat.com>
---
 drivers/net/virtio/virtio_ethdev.c | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/drivers/net/virtio/virtio_ethdev.c b/drivers/net/virtio/virtio_ethdev.c
index 7c4c1df00..7c2fe76f3 100644
--- a/drivers/net/virtio/virtio_ethdev.c
+++ b/drivers/net/virtio/virtio_ethdev.c
@@ -1972,6 +1972,8 @@ virtio_dev_configure(struct rte_eth_dev *dev)
 	const struct rte_eth_rxmode *rxmode = &dev->data->dev_conf.rxmode;
 	const struct rte_eth_txmode *txmode = &dev->data->dev_conf.txmode;
 	struct virtio_hw *hw = dev->data->dev_private;
+	uint32_t ether_hdr_len = ETHER_HDR_LEN + VLAN_TAG_LEN +
+		hw->vtnet_hdr_size;
 	uint64_t rx_offloads = rxmode->offloads;
 	uint64_t tx_offloads = txmode->offloads;
 	uint64_t req_features;
@@ -1986,6 +1988,9 @@ virtio_dev_configure(struct rte_eth_dev *dev)
 			return ret;
 	}
 
+	if (rxmode->max_rx_pkt_len > hw->max_mtu + ether_hdr_len)
+		req_features &= ~(1ULL << VIRTIO_NET_F_MTU);
+
 	if (rx_offloads & (DEV_RX_OFFLOAD_UDP_CKSUM |
 			   DEV_RX_OFFLOAD_TCP_CKSUM))
 		req_features |= (1ULL << VIRTIO_NET_F_GUEST_CSUM);
@@ -2339,6 +2344,7 @@ virtio_dev_info_get(struct rte_eth_dev *dev, struct rte_eth_dev_info *dev_info)
 
 	host_features = VTPCI_OPS(hw)->get_features(hw);
 	dev_info->rx_offload_capa = DEV_RX_OFFLOAD_VLAN_STRIP;
+	dev_info->rx_offload_capa |= DEV_RX_OFFLOAD_JUMBO_FRAME;
 	if (host_features & (1ULL << VIRTIO_NET_F_GUEST_CSUM)) {
 		dev_info->rx_offload_capa |=
 			DEV_RX_OFFLOAD_TCP_CKSUM |
-- 
2.17.2

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [dpdk-dev] [PATCH v5] net/virtio: set offload flag for jumbo frames
  2019-02-05 11:17 [dpdk-dev] [PATCH v5] net/virtio: set offload flag for jumbo frames Jens Freimann
@ 2019-02-08  9:51 ` Maxime Coquelin
  2019-02-08 18:05 ` Maxime Coquelin
  1 sibling, 0 replies; 3+ messages in thread
From: Maxime Coquelin @ 2019-02-08  9:51 UTC (permalink / raw)
  To: Jens Freimann, dev; +Cc: tiwei.bie



On 2/5/19 12:17 PM, Jens Freimann wrote:
> Port configuration fails because offload flags don't match the expected
> value when max-pkt-len is set to a value that should enable receive port
> offloading but doesn't.
> 
> The .dev_infos_get callback can be called before the configure callback.
> At that time we don't know the maximum packet size yet because it is
> only set up when ports are started. So in virtio_dev_info_get() just
> always set the jumbo packet offload flag.
> 
> Check the maximum packet length at device configure time, because then we
> have access to the max-pkt-len value provided by the user. If the
> max-pkt-len exceeds the maximum MTU supported by the device we remove
> the VIRTIO_NET_F_MTU flag from requested features.
> 
> Fixes: a4996bd89c42 ("ethdev: new Rx/Tx offloads API")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Jens Freimann <jfreimann@redhat.com>
> ---
>   drivers/net/virtio/virtio_ethdev.c | 6 ++++++
>   1 file changed, 6 insertions(+)

Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>

Thanks,
Maxime

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [dpdk-dev] [PATCH v5] net/virtio: set offload flag for jumbo frames
  2019-02-05 11:17 [dpdk-dev] [PATCH v5] net/virtio: set offload flag for jumbo frames Jens Freimann
  2019-02-08  9:51 ` Maxime Coquelin
@ 2019-02-08 18:05 ` Maxime Coquelin
  1 sibling, 0 replies; 3+ messages in thread
From: Maxime Coquelin @ 2019-02-08 18:05 UTC (permalink / raw)
  To: Jens Freimann, dev; +Cc: tiwei.bie



On 2/5/19 12:17 PM, Jens Freimann wrote:
> Port configuration fails because offload flags don't match the expected
> value when max-pkt-len is set to a value that should enable receive port
> offloading but doesn't.
> 
> The .dev_infos_get callback can be called before the configure callback.
> At that time we don't know the maximum packet size yet because it is
> only set up when ports are started. So in virtio_dev_info_get() just
> always set the jumbo packet offload flag.
> 
> Check the maximum packet length at device configure time, because then we
> have access to the max-pkt-len value provided by the user. If the
> max-pkt-len exceeds the maximum MTU supported by the device we remove
> the VIRTIO_NET_F_MTU flag from requested features.
> 
> Fixes: a4996bd89c42 ("ethdev: new Rx/Tx offloads API")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Jens Freimann <jfreimann@redhat.com>
> ---
>   drivers/net/virtio/virtio_ethdev.c | 6 ++++++
>   1 file changed, 6 insertions(+)
> 

Applied to dpdk-next-virtio/master.

Thanks,
Maxime

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2019-02-08 18:05 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-02-05 11:17 [dpdk-dev] [PATCH v5] net/virtio: set offload flag for jumbo frames Jens Freimann
2019-02-08  9:51 ` Maxime Coquelin
2019-02-08 18:05 ` Maxime Coquelin

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).