xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: Wei Liu <wei.liu2@citrix.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	Paul Durrant <paul.durrant@citrix.com>,
	David Vrabel <david.vrabel@citrix.com>,
	"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
	Joao Martins <joao.m.martins@oracle.com>
Subject: Re: [RFC] netif: staging grants for requests
Date: Thu, 5 Jan 2017 11:54:45 +0000	[thread overview]
Message-ID: <20170105115445.GI13806@citrix.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1701041025000.17742@sstabellini-ThinkPad-X260>

On Wed, Jan 04, 2017 at 11:40:21AM -0800, Stefano Stabellini wrote:
> On Wed, 14 Dec 2016, Joao Martins wrote:
> > # Proposed Extension
> > 
> > ## Terminology
> > 
> > `data gref` refers to the reusable/staging grants, whereas `gref` are the
> > ones that are granted/revoked for each packet being sent. `command ring`
> > refers to the current ring, whereas `data list` refers to the one proposed
> > below.
> > 
> > ## Xenstore
> > 
> > "feature-staging-grants" is a capability to allow the use of a set of
> > recycled buffers permanently mapped at the device setup. If
> > advertised, the frontend will grant a region equivalent to ```maximum number
> > of slots per ring * size of buffer``` where:
> > 
> >  * `maximum number of slots per ring` is the number of request structure
> >    that can be fit within the command ring. By default a request
> >    structure consumes 16 bytes. The first 64 bytes of a ring are used by
> >    producer and consumer indicies.
> 
> This means that by default the number of slots is (4096-64)/16 = 252,
> correct?
> 

The number needs to be rounded down to power of 2 IIRC, so it would be
128.

Wei.

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

  reply	other threads:[~2017-01-05 11:54 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-14 18:11 [RFC] netif: staging grants for requests Joao Martins
2017-01-04 13:54 ` Wei Liu
2017-01-05 20:27   ` Joao Martins
2017-01-04 19:40 ` Stefano Stabellini
2017-01-05 11:54   ` Wei Liu [this message]
2017-01-05 20:27   ` Joao Martins
2017-01-06  0:30     ` Stefano Stabellini
2017-01-06 17:13       ` Joao Martins
2017-01-06 19:02         ` Stefano Stabellini
2017-01-06  9:33 ` Paul Durrant
2017-01-06 19:18   ` Stefano Stabellini
2017-01-06 20:19     ` Joao Martins
2017-01-09  9:03     ` Paul Durrant
2017-01-09 18:25       ` Stefano Stabellini
2017-01-06 20:08   ` Joao Martins
2017-01-09  8:56     ` Paul Durrant
2017-01-09 13:01       ` Joao Martins

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=20170105115445.GI13806@citrix.com \
    --to=wei.liu2@citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=david.vrabel@citrix.com \
    --cc=joao.m.martins@oracle.com \
    --cc=paul.durrant@citrix.com \
    --cc=sstabellini@kernel.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 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).