From owner-svn-src-all@freebsd.org Fri Jan 5 17:29:49 2018 Return-Path: Delivered-To: svn-src-all@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AF2EBEB5A29; Fri, 5 Jan 2018 17:29:49 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (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 7189173DB3; Fri, 5 Jan 2018 17:29:49 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1eXVoP-000Nah-SP; Fri, 05 Jan 2018 20:29:45 +0300 Date: Fri, 5 Jan 2018 20:29:45 +0300 From: Slawa Olhovchenkov To: Eugene Grosbein Cc: svn-src-head@freebsd.org, Steven Hartland , src-committers@freebsd.org, svn-src-all@freebsd.org Subject: Re: svn commit: r327559 - in head: . sys/net Message-ID: <20180105172945.GC5368@zxy.spb.ru> References: <201801042005.w04K5liB049411@repo.freebsd.org> <5A4E9397.9000308@grosbein.net> <20180105131105.GB5368@zxy.spb.ru> <5A4F7F70.5050106@grosbein.net> <20180105143825.GL19373@zxy.spb.ru> <5A4FAEF2.8000802@grosbein.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5A4FAEF2.8000802@grosbein.net> User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Jan 2018 17:29:49 -0000 On Fri, Jan 05, 2018 at 11:59:30PM +0700, Eugene Grosbein wrote: > 05.01.2018 21:38, Slawa Olhovchenkov wrote: > > >>> Irrelevant to RSS and etc. flowid distribution in lacp case work very > >>> bad. This is good and must be MFC (IMHO). > >> > >> It may work bad depending on NIC and/or traffic type. > >> It works just fine in common case of IP forwarding for packets with TCP/UDP inside. > >> > >> It can be easily disabled locally for specific cases when it does not work. > > > > Packet distrubuting on network equipment (lacp case) w/ enabled flowid cause > > uneven queue distributing. > > Once again: this heavily depends on local environment and this is not true for many cases. For any case resolving cavears need uncommon skills. It's true. Don't using flowid from hardware need negligible CPU power. Safe is disable flowid bDefault disable flowid is safe way w/o performace penalty.