From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH v2] nvme-pci: Use PCI bus address for data/queues in CMB
Date: Wed, 4 Oct 2017 08:30:28 +0200 [thread overview]
Message-ID: <20171004063027.GA20459@lst.de> (raw)
In-Reply-To: <20171002172128.GV8463@localhost.localdomain>
On Mon, Oct 02, 2017@11:21:29AM -0600, Keith Busch wrote:
> Yah, calling this a DMA address was a misnomer and confusing.
Abhishek, can you test if this works for you?
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Keith Busch <keith.busch@intel.com>
Cc: Christoph Hellwig <hch@lst.de>,
Abhishek Shah <abhishek.shah@broadcom.com>,
Jens Axboe <axboe@fb.com>, Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org, linux-pci@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com, stable@vger.kernel.org
Subject: Re: [PATCH v2] nvme-pci: Use PCI bus address for data/queues in CMB
Date: Wed, 4 Oct 2017 08:30:28 +0200 [thread overview]
Message-ID: <20171004063027.GA20459@lst.de> (raw)
In-Reply-To: <20171002172128.GV8463@localhost.localdomain>
On Mon, Oct 02, 2017 at 11:21:29AM -0600, Keith Busch wrote:
> Yah, calling this a DMA address was a misnomer and confusing.
Abhishek, can you test if this works for you?
WARNING: multiple messages have this Message-ID (diff)
From: hch@lst.de (Christoph Hellwig)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] nvme-pci: Use PCI bus address for data/queues in CMB
Date: Wed, 4 Oct 2017 08:30:28 +0200 [thread overview]
Message-ID: <20171004063027.GA20459@lst.de> (raw)
In-Reply-To: <20171002172128.GV8463@localhost.localdomain>
On Mon, Oct 02, 2017 at 11:21:29AM -0600, Keith Busch wrote:
> Yah, calling this a DMA address was a misnomer and confusing.
Abhishek, can you test if this works for you?
next prev parent reply other threads:[~2017-10-04 6:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-30 9:28 [PATCH v2] nvme-pci: Use PCI bus address for data/queues in CMB Abhishek Shah
2017-09-30 9:28 ` Abhishek Shah
2017-09-30 9:28 ` Abhishek Shah
2017-09-30 9:28 ` Abhishek Shah
2017-10-01 7:42 ` Christoph Hellwig
2017-10-01 7:42 ` Christoph Hellwig
2017-10-01 7:42 ` Christoph Hellwig
2017-10-01 7:42 ` Christoph Hellwig
2017-10-02 17:21 ` Keith Busch
2017-10-02 17:21 ` Keith Busch
2017-10-02 17:21 ` Keith Busch
2017-10-02 17:21 ` Keith Busch
2017-10-04 6:30 ` Christoph Hellwig [this message]
2017-10-04 6:30 ` Christoph Hellwig
2017-10-04 6:30 ` Christoph Hellwig
2017-10-04 9:37 ` Abhishek Shah
2017-10-04 9:37 ` Abhishek Shah
2017-10-04 9:37 ` Abhishek Shah
2017-10-04 9:37 ` Abhishek Shah
2017-10-11 10:00 ` Sagi Grimberg
2017-10-11 10:00 ` Sagi Grimberg
2017-10-11 10:00 ` Sagi Grimberg
2017-10-11 10:00 ` Sagi Grimberg
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=20171004063027.GA20459@lst.de \
--to=hch@lst.de \
/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.