€•CT      Œ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”ŒG/translations/zh_CN/networking/device_drivers/ethernet/microsoft/netvsc”Œ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”ŒG/translations/zh_TW/networking/device_drivers/ethernet/microsoft/netvsc”Œ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”ŒG/translations/it_IT/networking/device_drivers/ethernet/microsoft/netvsc”Œ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”ŒG/translations/ja_JP/networking/device_drivers/ethernet/microsoft/netvsc”Œ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”ŒG/translations/ko_KR/networking/device_drivers/ethernet/microsoft/netvsc”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒPortuguese (Brazilian)”…””}”hh‚sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”ŒG/translations/pt_BR/networking/device_drivers/ethernet/microsoft/netvsc”Œ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”ŒG/translations/sp_SP/networking/device_drivers/ethernet/microsoft/netvsc”Œ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Œcomment”“”)”}”(hŒ SPDX-License-Identifier: GPL-2.0”h]”hŒ SPDX-License-Identifier: GPL-2.0”…””}”hh·sbah}”(h]”h ]”h"]”h$]”h&]”Œ	xml:space”Œpreserve”uh1hµhhh²hh³Œa/var/lib/git/docbuild/linux/Documentation/networking/device_drivers/ethernet/microsoft/netvsc.rst”h´KubhŒsection”“”)”}”(hhh]”(hŒtitle”“”)”}”(hŒHyper-V network driver”h]”hŒHyper-V network driver”…””}”(hhÏh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhhÊh²hh³hÇh´KubhÉ)”}”(hhh]”(hÎ)”}”(hŒCompatibility”h]”hŒCompatibility”…””}”(hhàh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhhÝh²hh³hÇh´KubhŒ	paragraph”“”)”}”(hŒKThis driver is compatible with Windows Server 2012 R2, 2016 and
Windows 10.”h]”hŒKThis driver is compatible with Windows Server 2012 R2, 2016 and
Windows 10.”…””}”(hhðh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÇh´K
hhÝh²hubeh}”(h]”Œcompatibility”ah ]”h"]”Œcompatibility”ah$]”h&]”uh1hÈhhÊh²hh³hÇh´KubhÉ)”}”(hhh]”(hÎ)”}”(hŒFeatures”h]”hŒFeatures”…””}”(hj	  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhj  h²hh³hÇh´KubhÉ)”}”(hhh]”(hÎ)”}”(hŒChecksum offload”h]”hŒChecksum offload”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhj  h²hh³hÇh´KubhŒblock_quote”“”)”}”(hŒñThe netvsc driver supports checksum offload as long as the
Hyper-V host version does. Windows Server 2016 and Azure
support checksum offload for TCP and UDP for both IPv4 and
IPv6. Windows Server 2012 only supports checksum offload for TCP.
”h]”hï)”}”(hŒðThe netvsc driver supports checksum offload as long as the
Hyper-V host version does. Windows Server 2016 and Azure
support checksum offload for TCP and UDP for both IPv4 and
IPv6. Windows Server 2012 only supports checksum offload for TCP.”h]”hŒðThe netvsc driver supports checksum offload as long as the
Hyper-V host version does. Windows Server 2016 and Azure
support checksum offload for TCP and UDP for both IPv4 and
IPv6. Windows Server 2012 only supports checksum offload for TCP.”…””}”(hj.  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÇh´Khj*  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j(  h³hÇh´Khj  h²hubeh}”(h]”Œchecksum-offload”ah ]”h"]”Œchecksum offload”ah$]”h&]”uh1hÈhj  h²hh³hÇh´KubhÉ)”}”(hhh]”(hÎ)”}”(hŒReceive Side Scaling”h]”hŒReceive Side Scaling”…””}”(hjM  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhjJ  h²hh³hÇh´Kubj)  )”}”(hX  Hyper-V supports receive side scaling. For TCP & UDP, packets can
be distributed among available queues based on IP address and port
number.

