Re: Collision on NIC

From: Wes Peters (wes_at_softweyr.com)
Date: 05/31/03

  • Next message: Sean Chittenden: "Re: Network stack cloning / virtualization patches"
    To: Erwane Breton <breton@erwane.net>, freebsd-net@freebsd.org
    Date: Fri, 30 May 2003 17:14:53 -0700
    
    

    On Friday 30 May 2003 09:26, Erwane Breton wrote:
    > > > Well, I don't see the problem.
    > > >
    > > > My math says that that's .03% collision rate, which is so deep in
    > > > the noise as to be practically zero. What do you _think_ it
    > > > should be?
    > >
    > > Even Mr. Inventor of the ethernet himself regrets calling them
    > > collisions because that term has a bad ring people unfamiliar with
    > > the technological detail.
    > >
    > > Pete
    >
    > So there are no answers or solutions ?

    If it were a problem there might be a solution, but collisions
    are not a problem, they're normal on an ethernet. When you
    read "collision" you think "error." You must retrain your mind,
    collisions are normal operating procedure on ethernet. Really.
    If the collisions were above 10%, it would be cause for concern;
    at 0.03% I can only conclude that you have a switched ethernet
    and have occasional broadcast traffic. 0.03% is way too low for
    any half-duplex (i.e. built with hubs) network.

    Repeat after me: "Collisions are normal on ethernet. 0.03% is
    nothing to be upset about."

    -- 
             "Where am I, and what am I doing in this handbasket?"
    Wes Peters                                              wes@softweyr.com
    _______________________________________________
    freebsd-net@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-net
    To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"
    

  • Next message: Sean Chittenden: "Re: Network stack cloning / virtualization patches"

    Relevant Pages

    • Re: Collision on NIC
      ... >> Even Mr. Inventor of the ethernet himself regrets calling them collisions because ...
      (freebsd-net)
    • Re: Collision on NIC
      ... > Even Mr. Inventor of the ethernet himself regrets calling them collisions because ...
      (freebsd-net)
    • Re: Disable Exponential Backoff (retry) on Ethernet?
      ... looks like "simulated" collisions will be the way to go. ... PJ>Have you considered simulating the network at a slightly higher lever: ... PJ>Use ipfw pipes or similar to simulate packet loss (either set a queue ... Some years ago I wrote a netgraph node that connected to ethernet nodes ...
      (freebsd-net)
    • Re: Disable Exponential Backoff (retry) on Ethernet?
      ... type protocol) so I actually need collisions! ... I will need to send a packet to the Ethernet device and only ... Are you even using hardware that does collisions? ... 10/100mbit "switches" that only switched between the two segments (and ...
      (freebsd-net)
    • Re: Disable Exponential Backoff (retry) on Ethernet?
      ... If I have to, I will employ some form of simulation of collisions, but that ... hubs would get collisions, ... PJ>Use ipfw pipes or similar to simulate packet loss (either set a queue ... Some years ago I wrote a netgraph node that connected to ethernet nodes ...
      (freebsd-net)