mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jeff Moyer <jmoyer@redhat.com>
To: axboe@kernel.dk, hch@infradead.org
Cc: ed.cashin@acm.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] block: Reinstate BLK_DEF_MAX_SECTORS
Date: Thu, 13 Aug 2015 14:57:55 -0400	[thread overview]
Message-ID: <1439492277-14638-1-git-send-email-jmoyer@redhat.com> (raw)

Commit 34b48db66e08 (block: remove artificial max_hw_sectors cap)
caused performance regressions for streaming I/O workloads across
a range of storage from SATA disks to enterprise storage arrays.
I was unable to actually show a performance gain for any storage
I have access to.  However, the patch was introduced to boost
performance on software RAID over SATA disks, and I don't have
access to such a configuration.

The compromise is to reinstate BLK_DEF_MAX_SECTORS, but to bump it
up to 2560 from 1024.  This number should allow full stripe writes
to 10 data disks with a chunk size of 128KB, and at the same time
does not regress the storage I have access to.

[PATCH 1/2] Revert "block: remove artifical max_hw_sectors cap"
[PATCH 2/2] block: bump BLK_DEF_MAX_SECTORS to 2560

 block/blk-settings.c       |    4 +++-
 drivers/block/aoe/aoeblk.c |    2 +-
 include/linux/blkdev.h     |    1 +
 3 files changed, 5 insertions(+), 2 deletions(-)

             reply	other threads:[~2015-08-13 18:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-13 18:57 Jeff Moyer [this message]
2015-08-13 18:57 ` [PATCH 1/2] Revert "block: remove artifical max_hw_sectors cap" Jeff Moyer
2015-08-15  1:18   ` Ed Cashin
2015-08-13 18:57 ` [PATCH 2/2] block: bump BLK_DEF_MAX_SECTORS to 2560 Jeff Moyer
2015-08-18 20:22 ` [PATCH 0/2] block: Reinstate BLK_DEF_MAX_SECTORS 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=1439492277-14638-1-git-send-email-jmoyer@redhat.com \
    --to=jmoyer@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=ed.cashin@acm.org \
    --cc=hch@infradead.org \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®