Message ID | 1604892159-19990-1-git-send-email-tanhuazhong@huawei.com |
---|---|
Headers | show |
Series | net: hns3: updates for -next | expand |
On Mon, 9 Nov 2020 11:22:29 +0800 Huazhong Tan wrote: > + if (rx_vector->tx_group.coal.ql_enable) ^^^^^^^^ Is this supposed to be rx_group, not tx? > + hns3_set_vector_coalesce_rx_ql(rx_vector, > + rx_vector->rx_group.coal.int_ql);
On 2020/11/11 9:13, Jakub Kicinski wrote: > On Mon, 9 Nov 2020 11:22:29 +0800 Huazhong Tan wrote: >> + if (rx_vector->tx_group.coal.ql_enable) > ^^^^^^^^ > > Is this supposed to be rx_group, not tx? > yes, will fix it. thanks. >> + hns3_set_vector_coalesce_rx_ql(rx_vector, >> + rx_vector->rx_group.coal.int_ql); > > . >
On Mon, 9 Nov 2020 11:22:33 +0800 Huazhong Tan wrote: > Add dynamic interrupt moderation support for the HNS3 driver. > > Signed-off-by: Huazhong Tan <tanhuazhong@huawei.com> I'm slightly confused here. What does the adaptive moderation do in your driver/device if you still need DIM on top of it?
On 2020/11/11 9:20, Jakub Kicinski wrote: > On Mon, 9 Nov 2020 11:22:33 +0800 Huazhong Tan wrote: >> Add dynamic interrupt moderation support for the HNS3 driver. >> >> Signed-off-by: Huazhong Tan <tanhuazhong@huawei.com> > > I'm slightly confused here. What does the adaptive moderation do in > your driver/device if you still need DIM on top of it? > The driver's adaptive moderation and DIM are mutually-exclusive options, and DIM is used by default. Since it is hard to verify all cases that DIM can get a better result, so keep the adaptive moderation as an option now, which can be swicthed by the ethtool priv-flag. If DIM is ok for a long time, then we will send a separate patch to remove the adaptive moderation from the driver. Thanks. >