From: "David S. Miller" <davem@redhat.com>
To: sri@us.ibm.com
Cc: kuznet@ms2.inr.ac.ru, jgrimm2@us.ibm.com, netdev@oss.sgi.com
Subject: Re: SCTP path mtu support needs some ip layer support.
Date: Wed, 08 Jan 2003 15:06:38 -0800 (PST) [thread overview]
Message-ID: <20030108.150638.09647984.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0301081451110.2281-100000@dyn9-47-18-86.beaverton.ibm.com>
From: Sridhar Samudrala <sri@us.ibm.com>
Date: Wed, 8 Jan 2003 15:04:53 -0800 (PST)
1. Add a new argument to ip_queue_xmit() to pass the value of DF bit.
2. Use the __unused field in skb to pass the value of DF bit.
3. Let SCTP call its own routine that fills in the ip header with the
appropriate value in the DF bit, but this duplicates most of the code
in ip_queue_xmit(). Also ip_options_build() needs to be exported.
Which option do you prefer? Or can you suggest any better alternative?
Too bad there's not a 4th option, fix SCTP. This is really broken
that the data stream can get into a state where resegmentation cannot
be performed.
Sigh... I guess the new argument to ip_queue_xmit() is the least
intrusive.
next prev parent reply other threads:[~2003-01-08 23:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-08 23:04 SCTP path mtu support needs some ip layer support Sridhar Samudrala
2003-01-08 23:06 ` David S. Miller [this message]
2003-01-08 22:48 ` Jon Grimm
2003-01-08 23:45 ` David S. Miller
2003-01-08 23:56 ` Nivedita Singhvi
[not found] <3E1CCD72.6020100@us.ibm.com>
2003-01-13 20:48 ` kuznet
2003-01-13 21:07 ` Andi Kleen
2003-01-13 21:21 ` Nivedita Singhvi
2003-01-13 21:25 ` kuznet
2003-01-13 23:34 ` Jon Grimm
2003-01-13 22:54 ` Sridhar Samudrala
2003-01-13 23:03 ` Mika Liljeberg
2003-01-14 0:56 ` Sridhar Samudrala
2003-01-14 6:46 ` Mika Liljeberg
2003-01-13 23:22 ` kuznet
2003-01-14 0:49 ` Sridhar Samudrala
2003-01-14 1:22 ` kuznet
2003-01-14 18:44 ` Sridhar Samudrala
2003-01-14 20:11 ` Mika Liljeberg
2003-01-14 22:15 ` Sridhar Samudrala
2003-01-14 21:16 ` kuznet
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=20030108.150638.09647984.davem@redhat.com \
--to=davem@redhat.com \
--cc=jgrimm2@us.ibm.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@oss.sgi.com \
--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 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).