From: Hangbin Liu <liuhangbin@gmail.com>
To: netdev@vger.kernel.org
Cc: Jay Vosburgh <j.vosburgh@gmail.com>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Jonathan Toppins <jtoppins@redhat.com>,
Paolo Abeni <pabeni@redhat.com>,
Eric Dumazet <edumazet@google.com>,
Miroslav Lichvar <mlichvar@redhat.com>,
Richard Cochran <richardcochran@gmail.com>,
Hangbin Liu <liuhangbin@gmail.com>
Subject: [PATCH net-next] bonding: add software timestamping support
Date: Wed, 29 Mar 2023 11:13:37 +0800 [thread overview]
Message-ID: <20230329031337.3444547-1-liuhangbin@gmail.com> (raw)
At present, bonding attempts to obtain the timestamp (ts) information of
the active slave. However, this feature is only available for mode 1, 5,
and 6. For other modes, bonding doesn't even provide support for software
timestamping. To address this issue, let's call ethtool_op_get_ts_info
when there is no primary active slave. This will enable the use of software
timestamping for the bonding interface.
Signed-off-by: Hangbin Liu <liuhangbin@gmail.com>
---
drivers/net/bonding/bond_main.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/net/bonding/bond_main.c b/drivers/net/bonding/bond_main.c
index 00646aa315c3..f0856bec59f5 100644
--- a/drivers/net/bonding/bond_main.c
+++ b/drivers/net/bonding/bond_main.c
@@ -5709,9 +5709,7 @@ static int bond_ethtool_get_ts_info(struct net_device *bond_dev,
}
}
- info->so_timestamping = SOF_TIMESTAMPING_RX_SOFTWARE |
- SOF_TIMESTAMPING_SOFTWARE;
- info->phc_index = -1;
+ ret = ethtool_op_get_ts_info(bond_dev, info);
out:
dev_put(real_dev);
--
2.38.1
next reply other threads:[~2023-03-29 3:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-29 3:13 Hangbin Liu [this message]
2023-03-29 3:36 ` [PATCH net-next] bonding: add software timestamping support Jay Vosburgh
2023-03-30 4:01 ` Hangbin Liu
2023-03-30 4:39 ` Jay Vosburgh
2023-03-29 10:27 ` Miroslav Lichvar
2023-03-30 3:33 ` Hangbin Liu
2023-03-30 4:07 ` Jakub Kicinski
2023-03-30 4:12 ` Jay Vosburgh
2023-03-31 3:32 ` Hangbin Liu
2023-04-03 10:18 ` Miroslav Lichvar
2023-04-05 9:04 ` Hangbin Liu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230329031337.3444547-1-liuhangbin@gmail.com \
--to=liuhangbin@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=j.vosburgh@gmail.com \
--cc=jtoppins@redhat.com \
--cc=kuba@kernel.org \
--cc=mlichvar@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).