From: Chris Lalancette <clalance@redhat.com>
To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: [PATCH 0/4]: Expand xvd to support > 16 devices
Date: Mon, 23 Jun 2008 20:26:28 +0200 [thread overview]
Message-ID: <485FEAD4.3090009@redhat.com> (raw)
All,
Current blktap and blkfront are limited to 16 xvd devices (xvda -> xvdp).
This is enforced in the userland dom0 tools, but is also hard-coded into the
blkfront kernel code (even though modern dev_t can hold many more than 256
minors). Based on the discussion that we had here:
http://lists.xensource.com/archives/html/xen-devel/2008-05/msg00128.html
I ended up implementing Ian Jackson's suggestion here:
http://lists.xensource.com/archives/html/xen-devel/2008-05/msg00231.html
Basically, I left the old format alone, but added a new format that looks like:
1 << 28 | disk << 8 | partition xvd, disks or partitions 16 onwards
This format is used for any disks xvdq onward. Note that blktap has a hardcoded
limit of 100 devices that I did not change with this patch series; if that ends
up being a problem, then that's just a simple #define to change.
I did not expand the number of partitions available (it's still 15), although
there is space in the allocation to do that if someone wishes. More details are
in each individual patch.
Note that I developed this against RHEL-5 kernels and ported it over to
xen-unstable, and only compile tested it there.
Chris Lalancette
next prev reply other threads:[~2008-06-23 18:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-23 18:26 [PATCH 1/4]: Fix blkfront to accept expanded devices Chris Lalancette
2008-06-23 18:26 ` Chris Lalancette [this message]
2008-06-23 19:24 ` [PATCH 0/4]: Expand xvd to support > 16 devices Ian Jackson
2008-06-25 9:45 ` Chris Lalancette
2008-06-25 11:19 ` Keir Fraser
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=485FEAD4.3090009@redhat.com \
--to=clalance@redhat.com \
--cc=xen-devel@lists.xensource.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.