From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [PATCH v5 6/8] thunderbolt: Networking transmit and receive Date: Sun, 31 Jul 2016 11:45:13 -0700 (PDT) Message-ID: <20160731.114513.2022660088754330528.davem@davemloft.net> References: <1469693721-5641-7-git-send-email-amir.jer.levy@intel.com> <20160729140741.18ca3e35@xeon-e3> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: stephen@networkplumber.org, andreas.noever@gmail.com, gregkh@linuxfoundation.org, bhelgaas@google.com, corbet@lwn.net, linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org, netdev@vger.kernel.org, linux-doc@vger.kernel.org, thunderbolt-linux@intel.com, mika.westerberg@intel.com, tomas.winkler@intel.com To: amir.jer.levy@intel.com Return-path: In-Reply-To: Sender: linux-doc-owner@vger.kernel.org List-Id: netdev.vger.kernel.org From: "Levy, Amir (Jer)" Date: Sun, 31 Jul 2016 10:15:52 +0000 > The network stack thinks it is Ethernet, it might not accept Runt > frames, so the driver pads the frame in receive. The network stack doesn't care about this at all. It's wasted effort on your part.