From: Sinan Kaya <okaya@codeaurora.org>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, timur@codeaurora.org,
sulrich@codeaurora.org, linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v7 0/7] netdev: Eliminate duplicate barriers on weakly-ordered archs
Date: Tue, 27 Mar 2018 08:40:41 -0400 [thread overview]
Message-ID: <044d58fd-b6ea-6341-0cdf-d99c47fc241e@codeaurora.org> (raw)
In-Reply-To: <20180326.124846.2182144342929084561.davem@davemloft.net>
Dave,
On 3/26/2018 12:48 PM, David Miller wrote:
> From: Sinan Kaya <okaya@codeaurora.org>
> Date: Sun, 25 Mar 2018 10:39:14 -0400
>
>> Code includes wmb() followed by writel() in multiple places. writel()
>> already has a barrier on some architectures like arm64.
>>
>> This ends up CPU observing two barriers back to back before executing the
>> register write.
>>
>> Since code already has an explicit barrier call, changing writel() to
>> writel_relaxed().
>>
>> I did a regex search for wmb() followed by writel() in each drivers
>> directory.
>> I scrubbed the ones I care about in this series.
>>
>> I considered "ease of change", "popular usage" and "performance critical
>> path" as the determining criteria for my filtering.
>>
>> We used relaxed API heavily on ARM for a long time but
>> it did not exist on other architectures. For this reason, relaxed
>> architectures have been paying double penalty in order to use the common
>> drivers.
>>
>> Now that relaxed API is present on all architectures, we can go and scrub
>> all drivers to see what needs to change and what can remain.
>>
>> We start with mostly used ones and hope to increase the coverage over time.
>> It will take a while to cover all drivers.
>>
>> Feel free to apply patches individually.
>>
>> Changes since v6:
>> - bring back amazon ena and add mmiowb, remove
>> ena_com_write_sq_doorbell_rel().
>> - remove extra mmiowb in bnx2x
>> - correct spelling mistake in bnx2x: Replace doorbell barrier() with wmb()
>
> Series applied, thank you.
>
I don't know if you have been following "RFC on writel and writel_relaxed" thread
or not but there are some new developments about wmb() requirement.
Basically, wmb() should never be used before writel() as writel() seem to
provide coherency and observability guarantee.
wmb()+writel_relaxed() is slower on some architectures than plain writel()
I'll have to rework these patches to have writel() only.
Are you able to drop the applied ones so that I can post V7 or is it too late?
Sinan
--
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 12:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-25 14:39 [PATCH v7 0/7] netdev: Eliminate duplicate barriers on weakly-ordered archs Sinan Kaya
2018-03-25 14:39 ` [PATCH v7 1/7] net: qla3xxx: " Sinan Kaya
2018-03-25 14:39 ` [PATCH v7 2/7] qlcnic: " Sinan Kaya
2018-03-25 14:39 ` [PATCH v7 3/7] bnx2x: Replace doorbell barrier() with wmb() Sinan Kaya
2018-03-29 9:17 ` Elior, Ariel
2018-03-29 13:45 ` Sinan Kaya
2018-03-25 14:39 ` [PATCH v7 4/7] bnx2x: Eliminate duplicate barriers on weakly-ordered archs Sinan Kaya
2018-03-25 14:39 ` [PATCH v7 5/7] net: qlge: " Sinan Kaya
2018-03-25 14:39 ` [PATCH v7 6/7] bnxt_en: " Sinan Kaya
2018-03-25 20:24 ` Michael Chan
2018-03-25 14:39 ` [PATCH v7 7/7] net: ena: " Sinan Kaya
2018-03-26 16:48 ` [PATCH v7 0/7] netdev: " David Miller
2018-03-27 12:40 ` Sinan Kaya [this message]
2018-03-27 14:00 ` David Miller
2018-03-27 14:02 ` 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=044d58fd-b6ea-6341-0cdf-d99c47fc241e@codeaurora.org \
--to=okaya@codeaurora.org \
--cc=davem@davemloft.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sulrich@codeaurora.org \
--cc=timur@codeaurora.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;
as well as URLs for NNTP newsgroup(s).