<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:v =
"urn:schemas-microsoft-com:vml" xmlns:o =
"urn:schemas-microsoft-com:office:office" xmlns:w =
"urn:schemas-microsoft-com:office:word"><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.3243" name=GENERATOR><!--[if !mso]>
<STYLE>v\:* {
BEHAVIOR: url(#default#VML)
}
o\:* {
BEHAVIOR: url(#default#VML)
}
w\:* {
BEHAVIOR: url(#default#VML)
}
.shape {
BEHAVIOR: url(#default#VML)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
font-family: Tahoma;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
COLOR: blue; TEXT-DECORATION: underline
}
SPAN.EmailStyle18 {
COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal-reply
}
DIV.Section1 {
page: Section1
}
</STYLE>
</HEAD>
<BODY lang=EN-US vLink=blue link=blue>
<DIV><SPAN class=659095213-18012009><FONT face=Arial color=#0000ff size=2>After
first look: why did you put the list of the created devices into Globals (and
not, say, FDO) ?</FONT></SPAN></DIV>
<DIV><SPAN class=659095213-18012009><FONT face=Arial color=#0000ff size=2>How it
will work for multi-home machine ? (several HCA cards)</FONT></SPAN></DIV>
<DIV><SPAN class=659095213-18012009><FONT face=Arial color=#0000ff size=2>Would
anybode like to check it for various partition keys ?</FONT></SPAN></DIV><BR>
<BLOCKQUOTE dir=ltr
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> ofw-bounces@lists.openfabrics.org
[mailto:ofw-bounces@lists.openfabrics.org] <B>On Behalf Of </B>James
Yang<BR><B>Sent:</B> Tuesday, January 06, 2009 10:11 PM<BR><B>To:</B> Deepak
Gupta; Fab Tillier<BR><B>Cc:</B> ofw@lists.openfabrics.org<BR><B>Subject:</B>
RE: [ofw] Expose a vendor defined device in ibbus?<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=Section1>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Hi,<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Please review the
patch to create user defined devices by reading from registry. By default
there is only one IpoIB device enabled in mlx4_hca.inx file. This patch will
only work for ConnectX.<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">The paritition key if
set to default to FFFF, I didn’t test on other value. And the Ioctl part to
add partition key may also need to be verified.<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Thanks,<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">James<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<DIV>
<DIV class=MsoNormal style="TEXT-ALIGN: center" align=center><FONT
face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt">
<HR tabIndex=-1 align=center width="100%" SIZE=2>
</SPAN></FONT></DIV>
<P class=MsoNormal><B><FONT face=Tahoma size=2><SPAN
style="FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">From:</SPAN></FONT></B><FONT
face=Tahoma size=2><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">
mailmeatdkg@gmail.com [mailto:mailmeatdkg@gmail.com] <B><SPAN
style="FONT-WEIGHT: bold">On Behalf Of </SPAN></B>Deepak Gupta<BR><B><SPAN
style="FONT-WEIGHT: bold">Sent:</SPAN></B> Monday, January 05, 2009 10:51
PM<BR><B><SPAN style="FONT-WEIGHT: bold">To:</SPAN></B> Fab
Tillier<BR><B><SPAN style="FONT-WEIGHT: bold">Cc:</SPAN></B> Tzachi Dar; James
Yang; ofw@lists.openfabrics.org<BR><B><SPAN
style="FONT-WEIGHT: bold">Subject:</SPAN></B> Re: [ofw] Expose a vendor
defined device in ibbus?</SPAN></FONT><o:p></o:p></P></DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt">Have a gr8 New Year to all the members!!!.<BR><BR>Do
you we any updates on "<SPAN class=vrhwid><SPAN id=:6j>vendor defined device
in ibbus"?</SPAN><BR><BR><SPAN class=vrhwid>I wanted to create multiple vnic
interfaces irrespective of number of reachable IOCs.</SPAN><BR><BR><SPAN
class=vrhwid>Currently I am creating vnic child devices on "root"
bus.</SPAN><BR><SPAN class=vrhwid>Inside VNIC driver, I am looking for arrival
GUID_IB_AL_INTERFACE and hence contacting the IBAL.</SPAN><BR><SPAN
class=vrhwid>But since vnic devices are root enumerated, VNIC driver gets
loaded very earlier in boot phase (Before "Extended Base" group to which IB
Stack drivers belong) and hence VNIC device interfaces are not getting
initialized properly.</SPAN><BR><BR><SPAN class=vrhwid>If we are providing a
vendor defined device functionality in ibbus in near future, then it would be
worth for me to wait for it.</SPAN><BR><BR><SPAN class=vrhwid>Can any one
please comment on this.</SPAN><BR><BR><SPAN
class=vrhwid>Regards</SPAN><BR><SPAN
class=vrhwid>Deepak</SPAN><BR><BR><BR><o:p></o:p></SPAN></FONT></P></SPAN>
<DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt">On Mon, Dec 22, 2008 at 1:12 PM, Deepak Gupta <<A
href="mailto:deepak.gupta@qlogic.com">deepak.gupta@qlogic.com</A>>
wrote:<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt">All,<BR><BR>I came across one more question in my mind
which are I think is not clear to me after reading the whole thread.<BR><BR>In
new design being discussed:- <BR>Are we making sure that we can have more than
one child devices configured for the same IOC.<BR>Currently, there is one
child device created per IOC discovered.<BR><BR>Having more than one child
device configured for same IOC is a requirement if a user wants two different
ULP interfaces to be created on host side.<BR>Consider a case in which a host
is connected to a single IOC and IOC is connected to a ethernet network via
switch.<BR>If there are two different IP subnets then there is a requirement
of two different Ethernet interfaces on the host side too.<BR><BR>Please let
me know if you need more clarification of my question.<BR><BR>Regards<BR><FONT
color=#888888><SPAN
style="COLOR: #888888">Deepak</SPAN></FONT><o:p></o:p></SPAN></FONT></P>
<DIV>
<DIV>
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt"><FONT face="Times New Roman"
size=3><SPAN style="FONT-SIZE: 12pt"><o:p> </o:p></SPAN></FONT></P>
<DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt">On Sat, Dec 20, 2008 at 2:19 PM, Deepak Gupta <<A
href="mailto:deepak.gupta@qlogic.com"
target=_blank>deepak.gupta@qlogic.com</A>>
wrote:<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt"><FONT face="Times New Roman"
size=3><SPAN style="FONT-SIZE: 12pt">Please see
below.<BR><BR>Regards<BR>Deepak<o:p></o:p></SPAN></FONT></P>
<DIV>
<DIV>
<DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt">On Sat, Dec 20, 2008 at 12:42 AM, Fab Tillier <<A
href="mailto:ftillier@windows.microsoft.com"
target=_blank>ftillier@windows.microsoft.com</A>>
wrote:<o:p></o:p></SPAN></FONT></P>
<DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt">> On Wed, Dec 17, 2008 at 11:43 PM, Fab
Tillier<BR>> <<A href="mailto:ftillier@windows.microsoft.com"
target=_blank>ftillier@windows.microsoft.com</A>>
wrote:<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt"><FONT face="Times New Roman"
size=3><SPAN style="FONT-SIZE: 12pt">>> Are there other properties that
I have missed that are needed?<BR>><BR>> We need a way in which devices
created should be configured for<BR>> failovers ( ULPs like VNIC, SRP need
more configurable failovers).<BR>> Looking at IBAL's code it create the
devices based on the reachable<BR>> IOC's and thus failover's are possible
across the HCA/ports and not<BR>> across two different IOCs.<BR>> Users
can have a case in which two different IOCs connected to same<BR>> physical
network/storage (redundancy is provided for high availability)<BR>> and
want a failover across the IOCs.<o:p></o:p></SPAN></FONT></P></DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt">This would be done via LBFO for network devices, and
MPIO for storage devices. I think having the bus driver report a single
IOC that really maps to two IOCs on the fabric is asking for management
problems. Further, LBFO/MPIO can provide failover between different
device types, so the failover devices don't have to be identical
HW.<o:p></o:p></SPAN></FONT></P></DIV></DIV>
<DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt"><BR>I don't know about how MPIO works. But for
LBFO, BundleID param will have to be included in extended params then so
that user gets the freedom of bundling different failover
configurations.<BR> <o:p></o:p></SPAN></FONT></P></DIV>
<BLOCKQUOTE
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium none; PADDING-LEFT: 6pt; PADDING-BOTTOM: 0in; MARGIN-LEFT: 4.8pt; BORDER-LEFT: #cccccc 1pt solid; MARGIN-RIGHT: 0in; PADDING-TOP: 0in; BORDER-BOTTOM: medium none">
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt"><BR><FONT color=#888888><SPAN
style="COLOR: #888888"><BR>-Fab</SPAN></FONT><o:p></o:p></SPAN></FONT></P></BLOCKQUOTE></DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt"><o:p> </o:p></SPAN></FONT></P></DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt"><o:p> </o:p></SPAN></FONT></P></DIV></DIV></DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt"><o:p> </o:p></SPAN></FONT></P></DIV></BLOCKQUOTE></BODY></HTML>