From owner-freebsd-net@FreeBSD.ORG Tue Mar 15 02:44:36 2011 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 30647106566B for ; Tue, 15 Mar 2011 02:44:36 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-yi0-f54.google.com (mail-yi0-f54.google.com [209.85.218.54]) by mx1.freebsd.org (Postfix) with ESMTP id D9FAF8FC14 for ; Tue, 15 Mar 2011 02:44:35 +0000 (UTC) Received: by yie12 with SMTP id 12so69433yie.13 for ; Mon, 14 Mar 2011 19:44:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:date:to:cc:subject:message-id:reply-to :references:mime-version:content-type:content-disposition :in-reply-to:user-agent; bh=SJruwjlrzQDxujNggVc/GHAeMywuwEHVIqwIHB2tz9s=; b=bYkkQnIx9ovsRC66a4EqagzblXD4llNnZkJTMDL5al7cJixgL20diDNDJpJFEl7KdE zkEwNnEvG+7NcS9odv89rRdkh/esMS2KaCfNnC9xRHhsoyODd0sGzwPYzNCIrHTiaNex wiiFvqfZz4BmrzIH9H5bMrzZ/cnk7bQPskJzE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=VJsKtYdqs41n3bB8x3tDC+EQ7ifH6yAgx0S7RJrB2ZD0nivq44TZ9D/qbs3lLBEtqJ /bFJiUjxuwsgLeKm8aDk1cHdu4tXWG6kps2jc7sWChAjU5TcwWt0Y9wherGpJfQhkf95 1+ZlMa8NFPAGDOgfmr+QKo7NN25M2wMZV0RFk= Received: by 10.150.148.19 with SMTP id v19mr6729813ybd.349.1300157075125; Mon, 14 Mar 2011 19:44:35 -0700 (PDT) Received: from pyunyh@gmail.com ([174.35.1.224]) by mx.google.com with ESMTPS id p23sm2444418ybk.21.2011.03.14.19.44.32 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 14 Mar 2011 19:44:34 -0700 (PDT) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Mon, 14 Mar 2011 19:43:25 -0700 From: YongHyeon PYUN Date: Mon, 14 Mar 2011 19:43:25 -0700 To: Vijay Singh Message-ID: <20110315024325.GG1577@michelle.cdnetworks.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: freebsd-net@freebsd.org Subject: Re: Jumbo frame support for BGE_ASICREV_BCM5714 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Mar 2011 02:44:36 -0000 On Mon, Mar 14, 2011 at 05:54:29PM -0700, Vijay Singh wrote: > Hi all. I'm working off 7.1. Is there support for jumbo frames > available on bge(4) for BGE_ASICREV_BCM5714? > > regards, > vijay > > PS: my version of the code looks like this: > > case BGE_ASICREV_BCM5714_A0: > case BGE_ASICREV_BCM5780: > case BGE_ASICREV_BCM5714: > sc->bge_flags |= BGE_FLAG_5714_FAMILY /* | BGE_FLAG_JUMBO */; > /* FALLTHRU */ As you know, BCM5714, BCM5715 and BCM5780 use unique jumbo frame scheme that is not compatible with other controllers. All other Broadcom controllers have better jumbo frame scheme. These controllers have one send ring, one standard receive producer ring and one receive return ring. In order to receive jumbo frames on these controllers you have to increase Rx buffer size to hold 9k sized jumbo frame. Two Rx modes(standard Rx BDs and extended Rx BDs) are supported for these controllers. Using extended Rx BDs on BCM5714/BCM5715/BCM5780 reduces the number of Rx BDs to 256 entries which shall reduce the performance. I would use standard Rx BDs to hold 512 entries for RX buffers. I think I received jumbo frame support request for these controllers in past. At that time I had no interests on implementing it due to severe implementation differences. What is your main reason to use jumbo frame on this controller? What is your expectation on performance numbers? I guess no other OSes support jumbo frame on this controller.