For TCP & UDP, we can switch hash level between L3 and L4 by ethtool
command. TCP/UDP over IPv4 and v6 can be set differently. The default
hash level is L4. We currently only allow switching TX hash level
from within the guests.

On Azure, fragmented UDP packets have high loss rate with L4
hashing. Using L3 hashing is recommended in this case.

For example, for UDP over IPv4 on eth0:

To include UDP port numbers in hashing::

      ethtool -N eth0 rx-flow-hash udp4 sdfn

To exclude UDP port numbers in hashing::

      ethtool -N eth0 rx-flow-hash udp4 sd

To show UDP hash level::

      ethtool -n eth0 rx-flow-hash udp4
”h]”(hï)”}”(hŒŒHyper-V supports receive side scaling. For TCP & UDP, packets can
be distributed among available queues based on IP address and port
number.”h]”hŒŒHyper-V supports receive side scaling. For TCP & UDP, packets can
be distributed among available queues based on IP address and port
number.”…””}”(hj_  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÇh´Khj[  ubhï)”}”(hŒäFor TCP & UDP, we can switch hash level between L3 and L4 by ethtool
command. TCP/UDP over IPv4 and v6 can be set differently. The default
hash level is L4. We currently only allow switching TX hash level
from within the guests.”h]”hŒäFor TCP & UDP, we can switch hash level between L3 and L4 by ethtool
command. TCP/UDP over IPv4 and v6 can be set differently. The default
hash level is L4. We currently only allow switching TX hash level
from within the guests.”…””}”(hjm  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÇh´Khj[  ubhï)”}”(hŒsOn Azure, fragmented UDP packets have high loss rate with L4
hashing. Using L3 hashing is recommended in this case.”h]”hŒsOn Azure, fragmented UDP packets have high loss rate with L4
hashing. Using L3 hashing is recommended in this case.”…””}”(hj{  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÇh´K"hj[  ubhï)”}”(hŒ'For example, for UDP over IPv4 on eth0:”h]”hŒ'For example, for UDP over IPv4 on eth0:”…””}”(hj‰  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÇh´K%hj[  ubhï)”}”(hŒ(To include UDP port numbers in hashing::”h]”hŒ'To include UDP port numbers in hashing:”…””}”(hj—  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÇh´K'hj[  ubhŒliteral_block”“”)”}”(hŒ&ethtool -N eth0 rx-flow-hash udp4 sdfn”h]”hŒ&ethtool -N eth0 rx-flow-hash udp4 sdfn”…””}”hj§  sbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1j¥  h³hÇh´K)hj[  ubhï)”}”(hŒ(To exclude UDP port numbers in hashing::”h]”hŒ'To exclude UDP port numbers in hashing:”…””}”(hjµ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÇh´K+hj[  ubj¦  )”}”(hŒ$ethtool -N eth0 rx-flow-hash udp4 sd”h]”hŒ$ethtool -N eth0 rx-flow-hash udp4 sd”…””}”hjÃ  sbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1j¥  h³hÇh´K-hj[  ubhï)”}”(hŒTo show UDP hash level::”h]”hŒTo show UDP hash level:”…””}”(hjÑ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÇh´K/hj[  ubj¦  )”}”(hŒ!ethtool -n eth0 rx-flow-hash udp4”h]”hŒ!ethtool -n eth0 rx-flow-hash udp4”…””}”hjß  sbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1j¥  h³hÇh´K1hj[  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j(  h³hÇh´KhjJ  h²hubeh}”(h]”Œreceive-side-scaling”ah ]”h"]”Œreceive side scaling”ah$]”h&]”uh1hÈhj  h²hh³hÇh´KubhÉ)”}”(hhh]”(hÎ)”}”(hŒ Generic Receive Offload, aka GRO”h]”hŒ Generic Receive Offload, aka GRO”…””}”(hjþ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhjû  h²hh³hÇh´K4ubj)  )”}”(hŒŠThe driver supports GRO and it is enabled by default. GRO coalesces
like packets and significantly reduces CPU usage under heavy Rx
load.
”h]”hï)”}”(hŒ‰The driver supports GRO and it is enabled by default. GRO coalesces
like packets and significantly reduces CPU usage under heavy Rx
load.”h]”hŒ‰The driver supports GRO and it is enabled by default. GRO coalesces
like packets and significantly reduces CPU usage under heavy Rx
load.”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÇh´K5hj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j(  h³hÇh´K5hjû  h²hubeh}”(h]”Œgeneric-receive-offload-aka-gro”ah ]”h"]”Œ generic receive offload, aka gro”ah$]”h&]”uh1hÈhj  h²hh³hÇh´K4ubhÉ)”}”(hhh]”(hÎ)”}”(hŒ=Large Receive Offload (LRO), or Receive Side Coalescing (RSC)”h]”hŒ=Large Receive Offload (LRO), or Receive Side Coalescing (RSC)”…””}”(hj/  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhj,  h²hh³hÇh´K:ubj)  )”}”(hXK  The driver supports LRO/RSC in the vSwitch feature. It reduces the per packet
processing overhead by coalescing multiple TCP segments when possible. The
feature is enabled by default on VMs running on Windows Server 2019 and
later. It may be changed by ethtool command::

      ethtool -K eth0 lro on
      ethtool -K eth0 lro off
