From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Jan Harkes <jaharkes@cs.cmu.edu>
Cc: "Christopher Friesen" <cfriesen@nortelnetworks.com>,
linux-kernel@vger.kernel.org
Subject: Re: want opinions on possible glitch in 2.4 network error reporti ng
Date: Thu, 07 Feb 2002 15:10:26 -0500 [thread overview]
Message-ID: <3C62DF32.50FA6FC6@nortelnetworks.com> (raw)
In-Reply-To: <Pine.LNX.3.95.1020207125644.8721A-100000@chaos.analogic.com> <3C62CB25.75487AD5@nortelnetworks.com> <20020207195118.GB31329@ravel.coda.cs.cmu.edu>
Jan Harkes wrote:
>
> On Thu, Feb 07, 2002 at 01:44:53PM -0500, Chris Friesen wrote:
> > The possibility of random dropping of packets in the kernel means that an
> > infinite loop on sendto() will chew up the entire machine even if you've only
> > got a 10Mbit/s link. This seems just wrong.
>
> What happens if you have the 100Mbit/s side of the link and the receiver
> has a 9600baud dial-in modem....
>
> The sending side needs to do throttling based on packet loss anyways, it
> really doesn't matter that it's lost locally or on the network or at the
> receiving host.
Yes, this is true for general use. However, suppose I want to do an IP takeover
and send out arp packets to force an update of the arp caches of everyone on the
subnet. The network is tightly controlled and we know everything that's on it.
How do I guarantee that my packets get out of the local system and onto the
wire?
Currently I send three packets in a row on failover, and another three packets
every 10 seconds. It would still be nice to be assured that the packets
actually made it onto the wire.
This is linux, we like having absolute control over our system. Does it make
sense to have no possible way of guaranteeing that a specific packet has made it
onto the wire?
Chris
--
Chris Friesen | MailStop: 043/33/F10
Nortel Networks | work: (613) 765-0557
3500 Carling Avenue | fax: (613) 765-2986
Nepean, ON K2H 8E9 Canada | email: cfriesen@nortelnetworks.com
next prev parent reply other threads:[~2002-02-07 20:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-07 17:37 want opinions on possible glitch in 2.4 network error reporti ng Perches, Joe
2002-02-07 18:08 ` Richard B. Johnson
2002-02-07 18:44 ` Chris Friesen
2002-02-07 19:51 ` Jan Harkes
2002-02-07 20:10 ` Chris Friesen [this message]
2002-02-07 20:33 ` Richard B. Johnson
2002-02-07 21:06 ` Chris Friesen
2002-02-07 21:29 ` Richard B. Johnson
2002-02-07 22:29 ` Mark Frazer
2002-02-08 8:35 ` Ian Molton
-- strict thread matches above, loose matches on Subject: below --
2002-02-07 20:37 Perches, Joe
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=3C62DF32.50FA6FC6@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=jaharkes@cs.cmu.edu \
--cc=linux-kernel@vger.kernel.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