Linux PCI Non-Transparent Bridge framework and drivers
 help / color / mirror / Atom feed
From: Logan Gunthorpe <logang@deltatee.com>
To: "Glimcher, Boris" <Boris.Glimcher@dell.com>,
	"linux-ntb@googlegroups.com" <linux-ntb@googlegroups.com>
Subject: Re: ntb_tool cannot dma_alloc_coherent with CMA (over switchtec)
Date: Thu, 31 May 2018 12:48:32 -0600	[thread overview]
Message-ID: <52648710-cf4a-9072-c03b-9a0f3fe7c19d@deltatee.com> (raw)
In-Reply-To: <8A1F3ACA2F40C04FBF91985D6F491D7C0176649B@MX302CL01.corp.emc.com>


On 31/05/18 10:32 AM, Glimcher, Boris wrote:
> I’m trying to enlarge buffers I use in ntb_tool by using cma:

Hmm, not sure what the problem is. Is this x86?

It would also be useful to see a complete dmesg trace.

Logan

  reply	other threads:[~2018-05-31 18:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-31 16:32 ntb_tool cannot dma_alloc_coherent with CMA (over switchtec) Glimcher, Boris
2018-05-31 18:48 ` Logan Gunthorpe [this message]
2018-05-31 19:42   ` Glimcher, Boris
2018-05-31 19:31 ` Dave Jiang
2018-05-31 19:44   ` Glimcher, Boris
2018-05-31 20:15     ` Dave Jiang

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=52648710-cf4a-9072-c03b-9a0f3fe7c19d@deltatee.com \
    --to=logang@deltatee.com \
    --cc=Boris.Glimcher@dell.com \
    --cc=linux-ntb@googlegroups.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