From: David Miller <davem@davemloft.net>
To: parri.andrea@gmail.com
Cc: linux-kernel@vger.kernel.org, mst@redhat.com,
jasowang@redhat.com, john.fastabend@gmail.com,
edumazet@google.com, netdev@vger.kernel.org
Subject: Re: [PATCH] ptr_ring: Remove now-redundant smp_read_barrier_depends()
Date: Mon, 19 Feb 2018 11:11:38 -0500 (EST) [thread overview]
Message-ID: <20180219.111138.1929929854473154523.davem@davemloft.net> (raw)
In-Reply-To: <1518779173-30812-1-git-send-email-parri.andrea@gmail.com>
From: Andrea Parri <parri.andrea@gmail.com>
Date: Fri, 16 Feb 2018 12:06:13 +0100
> Because READ_ONCE() now implies smp_read_barrier_depends(), the
> smp_read_barrier_depends() in __ptr_ring_consume() is redundant;
> this commit removes it and updates the comments.
>
> Signed-off-by: Andrea Parri <parri.andrea@gmail.com>
Ok, if READ_ONCE() does a barrier now, this change makes sense.
Applied to net-next, thank you.
prev parent reply other threads:[~2018-02-19 16:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-16 11:06 Andrea Parri
2018-02-19 16:11 ` David Miller [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=20180219.111138.1929929854473154523.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jasowang@redhat.com \
--cc=john.fastabend@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=parri.andrea@gmail.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
all inboxes | Powered by JetHome®