[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-netdev
Subject:    RE: [EXT] Re: [PATCH v2 1/1] net: fec: add initial XDP support
From:       Shenwei Wang <shenwei.wang () nxp ! com>
Date:       2022-10-31 21:17:19
Message-ID: PAXPR04MB9185FC004E87082B04CB8A0D89379 () PAXPR04MB9185 ! eurprd04 ! prod ! outlook ! com
[Download RAW message or body]



> -----Original Message-----
> From: Andrew Lunn <andrew@lunn.ch>
> Sent: Monday, October 31, 2022 3:17 PM
> > > to disable the receiver, wait for it to indicate it really has
> > > stopped, and only then make these modifications.
> > >
> >
> > Sounds reasonable. How about moving the codes of updating ring size to
> > the place right after the enet reset inside the fec_restart? This
> > should clear those risky corner cases.
> 
> That sounds reasonable. But please add some comments. The driver has
> RX_RING_SIZE elements allocated, but you are only using a subset. This needs to
> be clear for when somebody implements the ethtool --rings option.
> 

The latest performance data regarding the native XDP has got improved a lot. The ring 
size change doesn't seem necessary any more. The v3 patch has removed that part
of codes, and that logic can be added back in future if necessary as well as the ethtool -rings option.

Thanks,
Shenwei

> And i still think it would be good to implement that code. As your numbers show,
> the ring size does affect performance, and it is hard to know if your hard coded
> XDP_RX_RING_SIZE is the right value, depending on what the eBPF program is
> doing. If the ethtool option was provided, it allows users to benchmark different
> ring sizes for their workload.
> 
>    Andrew
[prev in list] [next in list] [prev in thread] [next in thread]