From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pg0-f43.google.com (mail-pg0-f43.google.com [74.125.83.43]) by dpdk.org (Postfix) with ESMTP id 4D67429CA for ; Thu, 7 Dec 2017 00:05:21 +0100 (CET) Received: by mail-pg0-f43.google.com with SMTP id e14so3045056pgr.9 for ; Wed, 06 Dec 2017 15:05:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=n2LoI6a4lB3CYo0PDxpCNXer29vxVfYfFeQpemJKcdE=; b=XXSVx7uXTQr6e5hEA86o5jbzYSzt3bxWLh1Pl6V6/tJE2fDPJuYc74CprXapujASsy l5BGq/bTTaHnulay47C09qx+n8Ka/IILlJ+cWK22UhGwf/CJ890EruzLwlSWAf/BALEj lWRpQyQ+KPC6fCFAGWUwqaOSfpbTbj/DeiaQEpaACvKWwbDsJu/KALP2I0dIAK2hpmrl elh+6/i7NnudUzAj/SEQTuuAfsdimh1dWDKnD4Vw4iBFlg2rPvdAjGeBe7boQFRW+q+e utbRWajYSe/T8lHmZ9Bu7ElX//VQlK4EK1quwNPV77Gc6AbpoIUeUBoa3VbwBMDzcPTP 1/zA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=n2LoI6a4lB3CYo0PDxpCNXer29vxVfYfFeQpemJKcdE=; b=c3SweG9fnqKv1uNIUEmvM7Ou4VxuXL4d7x3Jds07ZKNoXRs/RLJD3MTHErkFgK3h39 E5sX6iO8WjywqyM0/nmNzl8x8y4btmNCtVQHID2eSG7ua455TExG3OvGJaXf/b/Q8y8M cGR6ACs2zts7RkVjqfYPyVfhI3cnRpAwjgOQF/Fi1z3aAe60VXAhSGF0mSGwwav71b7d kPxRzCyOjPslmTu6BlgOfCavuxvGYBCXkxJ55tfpNrq3bDqV0RCJtKmmPTo5AURbeeVb lVoMiQWdq/d3HRf95CRAHPM2waWAC8bZQFNpwx+7P5moTV4NWqkc5HPfYvVi8XDKeVa6 Vo/g== X-Gm-Message-State: AKGB3mIlnThpmglK5WtJpBOP5h5FWBd8iTzESa4zasGzECg/TekV9K0g r5h+XK1wdrf6LD3P4rNTcyyDYQ== X-Google-Smtp-Source: AGs4zMYuEBiIr2zLcDnh/MpKYDnf631EFtbMjbyRIOlLlIiMDPSN3hWHE5RZ9Jlk4nIhGnkOXqOVZw== X-Received: by 10.84.165.171 with SMTP id y40mr4403477pla.370.1512601520279; Wed, 06 Dec 2017 15:05:20 -0800 (PST) Received: from xeon-e3 (76-14-207-240.or.wavecable.com. [76.14.207.240]) by smtp.gmail.com with ESMTPSA id y20sm4921805pgc.52.2017.12.06.15.05.20 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 06 Dec 2017 15:05:20 -0800 (PST) Date: Wed, 6 Dec 2017 15:05:11 -0800 From: Stephen Hemminger To: "Dorsett, Michal" Cc: "users@dpdk.org" , "Maimon, Royi" , "Heijmans, Merav" Message-ID: <20171206150511.75ba1d12@xeon-e3> In-Reply-To: References: <20171205143431.79d47d61@xeon-e3> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-users] Round-robin instead of RSS X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Dec 2017 23:05:21 -0000 On Wed, 6 Dec 2017 06:43:02 +0000 "Dorsett, Michal" wrote: > I think my wording was not clear enough: > > Every packet that enters through the device will be delayed by our application for 1 second. > Given 10Gbps worth of traffic, for example, at an average packet size of 600 bytes, this is roughly 2M packets per second. > > A 710-series NIC makes use of 1M mbufs in a queue at the very most. In order for us to delay 2M packets, we need to create several queues per NIC. > I understand RSS is in the hardware, but hardware can be programmed, too, and hopefully turned off - and that's my question - whether, in addition to the RSS there is a round-robin policy that can be configured. > > Thanks, > > Michal What I was suggesting is keep an internal ring buffer of packets. Use a timer (rte_timer) to move the packets from ring buffer to device. If you poll timer at 1000 hz, that would only be 2000 packets per interval. The hardware queue can handle that. RSS only matters on receive. You can dump any packet in any Tx queue. On receive hardware supports: * all packets on single queue * packets spread across multiple queues by hash (RSS) * packets directed to queue based on flow (a.ka. Flow Director).