All of lore.kernel.org
 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 6/7] e1000: eliminate duplicate barriers on weakly-ordered archs
Date: Wed, 14 Mar 2018 18:41:51 -0700	[thread overview]
Message-ID: <CAKgT0UfJwYFy5g_2TE5W4MgdEvyH2CvBAS2imdw9UUiumuUOhQ@mail.gmail.com> (raw)
In-Reply-To: <1520997629-17361-6-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/e1000/e1000_main.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/ethernet/intel/e1000/e1000_main.c b/drivers/net/ethernet/intel/e1000/e1000_main.c
> index 3dd4aeb..e0e583a 100644
> --- a/drivers/net/ethernet/intel/e1000/e1000_main.c
> +++ b/drivers/net/ethernet/intel/e1000/e1000_main.c
> @@ -4573,7 +4573,7 @@ e1000_alloc_jumbo_rx_buffers(struct e1000_adapter *adapter,
>                  * such as IA-64).
>                  */
>                 wmb();
> -               writel(i, adapter->hw.hw_addr + rx_ring->rdt);
> +               writel_relaxed(i, adapter->hw.hw_addr + rx_ring->rdt);
>         }
>  }
>
> @@ -4688,7 +4688,7 @@ static void e1000_alloc_rx_buffers(struct e1000_adapter *adapter,
>                  * such as IA-64).
>                  */
>                 wmb();
> -               writel(i, hw->hw_addr + rx_ring->rdt);
> +               writel_relaxed(i, hw->hw_addr + rx_ring->rdt);
>         }
>  }
>

So you missed the writel in e1000_xmit_frame. You should probably get
that one too while you are doing these updates. The wmb() is in
e1000_tx_queue().

WARNING: multiple messages have this Message-ID (diff)
From: alexander.duyck@gmail.com (Alexander Duyck)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 6/7] e1000: eliminate duplicate barriers on weakly-ordered archs
Date: Wed, 14 Mar 2018 18:41:51 -0700	[thread overview]
Message-ID: <CAKgT0UfJwYFy5g_2TE5W4MgdEvyH2CvBAS2imdw9UUiumuUOhQ@mail.gmail.com> (raw)
In-Reply-To: <1520997629-17361-6-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/e1000/e1000_main.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/ethernet/intel/e1000/e1000_main.c b/drivers/net/ethernet/intel/e1000/e1000_main.c
> index 3dd4aeb..e0e583a 100644
> --- a/drivers/net/ethernet/intel/e1000/e1000_main.c
> +++ b/drivers/net/ethernet/intel/e1000/e1000_main.c
> @@ -4573,7 +4573,7 @@ e1000_alloc_jumbo_rx_buffers(struct e1000_adapter *adapter,
>                  * such as IA-64).
>                  */
>                 wmb();
> -               writel(i, adapter->hw.hw_addr + rx_ring->rdt);
> +               writel_relaxed(i, adapter->hw.hw_addr + rx_ring->rdt);
>         }
>  }
>
> @@ -4688,7 +4688,7 @@ static void e1000_alloc_rx_buffers(struct e1000_adapter *adapter,
>                  * such as IA-64).
>                  */
>                 wmb();
> -               writel(i, hw->hw_addr + rx_ring->rdt);
> +               writel_relaxed(i, hw->hw_addr + rx_ring->rdt);
>         }
>  }
>

So you missed the writel in e1000_xmit_frame. You should probably get
that one too while you are doing these updates. The wmb() is in
e1000_tx_queue().

WARNING: multiple messages have this Message-ID (diff)
From: Alexander Duyck <alexander.duyck@gmail.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH 6/7] e1000: eliminate duplicate barriers on weakly-ordered archs
Date: Wed, 14 Mar 2018 18:41:51 -0700	[thread overview]
Message-ID: <CAKgT0UfJwYFy5g_2TE5W4MgdEvyH2CvBAS2imdw9UUiumuUOhQ@mail.gmail.com> (raw)
In-Reply-To: <1520997629-17361-6-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/e1000/e1000_main.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/ethernet/intel/e1000/e1000_main.c b/drivers/net/ethernet/intel/e1000/e1000_main.c
> index 3dd4aeb..e0e583a 100644
> --- a/drivers/net/ethernet/intel/e1000/e1000_main.c
> +++ b/drivers/net/ethernet/intel/e1000/e1000_main.c
> @@ -4573,7 +4573,7 @@ e1000_alloc_jumbo_rx_buffers(struct e1000_adapter *adapter,
>                  * such as IA-64).
>                  */
>                 wmb();
> -               writel(i, adapter->hw.hw_addr + rx_ring->rdt);
> +               writel_relaxed(i, adapter->hw.hw_addr + rx_ring->rdt);
>         }
>  }
>
> @@ -4688,7 +4688,7 @@ static void e1000_alloc_rx_buffers(struct e1000_adapter *adapter,
>                  * such as IA-64).
>                  */
>                 wmb();
> -               writel(i, hw->hw_addr + rx_ring->rdt);
> +               writel_relaxed(i, hw->hw_addr + rx_ring->rdt);
>         }
>  }
>

So you missed the writel in e1000_xmit_frame. You should probably get
that one too while you are doing these updates. The wmb() is in
e1000_tx_queue().

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

