netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: Christoph Hellwig <hch@lst.de>,
	Tariq Toukan <tariqt@mellanox.com>,
	xavier.huwei@huawei.com, netdev@vger.kernel.org,
	linux-rdma@vger.kernel.org, Doug Ledford <dledford@redhat.com>,
	Jason Gunthorpe <jgg@mellanox.com>,
	Stephen Warren <swarren@nvidia.com>
Subject: Re: [PATCH V2] net/mlx4: Get rid of page operation after dma_alloc_coherent
Date: Wed, 19 Dec 2018 08:25:30 +0100	[thread overview]
Message-ID: <20181219072530.GA27733@lst.de> (raw)
In-Reply-To: <5196b89a-0de5-a53e-95c6-6381b4ed0982@wwwdotorg.org>

On Tue, Dec 18, 2018 at 05:12:41PM -0700, Stephen Warren wrote:
> On 12/18/18 1:56 PM, Christoph Hellwig wrote:
>> This goes in the right direction, but I think we need to stop
>> abusing the scatterlist for the coherent mapping entirely.  Something
>> like the patch below (based on yours):
>
> Oh, it was simple to get rid of the sg list usage than I thought; I'd 
> assume it would be touched in a bunch of other files.
>
> I had to make the additions shown below to get the adapter to get the 
> driver to probe without errors, but with these changes, ibping, ib_read_bw, 
> and ib_write_bw all work both directions:

I think the new coherent flag should probably use a bool instead of int,
even despite the fact that the old one still uses bool.

It might also be worth checking if we need the per-chunk and per-table
coherent flags, or if the per-chunk one is enough.

Otherwise this looks fine, feel free to resend it under your name as
you did the original patch and all the analysis and testing.

  reply	other threads:[~2018-12-19  7:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-18 19:06 [PATCH V2] net/mlx4: Get rid of page operation after dma_alloc_coherent Stephen Warren
2018-12-18 20:56 ` Christoph Hellwig
2018-12-19  0:12   ` Stephen Warren
2018-12-19  7:25     ` Christoph Hellwig [this message]
2018-12-19 17:31       ` Stephen Warren

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=20181219072530.GA27733@lst.de \
    --to=hch@lst.de \
    --cc=dledford@redhat.com \
    --cc=jgg@mellanox.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=swarren@nvidia.com \
    --cc=swarren@wwwdotorg.org \
    --cc=tariqt@mellanox.com \
    --cc=xavier.huwei@huawei.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).