From: David Miller <davem@davemloft.net>
To: hpreg@vmware.com
Cc: netdev@vger.kernel.org, doshir@vmware.com, pv-drivers@vmware.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net 2/2] vmxnet3: use DMA memory barriers where required
Date: Mon, 14 May 2018 22:45:01 -0400 (EDT) [thread overview]
Message-ID: <20180514.224501.737523188651166796.davem@davemloft.net> (raw)
In-Reply-To: <1526300090-78546-1-git-send-email-hpreg@vmware.com>
From: <hpreg@vmware.com>
Date: Mon, 14 May 2018 08:14:49 -0400
> The gen bits must be read first from (resp. written last to) DMA memory.
> The proper way to enforce this on Linux is to call dma_rmb() (resp.
> dma_wmb()).
>
> Signed-off-by: Regis Duchesne <hpreg@vmware.com>
> Acked-by: Ronak Doshi <doshir@vmware.com>
Applied and queued up for -stable.
prev parent reply other threads:[~2018-05-15 2:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-14 12:14 [PATCH net 2/2] vmxnet3: use DMA memory barriers where required hpreg
2018-05-15 2:45 ` David Miller [this message]
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=20180514.224501.737523188651166796.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=doshir@vmware.com \
--cc=hpreg@vmware.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pv-drivers@vmware.com \
/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).