From owner-freebsd-current@FreeBSD.ORG  Wed Nov 19 19:35:28 2014
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 00B98D91;
 Wed, 19 Nov 2014 19:35:27 +0000 (UTC)
Received: from mail.turbocat.net (mail.turbocat.net
 [IPv6:2a01:4f8:d16:4514::2])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id B48C991B;
 Wed, 19 Nov 2014 19:35:27 +0000 (UTC)
Received: from laptop015.home.selasky.org
 (cm-176.74.213.204.customer.telag.net [176.74.213.204])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (No client certificate requested)
 by mail.turbocat.net (Postfix) with ESMTPSA id 7B87A1FE023;
 Wed, 19 Nov 2014 20:35:25 +0100 (CET)
Message-ID: <546CF114.2050309@selasky.org>
Date: Wed, 19 Nov 2014 20:35:48 +0100
From: Hans Petter Selasky <hps@selasky.org>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
 rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: Adrian Chadd <adrian@freebsd.org>
Subject: Re: [RFC] Removal of M_FLOWID flag from m_flags [WAS: Add support
 for hardware transmit rate limiting queues]
References: <546CE948.2070105@selasky.org>
 <CAJ-VmokR-diHyDjETwQ8k5koY3cPQ=PHtfeqpkC7rHyrZb1FTQ@mail.gmail.com>
 <546CEEAB.7000207@selasky.org>
 <CAJ-Vmom3_gt-=sXsByO4Frw6FjLXZAitGH5=MOuaVvoZsQEnFg@mail.gmail.com>
In-Reply-To: <CAJ-Vmom3_gt-=sXsByO4Frw6FjLXZAitGH5=MOuaVvoZsQEnFg@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Lawrence Stewart <lstewart@freebsd.org>,
 FreeBSD Current <freebsd-current@freebsd.org>,
 Luigi Rizzo <rizzo@iet.unipi.it>, Navdeep Parhar <np@freebsd.org>
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Nov 2014 19:35:28 -0000

On 11/19/14 20:32, Adrian Chadd wrote:
> The RSS hash is also used for:
>
> * TCP timers,
> * UDP transmit, and
> * the transmit path in RSS aware drivers (igb / ixgbe)
>

I know, and the RSS flowid values are still preserved as before in the 
receive path. It is just about how you tell the upper/lower layers that 
there is something in the "m_pkthdr.flowid" which they can use to 
accelerate traffic.

--HPS