[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230418205023.414275ab@kernel.org>
Date: Tue, 18 Apr 2023 20:50:23 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Hangbin Liu <liuhangbin@...il.com>
Cc: netdev@...r.kernel.org, Jay Vosburgh <j.vosburgh@...il.com>,
"David S . Miller" <davem@...emloft.net>,
Paolo Abeni <pabeni@...hat.com>,
Eric Dumazet <edumazet@...gle.com>,
Liang Li <liali@...hat.com>,
Simon Horman <simon.horman@...igine.com>,
Miroslav Lichvar <mlichvar@...hat.com>
Subject: Re: [PATCHv5 net-next] bonding: add software tx timestamping
support
On Tue, 18 Apr 2023 11:48:41 +0800 Hangbin Liu wrote:
> Currently, bonding only obtain the timestamp (ts) information of
> the active slave, which is available only for modes 1, 5, and 6.
> For other modes, bonding only has software rx timestamping support.
>
> However, some users who use modes such as LACP also want tx timestamp
> support. To address this issue, let's check the ts information of each
> slave. If all slaves support tx timestamping, we can enable tx
> timestamping support for the bond.
>
> Add a note that the get_ts_info may be called with RCU, or rtnl or
> reference on the device in ethtool.h>
>
> Suggested-by: Miroslav Lichvar <mlichvar@...hat.com>
> Signed-off-by: Hangbin Liu <liuhangbin@...il.com>
> ---
> v5: remove ASSERT_RTNL since bond_ethtool_get_ts_info could be called
> without RTNL. Update ethtool kdoc.
I'll apply Jay's ack from v4 since these are not substantial changes.
Thanks!
Powered by blists - more mailing lists