From owner-freebsd-net@freebsd.org Thu Apr 20 18:28:44 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 70ED9D48791 for ; Thu, 20 Apr 2017 18:28:44 +0000 (UTC) (envelope-from vijju.singh@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 4F1513C4 for ; Thu, 20 Apr 2017 18:28:44 +0000 (UTC) (envelope-from vijju.singh@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 4B8F5D48790; Thu, 20 Apr 2017 18:28:44 +0000 (UTC) Delivered-To: net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4B2B9D4878F for ; Thu, 20 Apr 2017 18:28:44 +0000 (UTC) (envelope-from vijju.singh@gmail.com) Received: from mail-lf0-x22a.google.com (mail-lf0-x22a.google.com [IPv6:2a00:1450:4010:c07::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C58103C3; Thu, 20 Apr 2017 18:28:43 +0000 (UTC) (envelope-from vijju.singh@gmail.com) Received: by mail-lf0-x22a.google.com with SMTP id 75so33553572lfs.2; Thu, 20 Apr 2017 11:28:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=NTKJn1kBCkRwSjw0qcso4J4KCupxrHWXNx9edAseRU0=; b=Nkf7K7G7446S45ljlRiT9NQG3/V/OuVyd3cpfhe6HddUx4H7KIOGImwXJgS2RIGWvF 1R+HPT8SKr9MikL9/kE0rlXqXb8ZjN5EqNLKarJBFA+BiGuF3kRH9HZox1FtYQx7DlVR lpvFrKLbADUz1iLkevqR9C09LLS4xzD7milCQJSTjbYKKf/HllHybTkOgNxOVyKGmCmW mfW6nr7IupQOqx65VNusNLlFlLQamWDbFfngQrrqsE2MqtoYoeNq+T6TS5v4rv7gh+3c QQi3t2oZiwvZi8vq039seUp5WGBVOzsi9Ud8H/9eNiq5KJPXh3Aobrg1zUnRWa9fMgGk JWbQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=NTKJn1kBCkRwSjw0qcso4J4KCupxrHWXNx9edAseRU0=; b=IEc9w2xKE4/ztqjuN6tFrkgArft9SP7lw8gQP492X1oo2LPs3BSa8phvoqDD1H9cKs PySS/06j/S4qC+L0opIjwFCb5OtJPRjLnxaOASb4xaPu8aESLwFUHImgWh6LoL3ZlTui gXWZJoAYyb6ja5K5EQVNieJAdQEttPhiYcShYLDqpX804iDbJ4AMRoGtb51YzSLsOa9I EpC8cGwSIGQvw5cbzRkUpSDQ3TTCwaZjAr7LAnbQLTl75RfC7Wnn9+qp9Vvmv3g/e5Gu SjyHKB9zw2gdIF5WJjbJOP2eNSrLdjQVnHv0U8m9PZeGndT3JyjF5NGykC4AZpaDFDzm W0tw== X-Gm-Message-State: AN3rC/6T5YzeSjGyamOrWsu6//hDboRSwo41Zcgr6c91/jvhorQwj8c3 cdXs1SMR4IlR8oebHds3jAzybvyOTw== X-Received: by 10.25.233.213 with SMTP id j82mr3363161lfk.20.1492712921579; Thu, 20 Apr 2017 11:28:41 -0700 (PDT) MIME-Version: 1.0 Received: by 10.25.29.130 with HTTP; Thu, 20 Apr 2017 11:28:41 -0700 (PDT) In-Reply-To: References: <793b585e-8af4-56e3-97eb-942efbc8d06c@freebsd.org> From: Vijay Singh Date: Thu, 20 Apr 2017 11:28:41 -0700 Message-ID: Subject: Re: Intel 82545 & TSO To: Sean Bruno Cc: "freebsd-net@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Apr 2017 18:28:44 -0000 Sure I can do that, but I don't have control over the ESX systems we are running on. If the hardware supports TSO, then it shouldn't be too hard to supplement "lem" to support it as well. The descriptor format seems to be the same, so most likely copying over some code from "em" should do it. On Thu, Apr 20, 2017 at 10:55 AM, Sean Bruno wrote: > > > On 04/05/17 15:54, Vijay Singh wrote: > > This is from FreeBSD 10.3. > > > > On Wed, Apr 5, 2017 at 2:53 PM, Sean Bruno > > wrote: > > > > > > > > On 04/05/17 10:26, Vijay Singh wrote: > > > I am running FreeBSD as a guest on ESX 5.x and see Intel device > > 0x100F in > > > the guest. The man page for em(4) says: > > > > > > " The driver supports Transmit/Receive checksum offload and Jumbo > > > Frames on all but 82542-based adapters. Furthermore it supports TCP > > > segmentation offload (TSO) on all adapters but those based on the > > > 82543, 82544 and 82547 controller chips." > > > > > > This particular device is probed by the if_lem.c driver, but I see > no > > > support for TSO in that file. I have verified that TSO is enabled > on > > > the host. What am I missing? > > > > > > em0@pci0:2:0:0: class=0x020000 card=0x075015ad chip=0x100f8086 > > rev=0x01 hdr=0x00 > > > vendor = 'Intel Corporation' > > > device = '82545EM Gigabit Ethernet Controller (Copper)' > > > class = network > > > subclass = ethernet > > > > > > ifconfig -vvvm em0 > > > em0: flags=8843 metric 0 > > mtu 1500 > > > > > options=8009b HWCSUM,LINKSTATE> > > > > > capabilities=9009b HWTAGGING,VLAN_HWCSUM,VLAN_HWFILTER,LINKSTATE> > > > ether 02:a0:98:ec:26:1d > > > media: Ethernet autoselect (1000baseT ) > > > status: active > > > supported media: > > > media autoselect > > > media 100baseTX mediaopt full-duplex > > > media 100baseTX > > > media 10baseT/UTP mediaopt full-duplex > > > media 10baseT/UTP > > > > > > > > > -vijay > > > _______________________________________________ > > > > Just so that I'm sure, what version of FreeBSD is this from? > > > > sean > > > > > > I believe this a confusion from the fact that the 82545EM is controled > by the "lem" driver and not the "em" driver. > > The "lem" driver does not support TSO. > > If you want TSO support, you should be able to use a different ethernet > card model in ESX, no? > > sean > >