From: Andi Kleen <ak@muc.de>
To: "David S. Miller" <davem@redhat.com>
Cc: Andi Kleen <ak@suse.de>,
yoshfuji@linux-ipv6.org, ak@muc.de, netdev@oss.sgi.com
Subject: Re: [PATCH] Increase snd/rcv buffers in pppoe
Date: 26 Feb 2004 20:49:00 +0100
Date: Thu, 26 Feb 2004 20:49:00 +0100 [thread overview]
Message-ID: <20040226194900.GA8230@colin2.muc.de> (raw)
In-Reply-To: <20040223133233.71eecc99.davem@redhat.com>
Sorry for the late answer.
On Mon, Feb 23, 2004 at 01:32:33PM -0800, David S. Miller wrote:
> > > 2) IPV6 icmp does the same as ipv4, except this value is even more wrong there
> > > especially considering jumbograms. With current code, sending a jumbogram
> > > ipv6 icmp packet would simply fail, and I wonder if anyone has even tried
> > > this.
> >
> > Isn't even ICMPv6 limited to the minimum guaranteed MTU (1000 something) like ICMPv4 is to
> > 576 bytes?
>
> What about ECHO? I can't send an ICMPv6 jumbo sized ECHO and expect a fully quoted response
> back?
I don't think it should be only sized for big datagrams and other obscure cases.
Better is a reasonable default to fit at least 64K of data with a standard MTU like ~1.4K.
Or may resize it on MTU change, but I'm not sure that's worth the effort.
Are you working on this or should I prepare a new patch?
-Andi
next prev parent reply other threads:[~2004-02-26 19:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-22 23:47 [PATCH] Increase snd/rcv buffers in pppoe Andi Kleen
2004-02-23 7:26 ` David S. Miller
2004-02-23 10:53 ` Andi Kleen
2004-02-23 11:01 ` YOSHIFUJI Hideaki / 吉藤英明
2004-02-23 11:16 ` Andi Kleen
2004-02-23 11:38 ` YOSHIFUJI Hideaki / 吉藤英明
2004-02-23 18:26 ` David S. Miller
2004-02-23 20:12 ` Andi Kleen
2004-02-23 21:32 ` David S. Miller
2004-02-26 19:49 ` Andi Kleen [this message]
2004-02-26 20:42 ` David S. Miller
2004-02-26 20:52 ` Andi Kleen
2004-02-26 22:03 ` Andi Kleen
2004-02-26 22:22 ` David S. Miller
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=20040226194900.GA8230@colin2.muc.de \
--to=ak@muc.de \
--cc=ak@suse.de \
--cc=davem@redhat.com \
--cc=netdev@oss.sgi.com \
--cc=yoshfuji@linux-ipv6.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 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).