All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Tom Herbert <tom@herbertland.com>
Cc: Jiri Benc <jbenc@redhat.com>, Netdev <netdev@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: GSO with udp_tunnel_xmit_skb
Date: Fri, 6 Nov 2015 12:48:15 +0100	[thread overview]
Message-ID: <CAHmME9rp7ZJ_9=LHiQrO4ay_7mECj_jAmZBVHNT3Oi4uz8YxeQ@mail.gmail.com> (raw)
In-Reply-To: <CALx6S379Ma+u1rKCwyDWEHDZpQUjr9mB_YQ4=iySo9Lgga2PaQ@mail.gmail.com>

Hi Tom,

On Fri, Nov 6, 2015 at 8:19 AM, Tom Herbert <tom@herbertland.com> wrote:
> Is this about UFO or GSO (in email subject)? UFO should operate
> independently encapsulation or inner packet setting.

I suppose this is about UFO.

Specifically -- let's say I have a list of 500 skbs, which have their
data in place but don't yet have an IP or UDP header etc. I want to
send out these out using udp_tunnel_xmit_skb. Right now, if I just
send them all out, one after another, they don't seem to be getting
assembled into a super packet suitable for UFO. Instead, they're just
sent one at a time, and I get the vast majority of `perf top` CPU
usage in my ethernet card's driver and along the path to it -- the
problem that UFO is supposed to solve.

So my question is -- how can I make UFO happen with udp_tunnel_xmit_skb?

Thanks,
Jason

  reply	other threads:[~2015-11-06 11:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-05 10:52 GSO with udp_tunnel_xmit_skb Jason A. Donenfeld
2015-11-06  7:19 ` Tom Herbert
2015-11-06 11:48   ` Jason A. Donenfeld [this message]
2015-11-07 17:19     ` Maciej Żenczykowski
2015-11-07 22:39       ` Jason A. Donenfeld
2015-11-07 23:40         ` Maciej Żenczykowski
2015-11-08 10:36           ` Jason A. Donenfeld
2015-11-08 10:57             ` Herbert Xu
2015-11-08 14:57               ` Jason A. Donenfeld
2015-11-09  1:40                 ` Herbert Xu
2015-11-09  2:23                   ` Jason A. Donenfeld
2015-11-09  3:18                     ` Maciej Żenczykowski

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='CAHmME9rp7ZJ_9=LHiQrO4ay_7mECj_jAmZBVHNT3Oi4uz8YxeQ@mail.gmail.com' \
    --to=jason@zx2c4.com \
    --cc=jbenc@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=tom@herbertland.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.