From: Juergen Gross <jgross@suse.com>
To: xen-devel <xen-devel@lists.xenproject.org>
Cc: Anthony PERARD <anthony.perard@citrix.com>
Subject: Re: RING_FULL() equivalent for responses?
Date: Wed, 4 May 2016 10:04:25 +0200 [thread overview]
Message-ID: <5729AD09.5090202@suse.com> (raw)
In-Reply-To: <5729AC16.9040207@suse.com>
On 04/05/16 10:00, Juergen Gross wrote:
> Hi,
>
> during review of my qemu pvusb backend patch Anthony raised the
> question why my backend doesn't check for the ring being full before
> using RING_GET_RESPONSE().
>
> I've checked several existing backends and none of them is doing this
> test. To be precise: There is no macro to test this condition as
> RING_FULL() is doing this kind of test for the request ring only.
Aargh, forget it.
I've misread RING_FULL(). It is checking the request producer against
the response consumer, so everything is correct.
Sorry for the noise.
Juergen
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2016-05-04 8:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-04 8:00 RING_FULL() equivalent for responses? Juergen Gross
2016-05-04 8:04 ` Juergen Gross [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=5729AD09.5090202@suse.com \
--to=jgross@suse.com \
--cc=anthony.perard@citrix.com \
--cc=xen-devel@lists.xenproject.org \
/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.