From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bob Liu Subject: Re: [PATCH v7 0/2] public/io/netif.h: support for toeplitz hashing Date: Tue, 02 Feb 2016 13:02:27 +0800 Message-ID: <56B03863.40000@oracle.com> References: <1452592736-6463-1-git-send-email-paul.durrant@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aQT6w-0001sJ-1L for xen-devel@lists.xenproject.org; Tue, 02 Feb 2016 05:02:42 +0000 In-Reply-To: <1452592736-6463-1-git-send-email-paul.durrant@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Paul Durrant Cc: xen-devel@lists.xenproject.org List-Id: xen-devel@lists.xenproject.org Hi Paul, On 01/12/2016 05:58 PM, Paul Durrant wrote: > 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. > I have a question, why not make the "netif_ctrl_request" a part of the extra info segment? So that can reuse the origin transmit shared ring. -- Regards, -Bob