€•ia      Œ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/admin-guide/aoe/aoe”Œ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/admin-guide/aoe/aoe”Œ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/admin-guide/aoe/aoe”Œ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/admin-guide/aoe/aoe”Œ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/admin-guide/aoe/aoe”Œ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/admin-guide/aoe/aoe”Œ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ŒIntroduction”h]”hŒIntroduction”…””}”(hh¨hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hh£hžhhŸŒA/var/lib/git/docbuild/linux/Documentation/admin-guide/aoe/aoe.rst”h KubhŒ	paragraph”“”)”}”(hŒ`ATA over Ethernet is a network protocol that provides simple access to
block storage on the LAN.”h]”hŒ`ATA over Ethernet is a network protocol that provides simple access to
block storage on the LAN.”…””}”(hh¹hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Khh£hžhubhŒblock_quote”“”)”}”(hŒ/http://support.coraid.com/documents/AoEr11.txt
”h]”h¸)”}”(hŒ.http://support.coraid.com/documents/AoEr11.txt”h]”hŒ	reference”“”)”}”(hhÏh]”hŒ.http://support.coraid.com/documents/AoEr11.txt”…””}”(hhÓhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”hÏuh1hÑhhÍubah}”(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žhubh¸)”}”(hŒ@The EtherDrive (R) HOWTO for 2.6 and 3.x kernels is found at ...”h]”hŒ@The EtherDrive (R) HOWTO for 2.6 and 3.x kernels is found at ...”…””}”(hhíhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K	hh£hžhubhÈ)”}”(hŒBhttp://support.coraid.com/support/linux/EtherDrive-2.6-HOWTO.html
”h]”h¸)”}”(hŒAhttp://support.coraid.com/support/linux/EtherDrive-2.6-HOWTO.html”h]”hÒ)”}”(hj  h]”hŒAhttp://support.coraid.com/support/linux/EtherDrive-2.6-HOWTO.html”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”j  uh1hÑhhÿubah}”(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žhubh¸)”}”(hŒ\It has many tips and hints!  Please see, especially, recommended
tunings for virtual memory:”h]”hŒ\It has many tips and hints!  Please see, especially, recommended
tunings for virtual memory:”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Khh£hžhubhÈ)”}”(hŒKhttp://support.coraid.com/support/linux/EtherDrive-2.6-HOWTO-5.html#ss5.19
”h]”h¸)”}”(hŒJhttp://support.coraid.com/support/linux/EtherDrive-2.6-HOWTO-5.html#ss5.19”h]”hÒ)”}”(hj1  h]”hŒJhttp://support.coraid.com/support/linux/EtherDrive-2.6-HOWTO-5.html#ss5.19”…””}”(hj3  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”j1  uh1hÑhj/  ubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Khj+  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÇhŸh¶h Khh£hžhubh¸)”}”(hŒpThe aoetools are userland programs that are designed to work with this
driver.  The aoetools are on sourceforge.”h]”hŒpThe aoetools are userland programs that are designed to work with this
driver.  The aoetools are on sourceforge.”…””}”(hjM  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Khh£hžhubhÈ)”}”(hŒ!http://aoetools.sourceforge.net/
”h]”h¸)”}”(hŒ http://aoetools.sourceforge.net/”h]”hÒ)”}”(hja  h]”hŒ http://aoetools.sourceforge.net/”…””}”(hjc  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”ja  uh1hÑhj_  ubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Khj[  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÇhŸh¶h Khh£hžhubh¸)”}”(hŒThe scripts in this Documentation/admin-guide/aoe directory are intended to
document the use of the driver and are not necessary if you install
the aoetools.”h]”hŒThe scripts in this Documentation/admin-guide/aoe directory are intended to
document the use of the driver and are not necessary if you install
the aoetools.”…””}”(hj}  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Khh£hžhubeh}”(h]”Œintroduction”ah ]”h"]”Œintroduction”ah$]”h&]”uh1h¡hhhžhhŸh¶h Kubh¢)”}”(hhh]”(h§)”}”(hŒCreating Device Nodes”h]”hŒCreating Device Nodes”…””}”(hj–  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hj“  hžhhŸh¶h KubhÈ)”}”(hXˆ  Users of udev should find the block device nodes created
automatically, but to create all the necessary device nodes, use the
udev configuration rules provided in udev.txt (in this directory).

