From owner-freebsd-net@FreeBSD.ORG Thu Sep 8 16:28:23 2011 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E543D1065670; Thu, 8 Sep 2011 16:28:23 +0000 (UTC) (envelope-from kmacybsd@gmail.com) Received: from mail-ew0-f54.google.com (mail-ew0-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id EDF228FC18; Thu, 8 Sep 2011 16:28:22 +0000 (UTC) Received: by ewy1 with SMTP id 1so533147ewy.13 for ; Thu, 08 Sep 2011 09:28:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=JtHzWBhFaBsbyn4iJ26Y7T1x5K+/CUkY9p0Yo0UUVAQ=; b=tVJYY/a1FyoAlPeh17crmk4bdsU0rCXn3liiRtjDYuaBHkmKlTsTcYvPKMpazpFifx licevF7oFfAKWzKItLcQKyv8bzOUTN7DzkayYfP2f6jU3lzr5i7FRAIw3zsFy+I56Pht dlil6V5pHsnMqJA7GPO1n7GXWtk9WnlH4o8uM= MIME-Version: 1.0 Received: by 10.52.96.227 with SMTP id dv3mr965970vdb.230.1315499301480; Thu, 08 Sep 2011 09:28:21 -0700 (PDT) Sender: kmacybsd@gmail.com Received: by 10.52.113.169 with HTTP; Thu, 8 Sep 2011 09:28:21 -0700 (PDT) In-Reply-To: <1315498877.2804.10.camel@bwh-desktop> References: <201109080834.11607.jhb@freebsd.org> <201109081106.40714.jhb@freebsd.org> <1315498877.2804.10.camel@bwh-desktop> Date: Thu, 8 Sep 2011 18:28:21 +0200 X-Google-Sender-Auth: QrW52a0a4jANXgxaBjDW7HiIBf8 Message-ID: From: "K. Macy" To: Ben Hutchings Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Takuya ASADA , freebsd-net@freebsd.org, jfv@freebsd.org, John Baldwin , Navdeep Parhar Subject: Re: Adding Flow Director sysctls to ixgbe(4) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Sep 2011 16:28:24 -0000 > Whatever the mechanism is, the interface should allow for: > > - Flexible matching on layer 2, 3 and 4 header fields > - Masking out some bits before matching (e.g. ignoring priority bits of > =A0VLAN tag or least significant bits of IPv4 address) > - Priority of rules in case several match a single flow. =A0This may > =A0need to be combined with location, since in a TCAM location may > =A0determine priority. > - Requesting packets to be dropped, steered to a single RX queue, or > =A0steered to a range of RX queues (using a flow hash and indirection > =A0table) > - Use of multiple hash indirection tables Do you feel that the Linux API for this is the right place to start looking? Earlier you said: "The exact capabilities of the hardware are all quite different and we're still recovering from the early mistake of defining two subtly different interfaces." Have the two APIs been unified, if not which one do you believe is the "right" one? Cheers