From: Joe Damato <jdamato@fastly.com>
To: admiyo@os.amperecomputing.com
Cc: 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: Tue, 17 Dec 2024 11:04:04 -0800 [thread overview]
Message-ID: <Z2HLJD8z3wFNvnlV@LQ3V64L9R2> (raw)
In-Reply-To: <20241217182528.108062-2-admiyo@os.amperecomputing.com>
On Tue, Dec 17, 2024 at 01:25:28PM -0500, admiyo@os.amperecomputing.com wrote:
> From: Adam Young <admiyo@os.amperecomputing.com>
>
> Implementation of network driver for
> Management Control Transport Protocol(MCTP) over
> Platform Communication Channel(PCC)
>
> DMTF DSP:0292
> https://www.dmtf.org/sites/default/files/standards/documents/DSP0292_1.0.0WIP50.pdf
>
> MCTP devices are specified by entries in DSDT/SDST and
> reference channels specified in the PCCT.
>
> Communication with other devices use the PCC based
> doorbell mechanism.
>
> Signed-off-by: Adam Young <admiyo@os.amperecomputing.com>
> ---
> drivers/net/mctp/Kconfig | 13 ++
> drivers/net/mctp/Makefile | 1 +
> drivers/net/mctp/mctp-pcc.c | 320 ++++++++++++++++++++++++++++++++++++
> 3 files changed, 334 insertions(+)
> create mode 100644 drivers/net/mctp/mctp-pcc.c
[...]
> --- /dev/null
> +++ b/drivers/net/mctp/mctp-pcc.c
> @@ -0,0 +1,320 @@
[...]
> +static void mctp_pcc_client_rx_callback(struct mbox_client *c, void *buffer)
> +{
> + struct mctp_pcc_ndev *mctp_pcc_ndev;
> + struct mctp_pcc_hdr mctp_pcc_hdr;
> + struct pcpu_dstats *dstats;
> + struct mctp_skb_cb *cb;
> + struct sk_buff *skb;
> + void *skb_buf;
> + u32 data_len;
> +
> + mctp_pcc_ndev = container_of(c, struct mctp_pcc_ndev, inbox.client);
> + memcpy_fromio(&mctp_pcc_hdr, mctp_pcc_ndev->inbox.chan->shmem,
> + sizeof(struct mctp_pcc_hdr));
> + data_len = mctp_pcc_hdr.length + MCTP_HEADER_LENGTH;
> + skb = netdev_alloc_skb(mctp_pcc_ndev->mdev.dev, data_len);
> +
> + dstats = this_cpu_ptr(mctp_pcc_ndev->mdev.dev->dstats);
> + u64_stats_update_begin(&dstats->syncp);
> + if (data_len > mctp_pcc_ndev->mdev.dev->mtu) {
> + u64_stats_inc(&dstats->rx_drops);
> + u64_stats_inc(&dstats->rx_drops);
Double counting rx_drops ?
> + 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.
[...]
> +
> +static netdev_tx_t mctp_pcc_tx(struct sk_buff *skb, struct net_device *ndev)
> +{
> + struct mctp_pcc_ndev *mpnd = netdev_priv(ndev);
> + struct mctp_pcc_hdr *mctp_pcc_header;
> + struct pcpu_dstats *dstats;
> + void __iomem *buffer;
> + unsigned long flags;
> + int len = skb->len;
> +
> + dstats = this_cpu_ptr(ndev->dstats);
> + u64_stats_update_begin(&dstats->syncp);
> + u64_stats_inc(&dstats->tx_packets);
> + u64_stats_add(&dstats->tx_bytes, skb->len);
> + u64_stats_update_end(&dstats->syncp);
Likewise, as above with the helpers from include/linux/netdevice.h:
dev_dstats_tx_add( ... );
dev_dstats_tx_dropped( ... );
But, I'll let Jeremy weigh-in to make sure I've not misspoken.
[...]
> +
> +static void mctp_pcc_setup(struct net_device *ndev)
^^ nit: double space ?
[...]
> +static acpi_status lookup_pcct_indices(struct acpi_resource *ares,
> + void *context)
> +{
> + struct mctp_pcc_lookup_context *luc = context;
^^ nit: double space?
[...]
> +static int mctp_pcc_driver_add(struct acpi_device *acpi_dev)
> +{
[...]
> +
> + rc = devm_add_action_or_reset(dev, mctp_cleanup_netdev, ndev);
^^ nit: double space
next prev parent reply other threads:[~2024-12-17 19:04 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 [this message]
2024-12-18 0:09 ` Jeremy Kerr
2024-12-18 16:23 ` Adam Young
2024-12-18 18:17 ` Joe Damato
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=Z2HLJD8z3wFNvnlV@LQ3V64L9R2 \
--to=jdamato@fastly.com \
--cc=Jonathan.Cameron@huawei.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