There is a udev-install.sh script that shows how to install these
rules on your system.

There is also an autoload script that shows how to edit
/etc/modprobe.d/aoe.conf to ensure that the aoe module is loaded when
necessary.  Preloading the aoe module is preferable to autoloading,
however, because AoE discovery takes a few seconds.  It can be
confusing when an AoE device is not present the first time the a
command is run but appears a second later.
”h]”(h¸)”}”(hŒÀUsers of udev should find the block device nodes created
automatically, but to create all the necessary device nodes, use the
udev configuration rules provided in udev.txt (in this directory).”h]”hŒÀUsers of udev should find the block device nodes created
automatically, but to create all the necessary device nodes, use the
udev configuration rules provided in udev.txt (in this directory).”…””}”(hj¨  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Khj¤  ubh¸)”}”(hŒWThere is a udev-install.sh script that shows how to install these
rules on your system.”h]”hŒWThere is a udev-install.sh script that shows how to install these
rules on your system.”…””}”(hj¶  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K#hj¤  ubh¸)”}”(hXl  There is also an autoload script that shows how to edit
/etc/modprobe.d/aoe.conf to ensure that the aoe module is loaded when
necessary.  Preloading the aoe module is preferable to autoloading,
however, because AoE discovery takes a few seconds.  It can be
confusing when an AoE device is not present the first time the a
command is run but appears a second later.”h]”hXl  There is also an autoload script that shows how to edit
/etc/modprobe.d/aoe.conf to ensure that the aoe module is loaded when
necessary.  Preloading the aoe module is preferable to autoloading,
however, because AoE discovery takes a few seconds.  It can be
confusing when an AoE device is not present the first time the a
command is run but appears a second later.”…””}”(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 Khj“  hžhubeh}”(h]”Œcreating-device-nodes”ah ]”h"]”Œcreating device nodes”ah$]”h&]”uh1h¡hhhžhhŸh¶h Kubh¢)”}”(hhh]”(h§)”}”(hŒUsing Device Nodes”h]”hŒUsing Device Nodes”…””}”(hjã  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjà  hžhhŸh¶h K.ubhÈ)”}”(hX|  "cat /dev/etherd/err" blocks, waiting for error diagnostic output,
like any retransmitted packets.

"echo eth2 eth4 > /dev/etherd/interfaces" tells the aoe driver to
limit ATA over Ethernet traffic to eth2 and eth4.  AoE traffic from
untrusted networks should be ignored as a matter of security.  See
also the aoe_iflist driver option described below.

"echo > /dev/etherd/discover" tells the driver to find out what AoE
devices are available.

In the future these character devices may disappear and be replaced
by sysfs counterparts.  Using the commands in aoetools insulates
users from these implementation details.

The block devices are named like this::

      e{shelf}.{slot}
      e{shelf}.{slot}p{part}