Thread overview: 81+ 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 ` [Intel-wired-lan] " Sinan Kaya
2018-03-14  3:20 ` Sinan Kaya
2018-03-14  3:20 ` Sinan Kaya
2018-03-14  3:20 ` [PATCH 2/7] ixgbe: eliminate " Sinan Kaya
2018-03-14  3:20   ` [Intel-wired-lan] " Sinan Kaya
2018-03-14  3:20   ` Sinan Kaya
2018-03-15  1:47   ` Alexander Duyck
2018-03-15  1:47     ` [Intel-wired-lan] " Alexander Duyck
2018-03-15  1:47     ` Alexander Duyck
2018-03-14  3:20 ` [PATCH 3/7] RDMA/qedr: " Sinan Kaya
2018-03-14  3:20   ` Sinan Kaya
2018-03-14  4:12   ` Jason Gunthorpe
2018-03-14  4:12     ` Jason Gunthorpe
2018-03-14 12:06     ` okaya
2018-03-14 12:06       ` okaya at codeaurora.org
2018-03-15 22:23   ` Jason Gunthorpe
2018-03-15 22:23     ` Jason Gunthorpe
2018-03-14  3:20 ` [PATCH 4/7] igbvf: " Sinan Kaya
2018-03-14  3:20   ` [Intel-wired-lan] " Sinan Kaya
2018-03-14  3:20   ` Sinan Kaya
2018-03-15  1:48   ` Alexander Duyck
2018-03-15  1:48     ` [Intel-wired-lan] " Alexander Duyck
2018-03-15  1:48     ` Alexander Duyck
2018-03-14  3:20 ` [PATCH 5/7] igb: " Sinan Kaya
2018-03-14  3:20   ` [Intel-wired-lan] " Sinan Kaya
2018-03-14  3:20   ` Sinan Kaya
2018-03-15  1:50   ` Alexander Duyck
2018-03-15  1:50     ` [Intel-wired-lan] " Alexander Duyck
2018-03-15  1:50     ` Alexander Duyck
2018-03-14  3:20 ` [PATCH 6/7] e1000: " Sinan Kaya
2018-03-14  3:20   ` [Intel-wired-lan] " Sinan Kaya
2018-03-14  3:20   ` Sinan Kaya
2018-03-15  1:41   ` Alexander Duyck [this message]
2018-03-15  1:41     ` [Intel-wired-lan] " Alexander Duyck
2018-03-15  1:41     ` Alexander Duyck
2018-03-15 23:30     ` Sinan Kaya
2018-03-15 23:30       ` [Intel-wired-lan] " Sinan Kaya
2018-03-15 23:30       ` Sinan Kaya
2018-03-16  0:25       ` Alexander Duyck
2018-03-16  0:25         ` [Intel-wired-lan] " Alexander Duyck
2018-03-16  0:25         ` Alexander Duyck
2018-03-16  0:50         ` Sinan Kaya
2018-03-16  0:50           ` [Intel-wired-lan] " Sinan Kaya
2018-03-16  0:50           ` Sinan Kaya
2018-03-14  3:20 ` [PATCH 7/7] ixgbevf: " Sinan Kaya
2018-03-14  3:20   ` [Intel-wired-lan] " Sinan Kaya
2018-03-14  3:20   ` Sinan Kaya
2018-03-14  5:08   ` Timur Tabi
2018-03-14  5:08     ` [Intel-wired-lan] " Timur Tabi
2018-03-14  5:08     ` Timur Tabi
2018-03-14 12:13     ` okaya
2018-03-14 12:13       ` [Intel-wired-lan] " okaya
2018-03-14 12:13       ` okaya at codeaurora.org
2018-03-14 21:49       ` Alexander Duyck
2018-03-14 21:49         ` [Intel-wired-lan] " Alexander Duyck
2018-03-14 21:49         ` Alexander Duyck
2018-03-14 22:57         ` Sinan Kaya
2018-03-14 22:57           ` [Intel-wired-lan] " Sinan Kaya
2018-03-14 22:57           ` Sinan Kaya
2018-03-15  1:44           ` Alexander Duyck
2018-03-15  1:44             ` [Intel-wired-lan] " Alexander Duyck
2018-03-15  1:44             ` Alexander Duyck
2018-03-15  2:17             ` Sinan Kaya
2018-03-15  2:17               ` [Intel-wired-lan] " Sinan Kaya
2018-03-15  2:17               ` Sinan Kaya
2018-03-15 14:32               ` Alexander Duyck
2018-03-15 14:32                 ` [Intel-wired-lan] " Alexander Duyck
2018-03-15 14:32                 ` Alexander Duyck
2018-03-15 16:21                 ` Sinan Kaya
2018-03-15 16:21                   ` [Intel-wired-lan] " Sinan Kaya
2018-03-15 16:21                   ` Sinan Kaya
2018-03-15 16:27                   ` Sinan Kaya
2018-03-15 16:27                     ` [Intel-wired-lan] " Sinan Kaya
2018-03-15 16:27                     ` Sinan Kaya
2018-03-15 16:58                     ` Alexander Duyck
2018-03-15 16:58                       ` [Intel-wired-lan] " Alexander Duyck
2018-03-15 16:58                       ` Alexander Duyck
2018-03-15  1:45   ` Alexander Duyck
2018-03-15  1:45     ` [Intel-wired-lan] " 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=CAKgT0UfJwYFy5g_2TE5W4MgdEvyH2CvBAS2imdw9UUiumuUOhQ@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.