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 2/2] block: bump BLK_DEF_MAX_SECTORS to 2560
Date: Thu, 13 Aug 2015 14:57:57 -0400 [thread overview]
Message-ID: <1439492277-14638-3-git-send-email-jmoyer@redhat.com> (raw)
In-Reply-To: <1439492277-14638-1-git-send-email-jmoyer@redhat.com>
A value of 2560 (1280k) will accommodate a 10-data-disk stripe
write with chunk size 128k. In the testing I've done using
iozone, fio, and aio-stress across a number of different storage
devices, a value of 1280 does not show a big performance
difference from 512, but will hopefully help software RAID
setups using SATA disks, as reported by Christoph.
NOTE: drivers/block/aoe/aoeblk.c sets its own max_hw_sectors_kb to
BLK_DEF_MAX_SECTORS. So, this patch essentially changes aeoblk to
Use a larger maximum sector size, and I did not test this.
Signed-off-by: Jeff Moyer <jmoyer@redhat.com>
---
include/linux/blkdev.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/blkdev.h b/include/linux/blkdev.h
index 1fd459e1..dbc845f 100644
--- a/include/linux/blkdev.h
+++ b/include/linux/blkdev.h
@@ -1138,7 +1138,7 @@ extern int blk_verify_command(unsigned char *cmd, fmode_t has_write_perm);
enum blk_default_limits {
BLK_MAX_SEGMENTS = 128,
BLK_SAFE_MAX_SECTORS = 255,
- BLK_DEF_MAX_SECTORS = 1024,
+ BLK_DEF_MAX_SECTORS = 2560,
BLK_MAX_SEGMENT_SIZE = 65536,
BLK_SEG_BOUNDARY_MASK = 0xFFFFFFFFUL,
};
--
1.8.3.1
next prev parent 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 [PATCH 0/2] block: Reinstate BLK_DEF_MAX_SECTORS Jeff Moyer
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 ` Jeff Moyer [this message]
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-3-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®