linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pete Zaitcev <zaitcev@redhat.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Tony.P.Lee@nokia.com, lmb@suse.de, woody@co.intel.com,
	linux-kernel@vger.kernel.org, zaitcev@redhat.com
Subject: Re: InfiniBand BOF @ LSM - topics of interest
Date: Wed, 15 May 2002 01:01:07 -0400	[thread overview]
Message-ID: <20020515010107.A31154@devserv.devel.redhat.com> (raw)
In-Reply-To: <4D7B558499107545BB45044C63822DDE3A206F@mvebe001.NOE.Nokia.com> <E177od2-0000wp-00@the-village.bc.nu>

> Date: Wed, 15 May 2002 03:35:00 +0100 (BST)
> From: Alan Cox <alan@lxorguk.ukuu.org.uk>

> According to folks at Quantum the IB stuff isnt doing 'true' congestion
> control. At the moment its hard to tell since 1.0a doesn't deal with
> congestion management and the 2.0 congestion stuff isnt due out until
> later this year. Even then the Infiniband trade association folks use
> words like "hopefully eliminating the congestion" in their presentation to 
> describe their mechanism.

The thing about Infiniband is that its scope is so great.
If you consider Infiniband was only a glorified PCI with serial
connector, the congestion control is not an issue. Credits
are quite sufficient to provide per link flow control, and
everything would work nicely with a couple of switches.
Such was the original plan, anyways, but somehow cluster
ninjas managed to hijack the spec and we have the rabid
overengineering running amok. In fact, they ran so far
that Intel jumped ship and created PCI Express, and we
have discussions about congestion control. Sad, really...

-- Pete

  reply	other threads:[~2002-05-15  5:01 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-15  1:29 InfiniBand BOF @ LSM - topics of interest Tony.P.Lee
2002-05-15  2:35 ` Alan Cox
2002-05-15  5:01   ` Pete Zaitcev [this message]
2002-05-15 11:29     ` Alan Cox
2002-05-15 14:27       ` Ashok Raj
2002-05-15 16:34     ` Stephen Hemminger
  -- strict thread matches above, loose matches on Subject: below --
2002-05-16 23:42 Woodruff, Robert J
2002-05-16 10:37 Eric Brunner-Williams in Portland Maine
2002-05-15 23:58 Woodruff, Robert J
2002-05-16  0:32 ` Alan Cox
2002-05-15 20:47 Tony.P.Lee
2002-05-15 21:36 ` Russell Leighton
2002-05-15 22:41   ` Lars Marowsky-Bree
2002-05-16  4:51   ` Ashok Raj
2002-05-15 20:37 Woodruff, Robert J
2002-05-15 20:55 ` Pete Zaitcev
2002-05-15 21:01 ` Alan Cox
2002-05-14 22:15 Woodruff, Robert J
2002-05-15  2:42 ` Timothy D. Witham
2002-05-14 20:19 Tony.P.Lee
2002-05-14 20:42 ` Pete Zaitcev
2002-05-14 23:25 ` Jakob Østergaard
2002-05-14 23:58 ` Alan Cox
2002-05-15 15:45   ` Timothy D. Witham
2002-05-13 16:25 Woodruff, Robert J
2002-05-13 16:36 ` Pete Zaitcev
2002-05-14 20:09   ` Timothy D. Witham
2002-05-14 20:23     ` Pete Zaitcev
2002-05-14 20:33       ` Timothy D. Witham
2002-05-14 21:01         ` Timothy D. Witham
2002-05-13 23:42 ` Alan Cox
2002-05-13 23:26   ` Lars Marowsky-Bree
2002-05-14  0:19     ` Alan Cox
2002-05-14  0:19   ` Joel Becker
2002-05-15  0:11 ` Eric Brunner-Williams in Portland Maine

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=20020515010107.A31154@devserv.devel.redhat.com \
    --to=zaitcev@redhat.com \
    --cc=Tony.P.Lee@nokia.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lmb@suse.de \
    --cc=woody@co.intel.com \
    /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;
as well as URLs for NNTP newsgroup(s).