From: Lijun Pan <ljp@linux.ibm.com>
To: netdev@vger.kernel.org
Cc: sukadev@linux.ibm.com, drt@linux.ibm.com,
brking@linux.vnet.ibm.com, dnbanerg@us.ibm.com,
tlfalcon@linux.ibm.com, Lijun Pan <ljp@linux.ibm.com>
Subject: [PATCH net-next v2 0/2] rework the memory barrier for SCRQ entry
Date: Fri, 29 Jan 2021 19:19:03 -0600 [thread overview]
Message-ID: <20210130011905.1485-1-ljp@linux.ibm.com> (raw)
This series rework the memory barrier for SCRQ (Sub-Command-Response
Queue) entry.
v2: send to net-next.
Lijun Pan (2):
ibmvnic: rework to ensure SCRQ entry reads are properly ordered
ibmvnic: remove unnecessary rmb() inside ibmvnic_poll
drivers/net/ethernet/ibm/ibmvnic.c | 31 +++++++++++-------------------
1 file changed, 11 insertions(+), 20 deletions(-)
--
2.23.0
next reply other threads:[~2021-01-30 10:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-30 1:19 Lijun Pan [this message]
2021-01-30 1:19 ` [PATCH net-next v2 1/2] ibmvnic: rework to ensure SCRQ entry reads are properly ordered Lijun Pan
2021-01-30 1:19 ` [PATCH net-next v2 2/2] ibmvnic: remove unnecessary rmb() inside ibmvnic_poll Lijun Pan
2021-02-02 4:30 ` [PATCH net-next v2 0/2] rework the memory barrier for SCRQ entry patchwork-bot+netdevbpf
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=20210130011905.1485-1-ljp@linux.ibm.com \
--to=ljp@linux.ibm.com \
--cc=brking@linux.vnet.ibm.com \
--cc=dnbanerg@us.ibm.com \
--cc=drt@linux.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=sukadev@linux.ibm.com \
--cc=tlfalcon@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).