DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Medvedkin, Vladimir" <vladimir.medvedkin@intel.com>
To: David Marchand <david.marchand@redhat.com>
Cc: <dev@dpdk.org>, <rjarry@redhat.com>, <mb@smartsharesystems.com>,
	"Stephen Hemminger" <stephen@networkplumber.org>
Subject: Re: [PATCH v2] fib: network byte order IPv4 lookup
Date: Thu, 10 Oct 2024 12:19:32 +0100	[thread overview]
Message-ID: <5aae76fd-ac22-4ed0-9728-e898e8295517@intel.com> (raw)
In-Reply-To: <CAJFAV8xUOs_oVWaYPzZ5BMrrP8qt_sMFY53dYpEVk0m9p2+ZDA@mail.gmail.com>

Hi David,

On 09/10/2024 11:56, David Marchand wrote:
> On Wed, Oct 9, 2024 at 11:51 AM David Marchand
> <david.marchand@redhat.com> wrote:
>> Hi Vladimir,
>>
>> On Tue, Oct 8, 2024 at 7:16 PM Vladimir Medvedkin
>> <vladimir.medvedkin@intel.com> wrote:
>>> diff --git a/lib/fib/dir24_8_avx512.c b/lib/fib/dir24_8_avx512.c
>>> index 43dba28cfb..edd802abe4 100644
>>> --- a/lib/fib/dir24_8_avx512.c
>>> +++ b/lib/fib/dir24_8_avx512.c
>>> @@ -10,7 +10,7 @@
>>>
>>>   static __rte_always_inline void
>>>   dir24_8_vec_lookup_x16(void *p, const uint32_t *ips,
>>> -       uint64_t *next_hops, int size)
>>> +       uint64_t *next_hops, int size, bool be_addr)
>>>   {
>>>          struct dir24_8_tbl *dp = (struct dir24_8_tbl *)p;
>>>          __mmask16 msk_ext;
>>> @@ -28,6 +28,16 @@ dir24_8_vec_lookup_x16(void *p, const uint32_t *ips,
>>>                  res_msk = _mm512_set1_epi32(UINT16_MAX);
>>>
>>>          ip_vec = _mm512_loadu_si512(ips);
>>> +       if (be_addr) {
>>> +               const __m512i bswap32 = _mm512_set_epi8(
>> Some toolchains do not like _mm512_set_epi8 (reported by the CI).
> Probably related to gcc commit 4e6a811fad69 ("avx512fintrin.h
> (_mm512_set_epi16, [...]): New intrinsics.") introduced in gcc 9.
> Some distributions in the CI come with a gcc < 9.
>
> We had a similar situation in the hash library in the past,
> fba335b4b204 ("hash: fix Toeplitz hash implementation").
>
Thanks, I'll change it with _mm512_set_epi32(), afaik it should be 
supported by an old gcc

-- 
Regards,
Vladimir


  reply	other threads:[~2024-10-10 11:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-08 17:16 Vladimir Medvedkin
2024-10-08 21:26 ` Stephen Hemminger
2024-10-09  9:51 ` David Marchand
2024-10-09 10:56   ` David Marchand
2024-10-10 11:19     ` Medvedkin, Vladimir [this message]
2024-10-09 18:31 ` Stephen Hemminger
  -- strict thread matches above, loose matches on Subject: below --
2024-09-06 17:06 [PATCH] " Vladimir Medvedkin
2024-10-08 17:33 ` [PATCH v2] " Vladimir Medvedkin

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=5aae76fd-ac22-4ed0-9728-e898e8295517@intel.com \
    --to=vladimir.medvedkin@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=mb@smartsharesystems.com \
    --cc=rjarry@redhat.com \
    --cc=stephen@networkplumber.org \
    /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;
as well as URLs for NNTP newsgroup(s).