From: keith.busch@intel.com (Keith Busch)
Subject: Bug report - drivers/nvme/host/pci.c?
Date: Wed, 10 Jan 2018 14:59:25 -0700 [thread overview]
Message-ID: <20180110215925.GJ15154@localhost.localdomain> (raw)
In-Reply-To: <20180108094951.GB4673@lst.de>
On Mon, Jan 08, 2018@10:49:51AM +0100, hch@lst.de wrote:
> Anyway, moving the decision to after dma_map makes sense. What do you
> think of the untested patch below? I also (so far very crudely)
> enforces we only use SGLs if they fit into the same allocation as the
> equivalent PRPs, so that we don't need to check use_sgl at allocation
> time:
Thanks, this looks pretty good. I'm not going to be able to test this
till next week, though. Would be good to hear if someone else with a
capable device can can verify this is successful.
next prev parent reply other threads:[~2018-01-10 21:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-03 6:31 Bug report - drivers/nvme/host/pci.c? Fangjian (Turing)
[not found] ` <BY2PR04MB2101903E77826A0479550572861E0@BY2PR04MB2101.namprd04.prod.outlook.com>
2018-01-03 20:01 ` Keith Busch
2018-01-03 20:11 ` Keith Busch
2018-01-08 9:49 ` hch
2018-01-10 21:59 ` Keith Busch [this message]
[not found] ` <BY2PR04MB21010125E9B1334D2FA505E786130@BY2PR04MB2101.namprd04.prod.outlook.com>
2018-01-08 9:47 ` hch
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=20180110215925.GJ15154@localhost.localdomain \
--to=keith.busch@intel.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