From: David Vrabel <david.vrabel@citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Zoltan Kiss <zoltan.kiss@citrix.com>,
<jonathan.davies@citrix.com>, <wei.liu2@citrix.com>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<paul.durrant@citrix.com>, <xen-devel@lists.xenproject.org>
Subject: Re: [Xen-devel] [PATCH net-next v2 2/2] xen-netback: Grant copy the header instead of map and memcpy
Date: Wed, 2 Apr 2014 14:11:59 +0100 [thread overview]
Message-ID: <533C0C9F.8030205@citrix.com> (raw)
In-Reply-To: <1396352440.8667.117.camel@kazak.uk.xensource.com>
On 01/04/14 12:40, Ian Campbell wrote:
> On Mon, 2014-03-31 at 16:08 +0100, Zoltan Kiss wrote:
>>
>> __skb_put(skb, data_len);
>> + vif->tx_copy_ops[*copy_ops].source.u.ref = txreq.gref;
>> + vif->tx_copy_ops[*copy_ops].source.domid = vif->domid;
>> + vif->tx_copy_ops[*copy_ops].source.offset = txreq.offset;
>> +
>> + vif->tx_copy_ops[*copy_ops].dest.u.gmfn =
>> + virt_to_mfn(skb->data);
>> + vif->tx_copy_ops[*copy_ops].dest.domid = DOMID_SELF;
>> + vif->tx_copy_ops[*copy_ops].dest.offset =
>> + offset_in_page(skb->data);
>> +
>> + vif->tx_copy_ops[*copy_ops].len = data_len;
>> + vif->tx_copy_ops[*copy_ops].flags = GNTCOPY_source_gref;
>
> We have gnttab_set_map_op. Should we have gnttap_set_copy_op too?
A set of 3 might be useful I think.
gnttab_set_copy_op_ref_to_gfn()
gnttab_set_copy_op_gfn_to_ref()
gnttab_set_copy_op_ref_to_ref()
>
>> - BUG_ON(ret);
>> + else {
>> + gnttab_batch_copy(vif->tx_copy_ops, nr_cops);
>> + if (nr_mops != 0) {
>
>
> if (nr_mops) would do.
>
>> + ret = gnttab_map_refs(vif->tx_map_ops,
>
> So we use gnttab_batch_copy and gnttab_map_refs.
>
> Shouldn't we either use gnttab_batch_copy and gnttab_batch_map or
> gnttab_copy gnttab_map_refs. (where gnttab_copy might be a bare
> GNTTABOP_copy or might be a helper wrapper).
gnttab_batch_map() is not correct here since it does not update the p2m.
There is only one copy API (gnttab_batch_copy()).
> The point of the batch interface is to handle page unsharing etc, but
> doing it only for copies seems like a waste one way or another.
Both mapping and copy need to handle (hypervisor) paging/shaing and the
two calls Zoli has used do this.
gnttab_map_refs() is basically gnttab_batch_map() +
set_foreign_p2m_mapping().
I'd be in favour of a patch that:
- renamed gnttab_map_refs() to gnttab_batch_map_pages()
- refactored it to call gnttab_batch_map().
- added documentation
But I don't see why this would be a prerequisite for this series.
David
WARNING: multiple messages have this Message-ID (diff)
From: David Vrabel <david.vrabel@citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: jonathan.davies@citrix.com, wei.liu2@citrix.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
paul.durrant@citrix.com, Zoltan Kiss <zoltan.kiss@citrix.com>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH net-next v2 2/2] xen-netback: Grant copy the header instead of map and memcpy
Date: Wed, 2 Apr 2014 14:11:59 +0100 [thread overview]
Message-ID: <533C0C9F.8030205@citrix.com> (raw)
In-Reply-To: <1396352440.8667.117.camel@kazak.uk.xensource.com>
On 01/04/14 12:40, Ian Campbell wrote:
> On Mon, 2014-03-31 at 16:08 +0100, Zoltan Kiss wrote:
>>
>> __skb_put(skb, data_len);
>> + vif->tx_copy_ops[*copy_ops].source.u.ref = txreq.gref;
>> + vif->tx_copy_ops[*copy_ops].source.domid = vif->domid;
>> + vif->tx_copy_ops[*copy_ops].source.offset = txreq.offset;
>> +
>> + vif->tx_copy_ops[*copy_ops].dest.u.gmfn =
>> + virt_to_mfn(skb->data);
>> + vif->tx_copy_ops[*copy_ops].dest.domid = DOMID_SELF;
>> + vif->tx_copy_ops[*copy_ops].dest.offset =
>> + offset_in_page(skb->data);
>> +
>> + vif->tx_copy_ops[*copy_ops].len = data_len;
>> + vif->tx_copy_ops[*copy_ops].flags = GNTCOPY_source_gref;
>
> We have gnttab_set_map_op. Should we have gnttap_set_copy_op too?
A set of 3 might be useful I think.
gnttab_set_copy_op_ref_to_gfn()
gnttab_set_copy_op_gfn_to_ref()
gnttab_set_copy_op_ref_to_ref()
>
>> - BUG_ON(ret);
>> + else {
>> + gnttab_batch_copy(vif->tx_copy_ops, nr_cops);
>> + if (nr_mops != 0) {
>
>
> if (nr_mops) would do.
>
>> + ret = gnttab_map_refs(vif->tx_map_ops,
>
> So we use gnttab_batch_copy and gnttab_map_refs.
>
> Shouldn't we either use gnttab_batch_copy and gnttab_batch_map or
> gnttab_copy gnttab_map_refs. (where gnttab_copy might be a bare
> GNTTABOP_copy or might be a helper wrapper).
gnttab_batch_map() is not correct here since it does not update the p2m.
There is only one copy API (gnttab_batch_copy()).
> The point of the batch interface is to handle page unsharing etc, but
> doing it only for copies seems like a waste one way or another.
Both mapping and copy need to handle (hypervisor) paging/shaing and the
two calls Zoli has used do this.
gnttab_map_refs() is basically gnttab_batch_map() +
set_foreign_p2m_mapping().
I'd be in favour of a patch that:
- renamed gnttab_map_refs() to gnttab_batch_map_pages()
- refactored it to call gnttab_batch_map().
- added documentation
But I don't see why this would be a prerequisite for this series.
David
next prev parent reply other threads:[~2014-04-02 13:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-31 15:08 [PATCH net-next v2 1/2] xen-netback: Rename map ops Zoltan Kiss
2014-03-31 15:08 ` [PATCH net-next v2 2/2] xen-netback: Grant copy the header instead of map and memcpy Zoltan Kiss
2014-03-31 15:08 ` Zoltan Kiss
2014-04-01 9:40 ` Paul Durrant
2014-04-01 9:40 ` Paul Durrant
2014-04-01 18:55 ` Zoltan Kiss
2014-04-02 7:29 ` Ian Campbell
2014-04-02 7:29 ` Ian Campbell
2014-04-01 18:55 ` Zoltan Kiss
2014-04-01 11:40 ` Ian Campbell
2014-04-01 11:40 ` Ian Campbell
2014-04-01 19:09 ` Zoltan Kiss
2014-04-01 19:09 ` Zoltan Kiss
2014-04-02 7:32 ` Ian Campbell
2014-04-02 7:32 ` Ian Campbell
2014-04-02 13:11 ` David Vrabel [this message]
2014-04-02 13:11 ` David Vrabel
2014-04-02 13:15 ` [Xen-devel] " Ian Campbell
2014-04-02 13:15 ` Ian Campbell
2014-04-02 14:41 ` [Xen-devel] " Zoltan Kiss
2014-04-02 14:41 ` Zoltan Kiss
2014-04-01 11:18 ` [PATCH net-next v2 1/2] xen-netback: Rename map ops Ian Campbell
2014-04-01 11:18 ` Ian Campbell
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=533C0C9F.8030205@citrix.com \
--to=david.vrabel@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=jonathan.davies@citrix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paul.durrant@citrix.com \
--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 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.