From: Jakub Kicinski <kuba@kernel.org>
To: Wen Gu <guwen@linux.alibaba.com>
Cc: Ido Schimmel <idosch@idosch.org>,
wenjia@linux.ibm.com, jaka@linux.ibm.com, davem@davemloft.net,
edumazet@google.com, pabeni@redhat.com,
alibuda@linux.alibaba.com, tonylu@linux.alibaba.com,
linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
netdev@vger.kernel.org, danieller@nvidia.com
Subject: Re: [PATCH net-next v2 1/2] net/smc: introduce statistics for allocated ringbufs of link group
Date: Wed, 14 Aug 2024 07:48:26 -0700 [thread overview]
Message-ID: <20240814074826.38f211e9@kernel.org> (raw)
In-Reply-To: <586beba2-a632-4fe3-9fb5-e118af384204@linux.alibaba.com>
On Wed, 14 Aug 2024 11:12:41 +0800 Wen Gu wrote:
> > Danielle added one to libmnl:
> >
> > https://git.netfilter.org/libmnl/commit/?id=102942be401a99943b2c68981b238dadfa788f2d
> >
> > Intention is to use it in ethtool once it appears in a released version
> > of libmnl.
>
> Thanks, that is a good example.
FWIW - technically the kernel version of a uint / sint are only either
32b or 64b, because smaller types get padded to 4bytes in netlink
messages, anyway. But doesn't hurt for the get. For the put make sure
you don't narrow down too much.
next prev parent reply other threads:[~2024-08-14 14:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-07 7:59 [PATCH net-next v2 0/2] net/smc: introduce ringbufs usage statistics Wen Gu
2024-08-07 7:59 ` [PATCH net-next v2 1/2] net/smc: introduce statistics for allocated ringbufs of link group Wen Gu
2024-08-13 0:41 ` Jakub Kicinski
2024-08-13 9:55 ` Wen Gu
2024-08-13 14:40 ` Jakub Kicinski
2024-08-13 15:13 ` Ido Schimmel
2024-08-14 3:12 ` Wen Gu
2024-08-14 14:48 ` Jakub Kicinski [this message]
2024-08-15 6:51 ` Wen Gu
2024-08-14 3:10 ` Wen Gu
2024-08-14 14:50 ` Jakub Kicinski
2024-08-07 7:59 ` [PATCH net-next v2 2/2] net/smc: introduce statistics for ringbufs usage of net namespace Wen Gu
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=20240814074826.38f211e9@kernel.org \
--to=kuba@kernel.org \
--cc=alibuda@linux.alibaba.com \
--cc=danieller@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=guwen@linux.alibaba.com \
--cc=idosch@idosch.org \
--cc=jaka@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tonylu@linux.alibaba.com \
--cc=wenjia@linux.ibm.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).