From: "Jan Beulich" <JBeulich@novell.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: jeremy@goop.org, xen-devel@lists.xensource.com
Subject: Re: [GIT PULL] for-2.6.32/bug-fixes
Date: Wed, 18 May 2011 15:31:35 +0100 [thread overview]
Message-ID: <4DD3F4670200007800041E55@vpn.id2.novell.com> (raw)
In-Reply-To: <20110518132442.GB3238@dumpdata.com>
>>> On 18.05.11 at 15:24, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote:
>> >Well, req->ns_segments = 0, so nseg is zero, which means all
>> >of those for loops never get executed.
>>
>> This you say is the case for the request you saw the failure with, or
>> *all* barrier requests? In the latter case, what do you conclude this
>
> Good question. It was the first barrier request sent when guest tried to
> mount the filesystem. I will instrument the code to see what the other
> barriers contained when they were sent.
That wouldn't tell you anything if they're all empty, as there's nothing
preventing other guests (including other guest OSes) to still send
non-empty ones - after all the protocol allows for this.
Jan
>> from?
next prev parent reply other threads:[~2011-05-18 14:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-18 6:22 [GIT PULL] for-2.6.32/bug-fixes Jan Beulich
2011-05-18 13:24 ` Konrad Rzeszutek Wilk
2011-05-18 14:31 ` Jan Beulich [this message]
2011-05-18 14:56 ` Konrad Rzeszutek Wilk
2011-05-18 15:03 ` Jan Beulich
2011-05-18 15:13 ` Konrad Rzeszutek Wilk
2011-05-18 15:23 ` Jan Beulich
-- strict thread matches above, loose matches on Subject: below --
2011-05-16 20:35 Konrad Rzeszutek Wilk
2011-05-17 9:48 ` Jan Beulich
2011-05-17 10:07 ` Jan Beulich
2011-05-17 14:16 ` Konrad Rzeszutek Wilk
2011-05-17 15:06 ` Jan Beulich
2011-05-17 15:57 ` Konrad Rzeszutek Wilk
2011-05-17 16:24 ` Jan Beulich
2011-05-17 16:43 ` Konrad Rzeszutek Wilk
2011-01-27 18:52 Konrad Rzeszutek Wilk
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=4DD3F4670200007800041E55@vpn.id2.novell.com \
--to=jbeulich@novell.com \
--cc=jeremy@goop.org \
--cc=konrad.wilk@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).