All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: James Smart <jsmart2021@gmail.com>,
	linux-scsi@vger.kernel.org, linux-nvme@lists.infradead.org
Cc: Dick Kennedy <dick.kennedy@broadcom.com>,
	James Smart <james.smart@broadcom.com>
Subject: Re: [PATCH 08/15] lpfc: Separate NVMET RQ buffer posting from IO resources SGL/iocbq/context
Date: Thu, 11 May 2017 09:23:00 +0200	[thread overview]
Message-ID: <968af0f0-078b-fd85-363c-0fe3c111d3f8@suse.de> (raw)
In-Reply-To: <20170510190713.30171-9-jsmart2021@gmail.com>

On 05/10/2017 09:07 PM, James Smart wrote:
> Currently IO resources are mapped 1 to 1 with RQ buffers posted
> 
> Added logic to separate RQE buffers from IO op resources
> (sgl/iocbq/context). During initialization, the driver will determine
> how many SGLs it will allocate for NVMET (based on what the
> firmware reports) and associate a NVMET IOCBq and NVMET context
> structure with each one.
> 
> Now that hdr/data buffers are immediately reposted back to the RQ,
> 512 RQEs for each MRQ is sufficient. Also, since NVMET data buffers
> are now 128 bytes, lpfc_nvmet_mrq_post is not necessary anymore
> as we will always post the max (512) buffers per NVMET MRQ.
> 
> Signed-off-by: Dick Kennedy <dick.kennedy@broadcom.com>
> Signed-off-by: James Smart <james.smart@broadcom.com>
> ---
>  drivers/scsi/lpfc/lpfc.h       |  11 +-
>  drivers/scsi/lpfc/lpfc_attr.c  |  11 --
>  drivers/scsi/lpfc/lpfc_crtn.h  |   8 +-
>  drivers/scsi/lpfc/lpfc_init.c  |  92 ++-------------
>  drivers/scsi/lpfc/lpfc_mem.c   |  73 +-----------
>  drivers/scsi/lpfc/lpfc_nvmet.c | 246 +++++++++++++++++++++++++++++++----------
>  drivers/scsi/lpfc/lpfc_nvmet.h |   1 +
>  drivers/scsi/lpfc/lpfc_sli.c   |  88 +++++++++++++--
>  drivers/scsi/lpfc/lpfc_sli4.h  |   4 +-
>  9 files changed, 295 insertions(+), 239 deletions(-)
> 
Re-posting must die :-)

Reviewed-by: Hannes Reinecke <hare@suse.com>

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		   Teamlead Storage & Networking
hare@suse.de			               +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton
HRB 21284 (AG Nürnberg)

WARNING: multiple messages have this Message-ID (diff)
From: hare@suse.de (Hannes Reinecke)
Subject: [PATCH 08/15] lpfc: Separate NVMET RQ buffer posting from IO resources SGL/iocbq/context
Date: Thu, 11 May 2017 09:23:00 +0200	[thread overview]
Message-ID: <968af0f0-078b-fd85-363c-0fe3c111d3f8@suse.de> (raw)
In-Reply-To: <20170510190713.30171-9-jsmart2021@gmail.com>

On 05/10/2017 09:07 PM, James Smart wrote:
> Currently IO resources are mapped 1 to 1 with RQ buffers posted
> 
> Added logic to separate RQE buffers from IO op resources
> (sgl/iocbq/context). During initialization, the driver will determine
> how many SGLs it will allocate for NVMET (based on what the
> firmware reports) and associate a NVMET IOCBq and NVMET context
> structure with each one.
> 
> Now that hdr/data buffers are immediately reposted back to the RQ,
> 512 RQEs for each MRQ is sufficient. Also, since NVMET data buffers
> are now 128 bytes, lpfc_nvmet_mrq_post is not necessary anymore
> as we will always post the max (512) buffers per NVMET MRQ.
> 
> Signed-off-by: Dick Kennedy <dick.kennedy at broadcom.com>
> Signed-off-by: James Smart <james.smart at broadcom.com>
> ---
>  drivers/scsi/lpfc/lpfc.h       |  11 +-
>  drivers/scsi/lpfc/lpfc_attr.c  |  11 --
>  drivers/scsi/lpfc/lpfc_crtn.h  |   8 +-
>  drivers/scsi/lpfc/lpfc_init.c  |  92 ++-------------
>  drivers/scsi/lpfc/lpfc_mem.c   |  73 +-----------
>  drivers/scsi/lpfc/lpfc_nvmet.c | 246 +++++++++++++++++++++++++++++++----------
>  drivers/scsi/lpfc/lpfc_nvmet.h |   1 +
>  drivers/scsi/lpfc/lpfc_sli.c   |  88 +++++++++++++--
>  drivers/scsi/lpfc/lpfc_sli4.h  |   4 +-
>  9 files changed, 295 insertions(+), 239 deletions(-)
> 
Re-posting must die :-)

