From: Christoph Hellwig <hch@lst.de>
To: Jason Gunthorpe <jgg@mellanox.com>
Cc: "linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
Doug Ledford <dledford@redhat.com>,
Christoph Hellwig <hch@lst.de>,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>
Subject: Re: remove DMA_ATTR_WRITE_BARRIER
Date: Wed, 13 Nov 2019 17:03:44 +0100 [thread overview]
Message-ID: <20191113160344.GA12853@lst.de> (raw)
In-Reply-To: <20191113154712.GF21728@mellanox.com>
On Wed, Nov 13, 2019 at 03:47:18PM +0000, Jason Gunthorpe wrote:
> On Wed, Nov 13, 2019 at 08:32:12AM +0100, Christoph Hellwig wrote:
> > There is no implementation of the DMA_ATTR_WRITE_BARRIER flag left
> > now that the ia64 sn2 code has been removed. Drop the flag and
> > the calling convention to set it in the RDMA code.
>
> This looks OK, do you want it to go through the RDMA tree?
Either the dma-mapping or rdma tree is fine with me. I guess
there are more potential conflicts with rdma changes, so tht might
be the better choice.
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Jason Gunthorpe <jgg@mellanox.com>
Cc: Christoph Hellwig <hch@lst.de>,
Doug Ledford <dledford@redhat.com>,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>
Subject: Re: remove DMA_ATTR_WRITE_BARRIER
Date: Wed, 13 Nov 2019 17:03:44 +0100 [thread overview]
Message-ID: <20191113160344.GA12853@lst.de> (raw)
In-Reply-To: <20191113154712.GF21728@mellanox.com>
On Wed, Nov 13, 2019 at 03:47:18PM +0000, Jason Gunthorpe wrote:
> On Wed, Nov 13, 2019 at 08:32:12AM +0100, Christoph Hellwig wrote:
> > There is no implementation of the DMA_ATTR_WRITE_BARRIER flag left
> > now that the ia64 sn2 code has been removed. Drop the flag and
> > the calling convention to set it in the RDMA code.
>
> This looks OK, do you want it to go through the RDMA tree?
Either the dma-mapping or rdma tree is fine with me. I guess
there are more potential conflicts with rdma changes, so tht might
be the better choice.
next prev parent reply other threads:[~2019-11-13 16:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-13 7:32 remove DMA_ATTR_WRITE_BARRIER Christoph Hellwig
2019-11-13 7:32 ` Christoph Hellwig
2019-11-13 7:32 ` [PATCH 1/2] dma-mapping: remove the DMA_ATTR_WRITE_BARRIER flag Christoph Hellwig
2019-11-13 7:32 ` Christoph Hellwig
2019-11-13 7:32 ` [PATCH 2/2] IB/umem: remove the dmasync argument to ib_umem_get Christoph Hellwig
2019-11-13 7:32 ` Christoph Hellwig
2019-11-13 15:47 ` remove DMA_ATTR_WRITE_BARRIER Jason Gunthorpe
2019-11-13 15:47 ` Jason Gunthorpe
2019-11-13 16:03 ` Christoph Hellwig [this message]
2019-11-13 16:03 ` Christoph Hellwig
2019-11-14 18:23 ` Jason Gunthorpe
2019-11-14 18:23 ` Jason Gunthorpe
2019-11-17 10:34 ` [EXT] " Michal Kalderon
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=20191113160344.GA12853@lst.de \
--to=hch@lst.de \
--cc=dledford@redhat.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jgg@mellanox.com \
--cc=linux-rdma@vger.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 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.