All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: Paul Durrant <paul.durrant@citrix.com>, xen-devel@lists.xenproject.org
Cc: Wei Liu <wei.liuw2@citrix.com>,
	Ian Jackson <ian.jackson@eu.citrix.com>,
	David Vrabel <david.vrabel@citrix.com>,
	Jan Beulich <jbeulich@suse.com>
Subject: Re: [PATCH v4 RESEND] public/io/netif.h: make control ring hash protocol more general
Date: Thu, 3 Mar 2016 16:25:33 +0000	[thread overview]
Message-ID: <56D8657D.8050606@citrix.com> (raw)
In-Reply-To: <1456505540-21706-1-git-send-email-paul.durrant@citrix.com>

On 26/02/16 16:52, Paul Durrant wrote:
> This patch modified the control ring protocol (of which there is
> not yet an implementation) to make it more general. Most of the
> concepts are not limited to toeplitz hashing so it's best not to
> make them unnecessarily specific.
> 
> Apart from changing the names of various definitions and modifying
> comments, this patch:
> 
> - Adds a new control message type to select a hash algorithm.
> - Adds a reference implementation of the toeplitz hash.
> - Changes the 'toeplitz' extra info fragment into a 'hash' extra
>   info fragment and replaces the octet of padding with the index of
>   the algorithm that was used to create the hash value.
> - Relaxes the restriction that the mapping table has to be
>   power-of-2 sized.
> 
> The patch also fixes a few spelling typos noticed along the way.

Reviewed-by: David Vrabel <david.vrabel@citrix.com>

David

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  parent reply	other threads:[~2016-03-03 16:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-26 16:52 [PATCH v4 RESEND] public/io/netif.h: make control ring hash protocol more general Paul Durrant
2016-02-26 17:03 ` Paul Durrant
2016-03-01 11:21   ` Paul Durrant
2016-03-03 16:25 ` David Vrabel [this message]
2016-03-03 16:28   ` 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=56D8657D.8050606@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jbeulich@suse.com \
    --cc=paul.durrant@citrix.com \
    --cc=wei.liuw2@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.