From: "Jérôme Petazzoni" <jp@enix.org>
To: xen-devel@lists.xensource.com
Cc: James Bulpin <James.Bulpin@cl.cam.ac.uk>
Subject: Re: xen+drbd (partial?) success story
Date: Thu, 28 Apr 2005 19:23:21 +0200 [thread overview]
Message-ID: <42711C09.1000407@enix.org> (raw)
In-Reply-To: <1114708213.15408.569.camel@plym.cl.cam.ac.uk>
>>Badness in blk_plug_device at drivers/block/ll_rw_blk.c:1217
>> [<c02270d0>] blk_plug_device+0x80/0x90
>> [<c7101a27>] drbd_make_request_common+0x727/0x8f0 [drbd]
>>
>>
>
>Did you compile the drbd module with ARCH=xen?
>
>
That's it ! Thanks a lot.
I had compiled with Debian's module-assistant and dumbly assumed that it
would reuse the correct ARCH setting from the specified source tree.
I was wrong, andre-building the module package the correct flags
(MAKEFLAGS="ARCH=xen") gave me a different module, which worked
perfectly, without those messages.
By the way, performance of drbd-backed root device in a domU seems now
equal to performance of raw access in dom0. Great !
prev parent reply other threads:[~2005-04-28 17:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-28 15:51 xen+drbd (partial?) success story Jérôme Petazzoni
[not found] ` <eab08754050428100451c0451f@mail.gmail.com>
2005-04-28 17:06 ` Jérôme Petazzoni
2005-04-28 17:10 ` James Bulpin
2005-04-28 17:23 ` Jérôme Petazzoni [this message]
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=42711C09.1000407@enix.org \
--to=jp@enix.org \
--cc=James.Bulpin@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.