From: Tejun Heo <tj@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: [GIT PULL 2/2] libata changes for v4.18-rc1
Date: Tue, 5 Jun 2018 12:15:25 -0700 [thread overview]
Message-ID: <20180605191525.GF1351649@devbig577.frc2.facebook.com> (raw)
In-Reply-To: <20180605190807.GE1351649@devbig577.frc2.facebook.com>
Hello, Linus.
This is the second part of libata pull request.
* libata has always been limiting the maximum queue depth to 31, 1 set
aside mostly for historical reasons. This didn't use to make much
difference but Jens found out that modern hard drives can actually
perform measurably better with the extra one queue depth. Jens
updated libata core so that it can make use of full 32 queue depth.
* Damien updated command retry logic in error handling so that it
doesn't unnecessarily retry when upper layer (SCSI) is gonna handle
them.
* A couple misc changes.
Thanks.
The following changes since commit 75bc37fefc4471e718ba8e651aa74673d4e0a9eb:
Linux 4.17-rc4 (2018-05-06 16:57:38 -1000)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tj/libata.git for-4.18
for you to fetch changes up to 88e10092f6a623b88808f782b6637162b5b658fb:
sata_fsl: use the right type for tag bitshift (2018-05-14 08:14:21 -0700)
----------------------------------------------------------------
Andy Shevchenko (1):
ata: hpt37x: Convert to use match_string() helper
Christoph Hellwig (1):
sata_nv: don't use block layer bounce buffer
Damien Le Moal (5):
libata: Fix comment typo in ata_eh_analyze_tf()
libata: Fix ata_err_string()
libata: Make ata_dev_set_mode() less verbose
libata: Honor RQF_QUIET flag
libata: Fix command retry decision
Jens Axboe (10):
libata: introduce notion of separate hardware tags
libata: convert core and drivers to ->hw_tag usage
libata: bump ->qc_active to a 64-bit type
libata: use ata_tag_internal() consistently
libata: remove assumption that ATA_MAX_QUEUE - 1 is the max
sata_nv: set host can_queue count appropriately
libata: add extra internal command
libata: don't clamp queue depth to ATA_MAX_QUEUE - 1
ahci: enable full queue depth of 32
sata_fsl: use the right type for tag bitshift
drivers/ata/acard-ahci.c | 4 +-
drivers/ata/ahci.h | 2 +-
drivers/ata/libahci.c | 8 ++--
drivers/ata/libata-core.c | 61 ++++++++++++---------------
drivers/ata/libata-eh.c | 56 ++++++++++++++++++++-----
drivers/ata/libata-scsi.c | 19 +++++----
drivers/ata/pata_hpt37x.c | 13 +++---
drivers/ata/sata_dwc_460ex.c | 14 +++----
drivers/ata/sata_fsl.c | 10 ++---
drivers/ata/sata_mv.c | 26 ++++++------
drivers/ata/sata_nv.c | 98 +++++++++++++++++++-------------------------
drivers/ata/sata_sil24.c | 6 +--
include/linux/libata.h | 22 +++++-----
13 files changed, 177 insertions(+), 162 deletions(-)
--
tejun
next prev parent reply other threads:[~2018-06-05 19:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-05 19:08 [GIT PULL 1/2] libata changes for v4.18-rc1 Tejun Heo
2018-06-05 19:15 ` Tejun Heo [this message]
2018-06-18 7:33 ` Constant ata messages on console with commit 28361c403683 ("libata: add extra internal command") (was Re: [GIT PULL 2/2] libata changes for v4.18-rc1) Michael Ellerman
2018-06-18 14:33 ` Jens Axboe
2018-06-19 7:29 ` Michael Ellerman
2018-06-19 15:26 ` Jens Axboe
2018-06-19 15:39 ` Jens Axboe
2018-06-19 23:35 ` Michael Ellerman
2018-06-19 23:38 ` Jens Axboe
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=20180605191525.GF1351649@devbig577.frc2.facebook.com \
--to=tj@kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).