From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dan@nyansa.com>
Received: from mail-pa0-f41.google.com (mail-pa0-f41.google.com
 [209.85.220.41]) by dpdk.org (Postfix) with ESMTP id 2199A5925
 for <dev@dpdk.org>; Mon, 24 Feb 2014 00:41:55 +0100 (CET)
Received: by mail-pa0-f41.google.com with SMTP id fa1so5757356pad.14
 for <dev@dpdk.org>; Sun, 23 Feb 2014 15:43:21 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:from:content-type:subject:message-id:date:to
 :mime-version;
 bh=l12v7bgSY20XEOTnD9w2g1rXA0/a6tvl1qbWEpCE6Pw=;
 b=HK4tIuBX+r+aNtnoRLL/qpx30ga0tjerDN+fPncr2QU3Rp4kt0tkHiaBxnIH7K5l2O
 sNhV6Efb+m/uP5KJBYmhJFjWubxg0Y7BMcu/HoBh7wIlcE49qUblzped8HhUZ5hbbuJO
 5mYG5xL+lA8I01oBWmEkYJDZamvbYvYbwoBfk3un7yoK4b1MVL/NCVp7zqQ4U5q1UCsB
 AzY21QvqVrqvVN5vH9wQ1BEcCvtNbcqjfRf3jqIXk82KhIxrGT+4pPEP/rSZfPZUM2f4
 mrVk4AMicUw/EGZ6CyZnRk61MvHi36GfSgZjuW7iBkqTXAuxbmjEs+kAI3UEnplDQn56
 pWkg==
X-Gm-Message-State: ALoCoQklTQT1gE4sLg0TEmoxiO2ZkuuCoxSkIr6vhbiGEUz6X4KpO09M6TEGLQZsrPWQGkFk7JGQ
X-Received: by 10.66.216.129 with SMTP id oq1mr21253627pac.75.1393199001205;
 Sun, 23 Feb 2014 15:43:21 -0800 (PST)
Received: from [192.168.1.80] (c-76-103-138-196.hsd1.ca.comcast.net.
 [76.103.138.196])
 by mx.google.com with ESMTPSA id qh2sm105436241pab.13.2014.02.23.15.43.19
 for <dev@dpdk.org>
 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
 Sun, 23 Feb 2014 15:43:20 -0800 (PST)
From: Daniel Kan <dan@nyansa.com>
Message-Id: <71503436-5A40-4097-B1B0-8ED0B9DB6C3E@nyansa.com>
Date: Sun, 23 Feb 2014 15:43:17 -0800
To: dev@dpdk.org
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
X-Mailer: Apple Mail (2.1827)
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: [dpdk-dev] What's the performance significance of
	ixgbe_recv_pkts_bulk_alloc
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Sun, 23 Feb 2014 23:41:56 -0000

Hi,
While browsing through the ixgbe pmd code, I noticed that there is =
ixgbe_recv_pkts_bulk_alloc, which can be enabled if the following =
preconditions are met.=20

     *   rxq->rx_free_thresh >=3D RTE_PMD_IXGBE_RX_MAX_BURST
     *   rxq->rx_free_thresh < rxq->nb_rx_desc
     *   (rxq->nb_rx_desc % rxq->rx_free_thresh) =3D=3D 0
     *   =
rxq->nb_rx_desc<(IXGBE_MAX_RING_DESC-RTE_PMD_IXGBE_RX_MAX_BURST)

I presume the difference from the normal (non bulk) version has to do =
with buffer allocation. Can someone please explain the inner working of =
bulk_alloc and why one may or may not want to enable bulk_alloc mode?=20

I only see bulk_alloc is available for ixgbe driver and not igb and =
e1000. Why is that?

Thanks.

Dan=