From: Alasdair G Kergon <agk@redhat.com>
To: Mike Snitzer <snitzer@redhat.com>,
Jonathan Brassow <jbrassow@redhat.com>
Cc: dm-devel@redhat.com, ejt@redhat.com, agk@redhat.com
Subject: Re: [PATCH 1/2] dm: update max_io_len to support a split_io that is not a power of 2
Date: Mon, 30 Apr 2012 17:10:43 +0100 [thread overview]
Message-ID: <20120430161043.GB8713@agk-dp.fab.redhat.com> (raw)
In-Reply-To: <1335588269-807-1-git-send-email-snitzer@redhat.com>
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
next prev parent reply other threads:[~2012-04-30 16:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-28 4:44 [PATCH 1/2] dm: update max_io_len to support a split_io that is not a power of 2 Mike Snitzer
2012-04-28 4:44 ` [PATCH 2/2] dm thin: support for non power of 2 pool blocksize Mike Snitzer
2012-04-28 4:51 ` [PATCH] thinp-test-suite: " Mike Snitzer
2012-04-28 15:32 ` Mike Snitzer
2012-04-30 10:15 ` [PATCH] " Joe Thornber
2012-04-30 9:55 ` [PATCH 2/2] dm thin: " Joe Thornber
2012-04-30 17:33 ` Mike Snitzer
2012-05-01 9:41 ` Joe Thornber
2012-04-30 16:10 ` Alasdair G Kergon [this message]
2012-04-30 17:24 ` [PATCH 1/2] dm: update max_io_len to support a split_io that is not a power of 2 Mike Snitzer
2012-04-30 18:36 ` Alasdair G Kergon
2012-04-30 18:59 ` Mike Snitzer
2012-05-01 15:42 ` Brassow Jonathan
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=20120430161043.GB8713@agk-dp.fab.redhat.com \
--to=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=ejt@redhat.com \
--cc=jbrassow@redhat.com \
--cc=snitzer@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.