All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lars Marowsky-Bree <lmb@suse.de>
To: Russell Leighton <russ@elegant-software.com>, Tony.P.Lee@nokia.com
Cc: wookie@osdl.org, alan@lxorguk.ukuu.org.uk, woody@co.intel.com,
	linux-kernel@vger.kernel.org, zaitcev@redhat.com
Subject: Re: InfiniBand BOF @ LSM - topics of interest
Date: Thu, 16 May 2002 00:41:38 +0200	[thread overview]
Message-ID: <20020515224138.GJ27307@marowsky-bree.de> (raw)
In-Reply-To: <4D7B558499107545BB45044C63822DDE3A2071@mvebe001.NOE.Nokia.com> <3CE2D4DB.3020702@elegant-software.com>

On 2002-05-15T17:36:27,
   Russell Leighton <russ@elegant-software.com> said:

> Lot's of very cool ideas for IB ...not knowing much about IB, but
> being curious and interested, I have a question which may be stupid
> so I apoligize in advance if it is...
> 
> Can we really have these sort of low level IB interactions and have :
>    - security issues addressed, mostly an issue if the devices are over 
> a network w/other devices

The idea is that the IB interconnect is "trusted". Doing very low level kernel
operations cluster-style over a non-trusted link is asking for it; either you
lose security-wise or performance for authentication / encryption _will_ kill
you.

The real interesting question from my side is "availability"; how does the
kernel deal with crashed nodes, loss of link etc? If you already had agreed or
semi-standard interfaces here, we would gladly pick them up.

These generic cluster interfaces are being discussed as part of the Open
Clustering Framework now, and it would be good if a kernel developer reviewed
the discussions regarding the generic event mechanism proposed from a kernel
perspective.


Sincerely,
    Lars Marowsky-Brée <lmb@suse.de>

-- 
Immortality is an adequate definition of high availability for me.
	--- Gregory F. Pfister


  reply	other threads:[~2002-05-15 22:42 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-15 20:47 InfiniBand BOF @ LSM - topics of interest Tony.P.Lee
2002-05-15 21:36 ` Russell Leighton
2002-05-15 22:41   ` Lars Marowsky-Bree [this message]
2002-05-16  4:51   ` Ashok Raj
  -- 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: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-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=20020515224138.GJ27307@marowsky-bree.de \
    --to=lmb@suse.de \
    --cc=Tony.P.Lee@nokia.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=russ@elegant-software.com \
    --cc=woody@co.intel.com \
    --cc=wookie@osdl.org \
    --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 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.