From: "David S. Miller" <davem@redhat.com>
To: Ville Nuorvala <vnuorval@tcs.hut.fi>
Cc: usagi-core@linux-ipv6.org, netdev@oss.sgi.com
Subject: Re: [PATCH] IPv6: Allow nested IPv6 encapsulations on same node
Date: Thu, 28 Aug 2003 00:10:55 -0700 [thread overview]
Message-ID: <20030828001055.1aa32481.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0308271731140.7839-100000@rhea.tcs.hut.fi>
On Wed, 27 Aug 2003 19:42:21 +0300 (EEST)
Ville Nuorvala <vnuorval@tcs.hut.fi> wrote:
> In the old days ip6_build_xmit() was the way to go if you wanted
> fragmentation, but now ip6_fragment() _seems_ to be able to handle the
> whole thing without the help of ip6_append_data() & Co.
>
> I'll have to test this and get back to you!
Another point is that you really don't want to use sockets
here for another reason, you're going to get artificial queueing
limits bacause each tunnel packet gets charged to the socket.
prev parent reply other threads:[~2003-08-28 7:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0308271413450.7839-100000@rhea.tcs.hut.fi>
2003-08-27 11:20 ` [PATCH] IPv6: Allow nested IPv6 encapsulations on same node David S. Miller
[not found] ` <Pine.LNX.4.44.0308271441390.7839-100000@rhea.tcs.hut.fi>
2003-08-27 13:45 ` David S. Miller
[not found] ` <Pine.LNX.4.44.0308271731140.7839-100000@rhea.tcs.hut.fi>
2003-08-28 7:10 ` David S. 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=20030828001055.1aa32481.davem@redhat.com \
--to=davem@redhat.com \
--cc=netdev@oss.sgi.com \
--cc=usagi-core@linux-ipv6.org \
--cc=vnuorval@tcs.hut.fi \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).