”h]”(hï)”}”(hX  The driver supports LRO/RSC in the vSwitch feature. It reduces the per packet
processing overhead by coalescing multiple TCP segments when possible. The
feature is enabled by default on VMs running on Windows Server 2019 and
later. It may be changed by ethtool command::”h]”hX  The driver supports LRO/RSC in the vSwitch feature. It reduces the per packet
processing overhead by coalescing multiple TCP segments when possible. The
feature is enabled by default on VMs running on Windows Server 2019 and
later. It may be changed by ethtool command:”…””}”(hjA  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÇh´K;hj=  ubj¦  )”}”(hŒ.ethtool -K eth0 lro on
ethtool -K eth0 lro off”h]”hŒ.ethtool -K eth0 lro on
ethtool -K eth0 lro off”…””}”hjO  sbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1j¥  h³hÇh´K@hj=  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j(  h³hÇh´K;hj,  h²hubeh}”(h]”Œ8large-receive-offload-lro-or-receive-side-coalescing-rsc”ah ]”h"]”Œ=large receive offload (lro), or receive side coalescing (rsc)”ah$]”h&]”uh1hÈhj  h²hh³hÇh´K:ubhÉ)”}”(hhh]”(hÎ)”}”(hŒSR-IOV support”h]”hŒSR-IOV support”…””}”(hjn  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhjk  h²hh³hÇh´KDubj)  )”}”(hXõ  Hyper-V supports SR-IOV as a hardware acceleration option. If SR-IOV
is enabled in both the vSwitch and the guest configuration, then the
Virtual Function (VF) device is passed to the guest as a PCI
device. In this case, both a synthetic (netvsc) and VF device are
visible in the guest OS and both NIC's have the same MAC address.

