All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH v2 11/12] Documentation: fm10k: Add kernel documentation
Date: Wed, 10 Oct 2018 12:16:12 -0700	[thread overview]
Message-ID: <20181010191613.2770-12-jeffrey.t.kirsher@intel.com> (raw)
In-Reply-To: <20181010191613.2770-1-jeffrey.t.kirsher@intel.com>

Added the fm10k kernel documentation, which apparently was missing.

Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
---
 Documentation/networking/fm10k.rst | 141 +++++++++++++++++++++++++++++
 Documentation/networking/index.rst |   1 +
 MAINTAINERS                        |   1 +
 drivers/net/ethernet/intel/Kconfig |   3 +
 4 files changed, 146 insertions(+)
 create mode 100644 Documentation/networking/fm10k.rst

diff --git a/Documentation/networking/fm10k.rst b/Documentation/networking/fm10k.rst
new file mode 100644
index 000000000000..bf5e5942f28d
--- /dev/null
+++ b/Documentation/networking/fm10k.rst
@@ -0,0 +1,141 @@
+.. SPDX-License-Identifier: GPL-2.0+
+
+Linux* Base Driver for Intel(R) Ethernet Multi-host Controller
+==============================================================
+
+August 20, 2018
+Copyright(c) 2015-2018 Intel Corporation.
+
+Contents
+========
+- Identifying Your Adapter
+- Additional Configurations
+- Performance Tuning
+- Known Issues
+- Support
+
+Identifying Your Adapter
+========================
+The driver in this release is compatible with devices based on the Intel(R)
+Ethernet Multi-host Controller.
+
+For information on how to identify your adapter, and for the latest Intel
+network drivers, refer to the Intel Support website:
+http://www.intel.com/support
+
+
+Flow Control
+------------
+The Intel(R) Ethernet Switch Host Interface Driver does not support Flow
+Control. It will not send pause frames. This may result in dropped frames.
+
+
+Virtual Functions (VFs)
+-----------------------
+Use sysfs to enable VFs.
+Valid Range: 0-64
+
+For example::
+
+    echo $num_vf_enabled > /sys/class/net/$dev/device/sriov_numvfs //enable VFs
+    echo 0 > /sys/class/net/$dev/device/sriov_numvfs //disable VFs
+
+NOTE: Neither the device nor the driver control how VFs are mapped into config
+space. Bus layout will vary by operating system. On operating systems that
+support it, you can check sysfs to find the mapping.
+
+NOTE: When SR-IOV mode is enabled, hardware VLAN filtering and VLAN tag
+stripping/insertion will remain enabled. Please remove the old VLAN filter
+before the new VLAN filter is added. For example::
+
+    ip link set eth0 vf 0 vlan 100	// set vlan 100 for VF 0
+    ip link set eth0 vf 0 vlan 0	// Delete vlan 100
+    ip link set eth0 vf 0 vlan 200	// set a new vlan 200 for VF 0
+
+
+Additional Features and Configurations
+======================================
+
+Jumbo Frames
+------------
+Jumbo Frames support is enabled by changing the Maximum Transmission Unit (MTU)
+to a value larger than the default value of 1500.
+
+Use the ifconfig command to increase the MTU size. For example, enter the
+following where <x> is the interface number::
+
+    ifconfig eth<x> mtu 9000 up
+
+Alternatively, you can use the ip command as follows::
+
+    ip link set mtu 9000 dev eth<x>
+    ip link set up dev eth<x>
+
+This setting is not saved across reboots. The setting change can be made
+permanent by adding 'MTU=9000' to the file:
+
+- For RHEL: /etc/sysconfig/network-scripts/ifcfg-eth<x>
+- For SLES: /etc/sysconfig/network/<config_file>
+
+NOTE: The maximum MTU setting for Jumbo Frames is 15342. This value coincides
+with the maximum Jumbo Frames size of 15364 bytes.
+
+NOTE: This driver will attempt to use multiple page sized buffers to receive
+each jumbo packet. This should help to avoid buffer starvation issues when
+allocating receive packets.
+
+
+Generic Receive Offload, aka GRO
+--------------------------------
+The driver supports the in-kernel software implementation of GRO. GRO has
+shown that by coalescing Rx traffic into larger chunks of data, CPU
+utilization can be significantly reduced when under large Rx load. GRO is an
+evolution of the previously-used LRO interface. GRO is able to coalesce
+other protocols besides TCP. It's also safe to use with configurations that
+are problematic for LRO, namely bridging and iSCSI.
+
+
+
+Supported ethtool Commands and Options for Filtering
+----------------------------------------------------
+-n --show-nfc
+  Retrieves the receive network flow classification configurations.
+
+rx-flow-hash tcp4|udp4|ah4|esp4|sctp4|tcp6|udp6|ah6|esp6|sctp6
+  Retrieves the hash options for the specified network traffic type.
+
+-N --config-nfc
+  Configures the receive network flow classification.
+
+rx-flow-hash tcp4|udp4|ah4|esp4|sctp4|tcp6|udp6|ah6|esp6|sctp6 m|v|t|s|d|f|n|r
+  Configures the hash options for the specified network traffic type.
+
+- udp4: UDP over IPv4
+- udp6: UDP over IPv6
+- f Hash on bytes 0 and 1 of the Layer 4 header of the rx packet.
+- n Hash on bytes 2 and 3 of the Layer 4 header of the rx packet.
+
+
+Known Issues/Troubleshooting
+============================
+
+Enabling SR-IOV in a 64-bit Microsoft* Windows Server* 2012/R2 guest OS under Linux KVM
+---------------------------------------------------------------------------------------
+KVM Hypervisor/VMM supports direct assignment of a PCIe device to a VM. This
+includes traditional PCIe devices, as well as SR-IOV-capable devices based on
+the Intel Ethernet Controller XL710.
+
+
+Support
+=======
+For general information, go to the Intel support website at:
+
+https://www.intel.com/support/
+
+or the Intel Wired Networking project hosted by Sourceforge at:
+
+https://sourceforge.net/projects/e1000
+
+If an issue is identified with the released source code on a supported kernel
+with a supported adapter, email the specific information related to the issue
+to e1000-devel at lists.sf.net.
diff --git a/Documentation/networking/index.rst b/Documentation/networking/index.rst
index fcd710f2cc7a..8c8a0d2d39db 100644
--- a/Documentation/networking/index.rst
+++ b/Documentation/networking/index.rst
@@ -14,6 +14,7 @@ Contents:
    dpaa2/index
    e100
    e1000
