From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pg0-f49.google.com (mail-pg0-f49.google.com [74.125.83.49]) by dpdk.org (Postfix) with ESMTP id 74A4E2B8C for ; Thu, 9 Mar 2017 03:18:59 +0100 (CET) Received: by mail-pg0-f49.google.com with SMTP id 25so20251411pgy.0 for ; Wed, 08 Mar 2017 18:18:59 -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=pBB73p/Kg7bTHqphu3/HCnv+1yO8/OaXuUM70wJ4Gik=; b=Gj0cZKQ6gSqwzzSKrYfuGvheErvl0/t3DoPAEq1LBmD8bSQg2QU3N8S0CLr+T8PEn8 qC+Yy4hrMku4G599Jk964UZm/0/qzS6f6Z6wQOECG5fn8k+TY9EcUH7Xz6kewvwerUS4 zGH7RTa9XdaPlMVxlL7yBz6lsgS+Ml9GL+KwsAYiINZ+RkICGrTmRVOP2F3Y5IZAEV5B kmqNvMw2qy84BwqyJMYJ9TOoF/bbNfMbYOAJFka1XILRxh/ww0RuYUuxGbW8xFxY5T2I qzo4yke9BLvdDvhdokr7nuTBPRqBrZqBhsbD1BfuX/EsHBppTqyC/ALXPWZPpV7T4pBd Q5VA== 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=pBB73p/Kg7bTHqphu3/HCnv+1yO8/OaXuUM70wJ4Gik=; b=Dz3LfzA/y4Nc4sysXiZaA0iV05Wd3jsOod4b+4/qpcry0Ykwsbc4cFKoxKgSY/RLax OkmtfINy1RbxjYj2J8OJrHgoYXVKhFBy0kvFkthX2i42LdPqU/TIKDiR3HvC6UE/Obk9 3/2QpzCOs3P9drVnVKiFy5Y3oMby7JVtmTICaXkRSW0v51N9CAXobFfY/aKprLdHIeoO uRgi4NYAqzSEyXaggl1wkYT++n9JWsFCPEr2qw1BomV6wfIJi1rEcygNp8qFvqy2/2yD TPrRjfc8HdmgyHtJf1a6izBqO0eNs82AWXLiG4RBaYna6PJEF4dLbZfj+FNAzoFjYt1/ U8gg== X-Gm-Message-State: AMke39k89ie0h1fr1YHrmm7vooZOas9QGmPwwTZlPlDFnfnuiLUHyIXifzhHotX7uchMWg== X-Received: by 10.98.44.15 with SMTP id s15mr11038881pfs.161.1489025938426; Wed, 08 Mar 2017 18:18:58 -0800 (PST) Received: from xeon-e3 (204-195-18-65.wavecable.com. [204.195.18.65]) by smtp.gmail.com with ESMTPSA id 10sm8457482pfs.113.2017.03.08.18.18.58 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 08 Mar 2017 18:18:58 -0800 (PST) Date: Wed, 8 Mar 2017 18:18:56 -0800 From: Stephen Hemminger To: Shyam Shrivastav Cc: users@dpdk.org Message-ID: <20170308181856.43e59d65@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] RSS : All fragments to same Recv queue 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: Thu, 09 Mar 2017 02:18:59 -0000 On Wed, 8 Mar 2017 21:20:57 +0530 Shyam Shrivastav wrote: > Hi > > We want to use RSS supported by intel 82599 NIC, with one lcore running on > each processor and handling one receive queue. All fragments of an ipv4 > packet need to go to same receive queue and handled by same lcore for > lockless reassembly. Looks like Intel 82599 supports RSS IPv4 hashing > using just source and dest address fields and that should put all fragments > on same queue ( can be enabled by ETH_RSS_IPV4 in rte_eth_rss_conf->rs_hf). > Please let me know whether my understanding is correct. > > Thanks > Shyam Yes as long as you keep port numbers out of the RSS hash it should work, but you may have to deal with fragments arriving over different paths. There is nothing in IP architecture that prevents multi-pathing.