All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: Paul Durrant <Paul.Durrant@citrix.com>
Cc: Wei Liu <wei.liu2@citrix.com>,
	Ian Campbell <Ian.Campbell@citrix.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH net-next] xen-netback: improve guest-receive-side flow control
Date: Mon, 2 Dec 2013 11:53:38 +0000	[thread overview]
Message-ID: <529C74C2.5040105@citrix.com> (raw)
In-Reply-To: <9AAE0902D5BC7E449B7C8E4E778ABCD0195079@AMSPEX01CL01.citrite.net>

On 28/11/13 16:33, Paul Durrant wrote:
>> -----Original Message-----
>> From: Wei Liu [mailto:wei.liu2@citrix.com]
>> Sent: 28 November 2013 16:27
>> To: Paul Durrant
>> Cc: Wei Liu; xen-devel@lists.xen.org; Ian Campbell; David Vrabel
>> Subject: Re: [PATCH net-next] xen-netback: improve guest-receive-side flow
>> control
> [snip]
> 
>>>> I'm afraid this starting point is not correct. Consider you have a SKB
>>>> with very large linear buffer, you might need more than 2 slots to fit
>>>> that in, right?
>>>>
>>>
>>> I was wondering about that. Would a roundup of mtu to the nearest 4k
>> boundary be sufficient?
>>>
>>
>> I think we can reuse the logic in xenvif_gop_skb, there's a snippet used
>> to calculate how many slots are necessary for linear area. We just need
>> to avoid pulling requrests from the ring.
>>
> 
> Actually, DIV_ROUND(skb_headlen(skb), PAGE_SIZE) should give a cheap
> upper bound, shouldn't it? I don't want the code here to get too
> complex.

Make sure it does the right thing if the head is not page aligned etc.

David

  parent reply	other threads:[~2013-12-02 11:53 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-28 13:11 [PATCH net-next] xen-netback: improve guest-receive-side flow control Paul Durrant
2013-11-28 15:51 ` Wei Liu
2013-11-28 16:05   ` Paul Durrant
2013-11-28 16:27     ` Wei Liu
2013-11-28 16:33       ` Paul Durrant
2013-11-28 16:44         ` Wei Liu
2013-12-02 11:53         ` David Vrabel [this message]
2013-11-29  8:20       ` annie li
2013-11-29 10:03         ` Paul Durrant
2013-12-01  4:18           ` annie li
2013-12-02 10:52             ` Paul Durrant
2013-12-02 11:52 ` David Vrabel
2013-12-02 11:55   ` Paul Durrant
2013-12-02 11:59     ` David Vrabel
2013-12-02 12:01       ` Paul Durrant
2013-12-03 20:22     ` Konrad Rzeszutek Wilk

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=529C74C2.5040105@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Paul.Durrant@citrix.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xen.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.