All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Ming Lei <tom.leiming@gmail.com>
Cc: James Bottomley <James.Bottomley@hansenpartnership.com>,
	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>,
	Christoph Hellwig <hch@lst.de>
Subject: Re: [GIT PULL] final round of SCSI updates for the 5.2+ merge window
Date: Sat, 20 Jul 2019 08:46:38 -0400	[thread overview]
Message-ID: <yq14l3gx49d.fsf@oracle.com> (raw)
In-Reply-To: <CACVXFVNOPhiUhrgw07sna0dt5Jy2zckbNXDWPPRAGadXQAS_mQ@mail.gmail.com> (Ming Lei's message of "Sat, 20 Jul 2019 10:29:40 +0800")


Hi Ming!

>> 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 specifically asked me to queue these up. I presume the swiotlb
tweak is going through his DMA tree and it is therefore orthogonal to
the SCSI changes.

I do think it's important that we get these fixed up in 5.3. And given
that we're on the eve of the merge window, the time to get these changes
merged is now. I'd hate to see them miss another release...

-- 
Martin K. Petersen	Oracle Linux Engineering

  reply	other threads:[~2019-07-20 12:49 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
2019-07-20 12:46   ` Martin K. Petersen [this message]
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=yq14l3gx49d.fsf@oracle.com \
    --to=martin.petersen@oracle.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=akpm@linux-foundation.org \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=tom.leiming@gmail.com \
    --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.