From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: Alexander Duyck <alexander.duyck@gmail.com>,
Sinan Kaya <okaya@codeaurora.org>,
intel-wired-lan <intel-wired-lan@lists.osuosl.org>
Cc: Netdev <netdev@vger.kernel.org>,
Timur Tabi <timur@codeaurora.org>,
sulrich@codeaurora.org, linux-arm-kernel@lists.infradead.org,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v7 0/7] netdev: intel: Eliminate duplicate barriers on weakly-ordered archs
Date: Fri, 23 Mar 2018 16:58:16 -0700 [thread overview]
Message-ID: <1521849496.15055.16.camel@intel.com> (raw)
In-Reply-To: <CAKgT0UcaxM8Mj9Y9fR0B+aafTm1SzTqh+gHT5ozgvyaoHvrzRQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 3094 bytes --]
On Fri, 2018-03-23 at 14:53 -0700, Alexander Duyck wrote:
> On Fri, Mar 23, 2018 at 11:52 AM, Sinan Kaya <okaya@codeaurora.org>
> wrote:
> > 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.
>
> I looked over the set and they seem good.
>
> Reviewed-by: Alexander Duyck <alexander.h.duyck@intel.com>
Grrr, patch 1 does not apply cleanly to my next-queue tree (dev-queue
branch). I will deal with this series in a day or two, after I have dealt
with my driver pull requests.
> >
> > Changes since v6:
> > clean up between 2..6 and then make your Alex's changes on 1 and 7
> > The mmiowb shouldn't be needed for Rx. Only one CPU will be running
> > NAPI for the queue and we will synchronize this with a full writel
> > anyway when we re-enable the interrupts.
> >
> > Sinan Kaya (7):
> > i40e/i40evf: Eliminate duplicate barriers on weakly-ordered archs
> > ixgbe: eliminate duplicate barriers on weakly-ordered archs
> > igbvf: eliminate duplicate barriers on weakly-ordered archs
> > igb: eliminate duplicate barriers on weakly-ordered archs
> > fm10k: Eliminate duplicate barriers on weakly-ordered archs
> > ixgbevf: keep writel() closer to wmb()
> > ixgbevf: eliminate duplicate barriers on weakly-ordered archs
> >
> > drivers/net/ethernet/intel/fm10k/fm10k_main.c | 4 ++--
> > drivers/net/ethernet/intel/i40e/i40e_txrx.c | 14 ++++++++++----
> > drivers/net/ethernet/intel/i40evf/i40e_txrx.c | 4 ++--
> > drivers/net/ethernet/intel/igb/igb_main.c | 4 ++--
> > drivers/net/ethernet/intel/igbvf/netdev.c | 4 ++--
> > drivers/net/ethernet/intel/ixgbe/ixgbe_main.c | 8 ++++----
> > drivers/net/ethernet/intel/ixgbevf/ixgbevf.h | 5 -----
> > drivers/net/ethernet/intel/ixgbevf/ixgbevf_main.c | 11 ++++++++---
> > 8 files changed, 30 insertions(+), 24 deletions(-)
> >
> > --
> > 2.7.4
> >
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2018-03-23 23:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-23 18:52 [PATCH v7 0/7] netdev: intel: Eliminate duplicate barriers on weakly-ordered archs Sinan Kaya
2018-03-23 18:52 ` [PATCH v7 1/7] i40e/i40evf: " Sinan Kaya
2018-03-23 18:52 ` [PATCH v7 2/7] ixgbe: eliminate " Sinan Kaya
2018-03-23 18:52 ` [PATCH v7 3/7] igbvf: " Sinan Kaya
2018-03-23 18:52 ` [PATCH v7 4/7] igb: " Sinan Kaya
2018-03-23 18:52 ` [PATCH v7 5/7] fm10k: Eliminate " Sinan Kaya
2018-03-23 18:52 ` [PATCH v7 6/7] ixgbevf: keep writel() closer to wmb() Sinan Kaya
2018-03-23 18:53 ` [PATCH v7 7/7] ixgbevf: eliminate duplicate barriers on weakly-ordered archs Sinan Kaya
2018-03-23 21:53 ` [PATCH v7 0/7] netdev: intel: Eliminate " Alexander Duyck
2018-03-23 23:58 ` Jeff Kirsher [this message]
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 ` Aw: " Lino Sanfilippo
2018-03-27 14:38 ` Alexander Duyck
2018-03-27 14:48 ` Sinan Kaya
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=1521849496.15055.16.camel@intel.com \
--to=jeffrey.t.kirsher@intel.com \
--cc=alexander.duyck@gmail.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=okaya@codeaurora.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).