On Wed, Jan 08, 2014 at 07:39:21PM +0800, majianpeng wrote: > Let's the stripe_size of back device is io_opt of request_queue make > good sense. > > Signed-off-by: Jianpeng Ma <[email protected]> > --- > drivers/md/bcache/super.c | 6 +++++- > 1 file changed, 5 insertions(+), 1 deletion(-) > > diff --git a/drivers/md/bcache/super.c b/drivers/md/bcache/super.c > index c57bfa0..21f77c1 100644 > --- a/drivers/md/bcache/super.c > +++ b/drivers/md/bcache/super.c > @@ -759,11 +759,15 @@ static int bcache_device_init(struct bcache_device *d, > unsigned block_size, > sector_t sectors) > { > struct request_queue *q; > + struct cached_dev *dc; > size_t n; > int minor; > > + dc = container_of(d, struct cached_dev, disk); > + q = bdev_get_queue(dc->bdev); > + > if (!d->stripe_size) > - d->stripe_size = 1 << 31; > + d->stripe_size = min_t(unsigned, 1 << 31, q->limits.io_opt); > > d->nr_stripes = DIV_ROUND_UP_ULL(sectors, d->stripe_size);
We only care about stripe size if we're trying to flush dirty data by stripe - this is for writeback with raid5/6 stripe awareness. There's currently no way to enable this functionality, the patch that enables it is going into 3.14. If we don't have that stuff enabled, we only care about stripes insofar as we have to track dirty data at _some_ granularity. -- To unsubscribe from this list: send the line "unsubscribe linux-bcache" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
