From: rohit maheshwari <rohitm@chelsio.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, borisp@mellanox.com,
secdev@chelsio.com
Subject: Re: [PATCH net-next] cxgb4/chcr: nic-tls stats in ethtool
Date: Tue, 31 Mar 2020 19:56:31 +0530 [thread overview]
Message-ID: <cad731af-19c0-f16c-0c43-332de5d3dee0@chelsio.com> (raw)
In-Reply-To: <20200322135725.6cdc37a8@kicinski-fedora-PC1C0HJN>
On 23/03/20 2:27 AM, Jakub Kicinski wrote:
> On Sat, 21 Mar 2020 16:53:36 +0530 Rohit Maheshwari wrote:
>> Included nic tls statistics in ethtool stats.
>>
>> Signed-off-by: Rohit Maheshwari <rohitm@chelsio.com>
>> ---
>> .../ethernet/chelsio/cxgb4/cxgb4_ethtool.c | 57 +++++++++++++++++++
>> 1 file changed, 57 insertions(+)
>>
>> diff --git a/drivers/net/ethernet/chelsio/cxgb4/cxgb4_ethtool.c b/drivers/net/ethernet/chelsio/cxgb4/cxgb4_ethtool.c
>> index 398ade42476c..4998f1d1e218 100644
>> --- a/drivers/net/ethernet/chelsio/cxgb4/cxgb4_ethtool.c
>> +++ b/drivers/net/ethernet/chelsio/cxgb4/cxgb4_ethtool.c
>> @@ -134,6 +134,28 @@ static char loopback_stats_strings[][ETH_GSTRING_LEN] = {
>> "bg3_frames_trunc ",
>> };
>>
>> +#ifdef CONFIG_CHELSIO_TLS_DEVICE
>> +struct chcr_tls_stats {
>> + u64 tx_tls_encrypted_packets;
>> + u64 tx_tls_encrypted_bytes;
>> + u64 tx_tls_ctx;
>> + u64 tx_tls_ooo;
>> + u64 tx_tls_skip_no_sync_data;
>> + u64 tx_tls_drop_no_sync_data;
>> + u64 tx_tls_drop_bypass_req;
> I don't understand why you need to have a structure for this, and then
> you memset it to 0, unnecessarily, but I guess that's just a matter of
> taste.
Yeah, this memset is pure stupidity, I'll remove it and this new
structure as well. Thanks for the suggestion.
>> +};
>> +
>> +static char chcr_tls_stats_strings[][ETH_GSTRING_LEN] = {
>> + "tx_tls_encrypted_pkts ",
>> + "tx_tls_encrypted_bytes ",
>> + "tx_tls_ctx ",
>> + "tx_tls_ooo ",
>> + "tx_tls_skip_nosync_data",
>> + "tx_tls_drop_nosync_data",
>> + "tx_tls_drop_bypass_req ",
> These, however, are not correct - please remove the spaces at the end,
> otherwise your names are different than for other vendors. And there is
> an underscore in the middle of "no_sync".
>
> When you're told to adhere to API recommendation, please adhere to it
> exactly.
These spaces are used for alignment, so the statistics will be readable
for end user. As far as I understood, these are minimum set of TLS
related statistics, with or without space it will remain same for end
user. Please let me know if I am interpreting it wrong.
However I agree about the no_sync, I'll change it in my
next patch.
prev parent reply other threads:[~2020-03-31 14:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-21 11:23 [PATCH net-next] cxgb4/chcr: nic-tls stats in ethtool Rohit Maheshwari
2020-03-22 20:57 ` Jakub Kicinski
2020-03-31 14:26 ` rohit maheshwari [this message]
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=cad731af-19c0-f16c-0c43-332de5d3dee0@chelsio.com \
--to=rohitm@chelsio.com \
--cc=borisp@mellanox.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=secdev@chelsio.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).