From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pa0-f53.google.com (mail-pa0-f53.google.com [209.85.220.53]) by dpdk.org (Postfix) with ESMTP id B71885A3E for ; Mon, 27 Jul 2015 20:02:44 +0200 (CEST) Received: by pabkd10 with SMTP id kd10so55187334pab.2 for ; Mon, 27 Jul 2015 11:02: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 :content-type; bh=ujf1n11kSHrt8hFW6E14iRwguOOU57sHTuuEMUvBkiM=; b=UUIaSxbhyrBpQRGAYi5yMU8vUcI+cLCRUjDr4ZNjsjd49AlgCAlLDDSAp/VFN4e1ex la6c2Gg+EwKFnjbir1+tf7YM9hBlwwxulvjYKcW5cjBHoWeyEHXr8uVVoCE/GxdLZbaD Cou6in2CjSEbT4sbsvNIlN87/SuJNpLkHoJUfmb19dYhWDJImC1wtIkIIBTU9pdJqbc3 ejcNBP8SG787GusySrOoukPcQnZic3dTyTcRdKG1+hwqbYSmFtWCsC8b+C7KO0tM+WEO 7UJU3tBjRCpiKaLdDylBp3DrAEVHk9GW+lnFC63mR4wf8U8c0cnJKYl8XY8KpUovq+WN rLAA== X-Received: by 10.66.176.202 with SMTP id ck10mr60827973pac.15.1438020164047; Mon, 27 Jul 2015 11:02:44 -0700 (PDT) Received: from [204.57.7.4] ([204.57.7.4]) by smtp.googlemail.com with ESMTPSA id fi7sm30673198pdb.25.2015.07.27.11.02.42 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 27 Jul 2015 11:02:43 -0700 (PDT) Message-ID: <55B6729E.60104@gmail.com> Date: Mon, 27 Jul 2015 11:04:14 -0700 From: Masoud Moshref Javadi 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" Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jul 2015 18:02:45 -0000 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