diff options
author | Chris Lalancette <clalance@redhat.com> | 2008-09-17 14:30:32 -0700 |
---|---|---|
committer | Jens Axboe <jens.axboe@oracle.com> | 2008-10-09 08:56:18 +0200 |
commit | 9246b5f06deeea541e7c62437c2ad19a0b1172c0 (patch) | |
tree | b7af564d1e32ce4eceba6f6a438256d6c3ca77fd /block | |
parent | 9c02f2b02e29a2244e36c6e1f246080d8afc6cff (diff) | |
download | linux-3.10-9246b5f06deeea541e7c62437c2ad19a0b1172c0.tar.gz linux-3.10-9246b5f06deeea541e7c62437c2ad19a0b1172c0.tar.bz2 linux-3.10-9246b5f06deeea541e7c62437c2ad19a0b1172c0.zip |
block: Expand Xen blkfront for > 16 xvd
Until recently, the maximum number of xvd block devices you could attach
to a Xen domU was 16. This limitation turned out to be problematic for
some users, so it was expanded to handle a much larger number of disks.
However, this requires a couple of changes in the way that blkfront
scans for disks. This functionality is already present in the Xen
linux-2.6.18-xen.hg tree; the attached patch adds this functionality to
the mainline xen-blkfront implementation. I successfully tested it on a
2.6.25 tree, and build tested it on 2.6.27-rc3.
Signed-off-by: Chris Lalancette <clalance@redhat.com>
Acked-by: Jeremy Fitzhardinge <jeremy@goop.org>
Signed-off-by: Jens Axboe <jens.axboe@oracle.com>
Diffstat (limited to 'block')
0 files changed, 0 insertions, 0 deletions