From: Nivedita Singhvi <niv@us.ibm.com>
To: Andi Kleen <ak@suse.de>
Cc: ruddk@us.ibm.com, netdev@oss.sgi.com, chester.f.johnson@intel.com
Subject: Re: PMTU issues due to TOS field manipulation (for DSCP)
Date: Wed, 10 Dec 2003 13:11:41 -0800 [thread overview]
Message-ID: <3FD78C0D.4030609@us.ibm.com> (raw)
In-Reply-To: <20031210215527.239fb33f.ak@suse.de>
Andi Kleen wrote:
> Only the router would need to change (and rewrite ICMP messages, which is a
> bit nasty, but then compatibility is not always fun)
True, but I get a sinking feeling when I hear we have to change
router/icmp code. The word "only" seems inappropriate ;).
> -Andi
>
> P.S.: I am not opposed to fixing linux for this, just I have my doubts
> that fixing all end hosts is a practical solution for the problem.
The reason it seems simpler to me, at least, and I don't
speak for Kevin or the person at Intel who first reported
the problem, is that I see only a few people (well, only
Intel :)) running into the problem. So if there were a
patch available or the fix were in some release, only
the few end hosts who actually needed it would need to
upgrade. Otherwise, rollout would be evolutionary.
But also open to other approaches...
thanks,
Nivedita
next prev parent reply other threads:[~2003-12-10 21:11 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-10 18:23 PMTU issues due to TOS field manipulation (for DSCP) Kevin W. Rudd
2003-12-10 19:34 ` Andi Kleen
2003-12-10 20:20 ` Julian Anastasov
2003-12-10 20:33 ` Nivedita Singhvi
2003-12-10 21:18 ` Julian Anastasov
2003-12-10 22:36 ` Nivedita Singhvi
2003-12-10 22:51 ` David S. Miller
2003-12-10 23:15 ` Julian Anastasov
2003-12-10 23:20 ` David S. Miller
2003-12-11 0:06 ` Julian Anastasov
2003-12-11 0:09 ` David S. Miller
2003-12-11 0:34 ` Julian Anastasov
2003-12-12 8:31 ` David S. Miller
2003-12-12 23:38 ` Julian Anastasov
2003-12-18 23:17 ` Kevin W. Rudd
2004-01-19 22:43 ` Kevin W. Rudd
2004-01-20 4:29 ` David S. Miller
2003-12-13 0:10 ` Julian Anastasov
2004-03-04 9:36 ` David S. Miller
2004-03-04 20:56 ` Julian Anastasov
2004-03-04 22:02 ` kuznet
2004-03-06 11:55 ` Julian Anastasov
2004-03-06 16:02 ` Julian Anastasov
2003-12-10 20:26 ` Kevin W. Rudd
2003-12-10 20:52 ` Andi Kleen
2003-12-10 20:30 ` Nivedita Singhvi
2003-12-10 20:55 ` Andi Kleen
2003-12-10 21:11 ` Nivedita Singhvi [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-10 21:35 Johnson, Chester F
2003-12-10 23:36 Johnson, Chester F
2003-12-11 0:17 ` Julian Anastasov
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=3FD78C0D.4030609@us.ibm.com \
--to=niv@us.ibm.com \
--cc=ak@suse.de \
--cc=chester.f.johnson@intel.com \
--cc=netdev@oss.sgi.com \
--cc=ruddk@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 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).