On Tuesday 07 May 2013 07:36:52 Brian J. Murrell wrote:
On Tue, 2013-05-07 at 16:57 +0530, linux freaker wrote:
> I can try it once more but really I feel its painful.
It is, which is why we encourage people to use the I/B stack provided by
RedHat, already built into their kernel and the corresponding user-space
packages.
It seems that a lot of people (think they) need to install the Mellanox
I/B stack instead. Perhaps this is true for your (and everyone else's)
case, or perhaps not. I can't really tell, and am not really involved
closely enough in I/B to know.
But ultimately, I wonder why, given all of the apparent need for
whatever Mellanox does differently than the upstream OFED and/or RH I/B
stacks are doing, that these needs for the Mellanox stack are not being
pushed back into either OFED or the upstream kernel I/B stack. Life
really would be so much easier for so many people if it were.
Maybe if Mellanox hears from enough of their customers about the pain it
is to use their hardware they might try to get their stuff upstream.
b.
_______________________________________________
HPDD-discuss mailing list
HPDD-discuss(a)lists.01.org
https://lists.01.org/mailman/listinfo/hpdd-discuss
Totally agree with that. It would be nice to know why OFED [even the original
one as far as I understand] needs to change both the API and the ABI of half
kernel and why such change is not upstream if it is needed. Luckly with OFED
3.5 they are moving to a compat layer, so this will make life a little easier,
but still I don't see why you need a 4477 lines long perl script to install
OFED when it should just be a matter of yum install metapackage-name.
To that add that I see some missing feature from Mellanox version, like
NFSoRDMA.
Enrico