From: Torrey Hoffman <torrey.hoffman@myrio.com>
To: "'Alan Cox'" <alan@lxorguk.ukuu.org.uk>, Nat Ersoz <nat.ersoz@myrio.com>
Cc: linux-kernel@vger.kernel.org
Subject: RE: IGMP join/leave time variability
Date: Thu, 26 Jul 2001 10:47:05 -0700 [thread overview]
Message-ID: <D52B19A7284D32459CF20D579C4B0C0211C961@mail0.myrio.com> (raw)
Alan Cox wrote:
> Read the IGMP RFC documents they discuss in detail the cases
> where time delays and randomness are needed and important.
I'm one of Nat's co-workers, also looking at this problem.
RFC 2236, the IGMPv2 spec, states:
"
When a host joins a multicast group, it should immediately transmit
an unsolicited Version 2 Membership Report for that group, in case it
is the first member of that group on the network. To cover the
possibility of the initial Membership Report being lost or damaged,
it is recommended that it be repeated once or twice after short
delays [Unsolicited Report Interval].
"
>From this, I infer that there should be _no_ initial delay on sending
the IGMP join. In fact, a quick peek at the source confirms this:
(net/ipv4/igmp.c):
#define IGMP_Initial_Report_Delay (1*HZ)
/* IGMP_Initial_Report_Delay is not from IGMP specs!
* IGMP specs require to report membership immediately after
* joining a group, but we delay the first report by a
* small interval. It seems more natural and still does not
* contradict to specs provided this delay is small enough.
*/
But this "small interval" is actually very noticeable in our application.
I think we'll take it out of our version, and I believe it should be
removed from the standard kernel.
Regards,
Torrey Hoffman
next reply other threads:[~2001-07-26 17:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-26 17:47 Torrey Hoffman [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-07-26 18:07 Nat Ersoz
[not found] <no.id>
2001-07-26 11:59 ` Alan Cox
2001-07-26 17:51 ` Alan Cox
2001-07-27 9:27 ` David S. Miller
2001-07-26 2:04 Nat Ersoz
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=D52B19A7284D32459CF20D579C4B0C0211C961@mail0.myrio.com \
--to=torrey.hoffman@myrio.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=nat.ersoz@myrio.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
all inboxes | Powered by JetHome®