[ewg] EWG/OFED meeting agenda for today (May 15, 2012) - Meeting Minutes

Woodruff, Robert J robert.j.woodruff at intel.com
Thu May 17 12:11:04 PDT 2012


The decision was made to move the kernel version to 3.3 rather than 3.2
and thus the next OFED release will be called OFED-3.3 and is scheduled
to release at the end of July.

woody

-----Original Message-----
From: ewg-bounces at lists.openfabrics.org [mailto:ewg-bounces at lists.openfabrics.org] On Behalf Of Nikolova, Tatyana E
Sent: Thursday, May 17, 2012 12:09 PM
To: ewg at lists.openfabrics.org
Subject: Re: [ewg] EWG/OFED meeting agenda for today (May 15, 2012) - Meeting Minutes

Will there be OFED-3.2 GA and what is the date for it?

Thank you.
Tatyana

-----Original Message-----
From: ewg-bounces at lists.openfabrics.org [mailto:ewg-bounces at lists.openfabrics.org] On Behalf Of Steve Wise
Sent: Thursday, May 17, 2012 1:13 PM
To: ewg at lists.openfabrics.org
Subject: Re: [ewg] EWG/OFED meeting agenda for today (May 15, 2012) - Meeting Minutes

On 05/17/2012 11:43 AM, Woodruff, Robert J wrote:
> We discussed people's progress towards our goal of getting the initial
> backports for OFED-3.3 complete. The status is:
>
> NES driver: Patches have been submitted but have not yet been applied.
>
> Intel IB QIB Driver:
> 	SLES 11 SP2;  no backport patches were needed.
>      - RHEL 6.2  -- may need some backport patch(es), in progress
>      - 3.0, 3.1 and 3.2  kernels, in progress.
>      - we are still learning how all the pieces fit together, so we may have patches.
>      - still targeting month-end.
>
> Chelsio:
>
> the cxgb3/4 backports  are code-complete for 3.0, 3.1, and rhel6.2.
> - testing and code review under way
> - will submit these this week
>
> There was a question that we need to discuss more in our next meeting.
> It was what should we do if we find bugs in the upstream kernel code ?
> Will there be a way to apply bug fix patches to the OFED tree in addition
> To the backports ?

There is a way.  There are directories in the compat-rdma repository 
that get applied optionally with the admin_rdma.sh script:

linux-next-pending - these are patches you've submitted upstream but 
haven't been merged yet.

linux-next-cherry-picks - these are patches from upstream that we want 
in ofed but are too big or whatever to get pulled into the linux-stable 
tree.

crap - this directory holds patches that would never go upstream for 
whatever reason.

There are README files in each of these that explain their intended purpose.

And admin_rdma.sh allows pulling from them optionally:

[swise at build compat-rdma]$ ./scripts/admin_rdma.sh -?
Unexpected argument passed: -?
Usage: ./scripts/admin_rdma.sh [ refresh] [ --help | -h | -s | -n | -p | 
-c ]
    refresh - will update your all your patch offsets using quilt
         -s - get and apply pending-stable/ fixes purging old files there
         -n - apply the patches linux-next-cherry-picks directory
         -p - apply the patches on the linux-next-pending directory
         -c - apply the patches on the crap directory

Chelsio will have candidates for linux-next-cherry-picks up coming.


Steve.
_______________________________________________
ewg mailing list
ewg at lists.openfabrics.org
http://lists.openfabrics.org/cgi-bin/mailman/listinfo/ewg
_______________________________________________
ewg mailing list
ewg at lists.openfabrics.org
http://lists.openfabrics.org/cgi-bin/mailman/listinfo/ewg



More information about the ewg mailing list