From: Paul Durrant <paul.durrant@citrix.com>
To: xen-devel@lists.xenproject.org
Cc: Paul Durrant <paul.durrant@citrix.com>
Subject: [PATCH v4 0/3] public/io/netif.h: support for toeplitz hashing
Date: Thu, 7 Jan 2016 13:05:09 +0000 [thread overview]
Message-ID: <1452171912-29857-1-git-send-email-paul.durrant@citrix.com> (raw)
This series documents changes needed to support toeplitz hashing in a
backend, configurable by the frontend.
Patch #1 is a clean-up patch that clarifies the guest transmit and
receive side packet formats.
Patch #2 documents a new 'control ring' for passing bulk data between
frontend and backend. This is needed for passing the hash mapping table
and hash key. It also documents messages to allow a frontend to configure
toeplitz hashing.
Patch #3 documents a new extra info segment that can be used for passing
hash values along with packets on both the transmit and receive side.
next reply other threads:[~2016-01-07 13:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 13:05 Paul Durrant [this message]
2016-01-07 13:05 ` [PATCH v4 1/3] public/io/netif.h: document transmit and receive wire formats separately Paul Durrant
2016-01-08 15:24 ` Ian Campbell
2016-01-08 15:56 ` Paul Durrant
2016-01-08 16:10 ` Ian Campbell
2016-01-07 13:05 ` [PATCH v4 2/3] public/io/netif.h: document control ring and toeplitz hashing Paul Durrant
2016-01-08 15:53 ` Ian Campbell
2016-01-08 16:19 ` Paul Durrant
2016-01-08 16:46 ` Ian Campbell
2016-01-08 17:07 ` Paul Durrant
2016-01-08 17:22 ` Ian Campbell
2016-01-08 17:35 ` Paul Durrant
2016-01-08 16:07 ` David Vrabel
2016-01-08 16:21 ` Paul Durrant
2016-01-08 16:22 ` David Vrabel
2016-01-07 13:05 ` [PATCH v4 3/3] public/io/netif.h: document new extra info for passing hash values Paul Durrant
2016-01-08 16:05 ` Ian Campbell
2016-01-08 16:26 ` Paul Durrant
2016-01-08 16:48 ` 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=1452171912-29857-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).