From: Jeremy Kerr <jk@codeconstruct.com.au>
To: Adam Young <admiyo@amperemail.onmicrosoft.com>,
Adam Young <admiyo@os.amperecomputing.com>,
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>
Cc: 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: [net-next v41] mctp pcc: Implement MCTP over PCC Transport
Date: Wed, 13 May 2026 09:22:56 +0800 [thread overview]
Message-ID: <f770a0af82fce258aa3d6866d00f5a6bd1a97f47.camel@codeconstruct.com.au> (raw)
In-Reply-To: <aecf0ac6-0dcc-4b7c-bcd7-dd78082161a0@amperemail.onmicrosoft.com>
Hi Adam,
> > Adding the skb_linearize() there is unnecessary, and creates ambiguity
> > about the structure of the skbs that we're dealing with in that path.
> >
> OK, I get it now. I was thinking that the Fragmentation was a likely
> part of the progression, as default MCTP packets are so small.
OK, beware of potential confusion; there are two separate concepts here,
"MCTP fragmentation" and "skbs that have fragments".
"MCTP fragmentation" is implemented by the MCTP core, and splits large
MCTP messages into smaller packets; each packet being a separate skb,
with its own MCTP header.
Your transport driver does not need to care about this; it is only
concerned with transferring those individual skbs.
"skbs that have fragments" refers to the possibility that the data
represented by a skb may be held in scatter-gather format, rather than
(or in addition to) the skb->data buffer.
Your transport driver does not need to care about this either, as it is
not claiming to support fragmented skbs, so all of the skbs that reach
->ndo_start_xmit() will be linear.
> Yeah, I saw those, and was processing through them. I have found
> similar type issues running against Codex.
>
> Some of the issues I found are due to the interactions with the PCC
> layer, and need to be addressed there. It leads to some edge conditions
> that are, for me, impossible to produce right now. There is one change
> it suggests which I thought I had already made.
>
> If those changes are going to cause significatnt changes, I will
> probably also integrate your suggestion on how to deal with IRQ-safe
> stats posting.
OK, sounds good.
Cheers,
Jeremy
prev parent reply other threads:[~2026-05-13 1:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-10 16:32 [net-next v41] mctp pcc: Implement MCTP over PCC Transport Adam Young
2026-05-11 2:19 ` Jeremy Kerr
2026-05-11 14:52 ` Adam Young
2026-05-12 4:07 ` Jeremy Kerr
2026-05-12 16:38 ` Adam Young
2026-05-13 1:22 ` Jeremy Kerr [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=f770a0af82fce258aa3d6866d00f5a6bd1a97f47.camel@codeconstruct.com.au \
--to=jk@codeconstruct.com.au \
--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=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