All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: herbert@gondor.apana.org.au
Cc: sri@us.ibm.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next-2.6 0/5] Add support for software UDP fragmentation offload(UFO)
Date: Sun, 12 Jul 2009 14:39:42 -0700 (PDT)	[thread overview]
Message-ID: <20090712.143942.73393103.davem@davemloft.net> (raw)
In-Reply-To: <20090710010405.GA32639@gondor.apana.org.au>

From: Herbert Xu <herbert@gondor.apana.org.au>
Date: Fri, 10 Jul 2009 09:04:05 +0800

> On Thu, Jul 09, 2009 at 11:09:41AM -0700, Sridhar Samudrala wrote:
>> The following set of patches fixes support for UDP fragmentation offload
>> in the core networking stack to send/receive large UDP packets over UFO
>> enabled devices and fallback to software UFO when the outgoing device 
>> doesn't support UFO.
>> These patches enable setting UFO on virtio-net and tap devices and allow
>> large UDP packets to be sent between guest to host and inter guest under
>> KVM.
>> 
>> [PATCH net-next-2.6 1/5] udpv4: Handle large incoming UDP/IPv4 packets and support software UFO.
>> [PATCH net-next-2.6 2/5] udpv6: Fix HW checksum support for outgoing UFO packets
>> [PATCH net-next-2.6 3/5] udpv6: Fix gso_size setting in ip6_ufo_append_data
>> [PATCH net-next-2.6 4/5] udpv6: Remove unused skb argument of ipv6_select_ident()
>> [PATCH net-next-2.6 5/5] udpv6: Handle large incoming UDP/IPv6 packets and support software UFO
> 
> Acked-by: Herbert Xu <herbert@gondor.apana.org.au>

Looks good to me, all applied, thanks!

      reply	other threads:[~2009-07-12 21:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-09 18:09 [PATCH net-next-2.6 0/5] Add support for software UDP fragmentation offload(UFO) Sridhar Samudrala
2009-07-10  1:04 ` Herbert Xu
2009-07-12 21:39   ` David Miller [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=20090712.143942.73393103.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=netdev@vger.kernel.org \
    --cc=sri@us.ibm.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.