All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Oleksandr Andrushchenko <andr2000@gmail.com>
Cc: alsa-devel@alsa-project.org,
	Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>,
	tiwai@suse.de, Clemens Ladisch <clemens@ladisch.de>,
	Takashi Sakamoto <o-takashi@sakamocchi.jp>,
	Oleksandr Grytsov <oleksandr_grytsov@epam.com>,
	xen-devel@lists.xenproject.org
Subject: Re: [Xen-devel][PATCH v2 2/3] sndif: Add explicit back and front synchronization
Date: Thu, 15 Mar 2018 16:17:24 -0400	[thread overview]
Message-ID: <20180315201724.GN10870@char.us.oracle.com> (raw)
In-Reply-To: <1521043365-26813-3-git-send-email-andr2000@gmail.com>

> + ******************************************************************************
> + *                        Back to front events delivery
> + ******************************************************************************
> + * In order to deliver asynchronous events from back to front a shared page is
> + * allocated by front and its granted reference propagated to back via
> + * XenStore entries (evt-ring-ref/evt-event-channel).
> + * This page has a common header used by both front and back to synchronize
> + * access and control event's ring buffer, while back being a producer of the
> + * events and front being a consumer. The rest of the page after the header
> + * is used for event packets.
> + *
> + * Upon reception of an event(s) front may confirm its reception
> + * for either each event, group of events or none.
> + */
> +
> +struct xensnd_event_page {
> +    uint32_t in_cons;
> +    uint32_t in_prod;
> +    uint8_t reserved[24];

Could this be aligned at 64 bytes?
> +};
> +

  reply	other threads:[~2018-03-15 20:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-14 16:02 [Xen-devel][PATCH v2 0/3] sndif: add explicit back and front synchronization Oleksandr Andrushchenko
2018-03-14 16:02 ` [PATCH v2 1/3] sndif: Introduce protocol version Oleksandr Andrushchenko
2018-03-14 16:02 ` [Xen-devel][PATCH " Oleksandr Andrushchenko
2018-03-15 20:14   ` Konrad Rzeszutek Wilk
2018-03-15 20:14   ` [PATCH " Konrad Rzeszutek Wilk
2018-03-14 16:02 ` [Xen-devel][PATCH v2 2/3] sndif: Add explicit back and front synchronization Oleksandr Andrushchenko
2018-03-15 20:17   ` Konrad Rzeszutek Wilk [this message]
2018-03-16  6:24     ` Oleksandr Andrushchenko
2018-03-16  6:24     ` [PATCH " Oleksandr Andrushchenko
2018-03-15 20:17   ` Konrad Rzeszutek Wilk
2018-03-14 16:02 ` Oleksandr Andrushchenko
2018-03-14 16:02 ` [Xen-devel][PATCH v2 3/3] sndif: Add explicit back and front parameter negotiation Oleksandr Andrushchenko
2018-03-14 16:02 ` [PATCH " Oleksandr Andrushchenko

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=20180315201724.GN10870@char.us.oracle.com \
    --to=konrad.wilk@oracle.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=andr2000@gmail.com \
    --cc=clemens@ladisch.de \
    --cc=o-takashi@sakamocchi.jp \
    --cc=oleksandr_andrushchenko@epam.com \
    --cc=oleksandr_grytsov@epam.com \
    --cc=tiwai@suse.de \
    --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.