From: Zoltan Kiss <zoltan.kiss@citrix.com>
To: Stefan Bader <stefan.bader@canonical.com>,
Wei Liu <wei.liu2@citrix.com>,
Eric Dumazet <eric.dumazet@gmail.com>
Cc: <netdev@vger.kernel.org>, <xen-devel@lists.xen.org>,
David Vrabel <david.vrabel@citrix.com>,
Konrad Wilk <konrad.wilk@oracle.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: [PATCH net-next] xen-netfront: try linearizing SKB if it occupies too many slots
Date: Wed, 2 Jul 2014 14:12:14 +0100 [thread overview]
Message-ID: <53B4052E.10008@citrix.com> (raw)
In-Reply-To: <53B3F9BF.603@canonical.com>
Hi,
Yes, it lost traction recently a little bit. The latest idea is to use
the skb segmenting code in netfront to slice up the skb until it becomes
a set of skbs which can fit through the ring. But to test that out I
need to make pktgen work with TCP, that's where this got stopped.
Zoli
On 02/07/14 13:23, Stefan Bader wrote:
> On 30.05.2014 14:07, Zoltan Kiss wrote:
>> On 30/05/14 09:06, Stefan Bader wrote:
>>> On 16.05.2014 18:29, Zoltan Kiss wrote:
>>>> On 16/05/14 16:34, Wei Liu wrote:
>>>>> On Fri, May 16, 2014 at 08:22:19AM -0700, Eric Dumazet wrote:
>>>>>> On Fri, 2014-05-16 at 15:36 +0100, Wei Liu wrote:
>>>>>>> On Fri, May 16, 2014 at 07:21:08AM -0700, Eric Dumazet wrote:
>>>>>>>> On Fri, 2014-05-16 at 14:11 +0100, Wei Liu wrote:
>
> Hi Zoltan,
>
> I lost a bit track about this. I think I saw some summary about brainstorming
> something similar but for the backend from you (not sure). I think during last
> Xen Hackathon. I cannot remember that got to some solution on the netfront side.
> Do I miss something?
>
> -Stefan
>>
>> Regads,
>>
>> Zoltan
next prev parent reply other threads:[~2014-07-02 13:12 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-16 11:08 [PATCH net-next] xen-netfront: try linearizing SKB if it occupies too many slots Wei Liu
2014-05-16 13:04 ` Eric Dumazet
2014-05-16 13:11 ` Wei Liu
2014-05-16 13:11 ` Wei Liu
2014-05-16 14:21 ` Eric Dumazet
2014-05-16 14:21 ` Eric Dumazet
2014-05-16 14:36 ` Wei Liu
2014-05-16 15:22 ` Eric Dumazet
2014-05-16 15:22 ` Eric Dumazet
2014-05-16 15:34 ` Wei Liu
2014-05-16 16:29 ` Zoltan Kiss
2014-05-16 16:47 ` Eric Dumazet
2014-05-16 16:51 ` Zoltan Kiss
2014-05-16 16:51 ` Zoltan Kiss
2014-05-16 17:00 ` Eric Dumazet
2014-05-16 17:00 ` Eric Dumazet
2014-05-16 16:47 ` Eric Dumazet
2014-05-16 16:54 ` Wei Liu
2014-05-16 16:54 ` Wei Liu
2014-05-19 16:47 ` Zoltan Kiss
2014-05-19 16:47 ` Zoltan Kiss
2014-05-30 8:06 ` Stefan Bader
2014-05-30 12:07 ` Zoltan Kiss
2014-05-30 12:07 ` Zoltan Kiss
2014-05-30 12:37 ` Stefan Bader
2014-05-30 12:37 ` Stefan Bader
2014-07-02 12:23 ` Stefan Bader
2014-07-02 12:23 ` Stefan Bader
2014-07-02 13:12 ` Zoltan Kiss [this message]
2014-07-02 13:12 ` Zoltan Kiss
2014-05-30 12:11 ` Wei Liu
2014-05-30 12:11 ` Wei Liu
2014-05-30 12:28 ` Stefan Bader
2014-05-30 12:38 ` Wei Liu
2014-05-30 12:38 ` Wei Liu
2014-05-30 12:28 ` Stefan Bader
2014-05-30 12:28 ` David Laight
2014-05-30 12:28 ` David Laight
2014-05-30 12:35 ` Wei Liu
2014-05-30 12:35 ` Wei Liu
2014-05-30 8:06 ` Stefan Bader
2014-05-16 16:29 ` Zoltan Kiss
2014-05-16 15:34 ` Wei Liu
2014-05-16 14:36 ` Wei Liu
2014-05-16 13:04 ` Eric Dumazet
-- strict thread matches above, loose matches on Subject: below --
2014-05-16 11:08 Wei Liu
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=53B4052E.10008@citrix.com \
--to=zoltan.kiss@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=eric.dumazet@gmail.com \
--cc=konrad.wilk@oracle.com \
--cc=netdev@vger.kernel.org \
--cc=stefan.bader@canonical.com \
--cc=wei.liu2@citrix.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 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.