From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: kys@microsoft.com, haiyangz@microsoft.com,
netdev@vger.kernel.org, devel@linuxdriverproject.org,
linux-kernel@vger.kernel.org, jasowang@redhat.com
Subject: Re: [PATCH 0/2] hv_netvsc: linearize SKBs bigger than MAX_PAGE_BUFFER_COUNT-2 pages
Date: Wed, 08 Apr 2015 18:47:18 +0200 [thread overview]
Message-ID: <874moq4lex.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <20150408.122810.2304841162873681785.davem@davemloft.net> (David Miller's message of "Wed, 08 Apr 2015 12:28:10 -0400 (EDT)")
David Miller <davem@davemloft.net> writes:
> From: Vitaly Kuznetsov <vkuznets@redhat.com>
> Date: Wed, 8 Apr 2015 17:54:04 +0200
>
>> This patch series fixes the same issue which was fixed in Xen with commit
>> 97a6d1bb2b658ac85ed88205ccd1ab809899884d ("xen-netfront: Fix handling packets on
>> compound pages with skb_linearize").
>
> This patch series only applies on net-next, so that's where I put it.
Yes, it is for net-next, thanks.
>
> Please be completely explicit about this in the future, rather than
> forcing me to try and figure it out.
Sorry, I will, for some reason I thought it was the default.
>
> Thanks.
--
Vitaly
prev parent reply other threads:[~2015-04-08 16:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-08 15:54 [PATCH 0/2] hv_netvsc: linearize SKBs bigger than MAX_PAGE_BUFFER_COUNT-2 pages Vitaly Kuznetsov
2015-04-08 15:54 ` [PATCH 1/2] hv_netvsc: use single existing drop path in netvsc_start_xmit Vitaly Kuznetsov
2015-04-08 15:54 ` Vitaly Kuznetsov
2015-04-08 15:54 ` [PATCH 2/2] hv_netvsc: try linearizing big SKBs before dropping them Vitaly Kuznetsov
2015-04-08 15:54 ` Vitaly Kuznetsov
2015-04-08 16:28 ` [PATCH 0/2] hv_netvsc: linearize SKBs bigger than MAX_PAGE_BUFFER_COUNT-2 pages David Miller
2015-04-08 16:47 ` Vitaly Kuznetsov [this message]
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=874moq4lex.fsf@vitty.brq.redhat.com \
--to=vkuznets@redhat.com \
--cc=davem@davemloft.net \
--cc=devel@linuxdriverproject.org \
--cc=haiyangz@microsoft.com \
--cc=jasowang@redhat.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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.