From: "Morten Brørup" <mb@smartsharesystems.com>
To: "Mattias Rönnblom" <mattias.ronnblom@ericsson.com>,
"David Marchand" <david.marchand@redhat.com>
Cc: "Thomas Monjalon" <thomas@monjalon.net>, dev <dev@dpdk.org>,
"Onar Olsen" <onar.olsen@ericsson.com>,
"Honnappa Nagarahalli" <Honnappa.Nagarahalli@arm.com>,
nd <nd@arm.com>,
"Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
"Stephen Hemminger" <stephen@networkplumber.org>,
"Mattias Rönnblom" <hofors@lysator.liu.se>,
"Chengwen Feng" <fengchengwen@huawei.com>,
"Ola Liljedahl" <ola.liljedahl@arm.com>
Subject: RE: [PATCH v9] eal: add seqlock
Date: Wed, 1 Jun 2022 11:10:43 +0200 [thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35D870CB@smartserver.smartshare.dk> (raw)
In-Reply-To: <82725a22-d257-223d-2c84-b2f5270a6356@ericsson.com>
> From: Mattias Rönnblom [mailto:mattias.ronnblom@ericsson.com]
> Sent: Wednesday, 1 June 2022 11.02
>
> On 2022-05-31 13:52, David Marchand wrote:
> > On Mon, May 23, 2022 at 4:24 PM Mattias Rönnblom
> > <mattias.ronnblom@ericsson.com> wrote:
> >>
> >> A sequence lock (seqlock) is a synchronization primitive which
> allows
> >> for data-race free, low-overhead, high-frequency reads, suitable for
> >> data structures shared across many cores and which are updated
> >> relatively infrequently.
> >>
> >> A seqlock permits multiple parallel readers. A spinlock is used to
> >> serialize writers. In cases where there is only a single writer, or
> >> writer-writer synchronization is done by some external means, the
> >> "raw" sequence counter type (and accompanying rte_seqcount_*()
> >> functions) may be used instead.
> >>
> >> To avoid resource reclamation and other issues, the data protected
> by
> >> a seqlock is best off being self-contained (i.e., no pointers
> [except
> >> to constant data]).
> >>
> >
> > Overall, comments were addressed and the patch looks ready.
> > Last call before merging?
> >
> >
>
> I don't have anything to add. Thanks.
Please don't hold back merging on my behalf; you may disregard my previous email regarding the v9 patch.
next prev parent reply other threads:[~2022-06-01 9:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220513103820.3e34fcb9@hermes.local>
2022-05-15 12:24 ` [PATCH v7] " Mattias Rönnblom
2022-05-15 12:39 ` Mattias Rönnblom
2022-05-15 15:19 ` Morten Brørup
2022-05-15 17:54 ` Mattias Rönnblom
2022-05-16 8:30 ` Morten Brørup
2022-05-15 15:23 ` Morten Brørup
2022-05-20 6:02 ` Mattias Rönnblom
2022-05-23 11:31 ` [PATCH v8] " Mattias Rönnblom
2022-05-23 14:23 ` [PATCH v9] " Mattias Rönnblom
2022-05-31 11:52 ` David Marchand
2022-06-01 9:01 ` Mattias Rönnblom
2022-06-01 9:10 ` Morten Brørup [this message]
2022-05-31 22:45 ` Stephen Hemminger
2022-06-01 6:07 ` Morten Brørup
2022-06-01 8:19 ` Mattias Rönnblom
2022-06-01 16:15 ` Stephen Hemminger
2022-06-01 19:33 ` Mattias Rönnblom
2022-05-31 22:49 ` Stephen Hemminger
2022-05-31 22:57 ` Honnappa Nagarahalli
2022-06-07 9:25 ` David Marchand
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=98CBD80474FA8B44BF855DF32C47DC35D870CB@smartserver.smartshare.dk \
--to=mb@smartsharesystems.com \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=hofors@lysator.liu.se \
--cc=konstantin.ananyev@intel.com \
--cc=mattias.ronnblom@ericsson.com \
--cc=nd@arm.com \
--cc=ola.liljedahl@arm.com \
--cc=onar.olsen@ericsson.com \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
/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).