Reviewed-by: Hannes Reinecke <hare at suse.com>

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		   Teamlead Storage & Networking
hare at suse.de			               +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 N?rnberg
GF: F. Imend?rffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton
HRB 21284 (AG N?rnberg)

  reply	other threads:[~2017-05-11  7:23 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-10 19:06 [PATCH 00/15] lpfc updates for 11.2.0.14 James Smart
2017-05-10 19:06 ` James Smart
2017-05-10 19:06 ` [PATCH 01/15] lpfc: Fix used-RPI accounting problem James Smart
2017-05-10 19:06   ` James Smart
2017-05-11  6:04   ` Hannes Reinecke
2017-05-11  6:04     ` Hannes Reinecke
2017-05-10 19:07 ` [PATCH 02/15] lpfc: Fix system crash when port is reset James Smart
2017-05-10 19:07   ` James Smart
2017-05-11  6:05   ` Hannes Reinecke
2017-05-11  6:05     ` Hannes Reinecke
2017-05-15 19:31   ` Guilherme G. Piccoli
2017-05-10 19:07 ` [PATCH 03/15] lpfc: Adding additional stats counters for nvme James Smart
2017-05-10 19:07   ` James Smart
2017-05-11  6:06   ` Hannes Reinecke
2017-05-11  6:06     ` Hannes Reinecke
2017-05-10 19:07 ` [PATCH 04/15] lpfc: Fix nvmet RQ resource needs for large block writes James Smart
2017-05-10 19:07   ` James Smart
2017-05-11  6:18   ` Hannes Reinecke
2017-05-11  6:18     ` Hannes Reinecke
2017-05-15 21:48     ` James Smart
2017-05-15 21:48       ` James Smart
2017-05-10 19:07 ` [PATCH 05/15] lpfc: Fix NVMEI driver not decrementing counter causing bad rport state James Smart
2017-05-10 19:07   ` James Smart
2017-05-11  6:18   ` Hannes Reinecke
2017-05-11  6:18     ` Hannes Reinecke
2017-05-10 19:07 ` [PATCH 06/15] lpfc: Fix NMI watchdog assertions when running nvmet IOPS tests James Smart
2017-05-10 19:07   ` James Smart
2017-05-11  6:21   ` Hannes Reinecke
2017-05-11  6:21     ` Hannes Reinecke
2017-05-10 19:07 ` [PATCH 07/15] lpfc: Separate NVMET data buffer pool fir ELS/CT James Smart
2017-05-10 19:07   ` James Smart
2017-05-11  6:22   ` Hannes Reinecke
2017-05-11  6:22     ` Hannes Reinecke
2017-05-10 19:07 ` [PATCH 08/15] lpfc: Separate NVMET RQ buffer posting from IO resources SGL/iocbq/context James Smart
2017-05-10 19:07   ` James Smart
2017-05-11  7:23   ` Hannes Reinecke [this message]
2017-05-11  7:23     ` Hannes Reinecke
2017-05-10 19:07 ` [PATCH 09/15] lpfc: Added recovery logic for running out of NVMET IO context resources James Smart
2017-05-10 19:07   ` James Smart
2017-05-11  7:24   ` Hannes Reinecke
2017-05-11  7:24     ` Hannes Reinecke
2017-05-10 19:07 ` [PATCH 10/15] lpfc: Fix NVME I+T not registering NVME as a supported FC4 type James Smart
2017-05-10 19:07   ` James Smart
2017-05-11  7:35   ` Hannes Reinecke
2017-05-11  7:35     ` Hannes Reinecke
2017-05-15 21:57     ` James Smart
2017-05-15 21:57       ` James Smart
2017-05-10 19:07 ` [PATCH 11/15] lpfc: Fix debugfs root inode "lpfc" not getting deleted on driver unload James Smart
2017-05-10 19:07   ` James Smart
2017-05-11  7:45   ` Hannes Reinecke
2017-05-11  7:45     ` Hannes Reinecke
2017-05-10 19:07 ` [PATCH 12/15] lpfc: Cleanup entry_repost settings on SLI4 queues James Smart
2017-05-10 19:07   ` James Smart
2017-05-11  7:49   ` Hannes Reinecke
2017-05-11  7:49     ` Hannes Reinecke
2017-05-15 22:13     ` James Smart
2017-05-15 22:13       ` James Smart
2017-05-10 19:07 ` [PATCH 13/15] lpfc: Fix NVMEI's handling of NVMET's PRLI response attributes James Smart
2017-05-10 19:07   ` James Smart
2017-05-11  7:50   ` Hannes Reinecke
2017-05-11  7:50     ` Hannes Reinecke
2017-05-10 19:07 ` [PATCH 14/15] lpfc: Add MDS Diagnostic support James Smart
2017-05-10 19:07   ` James Smart
2017-05-11  7:51   ` Hannes Reinecke
2017-05-11  7:51     ` Hannes Reinecke
2017-05-10 19:07 ` [PATCH 15/15] lpfc: update version to 11.2.0.14 James Smart
2017-05-10 19:07   ` James Smart
2017-05-11  7:51   ` Hannes Reinecke
2017-05-11  7:51     ` Hannes Reinecke

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=968af0f0-078b-fd85-363c-0fe3c111d3f8@suse.de \
    --to=hare@suse.de \
    --cc=dick.kennedy@broadcom.com \
    --cc=james.smart@broadcom.com \
    --cc=jsmart2021@gmail.com \
    --cc=linux-nvme@lists.infradead.org \
    --cc=linux-scsi@vger.kernel.org \
    /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.