... so that "e0.2" is the third blade from the left (slot 2) in the
first shelf (shelf address zero).  That's the whole disk.  The first
partition on that disk would be "e0.2p1".
”h]”(h¸)”}”(hŒb"cat /dev/etherd/err" blocks, waiting for error diagnostic output,
like any retransmitted packets.”h]”hŒfâ€œcat /dev/etherd/errâ€ blocks, waiting for error diagnostic output,
like any retransmitted packets.”…””}”(hjõ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K0hjñ  ubh¸)”}”(hŒû"echo eth2 eth4 > /dev/etherd/interfaces" tells the aoe driver to
limit ATA over Ethernet traffic to eth2 and eth4.  AoE traffic from
untrusted networks should be ignored as a matter of security.  See
also the aoe_iflist driver option described below.”h]”hŒÿâ€œecho eth2 eth4 > /dev/etherd/interfacesâ€ tells the aoe driver to
limit ATA over Ethernet traffic to eth2 and eth4.  AoE traffic from
untrusted networks should be ignored as a matter of security.  See
also the aoe_iflist driver option described below.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K3hjñ  ubh¸)”}”(hŒZ"echo > /dev/etherd/discover" tells the driver to find out what AoE
devices are available.”h]”hŒ^â€œecho > /dev/etherd/discoverâ€ tells the driver to find out what AoE
devices are available.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K8hjñ  ubh¸)”}”(hŒ­In the future these character devices may disappear and be replaced
by sysfs counterparts.  Using the commands in aoetools insulates
users from these implementation details.”h]”hŒ­In the future these character devices may disappear and be replaced
by sysfs counterparts.  Using the commands in aoetools insulates
users from these implementation details.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K;hjñ  ubh¸)”}”(hŒ'The block devices are named like this::”h]”hŒ&The block devices are named like this:”…””}”(hj-  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K?hjñ  ubhŒliteral_block”“”)”}”(hŒ&e{shelf}.{slot}
e{shelf}.{slot}p{part}”h]”hŒ&e{shelf}.{slot}
e{shelf}.{slot}p{part}”…””}”hj=  sbah}”(h]”h ]”h"]”h$]”h&]”Œ	xml:space”Œpreserve”uh1j;  hŸh¶h KAhjñ  ubh¸)”}”(hŒ²... so that "e0.2" is the third blade from the left (slot 2) in the
first shelf (shelf address zero).  That's the whole disk.  The first
partition on that disk would be "e0.2p1".”h]”hŒ¼... so that â€œe0.2â€ is the third blade from the left (slot 2) in the
first shelf (shelf address zero).  Thatâ€™s the whole disk.  The first
partition on that disk would be â€œe0.2p1â€.”…””}”(hjM  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KDhjñ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÇhŸh¶h K0hjà  hžhubeh}”(h]”Œusing-device-nodes”ah ]”h"]”Œusing device nodes”ah$]”h&]”uh1h¡hhhžhhŸh¶h K.ubh¢)”}”(hhh]”(h§)”}”(hŒUsing sysfs”h]”hŒUsing sysfs”…””}”(hjl  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hji  hžhhŸh¶h KIubhÈ)”}”(hX1  Each aoe block device in /sys/block has the extra attributes of
state, mac, and netif.  The state attribute is "up" when the device
is ready for I/O and "down" if detected but unusable.  The
"down,closewait" state shows that the device is still open and
cannot come up again until it has been closed.

The mac attribute is the ethernet address of the remote AoE device.
The netif attribute is the network interface on the localhost
through which we are communicating with the remote AoE device.

There is a script in this directory that formats this information in
a convenient way.  Users with aoetools should use the aoe-stat
command::

  root@makki root# sh Documentation/admin-guide/aoe/status.sh
     e10.0            eth3              up
     e10.1            eth3              up
     e10.2            eth3              up
     e10.3            eth3              up
     e10.4            eth3              up
     e10.5            eth3              up
     e10.6            eth3              up
     e10.7            eth3              up
     e10.8            eth3              up
     e10.9            eth3              up
      e4.0            eth1              up
      e4.1            eth1              up
      e4.2            eth1              up
      e4.3            eth1              up
      e4.4            eth1              up
      e4.5            eth1              up
      e4.6            eth1              up
      e4.7            eth1              up
      e4.8            eth1              up
      e4.9            eth1              up

Use /sys/module/aoe/parameters/aoe_iflist (or better, the driver
option discussed below) instead of /dev/etherd/interfaces to limit
AoE traffic to the network interfaces in the given
whitespace-separated list.  Unlike the old character device, the
sysfs entry can be read from as well as written to.

