xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Paul Durrant <paul.durrant@citrix.com>
To: xen-devel@lists.xenproject.org
Cc: Paul Durrant <paul.durrant@citrix.com>
Subject: [PATCH v2 0/4] Updates to public/io/netif.h
Date: Fri, 16 Oct 2015 13:40:35 +0100	[thread overview]
Message-ID: <1444999239-24681-1-git-send-email-paul.durrant@citrix.com> (raw)

This series makes several modifications to netif.h in anticipation of
implementing NDIS RSS support in the Windows frontend driver.

Patch #1 documents the (sad) reality of the netif_rx_request/response id
field, which has been long overdue.

Patch #2 adds a definition of the NETRXF_gso_prefix flag which has been
present in the Linux variant of the header for several years

Patch #3 adds documentation for how negotiation of a hash algortithm to
be used on the frontend receive side should be done.

Patch #4 adds a new netif_extra_info type for passing hash values between
backend and frontend (or vice versa).

             reply	other threads:[~2015-10-16 12:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-16 12:40 Paul Durrant [this message]
2015-10-16 12:40 ` [PATCH v2 1/4] public/io/netif.h: document the reality of netif_rx_request/reponse id Paul Durrant
2015-10-16 12:40 ` [PATCH v2 2/4] public/io/netif.h: add definition of gso_prefix flag Paul Durrant
2015-10-16 15:14   ` Paul Durrant
2015-10-16 12:40 ` [PATCH v2 3/4] public/io/netif.h: add documentation for hash negotiation and mapping Paul Durrant
2015-10-16 12:40 ` [PATCH v2 4/4] public/io/netif.h: add extra info slots for passing hash values Paul Durrant

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=1444999239-24681-1-git-send-email-paul.durrant@citrix.com \
    --to=paul.durrant@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 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).