This is a note to let you know that I have just added a patch titled
xen-netfront: Fix handling packets on compound pages with skb_linearize
to the linux-3.13.y-queue branch of the 3.13.y-ckt extended stable tree
which can be found at:
http://kernel.ubuntu.com/git?p=ubuntu/linux.git;a=sho
This is a note to let you know that I have just added a patch titled
xen-netfront: Fix handling packets on compound pages with skb_linearize
to the linux-3.16.y-queue branch of the 3.16.y-ckt extended stable tree
which can be found at:
http://kernel.ubuntu.com/git?p=ubuntu/linux.git;a=sho
On Wed, Dec 10, 2014 at 05:26:28PM +, Luis Henriques wrote:
> This is a note to let you know that I have just added a patch titled
>
> xen-netfront: Fix handling packets on compound pages with skb_linearize
>
> to the linux-3.16.y-queue branch of the 3.16.y-ckt extended stable tree
> whi
This is a note to let you know that I have just added a patch titled
xen-netfront: Fix handling packets on compound pages with skb_linearize
to the linux-3.16.y-queue branch of the 3.16.y-ckt extended stable tree
which can be found at:
http://kernel.ubuntu.com/git?p=ubuntu/linux.git;a=sho
On Mon, Dec 08, 2014 at 11:11:15AM +, David Vrabel wrote:
> On 08/12/14 10:19, Luis Henriques wrote:
> > On Mon, Dec 01, 2014 at 09:55:24AM +0100, Stefan Bader wrote:
> >> On 11.08.2014 19:32, Zoltan Kiss wrote:
> >>> There is a long known problem with the netfront/netback interface: if the
>
On 08/12/14 10:19, Luis Henriques wrote:
> On Mon, Dec 01, 2014 at 09:55:24AM +0100, Stefan Bader wrote:
>> On 11.08.2014 19:32, Zoltan Kiss wrote:
>>> There is a long known problem with the netfront/netback interface: if the
>>> guest
>>> tries to send a packet which constitues more than MAX_SKB_
On Mon, Dec 01, 2014 at 09:55:24AM +0100, Stefan Bader wrote:
> On 11.08.2014 19:32, Zoltan Kiss wrote:
> > There is a long known problem with the netfront/netback interface: if the
> > guest
> > tries to send a packet which constitues more than MAX_SKB_FRAGS + 1 ring
> > slots,
> > it gets dropp
On 01.12.2014 14:59, Zoltan Kiss wrote:
>
>
> On 01/12/14 13:36, David Vrabel wrote:
>> On 01/12/14 08:55, Stefan Bader wrote:
>>> On 11.08.2014 19:32, Zoltan Kiss wrote:
There is a long known problem with the netfront/netback interface: if the
guest
tries to send a packet which c
On 01/12/14 13:36, David Vrabel wrote:
On 01/12/14 08:55, Stefan Bader wrote:
On 11.08.2014 19:32, Zoltan Kiss wrote:
There is a long known problem with the netfront/netback interface: if the guest
tries to send a packet which constitues more than MAX_SKB_FRAGS + 1 ring slots,
it gets dropped
On 01/12/14 08:55, Stefan Bader wrote:
> On 11.08.2014 19:32, Zoltan Kiss wrote:
>> There is a long known problem with the netfront/netback interface: if the
>> guest
>> tries to send a packet which constitues more than MAX_SKB_FRAGS + 1 ring
>> slots,
>> it gets dropped. The reason is that netba
On 11.08.2014 19:32, Zoltan Kiss wrote:
> There is a long known problem with the netfront/netback interface: if the
> guest
> tries to send a packet which constitues more than MAX_SKB_FRAGS + 1 ring
> slots,
> it gets dropped. The reason is that netback maps these slots to a frag in the
> frags a
From: Zoltan Kiss
Date: Mon, 11 Aug 2014 18:32:23 +0100
> There is a long known problem with the netfront/netback interface: if the
> guest
> tries to send a packet which constitues more than MAX_SKB_FRAGS + 1 ring
> slots,
> it gets dropped. The reason is that netback maps these slots to a fra
There is a long known problem with the netfront/netback interface: if the guest
tries to send a packet which constitues more than MAX_SKB_FRAGS + 1 ring slots,
it gets dropped. The reason is that netback maps these slots to a frag in the
frags array, which is limited by size. Having so many slots c
13 matches
Mail list logo
