From: Joe Damato <jdamato@fastly.com>
To: Adam Young <admiyo@amperemail.onmicrosoft.com>
Cc: admiyo@os.amperecomputing.com,
Jeremy Kerr <jk@codeconstruct.com.au>,
Matt Johnston <matt@codeconstruct.com.au>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Sudeep Holla <sudeep.holla@arm.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Huisong Li <lihuisong@huawei.com>
Subject: Re: [PATCH v9 1/1] mctp pcc: Implement MCTP over PCC Transport
Date: Wed, 18 Dec 2024 10:17:06 -0800 [thread overview]
Message-ID: <Z2MRouOBizgKt-h_@LQ3V64L9R2> (raw)
In-Reply-To: <7bfb8a48-8a14-47cb-bd69-1d864535aeba@amperemail.onmicrosoft.com>
On Wed, Dec 18, 2024 at 11:23:06AM -0500, Adam Young wrote:
>
> On 12/17/24 14:04, Joe Damato wrote:
[...]
> >
> > > + u64_stats_update_end(&dstats->syncp);
> > > + return;
> > > + }
> > > + if (!skb) {
> > > + u64_stats_inc(&dstats->rx_drops);
> > > + u64_stats_update_end(&dstats->syncp);
> > > + return;
> > > + }
> > > + u64_stats_inc(&dstats->rx_packets);
> > > + u64_stats_add(&dstats->rx_bytes, data_len);
> > > + u64_stats_update_end(&dstats->syncp);
> > I suspect what Jeremy meant (but please feel free to correct me if
> > I'm mistaken, Jeremy) was that you may want to use the helpers in:
> >
> > include/linux/netdevice.h
> >
> > e.g.
> >
> > dev_dstats_rx_add(mctp_pcc_ndev->mdev.dev, data_len);
> > dev_dstats_rx_dropped(mctp_pcc_ndev->mdev.dev);
> >
> > etc.
>
> I don't see those function calls in the 6.13-rc3 tree I am working with.
> Are they coming later?
If you are adding new code you should target net-next/main, which
has commit 18eabadd73ae ("vrf: Make pcpu_dstats update functions
available to other modules.") which adds those functions.
Have you rebased recently? Maybe your local clone of the tree is
stale?
FWIW: you can use `git format-patch --base=auto ...` to include base
tree information which can be helpful for identifying issues like
the above.
prev parent reply other threads:[~2024-12-18 18:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-17 18:25 [PATCH v9 0/1] MCTP Over PCC Transport admiyo
2024-12-17 18:25 ` [PATCH v9 1/1] mctp pcc: Implement MCTP over " admiyo
2024-12-17 19:04 ` Joe Damato
2024-12-18 0:09 ` Jeremy Kerr
2024-12-18 16:23 ` Adam Young
2024-12-18 18:17 ` Joe Damato [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=Z2MRouOBizgKt-h_@LQ3V64L9R2 \
--to=jdamato@fastly.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=admiyo@amperemail.onmicrosoft.com \
--cc=admiyo@os.amperecomputing.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jk@codeconstruct.com.au \
--cc=kuba@kernel.org \
--cc=lihuisong@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeconstruct.com.au \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sudeep.holla@arm.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