All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Admissions Office" <admissions@internet.edu.nf>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Gigabit Etnernet router
Date: Tue, 25 Jun 2002 15:05:43 +0000	[thread overview]
Message-ID: <marc-lartc-102501765831651@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102492927609063@msgid-missing>


Good point . Such was the problem in the first series of Cisco 7000 units.
The company was only able to make them do 21.5MB  Having said that there
are still very few people who would be able to use this. In-house we have
built
several of these units using both 3Com and Intel cards. I find that two main
factors
were the most common reason for some sort of failure.. Heat from the cards
and
Intel cards were just problems. With the 3Com cards we never seems to have a
problem.

Also - a 100MB control connection was maintained over a third 3Com card.


> More to the point, where can you get a motherboard with 3 64x66 PCI
> buses?(!!)  Note that one gigabit card actually can use 2gigabits of
> PCI bandwidth (one in, one out), and a pci bus is nowhere near 100%
> efficient, so one 64x66 PCI bus has enough bandwidth to handle 1 such
> card at full bandwidth, not enough for 2.
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

      parent reply	other threads:[~2002-06-25 15:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-24 14:33 [LARTC] Gigabit Etnernet router M.F. PSIkappa
2002-06-24 23:25 ` bert hubert
2002-06-25  5:14 ` Don Cohen
2002-06-25 15:05 ` Admissions Office [this message]

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=marc-lartc-102501765831651@msgid-missing \
    --to=admissions@internet.edu.nf \
    --cc=lartc@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.