+   fm10k
    kapi
    z8530book
    msg_zerocopy
diff --git a/MAINTAINERS b/MAINTAINERS
index 54e719d02200..01a346754652 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -7347,6 +7347,7 @@ S:	Supported
 F:	Documentation/networking/e100.rst
 F:	Documentation/networking/e1000.rst
 F:	Documentation/networking/e1000e.txt
+F:	Documentation/networking/fm10k.rst
 F:	Documentation/networking/igb.txt
 F:	Documentation/networking/igbvf.txt
 F:	Documentation/networking/ixgb.txt
diff --git a/drivers/net/ethernet/intel/Kconfig b/drivers/net/ethernet/intel/Kconfig
index 76f926d4bf13..9ff6da335b2a 100644
--- a/drivers/net/ethernet/intel/Kconfig
+++ b/drivers/net/ethernet/intel/Kconfig
@@ -284,6 +284,9 @@ config FM10K
 
 	  <http://support.intel.com>
 
+	  More specific information on configuring the driver is in
+	  <file:Documentation/networking/fm10k.rst>.
+
 	  To compile this driver as a module, choose M here. The module
 	  will be called fm10k.  MSI-X interrupt support is required
 
-- 
2.17.1


  parent reply	other threads:[~2018-10-10 19:16 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-10 19:16 [Intel-wired-lan] [PATCH v2 00/12] Intel Wired LAN Documentation Updates Jeff Kirsher
2018-10-10 19:16 ` [Intel-wired-lan] [PATCH v2 01/12] Documentation: e100, e1000: Add missing SPDX header Jeff Kirsher
2018-10-11 15:39   ` Bowers, AndrewX
2018-10-12  1:27   ` Brown, Aaron F
2018-10-10 19:16 ` [Intel-wired-lan] [PATCH v2 02/12] Documentation: ixgb: Prepare documentation for RST conversion Jeff Kirsher
2018-10-11 15:39   ` Bowers, AndrewX
2018-10-11 20:20   ` Brown, Aaron F
2018-10-10 19:16 ` [Intel-wired-lan] [PATCH v2 03/12] Documentation: e1000e: " Jeff Kirsher
2018-10-11 15:40   ` Bowers, AndrewX
2018-10-11 20:29   ` Brown, Aaron F
2018-10-11 21:14   ` Brown, Aaron F
2018-10-10 19:16 ` [Intel-wired-lan] [PATCH v2 04/12] Documentation: igb: " Jeff Kirsher
2018-10-11 15:40   ` Bowers, AndrewX
2018-10-11 21:27   ` Brown, Aaron F
2018-10-10 19:16 ` [Intel-wired-lan] [PATCH v2 05/12] Documentation: igbvf: " Jeff Kirsher
2018-10-11 15:41   ` Bowers, AndrewX
2018-10-11 21:39   ` Brown, Aaron F
2018-10-10 19:16 ` [Intel-wired-lan] [PATCH v2 06/12] Documentation: ixgbe: " Jeff Kirsher
2018-10-11 15:41   ` Bowers, AndrewX
2018-10-11 16:40   ` Shannon Nelson
2018-10-11 23:50   ` Brown, Aaron F
2018-10-10 19:16 ` [Intel-wired-lan] [PATCH v2 07/12] Documentation: ixgbevf: " Jeff Kirsher
2018-10-11 15:41   ` Bowers, AndrewX
2018-10-11 21:45   ` Brown, Aaron F
2018-10-10 19:16 ` [Intel-wired-lan] [PATCH v2 08/12] Documentation: i40e: " Jeff Kirsher
2018-10-11 16:41   ` Shannon Nelson
2018-10-11 17:41     ` Keller, Jacob E
2018-10-12  0:51   ` Brown, Aaron F
2018-10-10 19:16 ` [Intel-wired-lan] [PATCH v2 09/12] Documentation: iavf: " Jeff Kirsher
2018-10-11 15:42   ` Bowers, AndrewX
2018-10-12  1:18   ` Brown, Aaron F
2018-10-12  1:26   ` Brown, Aaron F
2018-10-10 19:16 ` [Intel-wired-lan] [PATCH v2 10/12] Documentation: ice: " Jeff Kirsher
2018-10-11 15:43   ` Bowers, AndrewX
2018-10-12  1:29   ` Brown, Aaron F
2018-10-10 19:16 ` Jeff Kirsher [this message]
2018-10-11 15:43   ` [Intel-wired-lan] [PATCH v2 11/12] Documentation: fm10k: Add kernel documentation Bowers, AndrewX
2018-10-12  1:00   ` Brown, Aaron F
2018-10-10 19:16 ` [Intel-wired-lan] [PATCH v2 12/12] Documentation: intel: Convert to RST format Jeff Kirsher
2018-10-11 15:44   ` Bowers, AndrewX
2018-10-12  1:28   ` Brown, Aaron F

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20181010191613.2770-12-jeffrey.t.kirsher@intel.com \
    --to=jeffrey.t.kirsher@intel.com \
    --cc=intel-wired-lan@osuosl.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.