From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Chris Lalancette <clalance@redhat.com>
Cc: Jens Axboe <jens.axboe@oracle.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND]: Expand Xen blkfront for > 16 xvd
Date: Wed, 17 Sep 2008 11:11:59 -0700 [thread overview]
Message-ID: <48D1486F.7060506@goop.org> (raw)
In-Reply-To: <48D0BA0A.1070709@redhat.com>
Chris Lalancette wrote:
> 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>
>
Jens, do you have this one already?
Thanks,
J
next prev parent reply other threads:[~2008-09-17 18:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-17 8:04 Chris Lalancette
2008-09-17 18:11 ` Jeremy Fitzhardinge [this message]
2008-09-17 18:20 ` Jens Axboe
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=48D1486F.7060506@goop.org \
--to=jeremy@goop.org \
--cc=clalance@redhat.com \
--cc=jens.axboe@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome