From: Gerd Hoffmann <kraxel@redhat.com>
To: Derek Murray <Derek.Murray@cl.cam.ac.uk>
Cc: Xen Development Mailing List <xen-devel@lists.xensource.com>
Subject: userspace block backend / gntdev problems
Date: Fri, 04 Jan 2008 14:48:21 +0100 [thread overview]
Message-ID: <477E3925.7070404@redhat.com> (raw)
Hi,
I'm running into trouble over and over again with my userspace block
backend daemon (blkbackd) developed as part of the xenner project.
First problem is the fixed limit of 128 slots. The frontend submits up
to 32 requests, with up to 11 grants each. With the shared ring this
sums up to 353 grants per block device. When is blkbackd running in aio
mode, thus many requests are in flight at the same time and thus also
many grants mapped at the same time, the 128 limit is easily reached. I
don't even need to stress the disk with bonnie or something, just
booting the virtual machine is enougth. Any chance replace the
fix-sized array with a list to remove that hard-coded limit? Or at
least raise the limit to -- say -- 1024 grants?
Second problem is that batched grant mappings (using
xc_gnttab_map_grant_refs) don't work reliable. Symtoms I see are random
failures with ENOMEM for no obvious reason (128 grant limit is *far*
away). Also host kernel crashes (kernel 2.6.21-2952.fc8xen).
When using xc_gnttab_map_grant_ref only (no batching) and limiting the
number requests in flight to 8 (so we stay below the 128 grant limit)
everything works nicely though.
cheers,
Gerd
next reply other threads:[~2008-01-04 13:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-04 13:48 Gerd Hoffmann [this message]
2008-01-04 14:50 ` userspace block backend / gntdev problems Derek Murray
2008-01-04 15:24 ` Gerd Hoffmann
2008-01-21 18:41 ` Markus Armbruster
2008-01-25 23:29 ` Pat Campbell
2008-01-26 8:41 ` Markus Armbruster
2008-01-26 8:48 ` Keir Fraser
2008-01-28 0:40 ` Pat Campbell
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=477E3925.7070404@redhat.com \
--to=kraxel@redhat.com \
--cc=Derek.Murray@cl.cam.ac.uk \
--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.