Search the web
Sign In
New User? Sign Up
dat-discussions · DAT Collaborative
? Already a member? Sign in to Yahoo!

Yahoo! Groups Tips

Did you know...
Hear how Yahoo! Groups has changed the lives of others. Take me there.

Best of Y! Groups

   Check them out and nominate your group.
Having problems with message search? Fill out this form to ensure your group is one of the first to be migrated to the new message search system.

Messages

  Messages Help
Advanced
RFC: DAT 1.2 and 2.0 library build and installation   Message List  
Reply | Forward Message #4158 of 4166 |
RE: [dat-discussions] RFC: DAT 1.2 and 2.0 library build and installation

My understanding is that the RFC just allows the coexistence of different libraries but the consumers are still responsible of handling the difference between versions.
 
Thanks,
 
Jianxin


From: dat-discussions@yahoogroups.com [mailto:dat-discussions@yahoogroups.com] On Behalf Of Kanevsky, Arkady
Sent: Friday, September 21, 2007 1:45 PM
To: dat-discussions@yahoogroups.com
Cc: Lentini, James
Subject: RE: [dat-discussions] RFC: DAT 1.2 and 2.0 library build and installation

Then I do not see any problem with multiple libraries.
How do you handle the change of signatures between 1.2 and 2.0
in redirection table?
Thanks,
 

Arkady Kanevsky                       email: arkady@...

Network Appliance Inc.               phone: 781-768-5395

1601 Trapelo Rd. - Suite 16.        Fax: 781-895-1195

Waltham, MA 02451                   central phone: 781-768-5300

 


From: Davis, Arlin R [mailto:arlin.r.davis@...]
Sent: Thursday, September 20, 2007 1:30 PM
To: dat-discussions@yahoogroups.com
Cc: Lentini, James
Subject: RE: [dat-discussions] RFC: DAT 1.2 and 2.0 library build and installation

I am actually thinking about sticking with one dat.conf.

For example, OFED would change to look like the following:

#

# DAT 1.2 and 2.0 configuration file

#

# Each entry should have the following fields:

#

# <ia_name> <api_version> <threadsafety> <default> <lib_path> \

#           <provider_version> <ia_params> <platform_params>

#

# For the uDAPL cma provder, specify <ia_params> as one of the following:

#       network address, network hostname, or netdev name and 0 for port

#

# Simple (OpenIB-cma) default with netdev name provided first on list

# to enable use of same dat.conf version on all nodes

#

# Add examples for multiple interfaces and IPoIB HA fail over, and bonding

#

OpenIB-cma u1.2 nonthreadsafe default libdaplcma.so.1 dapl.1.2 "ib0 0" ""

OpenIB-cma-1 u1.2 nonthreadsafe default libdaplcma.so.1 dapl.1.2 "ib1 0" ""

OpenIB-cma-2 u1.2 nonthreadsafe default libdaplcma.so.1 dapl.1.2 "ib2 0" ""

OpenIB-cma-3 u1.2 nonthreadsafe default libdaplcma.so.1 dapl.1.2 "ib3 0" ""

OpenIB-bond u1.2 nonthreadsafe default libdaplcma.so.1 dapl.1.2 "bond0 0" ""

OpenIB-2-cma u2.0 nonthreadsafe default libdaplcma.so.2 dapl.2.0 "ib0 0" ""

OpenIB-2-cma-1 u2.0 nonthreadsafe default libdaplcma.so.2 dapl.2.0 "ib1 0" ""

OpenIB-2-cma-2 u2.0 nonthreadsafe default libdaplcma.so.2 dapl.2.0 "ib2 0" ""

OpenIB-2-cma-3 u2.0 nonthreadsafe default libdaplcma.so.2 dapl.2.0 "ib3 0" ""

OpenIB-2-bond u2.0 nonthreadsafe default libdaplcma.so.2 dapl.2.0 "bond0 0" ""


From: dat-discussions@yahoogroups.com [mailto:dat-discussions@yahoogroups.com] On Behalf Of Kanevsky, Arkady
Sent: Tuesday, September 18, 2007 5:47 AM
To: dat-discussions@yahoogroups.com
Cc: Lentini, James
Subject: RE: [dat-discussions] RFC: DAT 1.2 and 2.0 library build and installation

Arlin,

how do two proposed way impact configuration files?

Thanks,

Arkady Kanevsky                       email: arkady@netapp.com

Network Appliance Inc.               phone: 781-768-5395

1601 Trapelo Rd. - Suite 16.        Fax: 781-895-1195

Waltham, MA 02451                   central phone: 781-768-5300


From: Davis, Arlin R [mailto:arlin.r.davis@intel.com]
Sent: Monday, September 17, 2007 5:29 PM
To: dat-discussions@yahoogroups.com
Cc: Lentini, James
Subject: [dat-discussions] RFC: DAT 1.2 and 2.0 library build and installation

I am thinking about allowing coexistence of 1.2 and 2.0 libraries for the next release. This will insure that we continue to support 1.2 providers while new providers needing 2.0 features can also install and run on the same system. Does anyone see problems with this or have any suggestions other then separate naming conventions? I am thinking we will have to build/install 2.0 as dat2.conf, libdat2.so, libdapl2.so, and the development package as /usr/include/dat2/include.

comments?

Thanks,

-arlin



Wed Sep 26, 2007 4:07 am

xjx1998
Offline Offline
Send Email Send Email

Forward
Message #4158 of 4166 |
Expand Messages Author Sort by Date

I am thinking about allowing coexistence of 1.2 and 2.0 libraries for the next release. This will insure that we continue to support 1.2 providers while new...
Davis, Arlin R
ardyamhill
Offline Send Email
Sep 17, 2007
9:31 pm

I think allowing co-existence is very important. Otherwise, commercial software will not be able to gracefully transition from 1.2 to 2.0 over time. --Bill ...
Magro, Bill
bill.magro@...
Send Email
Sep 17, 2007
10:24 pm

Arlin, how do two proposed way impact configuration files? Thanks, Arkady Kanevsky email: arkady@... Network Appliance Inc....
Kanevsky, Arkady
arkadynetappcom
Offline Send Email
Sep 18, 2007
12:50 pm

I am actually thinking about sticking with one dat.conf. For example, OFED would change to look like the following: # # DAT 1.2 and 2.0 configuration file # #...
Davis, Arlin R
ardyamhill
Offline Send Email
Sep 20, 2007
5:32 pm

Then I do not see any problem with multiple libraries. How do you handle the change of signatures between 1.2 and 2.0 in redirection table? Thanks, Arkady...
Kanevsky, Arkady
arkadynetappcom
Offline Send Email
Sep 21, 2007
6:46 pm

My understanding is that the RFC just allows the coexistence of different libraries but the consumers are still responsible of handling the difference between...
Xiong, Jianxin
xjx1998
Offline Send Email
Sep 26, 2007
4:18 am
Advanced

Copyright © 2009 Yahoo! Inc. All rights reserved.
Privacy Policy - Terms of Service - Guidelines - Help