All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ming Lei <tom.leiming@gmail.com>
To: James Bottomley <James.Bottomley@hansenpartnership.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-scsi <linux-scsi@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] final round of SCSI updates for the 5.2+ merge window
Date: Sat, 20 Jul 2019 10:29:40 +0800	[thread overview]
Message-ID: <CACVXFVNOPhiUhrgw07sna0dt5Jy2zckbNXDWPPRAGadXQAS_mQ@mail.gmail.com> (raw)
In-Reply-To: <1563579201.1602.7.camel@HansenPartnership.com>

On Sat, Jul 20, 2019 at 8:38 AM James Bottomley
<James.Bottomley@hansenpartnership.com> wrote:
>
> This is the final round of mostly small fixes in our initial
> submit.  It's mostly minor fixes and driver updates.  The only change
> of note is adding a virt_boundary_mask to the SCSI host and host
> template to parametrise this for NVMe devices instead of having them do
> a call in slave_alloc.  It's a fairly straightforward conversion except
> in the two NVMe handling drivers that didn't set it who now have a
> virtual infinity parameter added.
>
> The patch is available here:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi.git scsi-fixes
>
> The short changelog is:
>
> Arnd Bergmann (1):
>       scsi: lpfc: reduce stack size with CONFIG_GCC_PLUGIN_STRUCTLEAK_VERBOSE
>
> Benjamin Block (3):
>       scsi: zfcp: fix GCC compiler warning emitted with -Wmaybe-uninitialized
>       scsi: zfcp: fix request object use-after-free in send path causing wrong traces
>       scsi: zfcp: fix request object use-after-free in send path causing seqno errors
>
> Christoph Hellwig (8):
>       scsi: megaraid_sas: set an unlimited max_segment_size
>       scsi: mpt3sas: set an unlimited max_segment_size for SAS 3.0 HBAs
>       scsi: IB/srp: set virt_boundary_mask in the scsi host
>       scsi: IB/iser: set virt_boundary_mask in the scsi host
>       scsi: storvsc: set virt_boundary_mask in the scsi host template
>       scsi: ufshcd: set max_segment_size in the scsi host template
>       scsi: core: take the DMA max mapping size into account

It has been observed on NVMe the above approach("take the DMA max
mapping size into account") causes performance regression, so I'd
suggest to fix dma_max_mapping_size() first.

Christoph has posted fix already, but looks not merged yet:

      https://lkml.org/lkml/2019/7/17/62


Thanks,
Ming Lei

  reply	other threads:[~2019-07-20  2:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-19 23:33 [GIT PULL] final round of SCSI updates for the 5.2+ merge window James Bottomley
2019-07-20  2:29 ` Ming Lei [this message]
2019-07-20 12:46   ` Martin K. Petersen
2019-07-20 18:40 ` pr-tracker-bot

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=CACVXFVNOPhiUhrgw07sna0dt5Jy2zckbNXDWPPRAGadXQAS_mQ@mail.gmail.com \
    --to=tom.leiming@gmail.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=torvalds@linux-foundation.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.