From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jan Beulich <JBeulich@novell.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 11:13:10 -0400 [thread overview]
Message-ID: <20110518151310.GC4709@dumpdata.com> (raw)
In-Reply-To: <4DD3FBED0200007800041E8E@vpn.id2.novell.com>
> >> 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.
> >
> > Aha! That is what you been trying to tell me. I will make a patch to make
> > sure to not overwrite the req->sector_number blindly. What other guest OSes
>
> Or use the patch I proposed?
Yes. Much superior to mine.
>
> > use barriers? I looked at Solaris (it uses 'feature-flush-cache'), NetBSD
> > ('feature-flush-cache') and Linux ('feature-barrier' and now in 2.6.40
> > 'feature-flush-cache').
> >
> > The GPLV Windows drivers have no barrier implementation - do you know if
> > the Novell ones are using barriers?
>
> No, I don't.
Any idea who might know?
next prev parent reply other threads:[~2011-05-18 15:13 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
2011-05-18 14:56 ` Konrad Rzeszutek Wilk
2011-05-18 15:03 ` Jan Beulich
2011-05-18 15:13 ` Konrad Rzeszutek Wilk [this message]
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=20110518151310.GC4709@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=JBeulich@novell.com \
--cc=jeremy@goop.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 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.