From: Nivedita Singhvi <niv@us.ibm.com>
To: Jon Grimm <jgrimm2@us.ibm.com>
Cc: "David S. Miller" <davem@redhat.com>,
sri@us.ibm.com, kuznet@ms2.inr.ac.ru, netdev@oss.sgi.com
Subject: Re: SCTP path mtu support needs some ip layer support.
Date: Wed, 08 Jan 2003 15:56:34 -0800 [thread overview]
Message-ID: <3E1CBAB2.78FE168A@us.ibm.com> (raw)
In-Reply-To: 3E1CAACB.5D1B82DB@us.ibm.com
Jon Grimm wrote:
>
> "David S. Miller" wrote:
> >
> > From: Sridhar Samudrala <sri@us.ibm.com>
> > Date: Wed, 8 Jan 2003 15:04:53 -0800 (PST)
> > Sigh... I guess the new argument to ip_queue_xmit() is the least
> > intrusive.
>
> I hate to mention it, but there is at least one other alternative (to
> complete the picture) that is to chunk up the messages into their
> smallest fragment and then bundle these chunks up to the MTU allowable
> packet.
> This however does each up space in the packet for each chunk header and
> require more processing at the other end to reassemble the records.
>
> IIRC, this is what OpenSS7s SCTP does, while the KAME SCTP manually
> controls the DF bit as per Sridhar's suggestion. There are tradeoffs
> in either approach.
Jon, from the performance standpoint, that would be the least
preferred approach, right? Also, adding the argument to ip_queue_xmit()
would at least be a general solution for other possible protocols,
raw apps, etc or features that might want to make use of it..
(heaven forbid ;))..
thanks,
Nivedita
next prev parent reply other threads:[~2003-01-08 23:56 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
2003-01-08 22:48 ` Jon Grimm
2003-01-08 23:45 ` David S. Miller
2003-01-08 23:56 ` Nivedita Singhvi [this message]
[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=3E1CBAB2.78FE168A@us.ibm.com \
--to=niv@us.ibm.com \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.