- Subject: Re: [PATCH 1/2] dm: update max_io_len to support a split_io that is not a power of 2
- From: Alasdair G Kergon <agk@xxxxxxxxxx>
- Date: Mon, 30 Apr 2012 17:10:43 +0100
- Cc: dm-devel@xxxxxxxxxx, ejt@xxxxxxxxxx, agk@xxxxxxxxxx
- In-reply-to: <1335588269-807-1-git-send-email-snitzer@redhat.com>
- Mail-followup-to: Mike Snitzer <snitzer@xxxxxxxxxx>, Jonathan Brassow <jbrassow@xxxxxxxxxx>, dm-devel@xxxxxxxxxx, ejt@xxxxxxxxxx, agk@xxxxxxxxxx
- Organization: Red Hat UK Ltd. Registered in England and Wales, number 03798903. Registered Office: 64 Baker Street, 4th floor, London, W1U 7DF.
- References: <1335588269-807-1-git-send-email-snitzer@redhat.com>
- Reply-to: device-mapper development <dm-devel@xxxxxxxxxx>
- User-agent: Mutt/1.5.18 (2008-05-17)
On Sat, Apr 28, 2012 at 12:44:28AM -0400, Mike Snitzer wrote:
> Required to support a target's use of a non power of 2 blocksize.
For which targets?
(merge_bvec supported?)
> + boundary = ti->split_io - do_div(tmp, ti->split_io);
sector_div()?
What about 32-bit arch + LBD + large split_io (from raid?)
- Is a 32-bit restriction on split_io unreasonable nowadays?
- OR reasonable on 32bit/LBD?
- OR fallback to old code there?
Alasdair
--
dm-devel mailing list
dm-devel@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/dm-devel
[DM Crypt]
[Fedora Desktop]
[ATA RAID]
[Fedora Marketing]
[Fedora Packaging]
[Fedora SELinux]
[Yosemite Discussion]
[Yosemite Photos]
[KDE Users]
[Fedora Tools]
[Fedora Docs]