From: Alejandro Lucero Palau <alucerop@amd.com>
To: Dave Jiang <dave.jiang@intel.com>,
alejandro.lucero-palau@amd.com, linux-cxl@vger.kernel.org,
netdev@vger.kernel.org, djbw@kernel.org, edward.cree@amd.com,
davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com
Subject: Re: [PATCH v27 5/5] sfc: support pio mapping based on cxl
Date: Wed, 10 Jun 2026 06:50:58 +0100 [thread overview]
Message-ID: <4b2a5d1b-632f-4685-91e2-4976d679b186@amd.com> (raw)
In-Reply-To: <5f3911d5-da9a-4ad7-a42d-765b27f3dfa0@intel.com>
On 6/9/26 23:18, Dave Jiang wrote:
>
> On 6/9/26 2:57 PM, alejandro.lucero-palau@amd.com wrote:
>> From: Alejandro Lucero <alucerop@amd.com>
>>
>> A PIO buffer is a region of device memory to which the driver can write a
>> packet for TX, with the device handling the transmit doorbell without
>> requiring a DMA for getting the packet data, which helps reducing latency
>> in certain exchanges. With CXL mem protocol this latency can be lowered
>> further.
>>
>> With a device supporting CXL and successfully initialised, use the cxl
>> region to map the memory range and use this mapping for PIO buffers.
>>
>> Add the disabling of those CXL-based PIO buffers if the callback for
>> potential cxl endpoint removal by the CXL core happens.
> ^ This seems to be missing?
Yes, this comes from v26. That is not happening anymore and I forgot to
remove the reference.
<snip>
>> + /* Set up the WC mapping */
>> +
>> +#ifdef CONFIG_SFC_CXL
>> + probe_data = container_of(efx, struct efx_probe_data, efx);
>> + if ((nic_data->datapath_caps3 &
>> + (1 << MC_CMD_GET_CAPABILITIES_V7_OUT_CXL_CONFIG_ENABLE_LBN)) &&
>> + probe_data->cxl_pio_initialised) {
>> + /* Using PIO through CXL mapping */
>> + nic_data->pio_write_base = probe_data->cxl->ctpio_cxl;
>> + nic_data->pio_write_vi_base = pio_write_vi_base;
>> +
>> + probe_data->cxl_pio_in_use = true;
> Don't think this is used anywhere.
>
> DJ
Right again and same reason: this is not needed anymore.
I will fix it.
Thanks!
<snip>
prev parent reply other threads:[~2026-06-10 5:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 21:57 [PATCH v27 0/5] Type2 device basic support alejandro.lucero-palau
2026-06-09 21:57 ` [PATCH v27 1/5] sfc: add cxl support alejandro.lucero-palau
2026-06-09 21:57 ` [PATCH v27 2/5] cxl/sfc: Map cxl regs alejandro.lucero-palau
2026-06-09 21:57 ` [PATCH v27 3/5] cxl/sfc: Initialize dpa without a mailbox alejandro.lucero-palau
2026-06-09 23:24 ` Dan Williams (nvidia)
2026-06-10 6:03 ` Alejandro Lucero Palau
2026-06-09 21:57 ` [PATCH v27 4/5] sfc: obtain and map cxl range using devm_cxl_probe_mem alejandro.lucero-palau
2026-06-09 21:58 ` Dave Jiang
2026-06-10 5:48 ` Alejandro Lucero Palau
2026-06-09 23:30 ` Dan Williams (nvidia)
2026-06-10 6:10 ` Alejandro Lucero Palau
2026-06-10 13:56 ` Alejandro Lucero Palau
2026-06-15 14:47 ` Alejandro Lucero Palau
2026-06-09 21:57 ` [PATCH v27 5/5] sfc: support pio mapping based on cxl alejandro.lucero-palau
2026-06-09 22:18 ` Dave Jiang
2026-06-10 5:50 ` Alejandro Lucero Palau [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=4b2a5d1b-632f-4685-91e2-4976d679b186@amd.com \
--to=alucerop@amd.com \
--cc=alejandro.lucero-palau@amd.com \
--cc=dave.jiang@intel.com \
--cc=davem@davemloft.net \
--cc=djbw@kernel.org \
--cc=edumazet@google.com \
--cc=edward.cree@amd.com \
--cc=kuba@kernel.org \
--cc=linux-cxl@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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