* [dpdk-dev] DEV_RX_OFFLOAD_SCATTER for ixgbe and igb devices
@ 2018-04-13 14:52 Stokes, Ian
2018-04-13 17:16 ` Ferruh Yigit
0 siblings, 1 reply; 3+ messages in thread
From: Stokes, Ian @ 2018-04-13 14:52 UTC (permalink / raw)
To: dev
Hi all,
Currently it's the case that for some NICs (e.g. igb driver or ixgbe driver based), scatter_rx needs to be enabled explicitly in the case where it was not configured before.
A patch submitted for ovs-dpdk proposes to check that the DEV_RX_OFFLOAD_SCATTER flag is present in rte_ethdev_info.rx_offload_capa before setting scatter_rx.
https://mail.openvswitch.org/pipermail/ovs-dev/2018-April/345901.html
While testing igb and ixgbe devices I spotted the DEV_RX_OFFLOAD_SCATTER flag is not set in rx_offload_capa.
As these devices require scatter_rx, should the scatter_rx flag be set for them as part of the eth_igb_infos_get() for igb and ixgbe_dev_info_get for ixgbe?
Thanks
Ian
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [dpdk-dev] DEV_RX_OFFLOAD_SCATTER for ixgbe and igb devices
2018-04-13 14:52 [dpdk-dev] DEV_RX_OFFLOAD_SCATTER for ixgbe and igb devices Stokes, Ian
@ 2018-04-13 17:16 ` Ferruh Yigit
2018-04-16 8:18 ` Stokes, Ian
0 siblings, 1 reply; 3+ messages in thread
From: Ferruh Yigit @ 2018-04-13 17:16 UTC (permalink / raw)
To: Stokes, Ian, dev; +Cc: Qi Zhang, Helin Zhang
On 4/13/2018 3:52 PM, Stokes, Ian wrote:
> Hi all,
>
> Currently it's the case that for some NICs (e.g. igb driver or ixgbe driver based), scatter_rx needs to be enabled explicitly in the case where it was not configured before.
>
> A patch submitted for ovs-dpdk proposes to check that the DEV_RX_OFFLOAD_SCATTER flag is present in rte_ethdev_info.rx_offload_capa before setting scatter_rx.
>
> https://mail.openvswitch.org/pipermail/ovs-dev/2018-April/345901.html
>
> While testing igb and ixgbe devices I spotted the DEV_RX_OFFLOAD_SCATTER flag is not set in rx_offload_capa.
>
> As these devices require scatter_rx, should the scatter_rx flag be set for them as part of the eth_igb_infos_get() for igb and ixgbe_dev_info_get for ixgbe?
I agree, since that offload is supported by PMD, should be in capability flag.
Would you mind sending a patch for it, we can continue to discuss on it?
Thanks,
ferruh
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [dpdk-dev] DEV_RX_OFFLOAD_SCATTER for ixgbe and igb devices
2018-04-13 17:16 ` Ferruh Yigit
@ 2018-04-16 8:18 ` Stokes, Ian
0 siblings, 0 replies; 3+ messages in thread
From: Stokes, Ian @ 2018-04-16 8:18 UTC (permalink / raw)
To: Yigit, Ferruh, dev; +Cc: Zhang, Qi Z, Zhang, Helin
> On 4/13/2018 3:52 PM, Stokes, Ian wrote:
> > Hi all,
> >
> > Currently it's the case that for some NICs (e.g. igb driver or ixgbe
> driver based), scatter_rx needs to be enabled explicitly in the case where
> it was not configured before.
> >
> > A patch submitted for ovs-dpdk proposes to check that the
> DEV_RX_OFFLOAD_SCATTER flag is present in rte_ethdev_info.rx_offload_capa
> before setting scatter_rx.
> >
> > https://mail.openvswitch.org/pipermail/ovs-dev/2018-April/345901.html
> >
> > While testing igb and ixgbe devices I spotted the DEV_RX_OFFLOAD_SCATTER
> flag is not set in rx_offload_capa.
> >
> > As these devices require scatter_rx, should the scatter_rx flag be set
> for them as part of the eth_igb_infos_get() for igb and ixgbe_dev_info_get
> for ixgbe?
>
> I agree, since that offload is supported by PMD, should be in capability
> flag.
> Would you mind sending a patch for it, we can continue to discuss on it?
>
> Thanks,
> Ferruh
Thanks for the confirmation Ferruh, will send a patch.
Thanks
Ian
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2018-04-16 8:18 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-04-13 14:52 [dpdk-dev] DEV_RX_OFFLOAD_SCATTER for ixgbe and igb devices Stokes, Ian
2018-04-13 17:16 ` Ferruh Yigit
2018-04-16 8:18 ` Stokes, Ian
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).