public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Suganath Prabu S <suganath-prabu.subramani@broadcom.com>
Cc: jejb@kernel.org, hch@infradead.org, martin.petersen@oracle.com,
	linux-scsi@vger.kernel.org, Sathya.Prakash@broadcom.com,
	kashyap.desai@broadcom.com, linux-kernel@vger.kernel.org,
	chaitra.basappa@broadcom.com, sreekanth.reddy@broadcom.com,
	linux-nvme@lists.infradead.org
Subject: Re: [PATCH v2 03/13] mpt3sas: SGL to PRP Translation for I/Os to NVMe  devices
Date: Thu, 27 Jul 2017 09:26:32 -0400	[thread overview]
Message-ID: <yq1a83qvwmv.fsf@oracle.com> (raw)
In-Reply-To: <1500038560-11231-4-git-send-email-suganath-prabu.subramani@broadcom.com> (Suganath Prabu S.'s message of "Fri, 14 Jul 2017 18:52:30 +0530")


Suganath,

> * Added support for translating the SGLs associated with incoming
> commands either to IEE SGL or NVMe PRPs for NVMe devices.

This all seems very convoluted. You should rely on the block layer
infrastructure instead of doing all this slicing and dicing by hand.

If the attached device is an NVMe drive, call blk_queue_virt_boundary()
and you will only receive requests that are suitable for a device with
PRP-style scatterlist constraints.

-- 
Martin K. Petersen	Oracle Linux Engineering

  reply	other threads:[~2017-07-27 13:27 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-14 13:22 [PATCH v2 00/13] mpt3sas driver NVMe support: Suganath Prabu S
2017-07-14 13:22 ` [PATCH v2 01/13] mpt3sas: Update MPI Header Suganath Prabu S
2017-08-03  6:24   ` Hannes Reinecke
2017-08-03  7:55     ` Johannes Thumshirn
2017-08-03  9:34       ` Sreekanth Reddy
2017-07-14 13:22 ` [PATCH v2 02/13] mpt3sas: Add nvme device support in slave alloc, target alloc and probe Suganath Prabu S
2017-08-03  6:27   ` Hannes Reinecke
2017-08-03 10:09     ` Sreekanth Reddy
2017-07-14 13:22 ` [PATCH v2 03/13] mpt3sas: SGL to PRP Translation for I/Os to NVMe devices Suganath Prabu S
2017-07-27 13:26   ` Martin K. Petersen [this message]
2017-07-14 13:22 ` [PATCH v2 04/13] mpt3sas: Added support for nvme encapsulated request message Suganath Prabu S
2017-08-03  6:33   ` Hannes Reinecke
2017-07-14 13:22 ` [PATCH v2 05/13] mpt3sas: API 's to support NVMe drive addition to SML Suganath Prabu S
2017-08-03  6:35   ` Hannes Reinecke
2017-07-14 13:22 ` [PATCH v2 06/13] mpt3sas: API's to remove nvme drive from sml Suganath Prabu S
2017-08-03  6:36   ` Hannes Reinecke
2017-07-14 13:22 ` [PATCH v2 07/13] mpt3sas: Handle NVMe PCIe device related events generated from firmware Suganath Prabu S
2017-08-03  6:38   ` Hannes Reinecke
2017-07-14 13:22 ` [PATCH v2 08/13] mpt3sas: Set NVMe device queue depth as 128 Suganath Prabu S
2017-08-03  6:39   ` Hannes Reinecke
2017-08-03  9:52     ` Sreekanth Reddy
2017-07-14 13:22 ` [PATCH v2 09/13] mpt3sas: scan and add nvme device after controller reset Suganath Prabu S
2017-08-03  6:40   ` Hannes Reinecke
2017-08-03 10:19     ` Sreekanth Reddy
2017-07-14 13:22 ` [PATCH v2 10/13] mpt3as: Add-Task-management-debug-info-for-NVMe-drives Suganath Prabu S
2017-08-03  6:43   ` Hannes Reinecke
2017-07-14 13:22 ` [PATCH v2 11/13] mpt3sas: NVMe drive support for BTDHMAPPING ioctl command and log info Suganath Prabu S
2017-08-03  6:44   ` Hannes Reinecke
2017-07-14 13:22 ` [PATCH v2 12/13] mpt3sas: Fix nvme drives checking for tlr Suganath Prabu S
2017-08-03  6:44   ` Hannes Reinecke
2017-07-14 13:22 ` [PATCH v2 13/13] mpt3sas: Update mpt3sas driver version Suganath Prabu S
2017-08-03  6:45   ` Hannes Reinecke
2017-07-25  5:20 ` [PATCH v2 00/13] mpt3sas driver NVMe support: Suganath Prabu Subramani
2017-08-02  8:14 ` Hannes Reinecke
2017-08-03  6:48   ` Hannes Reinecke
2017-08-05 13:53   ` Christoph Hellwig
2017-08-05 14:42     ` James Bottomley
2017-08-07 13:56       ` Kashyap Desai
2017-08-07 14:18         ` James Bottomley
2017-08-07 14:31           ` Kashyap Desai
2017-08-07 15:45             ` James Bottomley
2017-08-08  4:04               ` Keith Busch
2017-08-08  7:03                 ` Sreekanth Reddy
2017-08-08  7:29                   ` Keith Busch

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=yq1a83qvwmv.fsf@oracle.com \
    --to=martin.petersen@oracle.com \
    --cc=Sathya.Prakash@broadcom.com \
    --cc=chaitra.basappa@broadcom.com \
    --cc=hch@infradead.org \
    --cc=jejb@kernel.org \
    --cc=kashyap.desai@broadcom.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=sreekanth.reddy@broadcom.com \
    --cc=suganath-prabu.subramani@broadcom.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