The VF is enslaved by netvsc device.  The netvsc driver will transparently
switch the data path to the VF when it is available and up.
Network state (addresses, firewall, etc) should be applied only to the
netvsc device; the slave device should not be accessed directly in
most cases.  The exceptions are if some special queue discipline or
flow direction is desired, these should be applied directly to the
VF slave device.
”h]”(hï)”}”(hXJ  Hyper-V supports SR-IOV as a hardware acceleration option. If SR-IOV
is enabled in both the vSwitch and the guest configuration, then the
Virtual Function (VF) device is passed to the guest as a PCI
device. In this case, both a synthetic (netvsc) and VF device are
visible in the guest OS and both NIC's have the same MAC address.”h]”hXL  Hyper-V supports SR-IOV as a hardware acceleration option. If SR-IOV
is enabled in both the vSwitch and the guest configuration, then the
Virtual Function (VF) device is passed to the guest as a PCI
device. In this case, both a synthetic (netvsc) and VF device are
visible in the guest OS and both NICâ€™s have the same MAC address.”…””}”(hj€  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÇh´KEhj|  ubhï)”}”(hX¨  The VF is enslaved by netvsc device.  The netvsc driver will transparently
switch the data path to the VF when it is available and up.
Network state (addresses, firewall, etc) should be applied only to the
netvsc device; the slave device should not be accessed directly in
most cases.  The exceptions are if some special queue discipline or
flow direction is desired, these should be applied directly to the
VF slave device.”h]”hX¨  The VF is enslaved by netvsc device.  The netvsc driver will transparently
switch the data path to the VF when it is available and up.
Network state (addresses, firewall, etc) should be applied only to the
netvsc device; the slave device should not be accessed directly in
most cases.  The exceptions are if some special queue discipline or
flow direction is desired, these should be applied directly to the
VF slave device.”…””}”(hjŽ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÇh´KKhj|  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j(  h³hÇh´KEhjk  h²hubeh}”(h]”Œsr-iov-support”ah ]”h"]”Œsr-iov support”ah$]”h&]”uh1hÈhj  h²hh³hÇh´KDubhÉ)”}”(hhh]”(hÎ)”}”(hŒReceive Buffer”h]”hŒReceive Buffer”…””}”(hj­  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhjª  h²hh³hÇh´KTubj)  )”}”(hX2  Packets are received into a receive area which is created when device
is probed. The receive area is broken into MTU sized chunks and each may
contain one or more packets. The number of receive sections may be changed
via ethtool Rx ring parameters.

There is a similar send buffer which is used to aggregate packets
for sending.  The send area is broken into chunks, typically of 6144
bytes, each of section may contain one or more packets. Small
packets are usually transmitted via copy to the send buffer. However,
if the buffer is temporarily exhausted, or the packet to be transmitted is
an LSO packet, the driver will provide the host with pointers to the data
from the SKB. This attempts to achieve a balance between the overhead of
data copy and the impact of remapping VM memory to be accessible by the
host.
”h]”(hï)”}”(hŒùPackets are received into a receive area which is created when device
is probed. The receive area is broken into MTU sized chunks and each may
contain one or more packets. The number of receive sections may be changed
via ethtool Rx ring parameters.”h]”hŒùPackets are received into a receive area which is created when device
is probed. The receive area is broken into MTU sized chunks and each may
contain one or more packets. The number of receive sections may be changed
via ethtool Rx ring parameters.”…””}”(hj¿  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÇh´KUhj»  ubhï)”}”(hX6  There is a similar send buffer which is used to aggregate packets
for sending.  The send area is broken into chunks, typically of 6144
bytes, each of section may contain one or more packets. Small
packets are usually transmitted via copy to the send buffer. However,
if the buffer is temporarily exhausted, or the packet to be transmitted is
an LSO packet, the driver will provide the host with pointers to the data
from the SKB. This attempts to achieve a balance between the overhead of
data copy and the impact of remapping VM memory to be accessible by the
host.”h]”hX6  There is a similar send buffer which is used to aggregate packets
for sending.  The send area is broken into chunks, typically of 6144
bytes, each of section may contain one or more packets. Small
packets are usually transmitted via copy to the send buffer. However,
if the buffer is temporarily exhausted, or the packet to be transmitted is
an LSO packet, the driver will provide the host with pointers to the data
from the SKB. This attempts to achieve a balance between the overhead of
data copy and the impact of remapping VM memory to be accessible by the
host.”…””}”(hjÍ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÇh´KZhj»  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j(  h³hÇh´KUhjª  h²hubeh}”(h]”Œreceive-buffer”ah ]”h"]”Œreceive buffer”ah$]”h&]”uh1hÈhj  h²hh³hÇh´KTubhÉ)”}”(hhh]”(hÎ)”}”(hŒXDP support”h]”hŒXDP support”…””}”(hjì  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhjé  h²hh³hÇh´Keubj)  )”}”(hX  XDP (eXpress Data Path) is a feature that runs eBPF bytecode at the early
stage when packets arrive at a NIC card. The goal is to increase performance
for packet processing, reducing the overhead of SKB allocation and other
upper network layers.

