From: David Miller <davem@davemloft.net>
To: konrad@kernel.org
Cc: ian.campbell@citrix.com, netdev@vger.kernel.org,
xen-devel@lists.xen.org, edumazet@google.com,
annie.li@oracle.com, linux@eikelenboom.it,
stefan.bader@canonical.com
Subject: Re: [PATCH V3] xen/netfront: handle compound page fragments on transmit
Date: Wed, 21 Nov 2012 11:49:57 -0500 (EST) [thread overview]
Message-ID: <20121121.114957.441218567286373485.davem@davemloft.net> (raw)
In-Reply-To: <20121121151625.GA13127@konrad-lan.dumpdata.com>
From: Konrad Rzeszutek Wilk <konrad@kernel.org>
Date: Wed, 21 Nov 2012 10:16:27 -0500
> On Wed, Nov 21, 2012 at 12:02:16PM +0000, Ian Campbell wrote:
>> An SKB paged fragment can consist of a compound page with order > 0.
>> However the netchannel protocol deals only in PAGE_SIZE frames.
>>
>> Handle this in xennet_make_frags by iterating over the frames which
>> make up the page.
>>
>> This is the netfront equivalent to 6a8ed462f16b for netback.
>>
>> Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
>> Cc: netdev@vger.kernel.org
>> Cc: xen-devel@lists.xen.org
>> Cc: Eric Dumazet <edumazet@google.com>
>> Cc: Konrad Rzeszutek Wilk <konrad@kernel.org>
>
> Acked-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
>
> David, would you like me to send it to Linus via my tree or are you
> OK sending him a git pull with this patch (and hopefully some other
> ones?)
I'll merge this to Linus via my net tree, thanks.
next prev parent reply other threads:[~2012-11-21 16:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-21 12:02 [PATCH V3] xen/netfront: handle compound page fragments on transmit Ian Campbell
2012-11-21 13:45 ` [Xen-devel] " Stefan Bader
2012-11-21 15:13 ` Eric Dumazet
2012-11-21 15:16 ` Konrad Rzeszutek Wilk
2012-11-21 16:49 ` David Miller [this message]
2012-11-22 14:15 ` 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=20121121.114957.441218567286373485.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=annie.li@oracle.com \
--cc=edumazet@google.com \
--cc=ian.campbell@citrix.com \
--cc=konrad@kernel.org \
--cc=linux@eikelenboom.it \
--cc=netdev@vger.kernel.org \
--cc=stefan.bader@canonical.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).