From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Chris Lalancette <clalance@redhat.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH]: Expand Xen blkfront for > 16 xvd
Date: Mon, 18 Aug 2008 10:16:56 -0700 [thread overview]
Message-ID: <48A9AE88.3060507@goop.org> (raw)
In-Reply-To: <48A400EC.9040407@redhat.com>
Chris Lalancette wrote:
> Jeremy,
> 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 haven't tested this yet. You have tested it OK with some pvops
kernel? If so, send it to Jens Axboe with my ack.
> I successfully tested it on a 2.6.25 tree. I build tested it
> on 2.6.27-rc3, but couldn't get that tree to boot due to some other bug.
What other bug?
J
next prev parent reply other threads:[~2008-08-18 17:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-14 9:54 [PATCH]: Expand Xen blkfront for > 16 xvd Chris Lalancette
2008-08-14 9:54 ` Chris Lalancette
2008-08-18 17:16 ` Jeremy Fitzhardinge [this message]
2008-08-19 6:52 ` [Xen-devel] " Chris Lalancette
2008-08-19 6:52 ` Chris Lalancette
-- strict thread matches above, loose matches on Subject: below --
2008-08-19 6:59 Chris Lalancette
2008-08-19 6:59 ` Chris Lalancette
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=48A9AE88.3060507@goop.org \
--to=jeremy@goop.org \
--cc=clalance@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--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.