From owner-freebsd-current@FreeBSD.ORG Wed Jul 9 16:31:54 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 60690EFA; Wed, 9 Jul 2014 16:31:54 +0000 (UTC) Received: from mail-pa0-x22f.google.com (mail-pa0-x22f.google.com [IPv6:2607:f8b0:400e:c03::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2E3FE20ED; Wed, 9 Jul 2014 16:31:54 +0000 (UTC) Received: by mail-pa0-f47.google.com with SMTP id kq14so9365768pab.6 for ; Wed, 09 Jul 2014 09:31:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:mail-followup-to :references:mime-version:content-type:content-disposition :in-reply-to:user-agent; bh=AZ1R+HH2AMz2BYa6PfiTUQb4KUw21h7O4OCsUryvgwg=; b=bJ1VmnYoaH1t/xIghWBMTmqt0ZExVk893i8fQgKNIQ7D//CdKbw7uaDoGVE/wqtpn2 SjGb3gcO+WcccP8u3IvOFc3okgWSIwihBFkmA02RLOppIS5NEi0gSE4uDbWDBb0kStao Ac2d/3yaVJVqQwwa6aVcOes0GLfKAxLVb9qPVEq7JwCiH5J0zbQ7TQHAemtsGICXYyIP fS1xydUgCeUfzjMLpoUZr2EEhtFDevF7EenCqrktS4GAKZ3TtCczhq6qbyFSEr2WLiGt 59UWUaEDdefnKdfTqVv6qmIy/TC61gKvlLp3Xr1SbpsXO6pFrt3mxsEOV/BQO+MLk2H2 44Sw== X-Received: by 10.68.162.34 with SMTP id xx2mr16065213pbb.120.1404923513752; Wed, 09 Jul 2014 09:31:53 -0700 (PDT) Received: from ox ([24.6.44.228]) by mx.google.com with ESMTPSA id ob1sm29061125pdb.40.2014.07.09.09.31.52 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Wed, 09 Jul 2014 09:31:53 -0700 (PDT) Sender: Navdeep Parhar Date: Wed, 9 Jul 2014 09:31:46 -0700 From: Navdeep Parhar To: Hans Petter Selasky Subject: Re: [RFC] Add support for changing the flow ID of TCP connections Message-ID: <20140709163146.GA21731@ox> Mail-Followup-To: Hans Petter Selasky , freebsd-net@freebsd.org, FreeBSD Current References: <53BC2E73.6090700@selasky.org> <53BC43AE.3040409@FreeBSD.org> <53BD5385.4090208@selasky.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <53BD5385.4090208@selasky.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-net@freebsd.org, FreeBSD Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Jul 2014 16:31:54 -0000 On Wed, Jul 09, 2014 at 04:36:53PM +0200, Hans Petter Selasky wrote: > On 07/08/14 21:17, Navdeep Parhar wrote: ... > > > >I think we need to design this to be as generic as possible. I have > >quite a bit of code that does this stuff but I haven't pushed it > >upstream or even offered it for review (yet). > > > > Hi, > > When will the non hardware related patches be available for review? > I understand there are multiple ways to reach the same goal, and I > think it would be great if we could agree on a common API for > applications. Here is the kernel side of the patch: http://people.freebsd.org/~np/flow_pacing_kern.diff The registration parameters and the throttling parameters are probably cxgbe-centric, because that's what it was written for. We'll need to tidy up those structs certainly. And I'd like to add pps constraints to the throttling parameters (all it does is bandwidth right now). Regards, Navdeep