From: Sinan Kaya <okaya@codeaurora.org>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH v7 0/7] netdev: intel: Eliminate duplicate barriers on weakly-ordered archs
Date: Tue, 27 Mar 2018 10:48:11 -0400 [thread overview]
Message-ID: <6fe4e3a4-219f-68d7-25f1-72ab86aae42e@codeaurora.org> (raw)
In-Reply-To: <CAKgT0UfeMY0WsJGARrVxNsHzr8OnNSJ2jaYbBTGQNkR_uizJuQ@mail.gmail.com>
On 3/27/2018 10:38 AM, Alexander Duyck wrote:
>> We are being told that if you use writel(), then you don't need a wmb() on
>> all architectures.
> I'm not sure who told you that but that is incorrect, at least for
> x86. If you attempt to use writel() without the wmb() we will have to
> NAK the patches. We will accept the wmb() with writel_releaxed() since
> that solves things for ARM.
>
I added netdev and you to the RFC on writel and writel_relaxed list.
Feel free to raise your concerns.
--
Sinan Kaya
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.
next prev parent reply other threads:[~2018-03-27 14:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1521831180-25014-1-git-send-email-okaya@codeaurora.org>
2018-03-23 18:52 ` [Intel-wired-lan] [PATCH v7 1/7] i40e/i40evf: Eliminate duplicate barriers on weakly-ordered archs Sinan Kaya
2018-03-23 18:52 ` [Intel-wired-lan] [PATCH v7 2/7] ixgbe: eliminate " Sinan Kaya
2018-03-23 18:52 ` [Intel-wired-lan] [PATCH v7 3/7] igbvf: " Sinan Kaya
2018-03-23 18:52 ` [Intel-wired-lan] [PATCH v7 4/7] igb: " Sinan Kaya
2018-03-23 18:52 ` [Intel-wired-lan] [PATCH v7 5/7] fm10k: Eliminate " Sinan Kaya
2018-03-23 18:52 ` [Intel-wired-lan] [PATCH v7 6/7] ixgbevf: keep writel() closer to wmb() Sinan Kaya
2018-03-23 18:53 ` [Intel-wired-lan] [PATCH v7 7/7] ixgbevf: eliminate duplicate barriers on weakly-ordered archs Sinan Kaya
2018-03-23 21:53 ` [Intel-wired-lan] [PATCH v7 0/7] netdev: intel: Eliminate " Alexander Duyck
2018-03-23 23:58 ` Jeff Kirsher
2018-03-24 2:34 ` okaya
2018-03-27 12:42 ` Sinan Kaya
2018-03-27 14:04 ` Lino Sanfilippo
2018-03-27 14:23 ` Sinan Kaya
2018-03-27 14:33 ` Lino Sanfilippo
2018-03-27 14:38 ` Alexander Duyck
2018-03-27 14:48 ` Sinan Kaya [this message]
2018-03-27 16:54 ` Jeff Kirsher
2018-03-27 17:33 ` Sinan Kaya
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=6fe4e3a4-219f-68d7-25f1-72ab86aae42e@codeaurora.org \
--to=okaya@codeaurora.org \
--cc=intel-wired-lan@osuosl.org \
/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