All of lore.kernel.org
 help / color / mirror / Atom feed
From: R.E.Wolff@BitWizard.nl (Rogier Wolff)
To: James Sutherland <jas88@cam.ac.uk>
Cc: Rogier Wolff <R.E.Wolff@BitWizard.nl>, linux-kernel@vger.kernel.org
Subject: Re: 8139 full duplex?
Date: Fri, 16 Feb 2001 10:40:53 +0100 (MET)	[thread overview]
Message-ID: <200102160940.KAA02620@cave.bitwizard.nl> (raw)
In-Reply-To: <Pine.SOL.4.21.0102160930050.26108-100000@orange.csi.cam.ac.uk> from James Sutherland at "Feb 16, 2001 09:32:34 am"

James Sutherland wrote:
> > That would explain me seeing way too many collisions on that old hub
> > (which obviously doesn't support full-duplex).
> 
> No, it would just prevent your card working. Large numbers of collisions
> are normal during fast transfers across a hub.

Why would it completely "not work"? 

As long as the host doesn't have something to send while a recieve is
in progress, everything should work. A friend reports that he spent
lots of time trying to debug a network where "too many" collisions
were happening. Turns out one card was in full-duplex, while the other
side wasn't.

I benchmarked my old network at 10-12 seconds for a 100Mb
transfer. That sounds indeed as if there isn't a whole lot of
collisions happening. And I can immagine that the acks run into the
next data-packet all the time, so that performance would indeed be
very bad if the card was misconfigured. On the other hand I had one
machine that was taking 180 seconds for the 100Mb transfer.

Anyway, I remember fiddling with the eexpress 100 driver, and there
the driver was involved in switching the speeds, and doing some
management of the switchover of full-duplex/half-duplex. I'd expect
some message from the driver if it saw such a change. 

But you're saying that the 8139 chip does it internally, and fully  
automatically? Ok. Good. 

				Roger. 

-- 
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2137555 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
* There are old pilots, and there are bold pilots. 
* There are also old, bald pilots. 

  reply	other threads:[~2001-02-16  9:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-16  8:58 8139 full duplex? Rogier Wolff
2001-02-16  9:32 ` James Sutherland
2001-02-16  9:40   ` Rogier Wolff [this message]
2001-02-16 10:52     ` Roeland Th. Jansen
2001-02-16 11:15     ` James Sutherland
2001-02-16  9:46 ` Jeff Garzik
2001-02-16 10:03   ` Rogier Wolff
2001-02-16 11:19     ` James Sutherland
2001-02-16 10:09 ` Alan Cox

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=200102160940.KAA02620@cave.bitwizard.nl \
    --to=r.e.wolff@bitwizard.nl \
    --cc=jas88@cam.ac.uk \
    --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 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.