From: <Tony.P.Lee@nokia.com>
To: <alan@lxorguk.ukuu.org.uk>, <lmb@suse.de>
Cc: <woody@co.intel.com>, <linux-kernel@vger.kernel.org>,
<zaitcev@redhat.com>
Subject: RE: InfiniBand BOF @ LSM - topics of interest
Date: Tue, 14 May 2002 13:19:13 -0700 [thread overview]
Message-ID: <4D7B558499107545BB45044C63822DDE3A206D@mvebe001.NOE.Nokia.com> (raw)
> > On 2002-05-14T00:42:07,
> > Alan Cox <alan@lxorguk.ukuu.org.uk> said:
> >
> > > Kernel mode RPC over infiniband - relevant to mosix type
> stuff, to McVoy
> > > scalable cluster type stuff and also to things like file
> system offload
> >
> > For that, a generic comm interface would be a good thing to
> have first.
>
> It has to be fast, nonblocking and kernel callable. Cluster
> people count
> individual microseconds so its base layers must be extremely efficient
> even if there are "easy use" layers above. The obvious "easy
> use" layer being
> IP over infiniband.
>
I like to see user application such as VNC, SAMBA build directly
on top of IB API. I have couple of IB cards that can
send 10k 32KBytes message (320MB of data) every ~1 second over
1x link with only <7% CPU usage (single CPU xeon 700MHz).
I was very impressed.
Go thru the socket layer API would just slow thing down.
With IB bandwidth faster than standard 32/33MHZ PCI, one might
run DOOM over VNC over IB on remote computer faster
than a normal PC running DOOM locally....
One might create a OS that miror the complete process state
info (replicate all the modified page) everytime that
process is schedule out.
----------------------------------------------------------------
Tony Lee
next reply other threads:[~2002-05-14 20:19 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-14 20:19 Tony.P.Lee [this message]
2002-05-14 20:42 ` InfiniBand BOF @ LSM - topics of interest Pete Zaitcev
2002-05-14 23:25 ` Jakob Østergaard
2002-05-14 23:58 ` Alan Cox
2002-05-15 15:45 ` Timothy D. Witham
-- 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-15 1:29 Tony.P.Lee
2002-05-15 2:35 ` Alan Cox
2002-05-15 5:01 ` Pete Zaitcev
2002-05-15 11:29 ` Alan Cox
2002-05-15 14:27 ` Ashok Raj
2002-05-15 16:34 ` Stephen Hemminger
2002-05-14 22:15 Woodruff, Robert J
2002-05-15 2:42 ` 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=4D7B558499107545BB45044C63822DDE3A206D@mvebe001.NOE.Nokia.com \
--to=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 \
--cc=zaitcev@redhat.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).