mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: Paul Durrant <Paul.Durrant@citrix.com>
Cc: Zoltan Kiss <zoltan.kiss@citrix.com>,
	Wei Liu <wei.liu2@citrix.com>,
	"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Jonathan Davies" <Jonathan.Davies@citrix.com>
Subject: Re: [PATCH net-next v3 2/2] xen-netback: Grant copy the header instead of map and memcpy
Date: Thu, 3 Apr 2014 10:11:14 +0100	[thread overview]
Message-ID: <1396516274.4211.39.camel@kazak.uk.xensource.com> (raw)
In-Reply-To: <9AAE0902D5BC7E449B7C8E4E778ABCD02BB0E1@AMSPEX01CL01.citrite.net>

On Thu, 2014-04-03 at 09:07 +0100, Paul Durrant wrote:
> > -----Original Message-----
> > From: Zoltan Kiss
> > Sent: 02 April 2014 18:05
> > To: Ian Campbell; Wei Liu; xen-devel@lists.xenproject.org
> > Cc: Paul Durrant; netdev@vger.kernel.org; linux-kernel@vger.kernel.org;
> > Jonathan Davies; Zoltan Kiss
> > Subject: [PATCH net-next v3 2/2] xen-netback: Grant copy the header
> > instead of map and memcpy
> > 
> > An old inefficiency of the TX path that we are grant mapping the first slot,
> > and then copy the header part to the linear area. Instead, doing a grant copy
> > for that header straight on is more reasonable. Especially because there are
> > ongoing efforts to make Xen avoiding TLB flush after unmap when the page
> > were
> > not touched in Dom0. In the original way the memcpy ruined that.
> > The key changes:
> > - the vif has a tx_copy_ops array again
> > - xenvif_tx_build_gops sets up the grant copy operations
> > - we don't have to figure out whether the header and first frag are on the
> > same
> >   grant mapped page or not
> > Note, we only grant copy PKT_PROT_LEN bytes from the first slot, the rest (if
> > any) will be on the first frag, which is grant mapped. If the first slot is
> > smaller than PKT_PROT_LEN, then we grant copy that, and later
> > __pskb_pull_tail
> > will pull more from the frags (if any)
> > 
> > Signed-off-by: Zoltan Kiss <zoltan.kiss@citrix.com>
> 
> Looks good to me.
> 
> Reviewed-by: Paul Durrant <paul.durrant@citrix.com>

Me too:

Acked-by: Ian Campbell <ian.campbell@citrix.com>




  reply	other threads:[~2014-04-03  9:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-02 17:04 [PATCH net-next v3 1/2] xen-netback: Rename map ops Zoltan Kiss
2014-04-02 17:04 ` [PATCH net-next v3 2/2] xen-netback: Grant copy the header instead of map and memcpy Zoltan Kiss
2014-04-03  8:07   ` Paul Durrant
2014-04-03  9:11     ` Ian Campbell [this message]
2014-04-03 18:23   ` David Miller
2014-04-03  8:08 ` [PATCH net-next v3 1/2] xen-netback: Rename map ops Paul Durrant
2014-04-03  9:06 ` Ian Campbell
2014-04-03 18:23 ` David Miller
2014-04-04 14:47   ` Zoltan Kiss
2014-04-04 14:51     ` David Miller

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=1396516274.4211.39.camel@kazak.uk.xensource.com \
    --to=ian.campbell@citrix.com \
    --cc=Jonathan.Davies@citrix.com \
    --cc=Paul.Durrant@citrix.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.org \
    --cc=zoltan.kiss@citrix.com \
    /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

all inboxes | Powered by JetHome®