linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Duyck <alexander.duyck@gmail.com>
To: Sinan Kaya <okaya@codeaurora.org>
Cc: Netdev <netdev@vger.kernel.org>,
	Timur Tabi <timur@codeaurora.org>,
	sulrich@codeaurora.org, linux-arm-msm@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
	intel-wired-lan <intel-wired-lan@lists.osuosl.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 5/7] igb: eliminate duplicate barriers on weakly-ordered archs
Date: Wed, 14 Mar 2018 18:50:05 -0700	[thread overview]
Message-ID: <CAKgT0UfE0vvpOLaA0at=YPQDLpqC0yvKUdFb2hKi7P8fr0ZOcw@mail.gmail.com> (raw)
In-Reply-To: <1520997629-17361-5-git-send-email-okaya@codeaurora.org>

On Tue, Mar 13, 2018 at 8:20 PM, Sinan Kaya <okaya@codeaurora.org> wrote:
> Code includes wmb() followed by writel(). 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().
>
> Signed-off-by: Sinan Kaya <okaya@codeaurora.org>
> ---
>  drivers/net/ethernet/intel/igb/igb_main.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/net/ethernet/intel/igb/igb_main.c b/drivers/net/ethernet/intel/igb/igb_main.c
> index b88fae7..ba8ccb5 100644
> --- a/drivers/net/ethernet/intel/igb/igb_main.c
> +++ b/drivers/net/ethernet/intel/igb/igb_main.c
> @@ -8072,7 +8072,7 @@ void igb_alloc_rx_buffers(struct igb_ring *rx_ring, u16 cleaned_count)
>                  * such as IA-64).
>                  */
>                 wmb();
> -               writel(i, rx_ring->tail);
> +               writel_relaxed(i, rx_ring->tail);
>         }
>  }
>

This one missed the writel at the end of igb_tx_map().

  reply	other threads:[~2018-03-15  1:50 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-14  3:20 [PATCH 1/7] i40e/i40evf: Eliminate duplicate barriers on weakly-ordered archs Sinan Kaya
2018-03-14  3:20 ` [PATCH 2/7] ixgbe: eliminate " Sinan Kaya
2018-03-15  1:47   ` Alexander Duyck
2018-03-14  3:20 ` [PATCH 3/7] RDMA/qedr: " Sinan Kaya
2018-03-14  4:12   ` Jason Gunthorpe
2018-03-14 12:06     ` okaya
2018-03-15 22:23   ` Jason Gunthorpe
2018-03-14  3:20 ` [PATCH 4/7] igbvf: " Sinan Kaya
2018-03-15  1:48   ` Alexander Duyck
2018-03-14  3:20 ` [PATCH 5/7] igb: " Sinan Kaya
2018-03-15  1:50   ` Alexander Duyck [this message]
2018-03-14  3:20 ` [PATCH 6/7] e1000: " Sinan Kaya
2018-03-15  1:41   ` Alexander Duyck
2018-03-15 23:30     ` Sinan Kaya
2018-03-16  0:25       ` Alexander Duyck
2018-03-16  0:50         ` Sinan Kaya
2018-03-14  3:20 ` [PATCH 7/7] ixgbevf: " Sinan Kaya
2018-03-14  5:08   ` Timur Tabi
2018-03-14 12:13     ` okaya
2018-03-14 21:49       ` Alexander Duyck
2018-03-14 22:57         ` Sinan Kaya
2018-03-15  1:44           ` Alexander Duyck
2018-03-15  2:17             ` Sinan Kaya
2018-03-15 14:32               ` Alexander Duyck
2018-03-15 16:21                 ` Sinan Kaya
2018-03-15 16:27                   ` Sinan Kaya
2018-03-15 16:58                     ` Alexander Duyck
2018-03-15  1:45   ` Alexander Duyck

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='CAKgT0UfE0vvpOLaA0at=YPQDLpqC0yvKUdFb2hKi7P8fr0ZOcw@mail.gmail.com' \
    --to=alexander.duyck@gmail.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@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).