Quoting Bogdan Costescu <bogdan.costescu_at_[hidden]>:
>
> On Mon, 19 Jul 2004, DeJiang Jin wrote:
>
> > in documents and system log it is called as "3Com Gigabit NIC"
> > the driver is 3c2000
>
> OK. The Linux kernel comes with a driver called sk98lin that should
> support these cards. Please try this one too.
yes. you are right. using the driver sk98lin, Lam can work with our 3Com
Gigabit NIC. thank you.
>
> > when I used the "3Com NIC", I can open a ssh session from any node to
>
> > another node in the system. a interactive ssh session do use tcp
> > session.
>
> Functionality exists, but speed is lacking when the autonegotiation
> fails - whenever packets have to go into opposite directions (one
> being transmitted while another one comes in) there would be corrupted
> packets and TCP would need to retransmit them. That's why I asked
> about slow booting of LAM.
>
what's fail for negotiation when using 3c2000? for full-duplex or half-duplex?
the switch always shows the interfaces connected with the NICs are full-duplex
with 1000Mb/s.
and retransmiting missed packets is normal. they should be embeded in the
implementation of tcp. why is the module of lam sensitive to re-transmit
lossed packets. does it bypass the interface of tcp and exploit some features
of underlying layers for performance?
> --
> Bogdan Costescu
>
> IWR - Interdisziplinaeres Zentrum fuer Wissenschaftliches Rechnen
> Universitaet Heidelberg, INF 368, D-69120 Heidelberg, GERMANY
> Telephone: +49 6221 54 8869, Telefax: +49 6221 54 8868
> E-mail: Bogdan.Costescu_at_[hidden]
>
> _______________________________________________
> This list is archived at http://www.lam-mpi.org/MailArchives/lam/
>
|
