From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 6 Feb 2003 13:48:16 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 6 Feb 2003 13:48:16 -0500 Received: from pizda.ninka.net ([216.101.162.242]:27096 "EHLO pizda.ninka.net") by vger.kernel.org with ESMTP id ; Thu, 6 Feb 2003 13:48:15 -0500 Date: Thu, 06 Feb 2003 10:44:24 -0800 (PST) Message-Id: <20030206.104424.39167597.davem@redhat.com> To: christopher.leech@intel.com Cc: netdev@oss.sgi.com, linux-kernel@vger.kernel.org Subject: Re: skb_padto and small fragmented transmits From: "David S. Miller" In-Reply-To: <1044559370.4620.36.camel@localhost.localdomain> References: <1044559370.4620.36.camel@localhost.localdomain> X-FalunGong: Information control. X-Mailer: Mew version 2.1 on Emacs 21.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org From: Chris Leech Date: 06 Feb 2003 11:22:51 -0800 I fail to see how the statement "skb->len + skb->data_len" has any usable meaning, or how it can be anything other than a bug. This equation is the standard way to find the full length on any skb. For linear skbs, data_len is always zero. I asked Alan to use this formula so that greps on the source tree would always show data_len being taken into account, and thus usage would be consistent.