From: Chet Murthy <chet-aZOuKsOsJu3MbYB6QlFGEg@public.gmane.org>
To: Sebastian Riemer
<sebastian.riemer-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
Cc: "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: OFED 1.5.4.1 on Ubuntu 10.04 with Mellanox cards?
Date: Fri, 22 Jun 2012 12:02:46 -0700 [thread overview]
Message-ID: <5754967.2RWSFZticM@twitter> (raw)
In-Reply-To: <4FE4304E.3090002-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
Sebastian,
Thank you for taking the time to explain these things! It's a little
confusing ....
> Here a simple list of matching code:
> OFED-1.5.4 ---> kernel 3.2.x
> OFED-1.5.4.1 ---> kernel 3.3.x
(1) Is there a more-exhaustive list of the right kernel to use with
each OFED release? I was going by the OFED docs (e.g. release notes),
which seemed to indicate that for 1.5.4.1, the "right" range of
kernels was (kernel.org: 2.6.30 - 3.1), and specific kernel versions
for various distros.
(2) I'm pretty familiar with adminstering Debian systems and building
debian packages, hacking their insides, alienizing, hacking that
process, etc.
(I -think- ;-) The only real question for me is, which versions, with
which patches, of the various bits, will work together with this RoCEE
card.
(3) I'm -not at all- familiar with the workflow/process that Debian
Developers use. For instance, I don't really understand what you men
below:
> But you'll have to ensure that the kernel code matches the OFED user
> space. The kernel stuff included in OFED doesn't support latest kernels
> and is based on an older code base (e.g. OFED 1.5.4 kernel stuff is
> based on 2.6.30).
Do you mean that the kernel-ib RPM in 1.5.4 is the code form the
2.6.30 kernel? But then the list below doesn't seem to make sense.
> Here a simple list of matching code:
> OFED-1.5.4 ---> kernel 3.2.x
> OFED-1.5.4.1 ---> kernel 3.3.x
(4) I think what you're saying here
> the trick is to check out the latest pkg-ofed source from debian SVN
> (svn://svn.debian.org/svn/pkg-ofed/) and to update the upstream source
> by merging the stuff by extracting the source RPMs or even better by
> importing the source directly from the git repos of the OFED user space.
> In the "debian" directory there are some patches e.g. which change some
> stuff in shell scripts for the dash. These need to be adopted.
is:
(a) check out the stuff from svn.debian.org
(b) pull source from the OFED repos user-space
(c) -copy- that (latest) OFED source into the tree I checked-out
from debian
(d) make sure that the patches in the debian directories apply
properly to the various shellscripts
(e) build debian packages per usual
And per your instructions above, I believe you're saying I should be
using a 3.3.x kernel?
Thanks,
--chet--
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-06-22 19:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-22 0:46 OFED 1.5.4.1 on Ubuntu 10.04 with Mellanox cards? Chet Murthy
2012-06-22 8:43 ` Sebastian Riemer
[not found] ` <4FE4304E.3090002-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2012-06-22 19:02 ` Chet Murthy [this message]
2012-06-25 9:35 ` Sebastian Riemer
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=5754967.2RWSFZticM@twitter \
--to=chet-azouksosju3mbyb6qlfgeg@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sebastian.riemer-EIkl63zCoXaH+58JC4qpiA@public.gmane.org \
/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