It's helpful to trigger discovery after setting the list of allowed
interfaces.  The aoetools package provides an aoe-discover script
for this purpose.  You can also directly use the
/dev/etherd/discover special file described above.
”h]”(h¸)”}”(hX,  Each aoe block device in /sys/block has the extra attributes of
state, mac, and netif.  The state attribute is "up" when the device
is ready for I/O and "down" if detected but unusable.  The
"down,closewait" state shows that the device is still open and
cannot come up again until it has been closed.”h]”hX8  Each aoe block device in /sys/block has the extra attributes of
state, mac, and netif.  The state attribute is â€œupâ€ when the device
is ready for I/O and â€œdownâ€ if detected but unusable.  The
â€œdown,closewaitâ€ state shows that the device is still open and
cannot come up again until it has been closed.”…””}”(hj~  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KKhjz  ubh¸)”}”(hŒÀThe mac attribute is the ethernet address of the remote AoE device.
The netif attribute is the network interface on the localhost
through which we are communicating with the remote AoE device.”h]”hŒÀThe mac attribute is the ethernet address of the remote AoE device.
The netif attribute is the network interface on the localhost
through which we are communicating with the remote AoE device.”…””}”(hjŒ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KQhjz  ubh¸)”}”(hŒThere is a script in this directory that formats this information in
a convenient way.  Users with aoetools should use the aoe-stat
command::”h]”hŒŒThere is a script in this directory that formats this information in
a convenient way.  Users with aoetools should use the aoe-stat
command:”…””}”(hjš  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KUhjz  ubj<  )”}”(hXo  root@makki root# sh Documentation/admin-guide/aoe/status.sh
   e10.0            eth3              up
   e10.1            eth3              up
   e10.2            eth3              up
   e10.3            eth3              up
   e10.4            eth3              up
   e10.5            eth3              up
   e10.6            eth3              up
   e10.7            eth3              up
   e10.8            eth3              up
   e10.9            eth3              up
    e4.0            eth1              up
    e4.1            eth1              up
    e4.2            eth1              up
    e4.3            eth1              up
    e4.4            eth1              up
    e4.5            eth1              up
    e4.6            eth1              up
    e4.7            eth1              up
    e4.8            eth1              up
    e4.9            eth1              up”h]”hXo  root@makki root# sh Documentation/admin-guide/aoe/status.sh
   e10.0            eth3              up
   e10.1            eth3              up
   e10.2            eth3              up
   e10.3            eth3              up
   e10.4            eth3              up
   e10.5            eth3              up
   e10.6            eth3              up
   e10.7            eth3              up
   e10.8            eth3              up
   e10.9            eth3              up
    e4.0            eth1              up
    e4.1            eth1              up
    e4.2            eth1              up
    e4.3            eth1              up
    e4.4            eth1              up
    e4.5            eth1              up
    e4.6            eth1              up
    e4.7            eth1              up
    e4.8            eth1              up
    e4.9            eth1              up”…””}”hj¨  sbah}”(h]”h ]”h"]”h$]”h&]”jK  jL  uh1j;  hŸh¶h KYhjz  ubh¸)”}”(hX+  Use /sys/module/aoe/parameters/aoe_iflist (or better, the driver
option discussed below) instead of /dev/etherd/interfaces to limit
AoE traffic to the network interfaces in the given
whitespace-separated list.  Unlike the old character device, the
sysfs entry can be read from as well as written to.”h]”hX+  Use /sys/module/aoe/parameters/aoe_iflist (or better, the driver
option discussed below) instead of /dev/etherd/interfaces to limit
AoE traffic to the network interfaces in the given
whitespace-separated list.  Unlike the old character device, the
sysfs entry can be read from as well as written to.”…””}”(hj¶  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Kohjz  ubh¸)”}”(hŒéIt's helpful to trigger discovery after setting the list of allowed
interfaces.  The aoetools package provides an aoe-discover script
for this purpose.  You can also directly use the
/dev/etherd/discover special file described above.”h]”hŒëItâ€™s helpful to trigger discovery after setting the list of allowed
interfaces.  The aoetools package provides an aoe-discover script
for this purpose.  You can also directly use the
/dev/etherd/discover special file described above.”…””}”(hjÄ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Kuhjz  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÇhŸh¶h KKhji  hžhubeh}”(h]”Œusing-sysfs”ah ]”h"]”Œusing sysfs”ah$]”h&]”uh1h¡hhhžhhŸh¶h KIubh¢)”}”(hhh]”(h§)”}”(hŒDriver Options”h]”hŒDriver Options”…””}”(hjã  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjà  hžhhŸh¶h K{ubhÈ)”}”(hXï  There is a boot option for the built-in aoe driver and a
corresponding module parameter, aoe_iflist.  Without this option,
all network interfaces may be used for ATA over Ethernet.  Here is a
usage example for the module parameter::

  modprobe aoe_iflist="eth1 eth3"

