From: Adam Young <admiyo@amperemail.onmicrosoft.com>
To: "lihuisong (C)" <lihuisong@huawei.com>, admiyo@os.amperecomputing.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Jeremy Kerr <jk@codeconstruct.com.au>,
Matt Johnston <matt@codeconstruct.com.au>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>, Len Brown <lenb@kernel.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Robert Moore <robert.moore@intel.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Jassi Brar <jassisinghbrar@gmail.com>,
Sudeep Holla <sudeep.holla@arm.com>
Subject: Re: [PATCH v6 1/2] mctp pcc: Check before sending MCTP PCC response ACK
Date: Mon, 4 Nov 2024 13:44:28 -0500 [thread overview]
Message-ID: <fb13bbc9-9afb-4c69-bbd6-354db395813e@amperemail.onmicrosoft.com> (raw)
In-Reply-To: <6eba7c8b-000f-7be0-4a8a-53bf8d6dc25f@huawei.com>
On 11/3/24 22:17, lihuisong (C) wrote:
>>
>> I could make a further change and allow the driver to request the
>> remapped memory segment from the pcc layer, and couple to the
>> memory-remap to the client/channel. It seems like that code, too,
>> should be in the common layer. However most drivers would not know
>> to use this function yet, so the mechanism would have to be
>> optional, and only clean up if called this way.
> I agree this method.
> Don't remap twice for one shared memory.
> This remaping is reasonable in PCC layer. We can let PCC client to
> decide if PCC layer does remap and then they use it directly.
> For new driver like the driver you are uploading, driver can give PCC
> one flag to tell PCC layer remap when request channel.
> For old PCC client driver, do not send this flag, PPC layer do not
> remap. So no any impact on them.
I think we are actually in agreement here. No double mapping, but the
driver MAY request the mapping happen in the PCC layer. No impact on
existing drivers.
next prev parent reply other threads:[~2024-11-04 18:44 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 PCC Transport 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 [this message]
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
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=fb13bbc9-9afb-4c69-bbd6-354db395813e@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=jassisinghbrar@gmail.com \
--cc=jk@codeconstruct.com.au \
--cc=kuba@kernel.org \
--cc=lenb@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=rafael.j.wysocki@intel.com \
--cc=robert.moore@intel.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®