From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ie0-f176.google.com (mail-ie0-f176.google.com [209.85.223.176]) by dpdk.org (Postfix) with ESMTP id F091658DF for ; Thu, 9 Jan 2014 07:27:08 +0100 (CET) Received: by mail-ie0-f176.google.com with SMTP id at1so3046973iec.7 for ; Wed, 08 Jan 2014 22:28: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:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=BVd+oB1ZrUiv9RuQq/+ffmawyXMbL1o7rUcfy9e2VMw=; b=EDIPqdNcDXB1EOxpSiSmGuxM1BmogfcuY+2Fk/RhNAjsHQ6Pdzdwo2O5I80OAjalOa 8bg9Cv9Vi2wygN08yfloOG/UNtacU94S0A4OGLaatUbFU8nVForrnWsPCXZeqUv+uToE 0g5NYt5VQL3Tqzof1TZwbxZCfIRaedvZBnxwb3H+h5J6tP5Baw+lPMli5DKW0PxjJJcB 48UtrM0MtRjYWnHkXtCUF0W+XTBqILRkAbbN8CKH0XmlPnDVHARaWv9YItXT0m+4MxMa KaAmDuIhoKptlyBvrb+t+R/REAvLmt2eCPgvGCDdRMfQiIxMcXIRNH0i3IY/ppatRJwY ufRw== X-Gm-Message-State: ALoCoQlsrn8fwdMTD4GAJutnp5ZWa4z6H+ZpdZCKJYkL0MOhsPvUFsVOCqrLeeKK/XCB3RLKNG6K MIME-Version: 1.0 X-Received: by 10.50.100.170 with SMTP id ez10mr1611010igb.15.1389248900829; Wed, 08 Jan 2014 22:28:20 -0800 (PST) Received: by 10.64.8.140 with HTTP; Wed, 8 Jan 2014 22:28:20 -0800 (PST) In-Reply-To: <52CE22B7.8040904@neusoft.com> References: <52CE22B7.8040904@neusoft.com> Date: Wed, 8 Jan 2014 22:28:20 -0800 Message-ID: From: Stephen Hemminger To: chen_lp Content-Type: text/plain; charset=ISO-8859-1 Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] Does the rte_eth_tx_burst() function is multi-threaded safe when sending pkt in same port and same queue ? X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Jan 2014 06:27:09 -0000 The rx and tx functions are safe only if a queue is not shared by multiple threads (or the threads synchronize through some other mechanism). The safest design is to only use a queue on a single core. You will see different architectures in the examples. Some use one queue per core, and others use separate receive and transmit cores. On Wed, Jan 8, 2014 at 8:16 PM, chen_lp wrote: > > --------------------------------------------------------------------------------------------------- > Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s) > is intended only for the use of the intended recipient and may be confidential and/or privileged of > Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is > not the intended recipient, unauthorized use, forwarding, printing, storing, disclosure or copying > is strictly prohibited, and may be unlawful.If you have received this communication in error,please > immediately notify the sender by return e-mail, and delete the original message and all copies from > your system. Thank you. > ---------------------------------------------------------------------------------------------------