From: Kip Macy <kip.macy@gmail.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: xen-devel@lists.xensource.com, Steven Hand <Steven.Hand@cl.cam.ac.uk>
Subject: Re: Unstableness in grant table block drivers
Date: Wed, 13 Apr 2005 19:55:08 -0700 [thread overview]
Message-ID: <b1fa2917050413195530dcae2c@mail.gmail.com> (raw)
In-Reply-To: <425DD4FA.2060009@us.ibm.com>
If I do
3 VMs x 40 iSCSI LUNs/VM x foreach (lun) dd if=/dev/zero of=/dev/xbd<n> bs=64k
iscsi ops will stop going across the wire in 2 - 3 minutes. Access to
the LUNs from DOM0 still works. I haven't had a chance to try a
smaller configuration. This is all scripted so it only takes a minute
to set up, but I'm busy trying to get FreeBSD to run (and not have
DOM0 lockup) on a recent -unstable.
-Kip
On 4/13/05, Anthony Liguori <aliguori@us.ibm.com> wrote:
> Kip Macy wrote:
>
> >I think it is safe to say that the blkback/blkfront still have some
> >serious bugs to be fixed even in the absences of grant tables.
> >
> >
> How many is a lot of VBDs? I've done quite a bit of testing of the
> devices (with Xend and with VM-Tools) and I've found the block drivers
> to be very reliable. I've not gone much higher than 3 or 4 VBDs for
> each domain though.
>
> Regards,
> Anthony Liguoris
>
next prev parent reply other threads:[~2005-04-14 2:55 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <aliguori@us.ibm.com>
2005-04-14 1:18 ` Unstableness in grant table block drivers Anthony Liguori
2005-04-14 1:20 ` Steven Hand
2005-04-14 1:46 ` Anthony Liguori
2005-04-14 1:53 ` Kip Macy
2005-04-14 2:27 ` Anthony Liguori
2005-04-14 2:55 ` Kip Macy [this message]
2005-04-16 1:32 Ian Pratt
2005-04-16 15:39 ` Ryan Harper
2005-04-18 16:38 ` Christopher Clark
2005-04-18 16:45 ` Ryan Harper
2005-04-18 20:51 ` Ryan Harper
2005-04-20 18:52 ` Christopher Clark
2005-04-20 19:37 ` Ryan Harper
2005-04-22 18:57 ` Ryan Harper
2005-04-22 19:06 ` Anthony Liguori
2005-05-12 1:50 ` Xiaofeng Ling
-- strict thread matches above, loose matches on Subject: below --
2005-04-15 22:30 Ian Pratt
2005-04-16 1:18 ` Christopher Clark
2005-04-16 1:32 ` Christopher Clark
2005-04-16 3:03 ` David Hopwood
2005-04-14 10:24 Ian Pratt
2005-04-14 10:34 ` Ge van Geldorp
[not found] <E1DLu58-0005lx-KR@host-192-168-0-1-bcn-london>
2005-04-14 10:17 ` Ge van Geldorp
2005-04-14 1:16 Ian Pratt
2005-04-14 1:43 ` Anthony Liguori
2005-04-14 2:04 ` Christopher Clark
2005-04-14 2:17 ` Kip Macy
2005-04-14 2:25 ` Anthony Liguori
2005-04-14 15:00 ` Ryan Harper
2005-04-14 16:34 ` Christopher Clark
2005-04-14 17:28 ` Ryan Harper
2005-04-15 18:45 ` Christopher Clark
2005-04-15 21:14 ` Ryan Harper
2005-04-15 21:32 ` Kip Macy
2005-04-15 21:41 ` Ryan Harper
2005-04-15 21:46 ` Kip Macy
2005-04-15 21:50 ` Ryan Harper
2005-04-15 21:52 ` Ryan Harper
2005-04-15 22:07 ` Christopher Clark
2005-04-15 22:08 ` Ryan Harper
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=b1fa2917050413195530dcae2c@mail.gmail.com \
--to=kip.macy@gmail.com \
--cc=Steven.Hand@cl.cam.ac.uk \
--cc=aliguori@us.ibm.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.