From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pg0-f45.google.com (mail-pg0-f45.google.com [74.125.83.45]) by dpdk.org (Postfix) with ESMTP id 6B95B397D for ; Tue, 5 Dec 2017 23:34:39 +0100 (CET) Received: by mail-pg0-f45.google.com with SMTP id w7so1195330pgv.6 for ; Tue, 05 Dec 2017 14:34:39 -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=7EzrJU2c2I4rK5JY/1EN/jqHmiafSQcx6LE/0Hqats4=; b=N9eA3NqHc75R+MtA5FLTB7MyEtpDA4J524JiJhJwAXEZNR6OwYFlrVMQvsgQptX2mr 8atyEMbezGFt3z5KsYeqiRWmIOYG9BqkhgwqGoBmKIROuRYGRdFnuqiLZE7S7QNu8x5C 8SpIVupaH35bKGYhzJxa1m0VuoUG5K/TEBkc61o3IL81S6x5j50R2WQEDzpTKgOEsl33 fWL4sEcrJFZCYgnxTSRZu5jgY8u2PZ3EaHecS1pGUkbX4e4L8PdCr6q7/bUzBSlEefAx EDRKzcG9ejocMU9hIXysZaf2Kmj2Q80G/odx9nu/hdR+6om7EsgL/E9pR1CN+G+qLPmJ BeuA== 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=7EzrJU2c2I4rK5JY/1EN/jqHmiafSQcx6LE/0Hqats4=; b=sPBY95aw4lIKJciQBZM5h79Lx5OuNR+tAH2DdBecWgt9jfmuQq92GVHg02QnmHs2mJ GkXHvAfoAFRlCUe/ILd/8MVWE/R/bz4saiNJX2mgTsuBZ5T81t27WYfJB/9iin7nOhWi 74tr+hPXX60baL+IVtOEhYTegDlJameN5e/2QvoSz37PNcTSdIZ7MAIDnYkYpq9iS/HZ bMy6iAXrsfdh+RV4eZcNEaS94oJ+fHNBgdOVsD3pVRY4ZxvsfQwj+ywkr35EJ/jtAKh3 EUh8Xf0fkdIoj4gT/MO9obGStG9ppnVLWQgLGF/8aDO0960aJWciJ4AwGOC4UEcM62Vo Tdsw== X-Gm-Message-State: AJaThX6/an2YQSQEaRzRpN6UrmQYcJThsycfFSx34KCS4gd1ZAnsLs2/ AaSqfV16IFk4nenXxiETCn9Cvw== X-Google-Smtp-Source: AGs4zMZPKzhIkgwr63LOgxX1pfkGlpw6rWtxUzP0wxIp1qhX8y/e1K6R/ibbxtKZBgg36CMOFu/jdQ== X-Received: by 10.101.97.75 with SMTP id o11mr18654914pgv.363.1512513278486; Tue, 05 Dec 2017 14:34:38 -0800 (PST) Received: from xeon-e3 (76-14-207-240.or.wavecable.com. [76.14.207.240]) by smtp.gmail.com with ESMTPSA id 83sm1976384pfq.12.2017.12.05.14.34.38 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 05 Dec 2017 14:34:38 -0800 (PST) Date: Tue, 5 Dec 2017 14:34:31 -0800 From: Stephen Hemminger To: "Dorsett, Michal" Cc: "users@dpdk.org" , "Maimon, Royi" Message-ID: <20171205143431.79d47d61@xeon-e3> In-Reply-To: References: 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: Tue, 05 Dec 2017 22:34:39 -0000 On Tue, 5 Dec 2017 21:23:23 +0000 "Dorsett, Michal" wrote: > We are using an XL710 nic 4x10Gbps. > Our application needs to delay all packets in the system for at least the first second, and depending on the type of traffic mbufs may need to delay packets even more. > > Since the XL710 makes use of, at most, 1M mbufs in a queue and not more - we need to create several queues that provide enough mbufs for the nic not to starve. > > Because we handle extremely varied traffic, we may not be able to statically configure an RSS to load balance traffic evenly between the queues. > > Is it possible to set up a round-robin policy between the queues instead of RSS? > I realize the drawbacks - un-orderliness, etc. - but please assume we have our methods of handling those specific issues. > > Thanks, > > Michal Dorsett > Developer, Strategic IP Group > Desk: +972 962 4350 > Mobile: +972 50 771 6689 > Verint Cyber Intelligence > www.verint.com I don't work for Intel team and don't have XL710. But although XL710 may have limited hardware queue depth, there is no requirement that you give all the mbuf's directly to XL710 at once. If you have to hold off traffic, then just don't pass it to the device. RSS is built in the hardware.