hv_netvsc supports XDP in native mode, and transparently sets the XDP
program on the associated VF NIC as well.

Setting / unsetting XDP program on synthetic NIC (netvsc) propagates to
VF NIC automatically. Setting / unsetting XDP program on VF NIC directly
is not recommended, also not propagated to synthetic NIC, and may be
overwritten by setting of synthetic NIC.

XDP program cannot run with LRO (RSC) enabled, so you need to disable LRO
before running XDP::

      ethtool -K eth0 lro off

XDP_REDIRECT action is not yet supported.”h]”(hï)”}”(hŒõXDP (eXpress Data Path) is a feature that runs eBPF bytecode at the early
stage when packets arrive at a NIC card. The goal is to increase performance
for packet processing, reducing the overhead of SKB allocation and other
upper network layers.”h]”hŒõXDP (eXpress Data Path) is a feature that runs eBPF bytecode at the early
stage when packets arrive at a NIC card. The goal is to increase performance
for packet processing, reducing the overhead of SKB allocation and other
upper network layers.”…””}”(hjþ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÇh´Kfhjú  ubhï)”}”(hŒohv_netvsc supports XDP in native mode, and transparently sets the XDP
program on the associated VF NIC as well.”h]”hŒohv_netvsc supports XDP in native mode, and transparently sets the XDP
program on the associated VF NIC as well.”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÇh´Kkhjú  ubhï)”}”(hŒþSetting / unsetting XDP program on synthetic NIC (netvsc) propagates to
VF NIC automatically. Setting / unsetting XDP program on VF NIC directly
is not recommended, also not propagated to synthetic NIC, and may be
overwritten by setting of synthetic NIC.”h]”hŒþSetting / unsetting XDP program on synthetic NIC (netvsc) propagates to
VF NIC automatically. Setting / unsetting XDP program on VF NIC directly
is not recommended, also not propagated to synthetic NIC, and may be
overwritten by setting of synthetic NIC.”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÇh´Knhjú  ubhï)”}”(hŒ^XDP program cannot run with LRO (RSC) enabled, so you need to disable LRO
before running XDP::”h]”hŒ]XDP program cannot run with LRO (RSC) enabled, so you need to disable LRO
before running XDP:”…””}”(hj(  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÇh´Kshjú  ubj¦  )”}”(hŒethtool -K eth0 lro off”h]”hŒethtool -K eth0 lro off”…””}”hj6  sbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1j¥  h³hÇh´Kvhjú  ubhï)”}”(hŒ)XDP_REDIRECT action is not yet supported.”h]”hŒ)XDP_REDIRECT action is not yet supported.”…””}”(hjD  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÇh´Kxhjú  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j(  h³hÇh´Kfhjé  h²hubeh}”(h]”Œxdp-support”ah ]”h"]”Œxdp support”ah$]”h&]”uh1hÈhj  h²hh³hÇh´Keubeh}”(h]”Œfeatures”ah ]”h"]”Œfeatures”ah$]”h&]”uh1hÈhhÊh²hh³hÇh´Kubeh}”(h]”Œhyper-v-network-driver”ah ]”h"]”Œhyper-v network driver”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”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”}”(jm  jj  j  j   je  jb  jG  jD  jø  jõ  j)  j&  jh  je  j§  j¤  jæ  jã  j]  jZ  uŒ	nametypes”}”(jm  ‰j  ‰je  ‰jG  ‰jø  ‰j)  ‰jh  ‰j§  ‰jæ  ‰j]  ‰uh}”(jj  hÊj   hÝjb  j  jD  j  jõ  jJ  j&  jû  je  j,  j¤  jk  jã  jª  jZ  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.