€•¿`      Œsphinx.addnodes”Œdocument”“”)”}”(Œ	rawsource”Œ ”Œchildren”]”(Œtranslations”ŒLanguagesNode”“”)”}”(hhh]”(h Œpending_xref”“”)”}”(hhh]”Œdocutils.nodes”ŒText”“”ŒChinese (Simplified)”…””}”Œparent”hsbaŒ
attributes”}”(Œids”]”Œclasses”]”Œnames”]”Œdupnames”]”Œbackrefs”]”Œ	refdomain”Œstd”Œreftype”Œdoc”Œ	reftarget”Œ'/translations/zh_CN/infiniband/user_mad”Œmodname”NŒ	classname”NŒrefexplicit”ˆuŒtagname”hhhubh)”}”(hhh]”hŒChinese (Traditional)”…””}”hh2sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ'/translations/zh_TW/infiniband/user_mad”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒItalian”…””}”hhFsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ'/translations/it_IT/infiniband/user_mad”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒJapanese”…””}”hhZsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ'/translations/ja_JP/infiniband/user_mad”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒKorean”…””}”hhnsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ'/translations/ko_KR/infiniband/user_mad”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒSpanish”…””}”hh‚sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ'/translations/sp_SP/infiniband/user_mad”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubeh}”(h]”h ]”h"]”h$]”h&]”Œcurrent_language”ŒEnglish”uh1h
hhŒ	_document”hŒsource”NŒline”NubhŒsection”“”)”}”(hhh]”(hŒtitle”“”)”}”(hŒUserspace MAD access”h]”hŒUserspace MAD access”…””}”(hh¨hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hh£hžhhŸŒA/var/lib/git/docbuild/linux/Documentation/infiniband/user_mad.rst”h Kubh¢)”}”(hhh]”(h§)”}”(hŒDevice files”h]”hŒDevice files”…””}”(hhºhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hh·hžhhŸh¶h KubhŒblock_quote”“”)”}”(hŒëEach port of each InfiniBand device has a "umad" device and an
"issm" device attached.  For example, a two-port HCA will have two
umad devices and two issm devices, while a switch will have one
device of each type (for switch port 0).
”h]”hŒ	paragraph”“”)”}”(hŒêEach port of each InfiniBand device has a "umad" device and an
"issm" device attached.  For example, a two-port HCA will have two
umad devices and two issm devices, while a switch will have one
device of each type (for switch port 0).”h]”hŒòEach port of each InfiniBand device has a â€œumadâ€ device and an
â€œissmâ€ device attached.  For example, a two-port HCA will have two
umad devices and two issm devices, while a switch will have one
device of each type (for switch port 0).”…””}”(hhÐhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h KhhÊubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h Khh·hžhubeh}”(h]”Œdevice-files”ah ]”h"]”Œdevice files”ah$]”h&]”uh1h¡hh£hžhhŸh¶h Kubh¢)”}”(hhh]”(h§)”}”(hŒCreating MAD agents”h]”hŒCreating MAD agents”…””}”(hhïhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hhìhžhhŸh¶h KubhÉ)”}”(hX‡  A MAD agent can be created by filling in a struct ib_user_mad_reg_req
and then calling the IB_USER_MAD_REGISTER_AGENT ioctl on a file
descriptor for the appropriate device file.  If the registration
request succeeds, a 32-bit id will be returned in the structure.
For example::

      struct ib_user_mad_reg_req req = { /* ... */ };
      ret = ioctl(fd, IB_USER_MAD_REGISTER_AGENT, (char *) &req);
      if (!ret)
              my_agent = req.id;
      else
              perror("agent register");

Agents can be unregistered with the IB_USER_MAD_UNREGISTER_AGENT
ioctl.  Also, all agents registered through a file descriptor will
be unregistered when the descriptor is closed.

2014
     a new registration ioctl is now provided which allows additional
     fields to be provided during registration.
     Users of this registration call are implicitly setting the use of
     pkey_index (see below).
”h]”(hÏ)”}”(hX  A MAD agent can be created by filling in a struct ib_user_mad_reg_req
and then calling the IB_USER_MAD_REGISTER_AGENT ioctl on a file
descriptor for the appropriate device file.  If the registration
request succeeds, a 32-bit id will be returned in the structure.
For example::”h]”hX  A MAD agent can be created by filling in a struct ib_user_mad_reg_req
and then calling the IB_USER_MAD_REGISTER_AGENT ioctl on a file
descriptor for the appropriate device file.  If the registration
request succeeds, a 32-bit id will be returned in the structure.
For example:”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h KhhýubhŒliteral_block”“”)”}”(hŒ·struct ib_user_mad_reg_req req = { /* ... */ };
ret = ioctl(fd, IB_USER_MAD_REGISTER_AGENT, (char *) &req);
if (!ret)
        my_agent = req.id;
else
        perror("agent register");”h]”hŒ·struct ib_user_mad_reg_req req = { /* ... */ };
ret = ioctl(fd, IB_USER_MAD_REGISTER_AGENT, (char *) &req);
if (!ret)
        my_agent = req.id;
else
        perror("agent register");”…””}”hj  sbah}”(h]”h ]”h"]”h$]”h&]”Œ	xml:space”Œpreserve”uh1j  hŸh¶h KhhýubhÏ)”}”(hŒ²Agents can be unregistered with the IB_USER_MAD_UNREGISTER_AGENT
ioctl.  Also, all agents registered through a file descriptor will
be unregistered when the descriptor is closed.”h]”hŒ²Agents can be unregistered with the IB_USER_MAD_UNREGISTER_AGENT
ioctl.  Also, all agents registered through a file descriptor will
be unregistered when the descriptor is closed.”…””}”(hj!  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h KhhýubhŒdefinition_list”“”)”}”(hhh]”hŒdefinition_list_item”“”)”}”(hŒË2014
a new registration ioctl is now provided which allows additional
fields to be provided during registration.
Users of this registration call are implicitly setting the use of
pkey_index (see below).
”h]”(hŒterm”“”)”}”(hŒ2014”h]”hŒ2014”…””}”(hj<  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j:  hŸh¶h K%hj6  ubhŒ
definition”“”)”}”(hhh]”hÏ)”}”(hŒÅa new registration ioctl is now provided which allows additional
fields to be provided during registration.
Users of this registration call are implicitly setting the use of
pkey_index (see below).”h]”hŒÅa new registration ioctl is now provided which allows additional
fields to be provided during registration.
Users of this registration call are implicitly setting the use of
pkey_index (see below).”…””}”(hjO  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h K"hjL  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jJ  hj6  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j4  hŸh¶h K%hj1  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j/  hhýubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h Khhìhžhubeh}”(h]”Œcreating-mad-agents”ah ]”h"]”Œcreating mad agents”ah$]”h&]”uh1h¡hh£hžhhŸh¶h Kubh¢)”}”(hhh]”(h§)”}”(hŒReceiving MADs”h]”hŒReceiving MADs”…””}”(hj€  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hj}  hžhhŸh¶h K(ubhÉ)”}”(hXŠ  MADs are received using read().  The receive side now supports
RMPP. The buffer passed to read() must be at least one
struct ib_user_mad + 256 bytes. For example:

If the buffer passed is not large enough to hold the received
MAD (RMPP), the errno is set to ENOSPC and the length of the
buffer needed is set in mad.length.

Example for normal MAD (non RMPP) reads::

      struct ib_user_mad *mad;
      mad = malloc(sizeof *mad + 256);
      ret = read(fd, mad, sizeof *mad + 256);
      if (ret != sizeof mad + 256) {
              perror("read");
              free(mad);
      }

Example for RMPP reads::

      struct ib_user_mad *mad;
      mad = malloc(sizeof *mad + 256);
      ret = read(fd, mad, sizeof *mad + 256);
      if (ret == -ENOSPC)) {
              length = mad.length;
              free(mad);
              mad = malloc(sizeof *mad + length);
              ret = read(fd, mad, sizeof *mad + length);
      }
      if (ret < 0) {
              perror("read");
              free(mad);
      }

In addition to the actual MAD contents, the other struct ib_user_mad
fields will be filled in with information on the received MAD.  For
example, the remote LID will be in mad.lid.

If a send times out, a receive will be generated with mad.status set
to ETIMEDOUT.  Otherwise when a MAD has been successfully received,
mad.status will be 0.

poll()/select() may be used to wait until a MAD can be read.
”h]”(hÏ)”}”(hŒ¢MADs are received using read().  The receive side now supports
RMPP. The buffer passed to read() must be at least one
struct ib_user_mad + 256 bytes. For example:”h]”hŒ¢MADs are received using read().  The receive side now supports
RMPP. The buffer passed to read() must be at least one
struct ib_user_mad + 256 bytes. For example:”…””}”(hj’  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h K*hjŽ  ubhÏ)”}”(hŒžIf the buffer passed is not large enough to hold the received
MAD (RMPP), the errno is set to ENOSPC and the length of the
buffer needed is set in mad.length.”h]”hŒžIf the buffer passed is not large enough to hold the received
MAD (RMPP), the errno is set to ENOSPC and the length of the
buffer needed is set in mad.length.”…””}”(hj   hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h K.hjŽ  ubhÏ)”}”(hŒ)Example for normal MAD (non RMPP) reads::”h]”hŒ(Example for normal MAD (non RMPP) reads:”…””}”(hj®  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h K2hjŽ  ubj  )”}”(hŒ­struct ib_user_mad *mad;
mad = malloc(sizeof *mad + 256);
ret = read(fd, mad, sizeof *mad + 256);
if (ret != sizeof mad + 256) {
        perror("read");
        free(mad);
}”h]”hŒ­struct ib_user_mad *mad;
mad = malloc(sizeof *mad + 256);
ret = read(fd, mad, sizeof *mad + 256);
if (ret != sizeof mad + 256) {
        perror("read");
        free(mad);
}”…””}”hj¼  sbah}”(h]”h ]”h"]”h$]”h&]”j  j   uh1j  hŸh¶h K4hjŽ  ubhÏ)”}”(hŒExample for RMPP reads::”h]”hŒExample for RMPP reads:”…””}”(hjÊ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h K<hjŽ  ubj  )”}”(hXE  struct ib_user_mad *mad;
mad = malloc(sizeof *mad + 256);
ret = read(fd, mad, sizeof *mad + 256);
if (ret == -ENOSPC)) {
        length = mad.length;
        free(mad);
        mad = malloc(sizeof *mad + length);
        ret = read(fd, mad, sizeof *mad + length);
}
if (ret < 0) {
        perror("read");
        free(mad);
}”h]”hXE  struct ib_user_mad *mad;
mad = malloc(sizeof *mad + 256);
ret = read(fd, mad, sizeof *mad + 256);
if (ret == -ENOSPC)) {
        length = mad.length;
        free(mad);
        mad = malloc(sizeof *mad + length);
        ret = read(fd, mad, sizeof *mad + length);
}
if (ret < 0) {
        perror("read");
        free(mad);
}”…””}”hjØ  sbah}”(h]”h ]”h"]”h$]”h&]”j  j   uh1j  hŸh¶h K>hjŽ  ubhÏ)”}”(hŒ´In addition to the actual MAD contents, the other struct ib_user_mad
fields will be filled in with information on the received MAD.  For
example, the remote LID will be in mad.lid.”h]”hŒ´In addition to the actual MAD contents, the other struct ib_user_mad
fields will be filled in with information on the received MAD.  For
example, the remote LID will be in mad.lid.”…””}”(hjæ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h KLhjŽ  ubhÏ)”}”(hŒžIf a send times out, a receive will be generated with mad.status set
to ETIMEDOUT.  Otherwise when a MAD has been successfully received,
mad.status will be 0.”h]”hŒžIf a send times out, a receive will be generated with mad.status set
to ETIMEDOUT.  Otherwise when a MAD has been successfully received,
mad.status will be 0.”…””}”(hjô  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h KPhjŽ  ubhÏ)”}”(hŒ<poll()/select() may be used to wait until a MAD can be read.”h]”hŒ<poll()/select() may be used to wait until a MAD can be read.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h KThjŽ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K*hj}  hžhubeh}”(h]”Œreceiving-mads”ah ]”h"]”Œreceiving mads”ah$]”h&]”uh1h¡hh£hžhhŸh¶h K(ubh¢)”}”(hhh]”(h§)”}”(hŒSending MADs”h]”hŒSending MADs”…””}”(hj!  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hj  hžhhŸh¶h KWubhÉ)”}”(hX  MADs are sent using write().  The agent ID for sending should be
filled into the id field of the MAD, the destination LID should be
filled into the lid field, and so on.  The send side does support
RMPP so arbitrary length MAD can be sent. For example::

      struct ib_user_mad *mad;

      mad = malloc(sizeof *mad + mad_length);

      /* fill in mad->data */

      mad->hdr.id  = my_agent;        /* req.id from agent registration */
      mad->hdr.lid = my_dest;         /* in network byte order... */
      /* etc. */

      ret = write(fd, &mad, sizeof *mad + mad_length);
      if (ret != sizeof *mad + mad_length)
              perror("write");
”h]”(hÏ)”}”(hŒýMADs are sent using write().  The agent ID for sending should be
filled into the id field of the MAD, the destination LID should be
filled into the lid field, and so on.  The send side does support
RMPP so arbitrary length MAD can be sent. For example::”h]”hŒüMADs are sent using write().  The agent ID for sending should be
filled into the id field of the MAD, the destination LID should be
filled into the lid field, and so on.  The send side does support
RMPP so arbitrary length MAD can be sent. For example:”…””}”(hj3  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h KYhj/  ubj  )”}”(hXZ  struct ib_user_mad *mad;

mad = malloc(sizeof *mad + mad_length);

/* fill in mad->data */

mad->hdr.id  = my_agent;        /* req.id from agent registration */
mad->hdr.lid = my_dest;         /* in network byte order... */
/* etc. */

ret = write(fd, &mad, sizeof *mad + mad_length);
if (ret != sizeof *mad + mad_length)
        perror("write");”h]”hXZ  struct ib_user_mad *mad;

mad = malloc(sizeof *mad + mad_length);

/* fill in mad->data */

mad->hdr.id  = my_agent;        /* req.id from agent registration */
mad->hdr.lid = my_dest;         /* in network byte order... */
/* etc. */

ret = write(fd, &mad, sizeof *mad + mad_length);
if (ret != sizeof *mad + mad_length)
        perror("write");”…””}”hjA  sbah}”(h]”h ]”h"]”h$]”h&]”j  j   uh1j  hŸh¶h K^hj/  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h KYhj  hžhubeh}”(h]”Œsending-mads”ah ]”h"]”Œsending mads”ah$]”h&]”uh1h¡hh£hžhhŸh¶h KWubh¢)”}”(hhh]”(h§)”}”(hŒTransaction IDs”h]”hŒTransaction IDs”…””}”(hj`  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hj]  hžhhŸh¶h KmubhÉ)”}”(hX1  Users of the umad devices can use the lower 32 bits of the
transaction ID field (that is, the least significant half of the
field in network byte order) in MADs being sent to match
request/response pairs.  The upper 32 bits are reserved for use by
the kernel and will be overwritten before a MAD is sent.
”h]”hÏ)”}”(hX0  Users of the umad devices can use the lower 32 bits of the
transaction ID field (that is, the least significant half of the
field in network byte order) in MADs being sent to match
request/response pairs.  The upper 32 bits are reserved for use by
the kernel and will be overwritten before a MAD is sent.”h]”hX0  Users of the umad devices can use the lower 32 bits of the
transaction ID field (that is, the least significant half of the
field in network byte order) in MADs being sent to match
request/response pairs.  The upper 32 bits are reserved for use by
the kernel and will be overwritten before a MAD is sent.”…””}”(hjr  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h Kohjn  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h Kohj]  hžhubeh}”(h]”Œtransaction-ids”ah ]”h"]”Œtransaction ids”ah$]”h&]”uh1h¡hh£hžhhŸh¶h Kmubh¢)”}”(hhh]”(h§)”}”(hŒP_Key Index Handling”h]”hŒP_Key Index Handling”…””}”(hj‘  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjŽ  hžhhŸh¶h KvubhÉ)”}”(hX¨  The old ib_umad interface did not allow setting the P_Key index for
MADs that are sent and did not provide a way for obtaining the P_Key
index of received MADs.  A new layout for struct ib_user_mad_hdr
with a pkey_index member has been defined; however, to preserve binary
compatibility with older applications, this new layout will not be used
unless one of IB_USER_MAD_ENABLE_PKEY or IB_USER_MAD_REGISTER_AGENT2 ioctl's
are called before a file descriptor is used for anything else.

