All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Zoltan Kiss <zoltan.kiss@citrix.com>,
	<xen-devel@lists.xenproject.org>, <jonathan.davies@citrix.com>,
	<wei.liu2@citrix.com>, <linux-kernel@vger.kernel.org>,
	<netdev@vger.kernel.org>
Subject: Re: [Xen-devel] [PATCH net-next v7 4/9] xen-netback: Introduce TX grant mapping
Date: Thu, 13 Mar 2014 10:56:26 +0000	[thread overview]
Message-ID: <53218EDA.8040904@citrix.com> (raw)
In-Reply-To: <1394706812.25873.28.camel@kazak.uk.xensource.com>

On 13/03/14 10:33, Ian Campbell wrote:
> On Thu, 2014-03-06 at 21:48 +0000, Zoltan Kiss wrote:
>> @@ -135,13 +146,31 @@ struct xenvif {
>>  	pending_ring_idx_t pending_cons;
>>  	u16 pending_ring[MAX_PENDING_REQS];
>>  	struct pending_tx_info pending_tx_info[MAX_PENDING_REQS];
>> +	grant_handle_t grant_tx_handle[MAX_PENDING_REQS];
>>  
>>  	/* Coalescing tx requests before copying makes number of grant
>>  	 * copy ops greater or equal to number of slots required. In
>>  	 * worst case a tx request consumes 2 gnttab_copy.
>>  	 */
>>  	struct gnttab_copy tx_copy_ops[2*MAX_PENDING_REQS];
>> -
>> +	struct gnttab_map_grant_ref tx_map_ops[MAX_PENDING_REQS];
>> +	struct gnttab_unmap_grant_ref tx_unmap_ops[MAX_PENDING_REQS];
> 
> I wonder if we should break some of these arrays into separate
> allocations? Wasn't there a problem with sizeof(struct xenvif) at one
> point?

alloc_netdev() falls back to vmalloc() if the kmalloc failed so there's
no need to split these structures.

David

  parent reply	other threads:[~2014-03-13 10:56 UTC|newest]

Thread overview: 76+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-06 21:48 [PATCH net-next v7 0/9] xen-netback: TX grant mapping with SKBTX_DEV_ZEROCOPY instead of copy Zoltan Kiss
2014-03-06 21:48 ` [PATCH net-next v7 1/9] xen-netback: Use skb->cb for pending_idx Zoltan Kiss
2014-03-06 21:48   ` Zoltan Kiss
2014-03-06 21:48   ` Zoltan Kiss
2014-03-06 21:48 ` [PATCH net-next v7 2/9] xen-netback: Minor refactoring of netback code Zoltan Kiss
2014-03-06 21:48 ` Zoltan Kiss
2014-03-06 21:48 ` [PATCH net-next v7 3/9] xen-netback: Handle foreign mapped pages on the guest RX path Zoltan Kiss
2014-03-06 21:48   ` Zoltan Kiss
2014-03-06 21:48   ` Zoltan Kiss
2014-03-06 21:48 ` [PATCH net-next v7 4/9] xen-netback: Introduce TX grant mapping Zoltan Kiss
2014-03-13 10:17   ` Ian Campbell
2014-03-13 10:17   ` Ian Campbell
2014-03-13 12:34     ` Zoltan Kiss
2014-03-13 12:34     ` Zoltan Kiss
2014-03-13 10:33   ` Ian Campbell
2014-03-13 10:56     ` David Vrabel
2014-03-13 10:56     ` David Vrabel [this message]
2014-03-13 11:02       ` [Xen-devel] " Ian Campbell
2014-03-13 11:09         ` David Vrabel
2014-03-13 11:09         ` [Xen-devel] " David Vrabel
2014-03-13 11:13         ` Wei Liu
2014-03-13 11:13         ` [Xen-devel] " Wei Liu
2014-03-13 11:02       ` Ian Campbell
2014-03-13 13:17     ` Zoltan Kiss
2014-03-13 13:56       ` Ian Campbell
2014-03-13 17:43         ` Zoltan Kiss
2014-03-13 17:43         ` Zoltan Kiss
2014-03-13 13:56       ` Ian Campbell
2014-03-13 13:17     ` Zoltan Kiss
2014-03-13 10:33   ` Ian Campbell
2014-03-06 21:48 ` Zoltan Kiss
2014-03-06 21:48 ` [PATCH net-next v7 5/9] xen-netback: Remove old TX grant copy definitons and fix indentations Zoltan Kiss
2014-03-06 21:48   ` Zoltan Kiss
2014-03-06 21:48   ` Zoltan Kiss
2014-03-06 21:48 ` [PATCH net-next v7 6/9] xen-netback: Add stat counters for zerocopy Zoltan Kiss
2014-03-06 21:48   ` Zoltan Kiss
2014-03-06 21:48   ` Zoltan Kiss
2014-03-06 21:48 ` [PATCH net-next v7 7/9] xen-netback: Handle guests with too many frags Zoltan Kiss
2014-03-06 21:48 ` Zoltan Kiss
2014-03-06 21:48 ` [PATCH net-next v7 8/9] xen-netback: Timeout packets in RX path Zoltan Kiss
2014-03-06 21:48   ` Zoltan Kiss
2014-03-06 21:48   ` Zoltan Kiss
2014-03-13 10:39   ` Ian Campbell
2014-03-13 10:39   ` Ian Campbell
2014-03-06 21:48 ` [PATCH net-next v7 9/9] xen-netback: Aggregate TX unmap operations Zoltan Kiss
2014-03-06 21:48 ` Zoltan Kiss
2014-03-19 21:16   ` Zoltan Kiss
2014-03-19 21:16   ` Zoltan Kiss
2014-03-20  9:53     ` Paul Durrant
2014-03-20  9:53     ` Paul Durrant
2014-03-20 10:48     ` Wei Liu
2014-03-20 11:14       ` Paul Durrant
2014-03-20 11:14       ` Paul Durrant
2014-03-20 12:38         ` Wei Liu
2014-03-20 16:11           ` Zoltan Kiss
2014-03-20 16:11           ` Zoltan Kiss
2014-03-20 12:38         ` Wei Liu
2014-03-20 10:48     ` Wei Liu
2014-03-07 21:05 ` [PATCH net-next v7 0/9] xen-netback: TX grant mapping with SKBTX_DEV_ZEROCOPY instead of copy David Miller
2014-03-07 21:05 ` David Miller
2014-03-08 14:37   ` Zoltan Kiss
2014-03-08 23:57     ` David Miller
2014-03-10 10:15       ` Wei Liu
2014-03-10 10:15       ` Wei Liu
2014-03-12 15:40       ` Ian Campbell
2014-03-12 15:40       ` Ian Campbell
2014-03-12 18:49         ` Zoltan Kiss
2014-03-12 18:49         ` Zoltan Kiss
2014-03-13 10:43         ` Ian Campbell
2014-03-13 10:43         ` Ian Campbell
2014-03-08 23:57     ` David Miller
2014-03-08 14:37   ` Zoltan Kiss
2014-03-13 10:08 ` Ian Campbell
2014-03-13 10:08 ` Ian Campbell
2014-03-13 18:23   ` Zoltan Kiss
2014-03-13 18:23   ` Zoltan Kiss

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=53218EDA.8040904@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=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.