Patch Detail
get:
Show a patch.
patch:
Update a patch.
put:
Update a patch.
GET /api/patches/959944/?format=api
{ "id": 959944, "url": "http://patchwork.ozlabs.org/api/patches/959944/?format=api", "web_url": "http://patchwork.ozlabs.org/project/intel-wired-lan/patch/20180820200555.13072-1-jeffrey.t.kirsher@intel.com/", "project": { "id": 46, "url": "http://patchwork.ozlabs.org/api/projects/46/?format=api", "name": "Intel Wired Ethernet development", "link_name": "intel-wired-lan", "list_id": "intel-wired-lan.osuosl.org", "list_email": "intel-wired-lan@osuosl.org", "web_url": "", "scm_url": "", "webscm_url": "", "list_archive_url": "", "list_archive_url_format": "", "commit_url_format": "" }, "msgid": "<20180820200555.13072-1-jeffrey.t.kirsher@intel.com>", "list_archive_url": null, "date": "2018-08-20T20:05:55", "name": "[v4] Documentation: fm10k: Add kernel documentation", "commit_ref": null, "pull_url": null, "state": "superseded", "archived": false, "hash": "a09f7139573114dd14b62b27f21a1a3fa7b295ba", "submitter": { "id": 473, "url": "http://patchwork.ozlabs.org/api/people/473/?format=api", "name": "Kirsher, Jeffrey T", "email": "jeffrey.t.kirsher@intel.com" }, "delegate": { "id": 68, "url": "http://patchwork.ozlabs.org/api/users/68/?format=api", "username": "jtkirshe", "first_name": "Jeff", "last_name": "Kirsher", "email": "jeffrey.t.kirsher@intel.com" }, "mbox": "http://patchwork.ozlabs.org/project/intel-wired-lan/patch/20180820200555.13072-1-jeffrey.t.kirsher@intel.com/mbox/", "series": [ { "id": 61617, "url": "http://patchwork.ozlabs.org/api/series/61617/?format=api", "web_url": "http://patchwork.ozlabs.org/project/intel-wired-lan/list/?series=61617", "date": "2018-08-20T20:05:55", "name": "[v4] Documentation: fm10k: Add kernel documentation", "version": 4, "mbox": "http://patchwork.ozlabs.org/series/61617/mbox/" } ], "comments": "http://patchwork.ozlabs.org/api/patches/959944/comments/", "check": "pending", "checks": "http://patchwork.ozlabs.org/api/patches/959944/checks/", "tags": {}, "related": [], "headers": { "Return-Path": "<intel-wired-lan-bounces@osuosl.org>", "X-Original-To": [ "incoming@patchwork.ozlabs.org", "intel-wired-lan@lists.osuosl.org" ], "Delivered-To": [ "patchwork-incoming@bilbo.ozlabs.org", "intel-wired-lan@lists.osuosl.org" ], "Authentication-Results": [ "ozlabs.org;\n\tspf=pass (mailfrom) smtp.mailfrom=osuosl.org\n\t(client-ip=140.211.166.136; helo=silver.osuosl.org;\n\tenvelope-from=intel-wired-lan-bounces@osuosl.org;\n\treceiver=<UNKNOWN>)", "ozlabs.org;\n\tdmarc=fail (p=none dis=none) header.from=intel.com" ], "Received": [ "from silver.osuosl.org (smtp3.osuosl.org [140.211.166.136])\n\t(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))\n\t(No client certificate requested)\n\tby ozlabs.org (Postfix) with ESMTPS id 41vPrC21Njz9s78\n\tfor <incoming@patchwork.ozlabs.org>;\n\tTue, 21 Aug 2018 06:03:22 +1000 (AEST)", "from localhost (localhost [127.0.0.1])\n\tby silver.osuosl.org (Postfix) with ESMTP id 2D32F22FE8;\n\tMon, 20 Aug 2018 20:03:21 +0000 (UTC)", "from silver.osuosl.org ([127.0.0.1])\n\tby localhost (.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)\n\twith ESMTP id lGgfCXbN6w6x; Mon, 20 Aug 2018 20:03:19 +0000 (UTC)", "from ash.osuosl.org (ash.osuosl.org [140.211.166.34])\n\tby silver.osuosl.org (Postfix) with ESMTP id 8777B22F23;\n\tMon, 20 Aug 2018 20:03:19 +0000 (UTC)", "from whitealder.osuosl.org (smtp1.osuosl.org [140.211.166.138])\n\tby ash.osuosl.org (Postfix) with ESMTP id 573E71C0DB8\n\tfor <intel-wired-lan@lists.osuosl.org>;\n\tMon, 20 Aug 2018 20:03:19 +0000 (UTC)", "from localhost (localhost [127.0.0.1])\n\tby whitealder.osuosl.org (Postfix) with ESMTP id 5336886570\n\tfor <intel-wired-lan@lists.osuosl.org>;\n\tMon, 20 Aug 2018 20:03:19 +0000 (UTC)", "from whitealder.osuosl.org ([127.0.0.1])\n\tby localhost (.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)\n\twith ESMTP id F50Lod059BDK for <intel-wired-lan@lists.osuosl.org>;\n\tMon, 20 Aug 2018 20:03:18 +0000 (UTC)", "from mga09.intel.com (mga09.intel.com [134.134.136.24])\n\tby whitealder.osuosl.org (Postfix) with ESMTPS id 900C2865C4\n\tfor <intel-wired-lan@lists.osuosl.org>;\n\tMon, 20 Aug 2018 20:03:18 +0000 (UTC)", "from fmsmga004.fm.intel.com ([10.253.24.48])\n\tby orsmga102.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384;\n\t20 Aug 2018 13:03:17 -0700", "from jtkirshe-desk1.jf.intel.com ([134.134.177.59])\n\tby fmsmga004.fm.intel.com with ESMTP; 20 Aug 2018 13:03:17 -0700" ], "X-Virus-Scanned": [ "amavisd-new at osuosl.org", "amavisd-new at osuosl.org" ], "X-Greylist": "domain auto-whitelisted by SQLgrey-1.7.6", "X-Amp-Result": "SKIPPED(no attachment in message)", "X-Amp-File-Uploaded": "False", "X-ExtLoop1": "1", "X-IronPort-AV": "E=Sophos;i=\"5.53,266,1531810800\"; d=\"scan'208\";a=\"81916938\"", "From": "Jeff Kirsher <jeffrey.t.kirsher@intel.com>", "To": "intel-wired-lan@lists.osuosl.org", "Date": "Mon, 20 Aug 2018 13:05:55 -0700", "Message-Id": "<20180820200555.13072-1-jeffrey.t.kirsher@intel.com>", "X-Mailer": "git-send-email 2.17.1", "Subject": "[Intel-wired-lan] [PATCH v4] Documentation: fm10k: Add kernel\n\tdocumentation", "X-BeenThere": "intel-wired-lan@osuosl.org", "X-Mailman-Version": "2.1.24", "Precedence": "list", "List-Id": "Intel Wired Ethernet Linux Kernel Driver Development\n\t<intel-wired-lan.osuosl.org>", "List-Unsubscribe": "<https://lists.osuosl.org/mailman/options/intel-wired-lan>, \n\t<mailto:intel-wired-lan-request@osuosl.org?subject=unsubscribe>", "List-Archive": "<http://lists.osuosl.org/pipermail/intel-wired-lan/>", "List-Post": "<mailto:intel-wired-lan@osuosl.org>", "List-Help": "<mailto:intel-wired-lan-request@osuosl.org?subject=help>", "List-Subscribe": "<https://lists.osuosl.org/mailman/listinfo/intel-wired-lan>, \n\t<mailto:intel-wired-lan-request@osuosl.org?subject=subscribe>", "MIME-Version": "1.0", "Content-Type": "text/plain; charset=\"us-ascii\"", "Content-Transfer-Encoding": "7bit", "Errors-To": "intel-wired-lan-bounces@osuosl.org", "Sender": "\"Intel-wired-lan\" <intel-wired-lan-bounces@osuosl.org>" }, "content": "Added the fm10k kernel documentation, which apparently was missing.\n\nSigned-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>\n---\nv1/v2: Initial attempt to produce fm10k documentation\n\nv3: converted to RST format and addressed Shannon Nelson's feedback\n\nV4: Fixed documentation title, no reason for it to say \"README ...\" and\n addressed more of Shannon's feedback\n\n Documentation/networking/fm10k.rst | 139 +++++++++++++++++++++++++++++\n Documentation/networking/index.rst | 1 +\n MAINTAINERS | 1 +\n drivers/net/ethernet/intel/Kconfig | 3 +\n 4 files changed, 144 insertions(+)\n create mode 100644 Documentation/networking/fm10k.rst", "diff": "diff --git a/Documentation/networking/fm10k.rst b/Documentation/networking/fm10k.rst\nnew file mode 100644\nindex 000000000000..a061da652986\n--- /dev/null\n+++ b/Documentation/networking/fm10k.rst\n@@ -0,0 +1,139 @@\n+Linux* Base Driver for Intel(R) Ethernet Multi-host Controller\n+==============================================================\n+\n+August 20, 2018\n+Copyright(c) 2015-2018 Intel Corporation.\n+\n+Contents\n+========\n+- Identifying Your Adapter\n+- Additional Configurations\n+- Performance Tuning\n+- Known Issues\n+- Support\n+\n+Identifying Your Adapter\n+========================\n+The driver in this release is compatible with devices based on the Intel(R)\n+Ethernet Multi-host Controller.\n+\n+For information on how to identify your adapter, and for the latest Intel\n+network drivers, refer to the Intel Support website:\n+http://www.intel.com/support\n+\n+\n+Flow Control\n+------------\n+The Intel(R) Ethernet Switch Host Interface Driver does not support Flow\n+Control. It will not send pause frames. This may result in dropped frames.\n+\n+\n+Virtual Functions (VFs)\n+-----------------------\n+Use sysfs to enable VFs.\n+Valid Range: 0-64\n+\n+For example::\n+\n+ echo $num_vf_enabled > /sys/class/net/$dev/device/sriov_numvfsr //enable VFs\n+ echo 0 > /sys/class/net/$dev/device/sriov_numvfs //disable VFs\n+\n+NOTE: Neither the device nor the driver control how VFs are mapped into config\n+space. Bus layout will vary by operating system. On operating systems that\n+support it, you can check sysfs to find the mapping.\n+\n+NOTE: When SR-IOV mode is enabled, hardware VLAN filtering and VLAN tag\n+stripping/insertion will remain enabled. Please remove the old VLAN filter\n+before the new VLAN filter is added. For example::\n+\n+ ip link set eth0 vf 0 vlan 100\t// set vlan 100 for VF 0\n+ ip link set eth0 vf 0 vlan 0\t// Delete vlan 100\n+ ip link set eth0 vf 0 vlan 200\t// set a new vlan 200 for VF 0\n+\n+\n+Additional Features and Configurations\n+======================================\n+\n+Jumbo Frames\n+------------\n+Jumbo Frames support is enabled by changing the Maximum Transmission Unit (MTU)\n+to a value larger than the default value of 1500.\n+\n+Use the ifconfig command to increase the MTU size. For example, enter the\n+following where <x> is the interface number::\n+\n+ ifconfig eth<x> mtu 9000 up\n+\n+Alternatively, you can use the ip command as follows::\n+\n+ ip link set mtu 9000 dev eth<x>\n+ ip link set up dev eth<x>\n+\n+This setting is not saved across reboots. The setting change can be made\n+permanent by adding 'MTU=9000' to the file:\n+\n+- For RHEL: /etc/sysconfig/network-scripts/ifcfg-eth<x>\n+- For SLES: /etc/sysconfig/network/<config_file>\n+\n+NOTE: The maximum MTU setting for Jumbo Frames is 15342. This value coincides\n+with the maximum Jumbo Frames size of 15364 bytes.\n+\n+NOTE: This driver will attempt to use multiple page sized buffers to receive\n+each jumbo packet. This should help to avoid buffer starvation issues when\n+allocating receive packets.\n+\n+\n+Generic Receive Offload, aka GRO\n+--------------------------------\n+The driver supports the in-kernel software implementation of GRO. GRO has\n+shown that by coalescing Rx traffic into larger chunks of data, CPU\n+utilization can be significantly reduced when under large Rx load. GRO is an\n+evolution of the previously-used LRO interface. GRO is able to coalesce\n+other protocols besides TCP. It's also safe to use with configurations that\n+are problematic for LRO, namely bridging and iSCSI.\n+\n+\n+\n+Supported ethtool Commands and Options for Filtering\n+----------------------------------------------------\n+-n --show-nfc\n+ Retrieves the receive network flow classification configurations.\n+\n+rx-flow-hash tcp4|udp4|ah4|esp4|sctp4|tcp6|udp6|ah6|esp6|sctp6\n+ Retrieves the hash options for the specified network traffic type.\n+\n+-N --config-nfc\n+ Configures the receive network flow classification.\n+\n+rx-flow-hash tcp4|udp4|ah4|esp4|sctp4|tcp6|udp6|ah6|esp6|sctp6 m|v|t|s|d|f|n|r\n+ Configures the hash options for the specified network traffic type.\n+\n+- udp4: UDP over IPv4\n+- udp6: UDP over IPv6\n+- f Hash on bytes 0 and 1 of the Layer 4 header of the rx packet.\n+- n Hash on bytes 2 and 3 of the Layer 4 header of the rx packet.\n+\n+\n+Known Issues/Troubleshooting\n+============================\n+\n+Enabling SR-IOV in a 64-bit Microsoft* Windows Server* 2012/R2 guest OS under Linux KVM\n+---------------------------------------------------------------------------------------\n+KVM Hypervisor/VMM supports direct assignment of a PCIe device to a VM. This\n+includes traditional PCIe devices, as well as SR-IOV-capable devices based on\n+the Intel Ethernet Controller XL710.\n+\n+\n+Support\n+=======\n+For general information, go to the Intel support website at:\n+\n+https://www.intel.com/support/\n+\n+or the Intel Wired Networking project hosted by Sourceforge at:\n+\n+https://sourceforge.net/projects/e1000\n+\n+If an issue is identified with the released source code on a supported kernel\n+with a supported adapter, email the specific information related to the issue\n+to e1000-devel@lists.sf.net.\ndiff --git a/Documentation/networking/index.rst b/Documentation/networking/index.rst\nindex a9346dc77a74..779c1f141d94 100644\n--- a/Documentation/networking/index.rst\n+++ b/Documentation/networking/index.rst\n@@ -14,6 +14,7 @@ Contents:\n dpaa2/index\n e100\n e1000\n+ fm10k\n ixgb\n kapi\n z8530book\ndiff --git a/MAINTAINERS b/MAINTAINERS\nindex c472a14ae06d..be1adcd6477c 100644\n--- a/MAINTAINERS\n+++ b/MAINTAINERS\n@@ -7278,6 +7278,7 @@ S:\tSupported\n F:\tDocumentation/networking/e100.rst\n F:\tDocumentation/networking/e1000.rst\n F:\tDocumentation/networking/e1000e.txt\n+F:\tDocumentation/networking/fm10k.rst\n F:\tDocumentation/networking/igb.txt\n F:\tDocumentation/networking/igbvf.txt\n F:\tDocumentation/networking/ixgb.rst\ndiff --git a/drivers/net/ethernet/intel/Kconfig b/drivers/net/ethernet/intel/Kconfig\nindex fcb676398022..913dabbdfa81 100644\n--- a/drivers/net/ethernet/intel/Kconfig\n+++ b/drivers/net/ethernet/intel/Kconfig\n@@ -277,6 +277,9 @@ config FM10K\n \n \t <http://support.intel.com>\n \n+\t More specific information on configuring the driver is in\n+\t <file:Documentation/networking/fm10k.rst>.\n+\n \t To compile this driver as a module, choose M here. The module\n \t will be called fm10k. MSI-X interrupt support is required\n \n", "prefixes": [ "v4" ] }