RE: [Infiniband-general] Getting an Infiniband access layer in theLinux kernel

[Hefty, Sean]

Personally, I'm amazed that professional developers have to discuss or
defend modular, portable code.

Once the code has been submitted, then specific implementation problems
can be dealt with.

- Sean


-----Original Message-----
From: Tillier, Fabian [mailto:ftillier@xxxxxxxxxxxxxxxx] 
Sent: Thursday, February 05, 2004 2:03 PM
To: Chris Friesen; Greg KH
Cc: Randy.Dunlap; Hefty, Sean; linux-kernel@xxxxxxxxxxxxxxx;
hozer@xxxxxxxxx; Woodruff, Robert J; Magro, Bill; woody@xxxxxxxxxxxx;
infiniband-general@xxxxxxxxxxxxxxxxxxxxx
Subject: RE: [Infiniband-general] Getting an Infiniband access layer in
theLinux kernel

That is absolutely correct.  In addition to portability between kernel
versions and operating systems, there is also portability between
user-mode and kernel-mode within a single release.

- Fab

-----Original Message-----
From: Chris Friesen [mailto:cfriesen@xxxxxxxxxxxxxxxxxx] 
Sent: Thursday, February 05, 2004 1:57 PM
To: Greg KH
Cc: Tillier, Fabian; Randy.Dunlap; sean.hefty@xxxxxxxxx;
linux-kernel@xxxxxxxxxxxxxxx; hozer@xxxxxxxxx; woody@xxxxxxxxxxxx;
bill.magro@xxxxxxxxx; woody@xxxxxxxxxxxx;
infiniband-general@xxxxxxxxxxxxxxxxxxxxx
Subject: Re: [Infiniband-general] Getting an Infiniband access layer in
theLinux kernel

Greg KH wrote:

> Basically, what is lacking in the current kernel locks that the
> infiniband project has to have in order to work properly.  We can work
> from there.

I think their point is that they want the core device driver code to be 
portable across kernel versions, and across different OS's other than 
linux--which basically requires some kind of abstraction layer.

Chris

-- 
Chris Friesen                    | MailStop: 043/33/F10
Nortel Networks                  | work: (613) 765-0557
3500 Carling Avenue              | fax:  (613) 765-2986
Nepean, ON K2H 8E9 Canada        | email: cfriesen@xxxxxxxxxxxxxxxxxx

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/