DPDK patches and discussions
 help / color / mirror / Atom feed
From: Tyler Retzlaff <roretzla@linux.microsoft.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org, "Bruce Richardson" <bruce.richardson@intel.com>,
	"Cristian Dumitrescu" <cristian.dumitrescu@intel.com>,
	"David Hunt" <david.hunt@intel.com>,
	"Honnappa Nagarahalli" <honnappa.nagarahalli@arm.com>,
	"Ruifeng Wang" <ruifeng.wang@arm.com>,
	"Sameh Gobriel" <sameh.gobriel@intel.com>,
	"Vladimir Medvedkin" <vladimir.medvedkin@intel.com>,
	"Yipeng Wang" <yipeng1.wang@intel.com>,
	"Morten Brørup" <mb@smartsharesystems.com>
Subject: Re: [PATCH v3 0/7] use abstracted bit count functions
Date: Wed, 8 Nov 2023 10:42:04 -0800	[thread overview]
Message-ID: <20231108184204.GA21615@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net> (raw)
In-Reply-To: <2526782.TLnPLrj5Ze@thomas>

On Wed, Nov 08, 2023 at 05:57:01PM +0100, Thomas Monjalon wrote:
> 08/11/2023 09:34, Morten Brørup:
> > > From: Tyler Retzlaff [mailto:roretzla@linux.microsoft.com]
> > > Sent: Wednesday, 8 November 2023 00.38
> > > 
> > > The first set of conversions missed the long 'l' versions of the
> > > builtins that were being used. This series completes the conversion
> > > of remaining libraries from __builtin_ctzl, __builtin_clzl and
> > > __builtin_popcountl.
> > > 
> > > v3:
> > >   * add missing include of rte_bitops.h
> > >   * add 2 patches to cover use of __builtin_popcountl
> > > 
> > > v2:
> > >   * be explicit and use appropriate 32-bit and 64-bit leading
> > >     and trailing counting functions depending on the type of the
> > >     expression passed as an argument to the builtin.
> > 
> > Didn't notice v3 before ack'ing v2.
> > 
> > Series-acked-by: Morten Brørup <mb@smartsharesystems.com>
> 
> Squashed and applied, thanks.
> 
> Note: there are few builtin occurences in drivers.

yes, tests and drivers are on my list. i'm mostly addressing conversions
in libs right now.

> 
> 

      reply	other threads:[~2023-11-08 18:42 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-02  1:05 [PATCH 0/5] " Tyler Retzlaff
2023-11-02  1:05 ` [PATCH 1/5] table: " Tyler Retzlaff
2023-11-02  1:05 ` [PATCH 2/5] distributor: " Tyler Retzlaff
2023-11-02  1:05 ` [PATCH 3/5] hash: " Tyler Retzlaff
2023-11-02  1:05 ` [PATCH 4/5] member: " Tyler Retzlaff
2023-11-02  1:05 ` [PATCH 5/5] rcu: " Tyler Retzlaff
2023-11-02  7:39 ` [PATCH 0/5] " Morten Brørup
2023-11-02 15:27   ` Tyler Retzlaff
2023-11-02 15:33     ` Morten Brørup
2023-11-02 15:36       ` Tyler Retzlaff
2023-11-07 19:10 ` [PATCH v2 " Tyler Retzlaff
2023-11-07 19:10   ` [PATCH v2 1/5] distributor: " Tyler Retzlaff
2023-11-07 19:10   ` [PATCH v2 2/5] hash: " Tyler Retzlaff
2023-11-07 19:10   ` [PATCH v2 3/5] member: " Tyler Retzlaff
2023-11-07 19:10   ` [PATCH v2 4/5] rcu: " Tyler Retzlaff
2023-11-07 19:10   ` [PATCH v2 5/5] table: " Tyler Retzlaff
2023-11-08  8:25   ` [PATCH v2 0/5] " Morten Brørup
2023-11-07 23:38 ` [PATCH v3 0/7] " Tyler Retzlaff
2023-11-07 23:38   ` [PATCH v3 1/7] distributor: " Tyler Retzlaff
2023-11-07 23:38   ` [PATCH v3 2/7] hash: " Tyler Retzlaff
2023-11-07 23:38   ` [PATCH v3 3/7] member: " Tyler Retzlaff
2023-11-07 23:38   ` [PATCH v3 4/7] rcu: " Tyler Retzlaff
2023-11-07 23:38   ` [PATCH v3 5/7] table: " Tyler Retzlaff
2023-11-07 23:38   ` [PATCH v3 6/7] distributor: " Tyler Retzlaff
2023-11-07 23:38   ` [PATCH v3 7/7] hash: " Tyler Retzlaff
2023-11-08  8:47     ` CI test system not catching truncation bugs for 32-bit architectures? Morten Brørup
2023-11-08  8:34   ` [PATCH v3 0/7] use abstracted bit count functions Morten Brørup
2023-11-08 16:57     ` Thomas Monjalon
2023-11-08 18:42       ` Tyler Retzlaff [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=20231108184204.GA21615@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net \
    --to=roretzla@linux.microsoft.com \
    --cc=bruce.richardson@intel.com \
    --cc=cristian.dumitrescu@intel.com \
    --cc=david.hunt@intel.com \
    --cc=dev@dpdk.org \
    --cc=honnappa.nagarahalli@arm.com \
    --cc=mb@smartsharesystems.com \
    --cc=ruifeng.wang@arm.com \
    --cc=sameh.gobriel@intel.com \
    --cc=thomas@monjalon.net \
    --cc=vladimir.medvedkin@intel.com \
    --cc=yipeng1.wang@intel.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;
as well as URLs for NNTP newsgroup(s).