All of lore.kernel.org
 help / color / mirror / Atom feed
From: keith.busch@intel.com (Keith Busch)
Subject: Bug report - drivers/nvme/host/pci.c?
Date: Wed, 3 Jan 2018 13:11:31 -0700	[thread overview]
Message-ID: <20180103201131.GB11172@localhost.localdomain> (raw)
In-Reply-To: <20180103200140.GA11172@localhost.localdomain>

On Wed, Jan 03, 2018@01:01:41PM -0700, Keith Busch wrote:
> On Wed, Jan 03, 2018@07:46:05PM +0000, Chaitanya Kulkarni wrote:
> >    HI Fangjian,
> > 
> >    I ran your test on the latest kernel and I did not see the problem.
> <> 
> >    Is there a particular reason why you are using Linux version 4.15.0-rc1?
> > 
> >    Can you please check if you are having the same problem on the latest
> >    kernel as mentioned in my log?
> > 
> >    Regards,
> > 
> >    Chaitanya
> 
> I would guess the reporter has an IOMMU enabled that DMA maps into fewer
> entries than the virtual table has. Since that's possible, I think the
> WARN_ON is invalid unless you overwrite iod->nents to be the return of
> dma_map_sg, I think.

Just fyi, the driver selecting when to use SGL vs PRP is done prior to
DMA mapping the scatter list. An IOMMU may map a virtually contiguous
buffer into a single address, which is probably where biggest win for
SGL over PRP exists. I think this driver handling ought to be reworked.

  reply	other threads:[~2018-01-03 20:11 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 [this message]
2018-01-08  9:49       ` hch
2018-01-10 21:59         ` Keith Busch
     [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=20180103201131.GB11172@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 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.