From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <masood.moshref.j@gmail.com>
Received: from mail-pd0-f176.google.com (mail-pd0-f176.google.com
 [209.85.192.176]) by dpdk.org (Postfix) with ESMTP id 2E23FC5A8
 for <dts@dpdk.org>; Tue, 28 Jul 2015 00:45:45 +0200 (CEST)
Received: by pdbbh15 with SMTP id bh15so59048161pdb.1
 for <dts@dpdk.org>; Mon, 27 Jul 2015 15:45:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=message-id:date:from:user-agent:mime-version:to:subject:references
 :in-reply-to:content-type;
 bh=kRe7ZSDKlBWJPb60t4+P6IQz8vYoId7g0gmlTsLd1/I=;
 b=A1AuSneMMr6uV5tHvuW+Hvc5l+xAR6XEBjwMbp6ojSMQYiyU319zkvsQMmPW6+ajZ8
 44Bc2VqkvfxqD4omBXccqRPZPfpITXvsTF3DCtsh8qu8CH3VIsmL7woPakQdtPXKZ0gZ
 cWdpCBdKhviAGLxTcMcBImSiyhhQcW87UBXj7EXnVf6IXgFMM7HQRaWAorrsI4MeDYKd
 HbLNLNjH3OHLmCz6WCEu0kGSCcvNOJHiZrPsGdP4TQaMRan10J0AH6dM0MXBAd4++GuM
 JGDPJXzlSuHC59QsdW1kPAEVC8lnIeKya/Hx0hOIhYn5LLwnyPFAtC0C0Kmfp6xu240x
 /umw==
X-Received: by 10.70.90.67 with SMTP id bu3mr72000356pdb.2.1438037144513;
 Mon, 27 Jul 2015 15:45:44 -0700 (PDT)
Received: from [204.57.7.4] ([204.57.7.4])
 by smtp.googlemail.com with ESMTPSA id wc8sm6503670pab.45.2015.07.27.15.45.43
 for <dts@dpdk.org>
 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
 Mon, 27 Jul 2015 15:45:43 -0700 (PDT)
Message-ID: <55B6B4F2.4040408@gmail.com>
Date: Mon, 27 Jul 2015 15:47:14 -0700
From: Masoud Moshref Javadi <masood.moshref.j@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: "dts@dpdk.org" <dts@dpdk.org>
References: <55B6729E.60104@gmail.com>
In-Reply-To: <55B6729E.60104@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: Re: [dts] The semantics of rte_eth_rx_burst and
	rte_eth_rx_queue_count
X-BeenThere: dts@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: test suite reviews and discussions <dts.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dts>,
 <mailto:dts-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dts/>
List-Post: <mailto:dts@dpdk.org>
List-Help: <mailto:dts-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dts>,
 <mailto:dts-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jul 2015 22:45:45 -0000

Thanks
I figured that out by looking at the source code.

On 7/27/2015 11:04 AM, Masoud Moshref Javadi wrote:
> Hi,
>
> I don't understand the semantics of these two methods 
> (rte_eth_rx_burst and rte_eth_rx_queue_count).
>
> For rte_eth_rx_burst with burst of B.
>
>   * Does that mean it will not return until it receive at least B
>     packets? or it just returns with whatever packets that are in the
>     NIC's queue?
>   * Does that mean it will wait at least x clocks before returning 0
>     to B packets?
>
> For rte_eth_rx_queue_count:
>
>   * Does it go to the NIC and poll the # filled entries at its queue?
>     if yes, how much is its overhead?
>   * Do we need to call rte_eth_rx_burst (or similar methods) to make
>     it updated?
>
>
> Regards
>