From: Alexander Duyck <alexander.duyck@gmail.com>
To: Sinan Kaya <okaya@kernel.org>
Cc: Netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH v8 0/7] netdev: intel: Eliminate duplicate barriers on weakly-ordered archs
Date: Mon, 30 Jul 2018 13:06:54 -0700 [thread overview]
Message-ID: <CAKgT0UccAH-=MmAxZkh1jextAOeRs6-ZvMAT__K4F7u-vqeWFQ@mail.gmail.com> (raw)
In-Reply-To: <906d48a5-6eaf-a152-1936-05670b0a6ae8@kernel.org>
On Mon, Jul 30, 2018 at 12:20 PM, Sinan Kaya <okaya@kernel.org> wrote:
> +netdev,
>
> On 7/30/2018 9:45 AM, Alexander Duyck wrote:
>>
>> I haven't had a chance to work on this much myself. My understanding
>> is that igb has had the barriers updated, but I don't think any of the
>> other drivers have been worked over yet.
>
>
> Unfortunately, I have recently changed jobs and I no longer have the
> hardware to test my changes. I thought that you wanted to handle this
> yourself.
>
> I haven't seen any follow ups. I wanted to double check.
As I said so far igb has been the only one updated, and that was done
by a third party:
73017f4e051c8 igb: Use dma_wmb() instead of wmb() before doorbell writes
> I worked with several architecture leads on 4.17. All architectures
> support the updated barrier semantics now. It is time to clean up the
> network drivers.
Thanks for that update. As I said for now igb has the barriers
updated. The idea being that igb is the test vehicle for this so if we
go a kernel version or so without triggering any issues then we can
follow up with the other drivers.
The other thing we have to keep in mind is that unlike many other NICs
we have to also deal with emulations of our devices (e1000 and e1000e)
that may rely on certain barriers being used to enforce things like
SMP synchronization between CPUs, so we have to be careful as we roll
this out.
Thanks.
- Alex
next prev parent reply other threads:[~2018-07-30 21:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <173f1319-f030-4a3b-d730-86c7e113a747@kernel.org>
[not found] ` <CAKgT0UcbSfgg3mpv0Qr2-w8iHhbQMsyM3LcrM4YwAv8yTiq+Vw@mail.gmail.com>
2018-07-30 19:20 ` [PATCH v8 0/7] netdev: intel: Eliminate duplicate barriers on weakly-ordered archs Sinan Kaya
2018-07-30 20:06 ` Alexander Duyck [this message]
2018-04-02 19:06 Sinan Kaya
2018-04-03 2:59 ` Sinan Kaya
2018-04-03 17:47 ` Alexander Duyck
2018-04-03 17:50 ` Sinan Kaya
2018-04-03 18:26 ` Jeff Kirsher
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='CAKgT0UccAH-=MmAxZkh1jextAOeRs6-ZvMAT__K4F7u-vqeWFQ@mail.gmail.com' \
--to=alexander.duyck@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=okaya@kernel.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).