All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: <dev@dpdk.org>
Subject: Re: [RFC 0/7] Introduce FreeBSD macros for SAFE iteration
Date: Mon, 27 Jan 2025 10:43:41 -0800	[thread overview]
Message-ID: <20250127104341.749f7cff@hermes.local> (raw)
In-Reply-To: <Z5fNcu-Sju0IxkG_@bricha3-mobl1.ger.corp.intel.com>

On Mon, 27 Jan 2025 18:16:18 +0000
Bruce Richardson <bruce.richardson@intel.com> wrote:

> On Mon, Jan 27, 2025 at 10:03:54AM -0800, Stephen Hemminger wrote:
> > This series adds common macros for safe iteration over lists.
> > It is a subset copy of the macros from FreeBSD that are
> > missing from the Linux header sys/queue.h
> > 
> > Chose this over several other options:
> >   - let each driver define their own as needed.
> >     One Intel driver got it wrong, others will as well.
> >   - rename all the queue macros to RTE_XXX variants.
> >     Seems like useless renaming and confusion.
> >   - Several distros have libbsd package with the correct macros.
> >     But adding yet another dependency to DPDK would be annoying
> >     for something this basic.
> >   
> 
> Actually, I wouldn't be that quick to eliminate the last option. It may
> give us some additional options for simplification. For example, the
> strlcpy and strlcat functions are in libbsd too, and if we had that as
> mandatory dependency, perhaps we could remove some extra code there too?
> 
> /Bruce
> 

I would be ok with using libbsd but only if we didn't have to keep a parallel
copy for all the other compiler and OS variants. And would it be global or
a per-driver dependency?

  reply	other threads:[~2025-01-27 18:43 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-27 18:03 [RFC 0/7] Introduce FreeBSD macros for SAFE iteration Stephen Hemminger
2025-01-27 18:03 ` [RFC 1/7] eal: add queue macro extensions from FreeBSD Stephen Hemminger
2025-01-27 18:03 ` [RFC 2/7] net/qede: fix use after free Stephen Hemminger
2025-01-27 18:03 ` [RFC 3/7] bus/fslmc: " Stephen Hemminger
2025-01-27 18:03 ` [RFC 4/7] net/bnxt: " Stephen Hemminger
2025-01-27 19:25   ` Ajit Khaparde
2025-01-27 18:03 ` [RFC 5/7] net/iavf: replace local version of TAILQ_FOREACH_SAFE Stephen Hemminger
2025-01-27 18:04 ` [RFC 6/7] vhost: replace open coded TAILQ_FOREACH_SAFE Stephen Hemminger
2025-01-27 18:04 ` [RFC 7/7] raw/ifpga: use EAL version of TAILQ_FOREACH_SAFE Stephen Hemminger
2025-01-31  9:03   ` Xu, Rosen
2025-01-27 18:16 ` [RFC 0/7] Introduce FreeBSD macros for SAFE iteration Bruce Richardson
2025-01-27 18:43   ` Stephen Hemminger [this message]
2025-01-27 19:29     ` Morten Brørup
2025-01-27 23:14       ` Stephen Hemminger
2025-02-14 17:20 ` [PATCH v2 0/7] Introduce FOREACH_SAFE macros Stephen Hemminger
2025-02-14 17:20   ` [PATCH v2 1/7] eal: add queue macro extensions from FreeBSD Stephen Hemminger
2025-02-19 14:55     ` Thomas Monjalon
2025-02-21 23:05       ` Stephen Hemminger
2025-02-22  8:46         ` Thomas Monjalon
2025-03-12 23:02       ` Stephen Hemminger
2025-03-13  8:00         ` Morten Brørup
2025-03-13  8:56           ` Bruce Richardson
2025-03-13 14:35             ` Thomas Monjalon
2025-03-13 14:41               ` Morten Brørup
2025-03-13 16:24                 ` Stephen Hemminger
2025-03-13 16:40                   ` Morten Brørup
2025-03-13 17:01                     ` Stephen Hemminger
2025-02-14 17:20   ` [PATCH v2 2/7] net/qede: fix use after free Stephen Hemminger
2025-02-14 17:20   ` [PATCH v2 3/7] bus/fslmc: " Stephen Hemminger
2025-02-15 11:12     ` Hemant Agrawal
2025-02-14 17:20   ` [PATCH v2 4/7] net/bnxt: " Stephen Hemminger
2025-02-14 17:20   ` [PATCH v2 5/7] net/iavf: replace local version of TAILQ_FOREACH_SAFE Stephen Hemminger
2025-02-14 17:20   ` [PATCH v2 6/7] vhost: replace open coded TAILQ_FOREACH_SAFE Stephen Hemminger
2025-02-14 17:20   ` [PATCH v2 7/7] raw/ifpga: use EAL version of TAILQ_FOREACH_SAFE Stephen Hemminger
2025-02-15 15:44   ` [PATCH v2 0/7] Introduce FOREACH_SAFE macros Morten Brørup
2025-03-12 23:15 ` [PATCH v3 0/9] introduce common " Stephen Hemminger
2025-03-12 23:15   ` [PATCH v3 1/9] eal: add queue macro extensions from FreeBSD Stephen Hemminger
2025-03-12 23:15   ` [PATCH v3 2/9] net/qede: fix use after free Stephen Hemminger
2025-03-12 23:15   ` [PATCH v3 3/9] bus/fslmc: " Stephen Hemminger
2025-03-12 23:15   ` [PATCH v3 4/9] net/bnxt: " Stephen Hemminger
2025-03-12 23:15   ` [PATCH v3 5/9] net/iavf: replace local version of TAILQ_FOREACH_SAFE Stephen Hemminger
2025-03-12 23:15   ` [PATCH v3 6/9] vhost: replace open coded TAILQ_FOREACH_SAFE Stephen Hemminger
2025-03-12 23:15   ` [PATCH v3 7/9] raw/ifpga: use EAL version of TAILQ_FOREACH_SAFE Stephen Hemminger
2025-03-12 23:15   ` [PATCH v3 8/9] net/i40e: replace open coded version of LIST_FOREACH_SAFE Stephen Hemminger
2025-08-27 14:15     ` Burakov, Anatoly
2025-03-12 23:15   ` [PATCH v3 9/9] net/ice: " Stephen Hemminger
2025-08-27 14:14     ` Burakov, Anatoly
2025-08-18 16:34   ` [PATCH v3 0/9] introduce common FOREACH_SAFE macros Stephen Hemminger
2025-08-20  6:42     ` Morten Brørup
2025-08-27 14:14       ` Burakov, Anatoly
2025-08-27 15:08         ` Morten Brørup
2025-08-27 15:11           ` Thomas Monjalon
2025-08-27 15:56             ` Morten Brørup
2025-08-27 15:55           ` Bruce Richardson
2025-08-27 16:12             ` Stephen Hemminger

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=20250127104341.749f7cff@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.