The aoe_deadsecs module parameter determines the maximum number of
seconds that the driver will wait for an AoE device to provide a
response to an AoE command.  After aoe_deadsecs seconds have
elapsed, the AoE device will be marked as "down".  A value of zero
is supported for testing purposes and makes the aoe driver keep
trying AoE commands forever.

The aoe_maxout module parameter has a default of 128.  This is the
maximum number of unresponded packets that will be sent to an AoE
target at one time.

The aoe_dyndevs module parameter defaults to 1, meaning that the
driver will assign a block device minor number to a discovered AoE
target based on the order of its discovery.  With dynamic minor
device numbers in use, a greater range of AoE shelf and slot
addresses can be supported.  Users with udev will never have to
think about minor numbers.  Using aoe_dyndevs=0 allows device nodes
to be pre-created using a static minor-number scheme with the
aoe-mkshelf script in the aoetools.”h]”(h¸)”}”(hŒèThere is a boot option for the built-in aoe driver and a
corresponding module parameter, aoe_iflist.  Without this option,
all network interfaces may be used for ATA over Ethernet.  Here is a
usage example for the module parameter::”h]”hŒçThere is a boot option for the built-in aoe driver and a
corresponding module parameter, aoe_iflist.  Without this option,
all network interfaces may be used for ATA over Ethernet.  Here is a
usage example for the module parameter:”…””}”(hjõ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K}hjñ  ubj<  )”}”(hŒmodprobe aoe_iflist="eth1 eth3"”h]”hŒmodprobe aoe_iflist="eth1 eth3"”…””}”hj  sbah}”(h]”h ]”h"]”h$]”h&]”jK  jL  uh1j;  hŸh¶h K‚hjñ  ubh¸)”}”(hX`  The aoe_deadsecs module parameter determines the maximum number of
seconds that the driver will wait for an AoE device to provide a
response to an AoE command.  After aoe_deadsecs seconds have
elapsed, the AoE device will be marked as "down".  A value of zero
is supported for testing purposes and makes the aoe driver keep
trying AoE commands forever.”h]”hXd  The aoe_deadsecs module parameter determines the maximum number of
seconds that the driver will wait for an AoE device to provide a
response to an AoE command.  After aoe_deadsecs seconds have
elapsed, the AoE device will be marked as â€œdownâ€.  A value of zero
is supported for testing purposes and makes the aoe driver keep
trying AoE commands forever.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K„hjñ  ubh¸)”}”(hŒ˜The aoe_maxout module parameter has a default of 128.  This is the
maximum number of unresponded packets that will be sent to an AoE
target at one time.”h]”hŒ˜The aoe_maxout module parameter has a default of 128.  This is the
maximum number of unresponded packets that will be sent to an AoE
target at one time.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K‹hjñ  ubh¸)”}”(hXæ  The aoe_dyndevs module parameter defaults to 1, meaning that the
driver will assign a block device minor number to a discovered AoE
target based on the order of its discovery.  With dynamic minor
device numbers in use, a greater range of AoE shelf and slot
addresses can be supported.  Users with udev will never have to
think about minor numbers.  Using aoe_dyndevs=0 allows device nodes
to be pre-created using a static minor-number scheme with the
aoe-mkshelf script in the aoetools.”h]”hXæ  The aoe_dyndevs module parameter defaults to 1, meaning that the
driver will assign a block device minor number to a discovered AoE
target based on the order of its discovery.  With dynamic minor
device numbers in use, a greater range of AoE shelf and slot
addresses can be supported.  Users with udev will never have to
think about minor numbers.  Using aoe_dyndevs=0 allows device nodes
to be pre-created using a static minor-number scheme with the
aoe-mkshelf script in the aoetools.”…””}”(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 K}hjà  hžhubeh}”(h]”Œdriver-options”ah ]”h"]”Œdriver options”ah$]”h&]”uh1h¡hhhžhhŸh¶h K{ubeh}”(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”jl  Œ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  jÝ  jÚ  jf  jc  jÝ  jÚ  jF  jC  uŒ	nametypes”}”(j  ‰jÝ  ‰jf  ‰jÝ  ‰jF  ‰uh}”(j  h£jÚ  j“  jc  jà  jÚ  ji  jC  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.