All of lore.kernel.org
 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 v7 0/2] public/io/netif.h: support for toeplitz hashing
Date: Tue, 12 Jan 2016 09:58:54 +0000	[thread overview]
Message-ID: <1452592736-6463-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 adds further clarifications to the receive and transmit wire
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 and a new extra info segment that can be used for passing
hash values along with packets on both the transmit and receive side.

             reply	other threads:[~2016-01-12 10:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-12  9:58 Paul Durrant [this message]
2016-01-12  9:58 ` [PATCH v7 1/2] public/io/netif.h: clarifications to wire formats Paul Durrant
2016-01-18 14:55   ` Ian Campbell
2016-01-12  9:58 ` [PATCH v7 2/2] public/io/netif.h: document control ring and toeplitz hashing Paul Durrant
2016-01-18 16:07   ` Ian Campbell
2016-01-18 16:35     ` Jan Beulich
2016-01-18 16:57       ` Ian Campbell
     [not found]     ` <56dc5108a3054e5884b217357b73a3bc@AMSPEX02CL03.citrite.net>
2016-01-19 11:34       ` Ian Campbell
2016-01-18 10:15 ` [PATCH v7 0/2] public/io/netif.h: support for " Paul Durrant
2016-02-02  5:02 ` Bob Liu
2016-02-02  9:33   ` Paul Durrant
2016-02-02 11:05     ` Bob Liu

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=1452592736-6463-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 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.