mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Adam Young <admiyo@amperemail.onmicrosoft.com>
To: Jeremy Kerr <jk@codeconstruct.com.au>,
	admiyo@os.amperecomputing.com,
	Matt Johnston <matt@codeconstruct.com.au>,
	"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: [PATCH v6 2/2] mctp pcc: Implement MCTP over PCC Transport
Date: Tue, 5 Nov 2024 15:16:20 -0500	[thread overview]
Message-ID: <693f39f9-9505-4135-91db-a7280570fbc3@amperemail.onmicrosoft.com> (raw)
In-Reply-To: <675c2760e1ed64ee8e8bcd82c74af764d48fea6c.camel@codeconstruct.com.au>


On 11/1/24 04:55, Jeremy Kerr wrote:
> Just to clarify that: for physical (ie, null-EID) addressing, you don't
> need the hardware address, you need:
>
>   1) the outgoing interface's ifindex; and
>   2) the hardware address of the*remote*  endpoint, in whatever
>      format is appropriate for link type


So Here is what I was thinking:

Lets ignore the namespace for now, as that is a future-proofing thing 
and will be all 0.  If The OS listens on index 11 and the PLatform 
listens index 22, the HW address for the OS would be

00001122

and for the Platform

00002211

This is all the info  for the calling application to know both the 
ifindex and the remote endpoint.

They can re-order the address to 00002211 for the remote endpoint.  If 
they have the link they have the ifindex.  It seems like a clean solution.

Adding the inbox id ( to the HW address does not harm anything, and it 
makes things much more explicit.

It seems like removing either the inbox or the outbox id from the HW 
address is hiding information that should be exposed.  And the two 
together make up the hardware addressing for the device, just not in 
that exact format, but it maps directly.  That is what will be in the 
upcoming version of the spec as well.


  parent reply	other threads:[~2024-11-05 20:16 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-29 16:54 [PATCH v6 0/2] MCTP Over " admiyo
2024-10-29 16:54 ` [PATCH v6 1/2] mctp pcc: Check before sending MCTP PCC response ACK admiyo
2024-10-30  9:45   ` lihuisong (C)
2024-11-01  0:16     ` Adam Young
2024-11-01  1:30       ` lihuisong (C)
2024-11-02 15:34         ` Adam Young
2024-11-04  3:17           ` lihuisong (C)
2024-11-04 18:44             ` Adam Young
2024-10-29 16:54 ` [PATCH v6 2/2] mctp pcc: Implement MCTP over PCC Transport admiyo
2024-10-31  1:28   ` Jeremy Kerr
2024-10-31 15:50     ` Adam Young
2024-11-01  8:55       ` Jeremy Kerr
2024-11-01 21:19         ` Adam Young
2024-11-05 14:09           ` Jeremy Kerr
2024-11-06 15:59             ` Adam Young
2024-11-12  1:00               ` Jeremy Kerr
2024-11-13 18:41                 ` Adam Young
2024-11-05 20:16         ` Adam Young [this message]
2024-11-06 10:47           ` Jeremy Kerr
2024-10-31 11:26   ` kernel test robot
2024-10-31 12:07   ` kernel test robot
2024-10-31 12:38   ` kernel test robot
2024-10-31 13:09   ` kernel test robot

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=693f39f9-9505-4135-91db-a7280570fbc3@amperemail.onmicrosoft.com \
    --to=admiyo@amperemail.onmicrosoft.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=admiyo@os.amperecomputing.com \
    --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

all inboxes | Powered by JetHome®