- To: linux-raid@xxxxxxxxxxxxxxx
- Subject: Reason for md raid1 max_sectors_kb limited to 127?
- From: Sebastian Riemer <sebastian.riemer@xxxxxxxxxxxxxxxx>
- Date: Mon, 07 May 2012 11:41:43 +0200
- User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20111110 Iceowl/1.0b1 Icedove/3.0.11
Hi list,
I'm wondering why max_sectors_kb is set to 127 with md raid1.
This value is at 512 on normal HDDs.
If I do a file copy on ext4 on a normal HDD then I can see with
blktrace/blkparse that 128 KiB chunks are read and 512 KiB chunks are
written.
With md raid it looks like this: 124 KiB, 4 KiB, 124 KiB, 4 KiB, ... .
This looks very inefficient.
So, is there a particular reason that max_sectors_kb is set to 127?
Cheers,
Sebastian
--
Sebastian Riemer
Linux Kernel Developer
ProfitBricks GmbH
Greifswalder Str. 207
10405 Berlin, Germany
Tel.: +49 - 30 - 60 98 56 991 - 303
Fax: +49 - 30 - 51 64 09 22
Email: sebastian.riemer@xxxxxxxxxxxxxxxx
Web: http://www.profitbricks.com/
Sitz der Gesellschaft: Berlin
Registergericht: Amtsgericht Charlottenburg, HRB 125506 B
Geschäftsführer: Andreas Gauger, Achim Weiss
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
[ATA RAID]
[Linux SCSI Target Infrastructure]
[Managing RAID on Linux]
[Linux IDE]
[Linux SCSI]
[Linux Hams]
[Device-Mapper]
[Kernel]
[Linux Books]
[Linux Admin]
[Linux Net]
[GFS]
[RPM]
[git]
[Photos]
[Yosemite Photos]
[Yosemite News]
[AMD 64]
[Linux Networking]