> From: Mattias Rönnblom [mailto:mattias.ronnb...@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.ronnb...@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.
