All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: Ian Campbell <ian.campbell@citrix.com>, xen-devel@lists.xen.org
Cc: tim@xen.org, keir@xen.org, ian.jackson@eu.citrix.com,
	jbeulich@suse.com, "Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: [PATCH DOCDAY v2] netif.h: describe request/response structures in terms of binary layout
Date: Wed, 25 Feb 2015 13:57:02 +0000	[thread overview]
Message-ID: <54EDD4AE.1050408@citrix.com> (raw)
In-Reply-To: <1424871588-28809-1-git-send-email-ian.campbell@citrix.com>

On 25/02/15 13:39, Ian Campbell wrote:
> 
> + * Guest transmit
> + * ==============
> + *
> + * Ring slot size is 12 octets, however not all request/response
> + * structs use the full size.
> + *
> + * tx request data (netif_tx_request_t)
> + * ------------------------------------
> + *
> + *    0     1     2     3     4     5     6     7  octet
> + * +-----+-----+-----+-----+-----+-----+-----+-----+
> + * | grant ref             | offset    | flags     |
> + * +-----+-----+-----+-----+-----+-----+-----+-----+
> + * | id        | size      |
> + * +-----+-----+-----+-----+
> + *
> + * grant ref: Reference to buffer page.
> + * offset: Offset within buffer page.
> + * flags: NETTXF_*.
> + * id: request identifier, echoed in response.
> + * size: packet size in bytes.

This size field should be described better since it's a bit weird when a
packet it split across multiple requests -- I have to look at the
implementations every time.

David

  reply	other threads:[~2015-02-25 13:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-25 13:39 [PATCH DOCDAY v2] netif.h: describe request/response structures in terms of binary layout Ian Campbell
2015-02-25 13:57 ` David Vrabel [this message]
2015-03-02 17:08   ` Ian Campbell
2015-03-02 17:12     ` David Vrabel
2015-03-03 11:27 ` Ian Campbell

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=54EDD4AE.1050408@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jbeulich@suse.com \
    --cc=keir@xen.org \
    --cc=roger.pau@citrix.com \
    --cc=tim@xen.org \
    --cc=xen-devel@lists.xen.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.