mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Troy Benjegerdes <hozer@hozed.org>
To: "Woodruff, Robert J" <woody@co.intel.com>, bill.magro@intel.com
Cc: Greg KH <greg@kroah.com>,
	"Woodruff, Robert J" <woody@jf.intel.com>,
	infiniband-general@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: [Infiniband-general] Getting an Infiniband access layer in the linux kernel
Date: Tue, 3 Feb 2004 22:08:34 -0600	[thread overview]
Message-ID: <20040204040834.GF11222@kalmia.hozed.org> (raw)
In-Reply-To: <F595A0622682C44DBBE0BBA91E56A5ED1C3673@orsmsx410.jf.intel.com>

I don't think we need to wait for a vendor driver to put together a 2.6
IB access layer patch for review. I for one would like to see what
*just* the access layer, without anything else looks like.

Those of us with hardware know it works on 2.4 with a mellanox VPD.. the
real question is what the code looks like.

There are outstanding issues I've seen in performance testing related to
integration with the memory management subsystem.. if we integrate
directly into 2.6, we'll have the opportunity (but not the requirement) 
for more intelligent ways to deal locking and unlocking of memory.
I suspect that someone with more MMU-foo than myself will see some
intelligent way of useing the rmap changes.

In particular, I want someone paranoid about security to examine the
security model for allowing what processes get access to what IB card
resources.

On Tue, Feb 03, 2004 at 06:01:20PM -0800, Woodruff, Robert J wrote:
> Good I think the InfiniBand community would like to get some of the 
> code into 2.6. 
> 
> The access layer is all loadable modules and does not require any kernel
> changes. 
> But we will need to look into integrating it into the build environment 
> (and provide a patch for that). 
> 
> We will work with the InfiniBand HCA vendors, such as Mellanox and
> Fujitsu, to 
> get the 2.6 code tested on the hardware and put together a patch that
> can be submitted for review by the larger linux community. If you would
> like to see the code before we
> run it on 2.6, we could possibly do that as well. 
> 
> 
> woody
> 
> 
> -----Original Message-----
> From: Greg KH [mailto:greg@kroah.com] 
> Sent: Tuesday, February 03, 2004 5:03 PM
> To: Woodruff, Robert J
> Cc: Troy Benjegerdes; Woodruff, Robert J;
> infiniband-general@lists.sourceforge.net; linux-kernel@vger.kernel.org
> Subject: Re: [Infiniband-general] Getting an Infiniband access layer in
> the linux kernel
> 
> 
> On Tue, Feb 03, 2004 at 04:17:36PM -0800, Woodruff, Robert J wrote:
> > 
> > I heard from a friend of mine that 2.6 was closed to new features.
> > What sayith the community on allowing additional experimental drivers
> > (like the infiniband access layer) into 2.6 ? Can we still submit
> > something or do we have to wait till 2.7 ?
> 
> If it's a subsystem that does not touch any of the existing kernel (with
> the exception of adding it to the build and Kconfig), then it probably
> will not be a problem to add.
> 
> But then again, that all depends on what the code looks like, and none
> of us have seen that yet :)
> 
> thanks,
> 
> greg k-h

-- 
--------------------------------------------------------------------------
Troy Benjegerdes                'da hozer'                hozer@hozed.org  

Somone asked my why I work on this free (http://www.fsf.org/philosophy/)
software stuff and not get a real job. Charles Shultz had the best answer:

"Why do musicians compose symphonies and poets write poems? They do it
because life wouldn't have any meaning for them if they didn't. That's why
I draw cartoons. It's my life." -- Charles Shultz

  reply	other threads:[~2004-02-04  4:08 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-04  2:01 Woodruff, Robert J
2004-02-04  4:08 ` Troy Benjegerdes [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-02-05 20:16 Woodruff, Robert J
2004-02-05 21:54 ` Greg KH
2004-02-06 23:20   ` Jamie Lokier
2004-02-05 19:44 [Infiniband-general] Getting an Infiniband access layer in the Linux kernel Tillier, Fabian
2004-02-05 20:16 ` Greg KH
2004-02-05 19:38 [Infiniband-general] Getting an Infiniband access layer in the linux kernel King, Steven R
2004-02-05 21:51 ` Greg KH
2004-02-05 19:31 Raj, Ashok
     [not found] <33561BB7A415E04FBDC339D5E149C6E26C38FA@orsmsx405.jf.intel.com>
2004-02-05 18:55 ` Greg KH
2004-02-05 18:34 Raj, Ashok
2004-02-05 18:31 [Infiniband-general] Getting an Infiniband access layer in the Linux kernel Tillier, Fabian
2004-02-05 18:40 ` Greg KH
2004-02-05 18:53 ` Randy.Dunlap
2004-02-07  2:54 ` Jamie Lokier
     [not found] <C1B7430B33A4B14F80D29B5126C5E94703262582@orsmsx401.jf.intel.com>
2004-02-05 18:09 ` [Infiniband-general] Getting an Infiniband access layer in the linux kernel Greg KH
2004-02-04  4:53 Woodruff, Robert J
2004-02-04  0:17 Woodruff, Robert J
2004-02-04  1:03 ` Greg KH
2004-02-03 16:45 Woodruff, Robert J
2004-02-04 11:26 ` Masanori ITOH
2004-02-02 23:58 Woodruff, Robert J
2004-02-03  0:56 ` Greg KH
2004-02-03  1:38 ` Masanori ITOH
2004-02-03 22:37 ` Troy Benjegerdes

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=20040204040834.GF11222@kalmia.hozed.org \
    --to=hozer@hozed.org \
    --cc=bill.magro@intel.com \
    --cc=greg@kroah.com \
    --cc=infiniband-general@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=woody@co.intel.com \
    --cc=woody@jf.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

all inboxes | Powered by JetHome®