> On Feb 2, 2024, at 11:24 PM, Stephen Hemminger
> wrote:
>
> Caution: This message originated from an External Source. Use proper caution
> when opening attachments, clicking links, or responding.
>
>
> On Fri, 2 Feb 2024 11:32:26 -0800
> Andrew Boyer wrote:
>
>> When completion coalesc
> On Feb 2, 2024, at 11:28 PM, Stephen Hemminger
> wrote:
>
> Caution: This message originated from an External Source. Use proper caution
> when opening attachments, clicking links, or responding.
>
>
> On Fri, 2 Feb 2024 11:32:38 -0800
> Andrew Boyer wrote:
>
>> + memset(ctx, 0, si
> On Feb 2, 2024, at 11:26 PM, Stephen Hemminger
> wrote:
>
> Caution: This message originated from an External Source. Use proper caution
> when opening attachments, clicking links, or responding.
>
>
> On Fri, 2 Feb 2024 11:32:29 -0800
> Andrew Boyer wrote:
>
>> From: Neel Patel
>>
>
I see that cnxk has added inline assembly for the ARM "dsb st" barrier. We,
too, would like to add a use of this instruction. Can a helper function be
added to the atomics headers?
> drivers/ml/cnxk/cn10k_ml_dev.h:#define dsb_st ({ asm volatile("dsb st" : : :
> "memory"); })
What would the hel
On Feb 5, 2024, at 1:44 PM, Patrick Robb wrote:
Caution: This message originated from an External Source. Use proper caution
when opening attachments, clicking links, or responding.
Recheck-request: iol-intel-Functional
I saw this failed in CI testing for the DTS MTU_Update test but suspect
On Feb 6, 2024, at 9:24 PM, Morten Brørup wrote:
Caution: This message originated from an External Source. Use proper caution
when opening attachments, clicking links, or responding.
From: Akhil Goyal [mailto:gak...@marvell.com]
Sent: Tuesday, 6 February 2024 15.25
Cache the most recent VA
On Feb 19, 2024, at 10:24 AM, Yigit, Ferruh wrote:
On 2/16/2024 5:07 PM, Andrew Boyer wrote:
Add support for running DPDK applications directly on AMD Pensando
embedded HW. The platform exposes the device BARs through UIO. The
UIO code in the common/ionic library walks the sysfs filesystem
to i
On Feb 19, 2024, at 9:02 PM, Wathsala Wathawana Vithanage
wrote:
Caution: This message originated from an External Source. Use proper caution
when opening attachments, clicking links, or responding.
-Original Message-
From: Wathsala Wathawana Vithanage
mailto:wathsala.vithan...@arm
On Feb 19, 2024, at 9:02 PM, Honnappa Nagarahalli
wrote:
Caution: This message originated from an External Source. Use proper caution
when opening attachments, clicking links, or responding.
On Feb 16, 2024, at 11:07 AM, Andrew Boyer wrote:
Add support for running DPDK applications direct
> On Feb 22, 2024, at 1:40 PM, Boyer, Andrew wrote:
>
> This patchset introduces a new crypto PMD for AMD Pensando hardware
> accelerators. It allows applications running directly on the AMD Pensando
> DSC to offload cryptographic operations to hardware cryptographic blocks.
On Jan 24, 2024, at 12:16 PM, Jeremy Spewock wrote:
Hello maintainers,
In porting over the first ethdev suite to the new DTS framework, there was an
inconsistency that we found and we were wondering if anyone would be able to
shed some light on this. In general the inconsistency pertains to
On Apr 19, 2024, at 3:53 PM, Boyer, Andrew wrote:
diff --git a/drivers/crypto/ionic/ionic_crypto_main.c
b/drivers/crypto/ionic/ionic_crypto_main.c
new file mode 100644
index 00..7b26080bd1
--- /dev/null
+++ b/drivers/crypto/ionic/ionic_crypto_main.c
@@ -0,0 +1,42 @@
+/* SPDX-License
> On Apr 30, 2024, at 4:21 PM, Boyer, Andrew wrote:
>
> This patchset introduces a new crypto PMD for AMD Pensando hardware
> accelerators. It allows applications running directly on the AMD Pensando
> DSC to offload cryptographic operations to hardware cryptographic blocks.
>
> On Jun 4, 2024, at 9:28 AM, Boyer, Andrew wrote:
>
>
>> On Apr 30, 2024, at 4:21 PM, Boyer, Andrew wrote:
>>
>> This patchset introduces a new crypto PMD for AMD Pensando hardware
>> accelerators. It allows applications running directly on the AMD Pensand
> On Jun 1, 2024, at 9:57 AM, Akhil Goyal wrote:
>
> Caution: This message originated from an External Source. Use proper caution
> when opening attachments, clicking links, or responding.
>
>
>> Subject: [EXTERNAL] [PATCH v2 3/9] crypto/ionic: add device commands
>>
>> This defines the dev
On May 30, 2024, at 8:02 AM, Akhil Goyal wrote:
diff --git a/drivers/common/ionic/ionic_common_uio.c
b/drivers/common/ionic/ionic_common_uio.c
index e5c73faf96..c647b22eaf 100644
--- a/drivers/common/ionic/ionic_common_uio.c
+++ b/drivers/common/ionic/ionic_common_uio.c
@@ -23,10 +23,12 @@
#de
> On Jun 13, 2024, at 6:07 AM, Akhil Goyal wrote:
>
> Caution: This message originated from an External Source. Use proper caution
> when opening attachments, clicking links, or responding.
>
>
>> diff --git a/drivers/crypto/ionic/meson.build
>> b/drivers/crypto/ionic/meson.build
>> new fil
Hello John,
While Coverity is correct that this is a useless call, that's an internal
implementation detail of rte_bitmap_free() - not really something the caller
should know about.
Can we annotate rte_bitmap_free() in some way to eliminate these? This is not
the first PMD that's had this issue
> On Mar 11, 2025, at 11:51 AM, Stephen Hemminger
> wrote:
>
> Caution: This message originated from an External Source. Use proper caution
> when opening attachments, clicking links, or responding.
>
>
> The expression *dev->intf->setup_bars and dev->intf->setup_bars
> are equivalent.
>
>
19 matches
Mail list logo
