From: Ian Campbell <ian.campbell@citrix.com>
To: Jan Beulich <JBeulich@suse.com>, Paul Durrant <paul.durrant@citrix.com>
Cc: xen-devel@lists.xenproject.org, Keir Fraser <keir@xen.org>,
Ian Jackson <ian.jackson@eu.citrix.com>, Tim Deegan <tim@xen.org>
Subject: Re: [PATCH v7 2/2] public/io/netif.h: document control ring and toeplitz hashing
Date: Mon, 18 Jan 2016 16:57:09 +0000 [thread overview]
Message-ID: <1453136229.6020.199.camel@citrix.com> (raw)
In-Reply-To: <569D227102000078000C8234@prv-mh.provo.novell.com>
On Mon, 2016-01-18 at 09:35 -0700, Jan Beulich wrote:
> > > > On 18.01.16 at 17:07, <ian.campbell@citrix.com> wrote:
> > On Tue, 2016-01-12 at 09:58 +0000, Paul Durrant wrote:
> > > + * NETIF_CTRL_TYPE_SET_TOEPLITZ_MAPPING
> > > + * ------------------------------------
> > > + *
> > > + * This is sent by the frontend to set the content of the table
> > > mapping
> > > + * toeplitz hash value to queue number. The backend should calculate
> > > the
> > > + * hash from the packet header, use it as an index into the table
> > > (modulo
> > > + * the size of the table) and then steer the packet to the queue
> > > number
> > > + * found at that index.
> > > + *
> > > + * Request:
> > > + *
> > > + * type = NETIF_CTRL_TYPE_SET_TOEPLITZ_MAPPING
> > > + * data[0] = grant reference of page containing the mapping (sub-
> > > )table
> > > + * (assumed to start at beginning of grant)
> > > + * data[1] = size of (sub-)table in entries
> > > + * data[2] = offset, in entries, of sub-table within overall table
> >
> > Adding data[2] seems reasonable to me, but if you wanted to avoid
> > adding it
> > then saying data[1][8:0] == size and data[1][31:9] == offset would
> > allow a
> > size of 512 (biggest possible in a single gref) and 8.3M for the
> > offset.
>
> I may be lacking some context here, so please ignore if it reads
> like nonsense, but is the 9-bit width bound to a page size of 4k,
> or an inherent property of the Toeplitz algorithm?
The table entries are 8 bytes, so in that respect yes I suppose it is
related to the page size.
Paul thought it best not to do this any.
> In the former
> case I think we should try to avoid putting further limitations to
> 4k pages into any interface. (And as an aside, 512 is also not
> representable in 9 bits, but this can clearly be addressed quite
> easily.)
Indeed, looks like I miscounted.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-01-18 16:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-12 9:58 [PATCH v7 0/2] public/io/netif.h: support for toeplitz hashing Paul Durrant
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 [this message]
[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=1453136229.6020.199.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=ian.jackson@eu.citrix.com \
--cc=keir@xen.org \
--cc=paul.durrant@citrix.com \
--cc=tim@xen.org \
--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.