From: Andi Kleen <ak@muc.de>
To: "David S. Miller" <davem@redhat.com>
Cc: Andi Kleen <ak@muc.de>,
ak@suse.de, yoshfuji@linux-ipv6.org, netdev@oss.sgi.com
Subject: Re: [PATCH] Increase snd/rcv buffers in pppoe
Date: 26 Feb 2004 21:52:20 +0100
Date: Thu, 26 Feb 2004 21:52:20 +0100 [thread overview]
Message-ID: <20040226205220.GA29457@colin2.muc.de> (raw)
In-Reply-To: <20040226124245.5b3c77bf.davem@redhat.com>
On Thu, Feb 26, 2004 at 12:42:45PM -0800, David S. Miller wrote:
> On 26 Feb 2004 20:49:00 +0100
> Andi Kleen <ak@muc.de> wrote:
>
> > 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?
>
> Let's just leave things how we've changed them, and when people complain
> about jumbo MTU ipv6 icmp messages we'll address it.
Ah, I missed that you already checked it in. Sorry for the noise.
I will test now if your change really fixes the DSL performance problem.
-Andi
next prev parent reply other threads:[~2004-02-26 20:52 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
2004-02-26 20:42 ` David S. Miller
2004-02-26 20:52 ` Andi Kleen [this message]
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=20040226205220.GA29457@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).