All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: David Miller <davem@davemloft.net>
Cc: <david.vrabel@citrix.com>, <netdev@vger.kernel.org>,
	<xen-devel@lists.xenproject.org>, <wei.liu2@citrix.com>,
	<malcolm.crossley@citrix.com>
Subject: Re: [PATCHv1 net-next] xen-netback: remove unconditional pull_skb_tail in guest Tx path
Date: Wed, 5 Nov 2014 09:53:05 +0000	[thread overview]
Message-ID: <1415181185.11486.65.camel@citrix.com> (raw)
In-Reply-To: <20141104.164113.2265592775058059992.davem@davemloft.net>

On Tue, 2014-11-04 at 16:41 -0500, David Miller wrote:
> From: David Vrabel <david.vrabel@citrix.com>
> Date: Mon, 3 Nov 2014 17:23:51 +0000
> 
> > From: Malcolm Crossley <malcolm.crossley@citrix.com>
> > 
> > Unconditionally pulling 128 bytes into the linear buffer is not
> > required. Netback has already grant copied up-to 128 bytes from the
> > first slot of a packet into the linear buffer. The first slot normally
> > contain all the IPv4/IPv6 and TCP/UDP headers.
> > 
> > The unconditional pull would often copy frag data unnecessarily.  This
> > is a performance problem when running on a version of Xen where grant
> > unmap avoids TLB flushes for pages which are not accessed.  TLB
> > flushes can now be avoided for > 99% of unmaps (it was 0% before).
> > 
> > Grant unmap TLB flush avoidance will be available in a future version
> > of Xen (probably 4.6).
> > 
> > Signed-off-by: Malcolm Crossley <malcolm.crossley@citrix.com>
> > Signed-off-by: David Vrabel <david.vrabel@citrix.com>
> 
> Now that this has been discussed a bit, it is possible to get an ack or two?

I'd like to see the commit message expanded to explain why this isn't
introducing a (security) bug by not pulling enough stuff into the header
(IOW the conclusion of the discussion).

Ian.

  reply	other threads:[~2014-11-05  9:53 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-03 17:23 [PATCHv1 net-next] xen-netback: remove unconditional pull_skb_tail in guest Tx path David Vrabel
2014-11-03 17:39 ` Ian Campbell
2014-11-03 17:46   ` David Vrabel
2014-11-03 17:55     ` Ian Campbell
2014-11-03 17:55     ` Ian Campbell
2014-11-03 18:23     ` Zoltan Kiss
2014-11-03 18:23     ` [Xen-devel] " Zoltan Kiss
2014-11-04 21:17       ` David Miller
2014-11-04 21:17       ` [Xen-devel] " David Miller
2014-11-04 21:43         ` Eric Dumazet
2014-11-04 21:43         ` [Xen-devel] " Eric Dumazet
2014-11-05 10:46           ` David Vrabel
2014-11-05 10:53             ` Ian Campbell
2014-11-05 10:53             ` [Xen-devel] " Ian Campbell
2014-11-05 10:46           ` David Vrabel
2014-11-05  9:51         ` [Xen-devel] " Ian Campbell
2014-11-05 17:15           ` David Miller
2014-11-05 17:15           ` David Miller
2014-11-05  9:51         ` Ian Campbell
2014-11-03 17:46   ` David Vrabel
2014-11-03 17:39 ` Ian Campbell
2014-11-04 21:41 ` David Miller
2014-11-05  9:53   ` Ian Campbell [this message]
2014-11-05 17:16     ` David Miller
2014-11-05 17:16     ` David Miller
2014-11-05  9:53   ` Ian Campbell
2014-11-04 21:41 ` David Miller
  -- strict thread matches above, loose matches on Subject: below --
2014-11-03 17:23 David Vrabel

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=1415181185.11486.65.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=davem@davemloft.net \
    --cc=david.vrabel@citrix.com \
    --cc=malcolm.crossley@citrix.com \
    --cc=netdev@vger.kernel.org \
    --cc=wei.liu2@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.