From: Stephen Hemminger <stephen@networkplumber.org>
To: "Mattias Rönnblom" <hofors@lysator.liu.se>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Tyler Retzlaff <roretzla@linux.microsoft.com>
Subject: Re: RTE lock
Date: Tue, 5 Mar 2024 12:50:27 -0800 [thread overview]
Message-ID: <20240305125027.7814d9a8@hermes.local> (raw)
In-Reply-To: <0024db51-8b39-4aa7-969a-bde86fe1c764@lysator.liu.se>
On Tue, 5 Mar 2024 21:18:20 +0100
Mattias Rönnblom <hofors@lysator.liu.se> wrote:
> Shouldn't we have a DPDK-native mutex API, rather than using direct
> POSIX mutex lock calls?
>
> There are two reasons for this, as I see it
> 1) more cleanly support non-POSIX operating system (i.e., Microsoft
> Windows).
> 2) to discourage mechanical use of spinlocks in places where a regular
> mutex lock is more appropriate.
>
> I think (and hope) DPDK developers will tend to pick DPDK-native rather
> than other APIs as their first choice.
>
> For locks, they go for spinlocks, even in control (non-fast
> path/non-packet processing) code paths (e.g., calls made by the typical
> non-EAL thread).
>
> Using spinlocks to synchronize threads that may be preempted aren't
> great idea.
Maybe a wrapper, but actually implementing mutex with flock is complicated.
next prev parent reply other threads:[~2024-03-05 20:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-05 20:18 RTE lock Mattias Rönnblom
2024-03-05 20:50 ` Stephen Hemminger [this message]
2024-03-05 21:02 ` Tyler Retzlaff
2024-03-07 19:50 ` Mattias Rönnblom
2024-03-07 20:27 ` Stephen Hemminger
2024-03-08 9:44 ` Mattias Rönnblom
2024-03-06 8:46 ` Morten Brørup
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=20240305125027.7814d9a8@hermes.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=hofors@lysator.liu.se \
--cc=roretzla@linux.microsoft.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 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.