In September 2008, the IB_USER_MAD_ABI_VERSION will be incremented
to 6, the new layout of struct ib_user_mad_hdr will be used by
default, and the IB_USER_MAD_ENABLE_PKEY ioctl will be removed.
”h]”(hÏ)”}”(hXä  The old ib_umad interface did not allow setting the P_Key index for
MADs that are sent and did not provide a way for obtaining the P_Key
index of received MADs.  A new layout for struct ib_user_mad_hdr
with a pkey_index member has been defined; however, to preserve binary
compatibility with older applications, this new layout will not be used
unless one of IB_USER_MAD_ENABLE_PKEY or IB_USER_MAD_REGISTER_AGENT2 ioctl's
are called before a file descriptor is used for anything else.”h]”hXæ  The old ib_umad interface did not allow setting the P_Key index for
MADs that are sent and did not provide a way for obtaining the P_Key
index of received MADs.  A new layout for struct ib_user_mad_hdr
with a pkey_index member has been defined; however, to preserve binary
compatibility with older applications, this new layout will not be used
unless one of IB_USER_MAD_ENABLE_PKEY or IB_USER_MAD_REGISTER_AGENT2 ioctlâ€™s
are called before a file descriptor is used for anything else.”…””}”(hj£  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h KxhjŸ  ubhÏ)”}”(hŒÁIn September 2008, the IB_USER_MAD_ABI_VERSION will be incremented
to 6, the new layout of struct ib_user_mad_hdr will be used by
default, and the IB_USER_MAD_ENABLE_PKEY ioctl will be removed.”h]”hŒÁIn September 2008, the IB_USER_MAD_ABI_VERSION will be incremented
to 6, the new layout of struct ib_user_mad_hdr will be used by
default, and the IB_USER_MAD_ENABLE_PKEY ioctl will be removed.”…””}”(hj±  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h K€hjŸ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h KxhjŽ  hžhubeh}”(h]”Œp-key-index-handling”ah ]”h"]”Œp_key index handling”ah$]”h&]”uh1h¡hh£hžhhŸh¶h Kvubh¢)”}”(hhh]”(h§)”}”(hŒSetting IsSM Capability Bit”h]”hŒSetting IsSM Capability Bit”…””}”(hjÐ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjÍ  hžhhŸh¶h K…ubhÉ)”}”(hX“  To set the IsSM capability bit for a port, simply open the
corresponding issm device file.  If the IsSM bit is already set,
then the open call will block until the bit is cleared (or return
immediately with errno set to EAGAIN if the O_NONBLOCK flag is
passed to open()).  The IsSM bit will be cleared when the issm file
is closed.  No read, write or other operations can be performed on
the issm file.
”h]”hÏ)”}”(hX’  To set the IsSM capability bit for a port, simply open the
corresponding issm device file.  If the IsSM bit is already set,
then the open call will block until the bit is cleared (or return
immediately with errno set to EAGAIN if the O_NONBLOCK flag is
passed to open()).  The IsSM bit will be cleared when the issm file
is closed.  No read, write or other operations can be performed on
the issm file.”h]”hX’  To set the IsSM capability bit for a port, simply open the
corresponding issm device file.  If the IsSM bit is already set,
then the open call will block until the bit is cleared (or return
immediately with errno set to EAGAIN if the O_NONBLOCK flag is
passed to open()).  The IsSM bit will be cleared when the issm file
is closed.  No read, write or other operations can be performed on
the issm file.”…””}”(hjâ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h K‡hjÞ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K‡hjÍ  hžhubeh}”(h]”Œsetting-issm-capability-bit”ah ]”h"]”Œsetting issm capability bit”ah$]”h&]”uh1h¡hh£hžhhŸh¶h K…ubh¢)”}”(hhh]”(h§)”}”(hŒ
/dev files”h]”hŒ
/dev files”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjþ  hžhhŸh¶h KubhÉ)”}”(hX6  To create the appropriate character device files automatically with
udev, a rule like::

  KERNEL=="umad*", NAME="infiniband/%k"
  KERNEL=="issm*", NAME="infiniband/%k"

can be used.  This will create device nodes named::

  /dev/infiniband/umad0
  /dev/infiniband/issm0

for the first port, and so on.  The InfiniBand device and port
associated with these devices can be determined from the files::

  /sys/class/infiniband_mad/umad0/ibdev
  /sys/class/infiniband_mad/umad0/port

and::

  /sys/class/infiniband_mad/issm0/ibdev
  /sys/class/infiniband_mad/issm0/port”h]”(hÏ)”}”(hŒWTo create the appropriate character device files automatically with
udev, a rule like::”h]”hŒVTo create the appropriate character device files automatically with
udev, a rule like:”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h K’hj  ubj  )”}”(hŒKKERNEL=="umad*", NAME="infiniband/%k"
KERNEL=="issm*", NAME="infiniband/%k"”h]”hŒKKERNEL=="umad*", NAME="infiniband/%k"
KERNEL=="issm*", NAME="infiniband/%k"”…””}”hj!  sbah}”(h]”h ]”h"]”h$]”h&]”j  j   uh1j  hŸh¶h K•hj  ubhÏ)”}”(hŒ3can be used.  This will create device nodes named::”h]”hŒ2can be used.  This will create device nodes named:”…””}”(hj/  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h K˜hj  ubj  )”}”(hŒ+/dev/infiniband/umad0
/dev/infiniband/issm0”h]”hŒ+/dev/infiniband/umad0
/dev/infiniband/issm0”…””}”hj=  sbah}”(h]”h ]”h"]”h$]”h&]”j  j   uh1j  hŸh¶h Kšhj  ubhÏ)”}”(hŒfor the first port, and so on.  The InfiniBand device and port
associated with these devices can be determined from the files::”h]”hŒ~for the first port, and so on.  The InfiniBand device and port
associated with these devices can be determined from the files:”…””}”(hjK  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h Khj  ubj  )”}”(hŒJ/sys/class/infiniband_mad/umad0/ibdev
/sys/class/infiniband_mad/umad0/port”h]”hŒJ/sys/class/infiniband_mad/umad0/ibdev
/sys/class/infiniband_mad/umad0/port”…””}”hjY  sbah}”(h]”h ]”h"]”h$]”h&]”j  j   uh1j  hŸh¶h K hj  ubhÏ)”}”(hŒand::”h]”hŒand:”…””}”(hjg  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h K£hj  ubj  )”}”(hŒJ/sys/class/infiniband_mad/issm0/ibdev
/sys/class/infiniband_mad/issm0/port”h]”hŒJ/sys/class/infiniband_mad/issm0/ibdev
/sys/class/infiniband_mad/issm0/port”…””}”hju  sbah}”(h]”h ]”h"]”h$]”h&]”j  j   uh1j  hŸh¶h K¥hj  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K’hjþ  hžhubeh}”(h]”Œ	dev-files”ah ]”h"]”Œ
/dev files”ah$]”h&]”uh1h¡hh£hžhhŸh¶h Kubeh}”(h]”Œuserspace-mad-access”ah ]”h"]”Œuserspace mad access”ah$]”h&]”uh1h¡hhhžhhŸh¶h Kubeh}”(h]”h ]”h"]”h$]”h&]”Œsource”h¶uh1hŒcurrent_source”NŒcurrent_line”NŒsettings”Œdocutils.frontend”ŒValues”“”)”}”(h¦NŒ	generator”NŒ	datestamp”NŒsource_link”NŒ
source_url”NŒtoc_backlinks”Œentry”Œfootnote_backlinks”KŒsectnum_xform”KŒstrip_comments”NŒstrip_elements_with_classes”NŒstrip_classes”NŒreport_level”KŒ
halt_level”KŒexit_status_level”KŒdebug”NŒwarning_stream”NŒ	traceback”ˆŒinput_encoding”Œ	utf-8-sig”Œinput_encoding_error_handler”Œstrict”Œoutput_encoding”Œutf-8”Œoutput_encoding_error_handler”j¼  Œerror_encoding”Œutf-8”Œerror_encoding_error_handler”Œbackslashreplace”Œlanguage_code”Œen”Œrecord_dependencies”NŒconfig”NŒ	id_prefix”hŒauto_id_prefix”Œid”Œdump_settings”NŒdump_internals”NŒdump_transforms”NŒdump_pseudo_xml”NŒexpose_internals”NŒstrict_visitor”NŒ_disable_config”NŒ_source”h¶Œ_destination”NŒ_config_files”]”Œ7/var/lib/git/docbuild/linux/Documentation/docutils.conf”aŒfile_insertion_enabled”ˆŒraw_enabled”KŒline_length_limit”M'Œpep_references”NŒpep_base_url”Œhttps://peps.python.org/”Œpep_file_url_template”Œpep-%04d”Œrfc_references”NŒrfc_base_url”Œ&https://datatracker.ietf.org/doc/html/”Œ	tab_width”KŒtrim_footnote_reference_space”‰Œsyntax_highlight”Œlong”Œsmart_quotes”ˆŒsmartquotes_locales”]”Œcharacter_level_inline_markup”‰Œdoctitle_xform”‰Œdocinfo_xform”KŒsectsubtitle_xform”‰Œimage_loading”Œlink”Œembed_stylesheet”‰Œcloak_email_addresses”ˆŒsection_self_link”‰Œenv”NubŒreporter”NŒindirect_targets”]”Œsubstitution_defs”}”Œsubstitution_names”}”Œrefnames”}”Œrefids”}”Œnameids”}”(j–  j“  héhæjz  jw  j  j  jZ  jW  j‹  jˆ  jÊ  jÇ  jû  jø  jŽ  j‹  uŒ	nametypes”}”(j–  ‰hé‰jz  ‰j  ‰jZ  ‰j‹  ‰jÊ  ‰jû  ‰jŽ  ‰uh}”(j“  h£hæh·jw  hìj  j}  jW  j  jˆ  j]  jÇ  jŽ  jø  jÍ  j‹  jþ  uŒfootnote_refs”}”Œcitation_refs”}”Œautofootnotes”]”Œautofootnote_refs”]”Œsymbol_footnotes”]”Œsymbol_footnote_refs”]”Œ	footnotes”]”Œ	citations”]”Œautofootnote_start”KŒsymbol_footnote_start”K Œ
id_counter”Œcollections”ŒCounter”“”}”…”R”Œparse_messages”]”Œtransform_messages”]”Œtransformer”NŒinclude_log”]”Œ
decoration”Nhžhub.