From owner-freebsd-net@freebsd.org Sun Jan 8 00:08:33 2017 Return-Path: Delivered-To: freebsd-net@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 17DB1C95486 for ; Sun, 8 Jan 2017 00:08:33 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 070871B5A for ; Sun, 8 Jan 2017 00:08:33 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v0808Wfx075938 for ; Sun, 8 Jan 2017 00:08:32 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 193075] netmap: attaching to 'vale0' with netmap-libpcap causes a kernel panic Date: Sun, 08 Jan 2017 00:08:33 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: hiren@FreeBSD.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: Overcome By Events X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc resolution assigned_to bug_status Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Jan 2017 00:08:33 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D193075 Hiren Panchasara changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |luigi@FreeBSD.org Resolution|--- |Overcome By Events Assignee|freebsd-bugs@FreeBSD.org |freebsd-net@FreeBSD.org Status|New |Closed --- Comment #1 from Hiren Panchasara --- Please reopen if this is still a problem for your on latest -HEAD/11 with updated netmap. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Sun Jan 8 03:51:28 2017 Return-Path: Delivered-To: freebsd-net@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 149C0CA54F5 for ; Sun, 8 Jan 2017 03:51:28 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 D027012F1 for ; Sun, 8 Jan 2017 03:51:27 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v083pQ32011462 for ; Sun, 8 Jan 2017 03:51:27 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 213869] when setting an ipsec policy with spdadd src[port], outbound traffic from 2049/tcp is not encrypted Date: Sun, 08 Jan 2017 03:51:26 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: jasonmader@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Jan 2017 03:51:28 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213869 --- Comment #9 from Jason Mader --- Comment on attachment 178602 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D178602 Proposed patch (untested) This worked for me. root@safety:/usr/src/sys/netipsec # patch < ~/ipsec.c.diff Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |Index: sys/netipsec/ipsec.c |=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D |--- sys/netipsec/ipsec.c (revision 311647) |+++ sys/netipsec/ipsec.c (working copy) -------------------------- Patching file ipsec.c using Plan A... Hunk #1 succeeded at 241. Hunk #2 succeeded at 344 (offset 1 line). Hunk #3 succeeded at 501 (offset 1 line). Hunk #4 succeeded at 511 (offset 1 line). done root@safety:~ # setkey -DP fe80::%em0/64[any] fe80::a00:27ff:fefc:de09%em0[2049] tcp in ipsec esp/transport//require spid=3D1 seq=3D1 pid=3D806 refcnt=3D1 fe80::a00:27ff:fefc:de09%em0[2049] fe80::%em0/64[any] tcp out ipsec esp/transport//require spid=3D2 seq=3D0 pid=3D806 refcnt=3D1 I was able to NFSv4 mount a filesystem, and tcpdump is showing me that everything is ESP. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Sun Jan 8 12:40:54 2017 Return-Path: Delivered-To: freebsd-net@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 E2D94CA5605 for ; Sun, 8 Jan 2017 12:40:54 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 D21591B15 for ; Sun, 8 Jan 2017 12:40:54 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v08CerG2083063 for ; Sun, 8 Jan 2017 12:40:54 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 213869] when setting an ipsec policy with spdadd src[port], outbound traffic from 2049/tcp is not encrypted Date: Sun, 08 Jan 2017 12:40:54 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: commit-hook@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Jan 2017 12:40:55 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213869 --- Comment #10 from commit-hook@freebsd.org --- A commit references this bug: Author: ae Date: Sun Jan 8 12:40:08 UTC 2017 New revision: 311679 URL: https://svnweb.freebsd.org/changeset/base/311679 Log: Add direction argument to ipsec_setspidx_inpcb() function. This function is used only by ipsec_getpolicybysock() to fill security policy index selector for locally generated packets (that have INPCB). The function incorrectly assumes that spidx is the same for both directio= ns. Fix this by using new direction argument to specify correct INPCB security policy - sp_in or sp_out. There is no need to fill both policy indeces, because they are overwritten for each packet. This fixes security policy matching for outbound packets when user has specified TCP/UDP ports in the security policy upperspec. PR: 213869 MFC after: 1 week Changes: head/sys/netipsec/ipsec.c --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Sun Jan 8 18:48:18 2017 Return-Path: Delivered-To: freebsd-net@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 43CA3CA5A46 for ; Sun, 8 Jan 2017 18:48:18 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-pf0-x232.google.com (mail-pf0-x232.google.com [IPv6:2607:f8b0:400e:c00::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 14A81177B for ; Sun, 8 Jan 2017 18:48:18 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-pf0-x232.google.com with SMTP id f144so15325164pfa.2 for ; Sun, 08 Jan 2017 10:48:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=jEaeCAoPN1Hn+gI5AsBM4y9nnLI1FxOH49Wv/WvjEnM=; b=odb7ar/TZ+k4VqFki2poCm4qwvRmgtkzdon0tXX5Yow98FmpSgZ2f3z7tHQ2r5xfnO uXivTyxSATH6XVsCiOGX39DHtV2nlNxh6rJwMnlMA9bxcHrdEmOjthUNmDPvujBgcNSf //rr8huhnRNCXoZl0UCT5/ARFW9gf7xCLy9UMJVZrTZEp7aJvLyU3LlNsvo4hHKA39dO xlRblNFkBpZLZHhHnr8SaIoZqdhp8R+aTAHqPGbbKdoDZjQktfIogd7ptdtcCmaFQy1q 2Yb1mgI1HCuUCO62njjvQbGZ3A9SvCP75uADAcPFKueQJOVIjI8QrZbzFLwargk1UxT7 Hnaw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=jEaeCAoPN1Hn+gI5AsBM4y9nnLI1FxOH49Wv/WvjEnM=; b=on3Fi3xvaKyDjgpUiieOb0dYwkQuv+1F/ciqIsJ7eX2doW7347QWf66Te5UD0X0FLK ZT/NnLKWSSDoRJ3Yi+ZAA83cwDT/LwtfT+pbNuZjyeLWqijzl3s9AdZL4tSgp0b+LlVM mRIa84gHS6bwFjak/1syjCkWbYRYOd7uRqx2rJ3fUQz7NDQ4vwItxkG2sPEpNeVzUEVk C9QLAPQaWRAQz9f71tCNXeKzOOC2IFQay4SE+86fbUpH6Vf0u8Fcch/7CElT0t2e7+lJ 6WkG58m2UVNopjCuEvKMWPS5jk3LB0eB7CARYbKAlQnwkK1byXXEyZKFmzcWxKIc4lPh aYrw== X-Gm-Message-State: AIkVDXJLTSxSRRia1PrMrBP6xPfj8c82wzAd31WYvthLJlZmLZWpPOrq8NVFlXsK87UHyg== X-Received: by 10.84.238.201 with SMTP id l9mr44860749pln.168.1483901297750; Sun, 08 Jan 2017 10:48:17 -0800 (PST) Received: from raichu ([2604:4080:1102:0:ca60:ff:fe9d:3963]) by smtp.gmail.com with ESMTPSA id e1sm158841146pga.37.2017.01.08.10.48.17 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 08 Jan 2017 10:48:17 -0800 (PST) Sender: Mark Johnston Date: Sun, 8 Jan 2017 10:48:15 -0800 From: Mark Johnston To: Jim Cc: freebsd-net@freebsd.org Subject: Re: Panic in nd6_prefix_offlink() Message-ID: <20170108184815.GB34440@raichu> References: <20170107201119.22d9ceff88e935c2b3f072a1@bitmessage.ch> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170107201119.22d9ceff88e935c2b3f072a1@bitmessage.ch> User-Agent: Mutt/1.7.2 (2016-11-26) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Jan 2017 18:48:18 -0000 On Sat, Jan 07, 2017 at 08:11:19PM +0100, Jim wrote: > Hello, > > I observe frequent crashes on Beagle Bone Black running CURRENT r311106 at home. > My home LAN is connected to DSL provider. The CPE router gets assigned IPv6 address (ds-lite) and advertises prefix/route to the LAN. > Every night the DSL connection is terminated by provider. Upon connection is reestablished the new IPv6 prefix is assigned to router and then advertised to LAN. > This event seems to cause kernel panic on Beagelebone board which goes to db> prompt. > > Backtrace shows: nd6_timer() -> nd6_prefix_offlink() -> witness_assert() -> vpanic() > Here is the backtrace: Thanks for the report. This should be addressed by r311695. From owner-freebsd-net@freebsd.org Sun Jan 8 19:33:54 2017 Return-Path: Delivered-To: freebsd-net@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 0D168CA5919 for ; Sun, 8 Jan 2017 19:33:54 +0000 (UTC) (envelope-from punasipuli@t-online.de) Received: from mailout06.t-online.de (mailout06.t-online.de [194.25.134.19]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mailout00.t-online.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C8645190A for ; Sun, 8 Jan 2017 19:33:53 +0000 (UTC) (envelope-from punasipuli@t-online.de) Received: from fwd14.aul.t-online.de (fwd14.aul.t-online.de [172.20.26.242]) by mailout06.t-online.de (Postfix) with SMTP id 88B9141D6750 for ; Sun, 8 Jan 2017 20:33:44 +0100 (CET) Received: from [192.168.10.43] (EYxJz8ZBohxgB9mgm49ahCIY8MEUOx7XxC3nPUyA0lwOAokUX3BslSTlSsbX40Zwzo@[86.56.56.128]) by fwd14.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-SHA encrypted) esmtp id 1cQJDs-1tRo7E0; Sun, 8 Jan 2017 20:33:44 +0100 To: freebsd-net@freebsd.org From: diffusae Subject: Gigabit USB NIC for RPi Message-ID: <03145169-f546-01f7-e701-c76118b76bb9@t-online.de> Date: Sun, 8 Jan 2017 20:33:43 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-ID: EYxJz8ZBohxgB9mgm49ahCIY8MEUOx7XxC3nPUyA0lwOAokUX3BslSTlSsbX40Zwzo X-TOI-MSGID: 08d359c1-9101-4e3a-b848-f1e2c4dead9b X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Jan 2017 19:33:54 -0000 Hi! I am looking for an compatible USB2Gigabit ethernet adapter for a RPi. That should work with the ISO Images of FreeBSD 11 stable (armv6). Do you have any suggestions? Thanks in advance Regards, From owner-freebsd-net@freebsd.org Sun Jan 8 20:21:22 2017 Return-Path: Delivered-To: freebsd-net@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 A8C61CA5E44 for ; Sun, 8 Jan 2017 20:21:22 +0000 (UTC) (envelope-from BM-2cWfdfG5CJsquqkJyry7hZT9LypbSEWEkQ@bitmessage.ch) Received: from mail.bitmessage.ch (mail.bitmessage.ch [146.228.112.252]) (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 E69011C68; Sun, 8 Jan 2017 20:21:21 +0000 (UTC) (envelope-from BM-2cWfdfG5CJsquqkJyry7hZT9LypbSEWEkQ@bitmessage.ch) dkim-signature: v=1; a=rsa-sha256; d=bitmessage.ch; s=mail; c=relaxed/relaxed; q=dns/txt; h=From:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type:Content-Transfer-Encoding:In-Reply-To:References; bh=X5W5RelOVtIwL6rFZpuRVTmYPfgnyepG8cj1FLHcirw=; b=cGeNwsEUM+Dn43jhC8w+LYbESMqSZCnlGp5/y6vMr0tHi/0AuNujalTRoLAlm+NHuYcP2OZOt5kGox9/XmhoNDdpcAMiiCKFUYdmQYb/1wQQ5+LsDoAkJE0JUzAo9W7VW7/l/IZEvBZxhNWPwxHoDChKisACfsc7sCCR7koLJUc= Received: from lion.3 (149-13-91-98.pool.ovpn.se [149.13.91.98]) by mail.bitmessage.ch with ESMTPSA (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256) ; Sun, 8 Jan 2017 21:20:34 +0100 Date: Sun, 8 Jan 2017 21:21:11 +0100 From: Jim To: Mark Johnston Cc: freebsd-net@freebsd.org Subject: Re: Panic in nd6_prefix_offlink() Message-Id: <20170108212111.4619c442fb8c24bf0d3f5253@bitmessage.ch> In-Reply-To: <20170108184815.GB34440@raichu> References: <20170107201119.22d9ceff88e935c2b3f072a1@bitmessage.ch> <20170108184815.GB34440@raichu> X-Mailer: Sylpheed 3.5.1 (GTK+ 2.24.29; amd64-portbld-freebsd10.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Jan 2017 20:21:22 -0000 On Sun, 8 Jan 2017 10:48:15 -0800 Mark Johnston wrote: > On Sat, Jan 07, 2017 at 08:11:19PM +0100, Jim wrote: > > Hello, > > > > I observe frequent crashes on Beagle Bone Black running CURRENT r311106 at home. > > My home LAN is connected to DSL provider. The CPE router gets assigned IPv6 address (ds-lite) and advertises prefix/route to the LAN. > > Every night the DSL connection is terminated by provider. Upon connection is reestablished the new IPv6 prefix is assigned to router and then advertised to LAN. > > This event seems to cause kernel panic on Beagelebone board which goes to db> prompt. > > > > Backtrace shows: nd6_timer() -> nd6_prefix_offlink() -> witness_assert() -> vpanic() > > Here is the backtrace: > > Thanks for the report. This should be addressed by r311695. Great! Thanks for your attention and time. BR From owner-freebsd-net@freebsd.org Sun Jan 8 21:00:18 2017 Return-Path: Delivered-To: freebsd-net@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 2D036CA65A0 for ; Sun, 8 Jan 2017 21:00:18 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 240BC162A for ; Sun, 8 Jan 2017 21:00:18 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v08L01n0092914 for ; Sun, 8 Jan 2017 21:00:18 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201701082100.v08L01n0092914@kenobi.freebsd.org> From: bugzilla-noreply@FreeBSD.org To: freebsd-net@FreeBSD.org Subject: Problem reports for freebsd-net@FreeBSD.org that need special attention Date: Sun, 08 Jan 2017 21:00:18 +0000 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Jan 2017 21:00:18 -0000 To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- In Progress | 165622 | [ndis][panic][patch] Unregistered use of FPU in k In Progress | 203422 | mpd/ppoe not working with re(4) with revision 285 In Progress | 206581 | bxe_ioctl_nvram handler is faulty New | 204438 | setsockopt() handling of kern.ipc.maxsockbuf limi New | 205592 | TCP processing in IPSec causes kernel panic New | 206053 | kqueue support code of netmap causes panic New | 213410 | [carp] service netif restart causes hang only whe Open | 193452 | Dell PowerEdge 210 II -- Kernel panic bce (broadc Open | 194485 | Userland cannot add IPv6 prefix routes Open | 194515 | Fatal Trap 12 Kernel with vimage Open | 199136 | [if_tap] Added down_on_close sysctl variable to t Open | 202510 | [CARP] advertisements sourced from CARP IP cause Open | 206544 | sendmsg(2) (sendto(2) too?) can fail with EINVAL; Open | 211031 | [panic] in ng_uncallout when argument is NULL Open | 211962 | bxe driver queue soft hangs and flooding tx_soft_ Open | 212018 | Enable IPSEC_NAT_T in GENERIC kernel configuratio 16 problems total for which you should take action. From owner-freebsd-net@freebsd.org Sun Jan 8 21:57:50 2017 Return-Path: Delivered-To: freebsd-net@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 7BBFBCA62BB for ; Sun, 8 Jan 2017 21:57:50 +0000 (UTC) (envelope-from Mark.Martinec+freebsd@ijs.si) Received: from mail.ijs.si (mail.ijs.si [IPv6:2001:1470:ff80::25]) (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 38F4E1920 for ; Sun, 8 Jan 2017 21:57:50 +0000 (UTC) (envelope-from Mark.Martinec+freebsd@ijs.si) Received: from amavis-ori.ijs.si (localhost [IPv6:::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.ijs.si (Postfix) with ESMTPS id 3txXG24ZMcz1Wk for ; Sun, 8 Jan 2017 22:57:46 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ijs.si; h= user-agent:message-id:references:in-reply-to:organization :subject:subject:from:from:date:date:content-transfer-encoding :content-type:content-type:mime-version:received:received :received:received; s=jakla4; t=1483912663; x=1486504664; bh=X89 jv1HemPk88x56vRXVek2G+v1RRW08AuH6uVZ54eg=; b=MhhjyTGYeguQ3Fy44Qy u8qVn1N2XVf/NXFHbangnIKf1ppGl23BEm2YLjBXXEb/mnqOoDdzcTpV8DfD/HOw sCunIrKba/Ji2pkgYa6/wVybOZHMjGhCuDyrHRFpJ9w9cJ/yaXWk8D9LYpr7oUsF q3p7maURlgXK8YpDKYxv95QE= X-Virus-Scanned: amavisd-new at ijs.si Received: from mail.ijs.si ([IPv6:::1]) by amavis-ori.ijs.si (mail.ijs.si [IPv6:::1]) (amavisd-new, port 10026) with LMTP id 0WCNTXdhzxBz for ; Sun, 8 Jan 2017 22:57:43 +0100 (CET) Received: from mildred.ijs.si (mailbox.ijs.si [IPv6:2001:1470:ff80::143:1]) by mail.ijs.si (Postfix) with ESMTP id 3txXFz1v0Bz1Wf for ; Sun, 8 Jan 2017 22:57:43 +0100 (CET) Received: from nabiralnik.ijs.si (nabiralnik.ijs.si [IPv6:2001:1470:ff80::80:16]) by mildred.ijs.si (Postfix) with ESMTP id 3txXFz13RzzM4 for ; Sun, 8 Jan 2017 22:57:43 +0100 (CET) Received: from upc.si.94.140.92.23.dc.cable.static.telemach.net ([94.140.92.23]) by webmail.ijs.si with HTTP (HTTP/1.1 POST); Sun, 08 Jan 2017 22:57:43 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Sun, 08 Jan 2017 22:57:43 +0100 From: Mark Martinec To: freebsd-net@freebsd.org Subject: Re: Gigabit USB NIC for RPi Organization: Jozef Stefan Institute In-Reply-To: <03145169-f546-01f7-e701-c76118b76bb9@t-online.de> References: <03145169-f546-01f7-e701-c76118b76bb9@t-online.de> Message-ID: <1cddb94bf7aed5c3eb49785959b34251@ijs.si> X-Sender: Mark.Martinec+freebsd@ijs.si User-Agent: Roundcube Webmail/1.2.3 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Jan 2017 21:57:50 -0000 2017-01-08 20:33, diffusae wrote: > Hi! > > I am looking for an compatible USB2Gigabit ethernet adapter for a RPi. > That should work with the ISO Images of FreeBSD 11 stable (armv6). > > Do you have any suggestions? Raspberry Pi model 3 B and its predecessors only have USB 2.0 (not 3.0), which (according to Wikipedia) only goes up to about 280 Mbit/s, so an adapter to a gigabit ethernet is not particularly useful. You are not the only one to regret that RPi 3 did not introduce a proper Gb ethernet interface. Mark From owner-freebsd-net@freebsd.org Sun Jan 8 22:13:51 2017 Return-Path: Delivered-To: freebsd-net@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 857C6CA6D73 for ; Sun, 8 Jan 2017 22:13:51 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 6A00411FF for ; Sun, 8 Jan 2017 22:13:51 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v08MDoKb072803 for ; Sun, 8 Jan 2017 22:13:51 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 181741] [kernel] [patch] Packet loss when 'control' messages are present with large data (sendmsg(2)) Date: Sun, 08 Jan 2017 22:13:50 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: allanjude@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Jan 2017 22:13:51 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D181741 Allan Jude changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |allanjude@FreeBSD.org --- Comment #11 from Allan Jude --- (In reply to chris.torek from comment #10) Users are reporting failures on FreeNAS 9.10 that were traced back to your patch offered here. This simple test program: http://pastebin.ca/3755236 sends an FD between a child and a parent In the process, the SCM_RIGHTS is lost, and recvmsg returns a message with SCM_CREDS instead. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Mon Jan 9 00:22:55 2017 Return-Path: Delivered-To: freebsd-net@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 F0CACCA3257 for ; Mon, 9 Jan 2017 00:22:55 +0000 (UTC) (envelope-from admin@x245.save85off.com) Received: from x245.save85off.com (x245.save85off.com [43.240.238.245]) by mx1.freebsd.org (Postfix) with ESMTP id 9C4C91898 for ; Mon, 9 Jan 2017 00:22:55 +0000 (UTC) (envelope-from admin@x245.save85off.com) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; s=save85off; d=x245.save85off.com; h=MIME-Version:From:To:Date:Subject:Content-Type:Content-Transfer-Encoding; i=admin@x245.save85off.com; bh=vJ/sAb88xSzvJwXArXX1Wma9H7U=; b=Rw8Yyip7sGuCFVeV9iwra+Rpy4slWWW+fhrGKTTb+4sXzcTqTYqgHcGYvY5W5qBziTv6tIoT3+LJ nm+mCDb4lkgIByVELWlUu+X9aoIma2XuCzpRjWRuTwX0znXQ/So+qkzORgAxrv+cHWf4rxd5oQiF OSZDGOnzP18gRSCTSbY= DomainKey-Signature: a=rsa-sha1; c=nofws; q=dns; s=save85off; d=x245.save85off.com; b=KTCE6g4IZ4ubC7BARxaMJ+IScCczHWNjREG0W1yF6RHRwcgtknmdutHhVDSopEts15kBpV+tK0T3 Yh6azzbgKyZvr3/uPBFzETu9wiKR2U8E1JvLnoJZ6vk03ZY29xSJIfyo0W3GcsyVG3m0zRe+r/eF xSzRAsrE6y4ji7RlCoI=; From: "UGG Australia Boots" To: freebsd-net@freebsd.org Date: 9 Jan 2017 08:12:37 +0800 Subject: Holiday Treats for you! win 89$ MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jan 2017 00:22:56 -0000 From owner-freebsd-net@freebsd.org Mon Jan 9 00:37:13 2017 Return-Path: Delivered-To: freebsd-net@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 6EB2BCA2717 for ; Mon, 9 Jan 2017 00:37:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 5E02B1A09 for ; Mon, 9 Jan 2017 00:37:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v090bDL7098582 for ; Mon, 9 Jan 2017 00:37:13 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 181741] [kernel] [patch] Packet loss when 'control' messages are present with large data (sendmsg(2)) Date: Mon, 09 Jan 2017 00:37:13 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: chris.torek@gmail.com X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jan 2017 00:37:13 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D181741 --- Comment #12 from chris.torek@gmail.com --- The test code demonstrating the new bug is slightly wrong (or insufficient = at least). What's happening is that one of the attached patches also changes = the code in uipc_finalizecontrol() to always prepend SCM_CREDS to DGRAM sockets= .=20 The result is that you need a larger control-message buffer here so that you can get both the credentials (i.e., who sent you the fd) *and* the rights (= the fd itself). With the small control-message buffer you have room only for t= he prepended credentials. Apparently UNP_WANTCREDS is not set on the pre-connected SOCK_DGRAM socketp= air. So, dropping or altering that particular commit (so that it prepends SCM_C= REDS only if UNP_WANTCREDS is set, whether or not this is a one-shot stream-ish socket or repeating datagram socket) will make the test program run. Or, making its control message receive buffer bigger will also make the test program run... --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Mon Jan 9 07:55:04 2017 Return-Path: Delivered-To: freebsd-net@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 E059BCA6CE8 for ; Mon, 9 Jan 2017 07:55:04 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 D02651B0E for ; Mon, 9 Jan 2017 07:55:04 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v097t4ol051485 for ; Mon, 9 Jan 2017 07:55:04 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 183148] [patch] add getaddrinfo(1) tool from NetBSD Date: Mon, 09 Jan 2017 07:55:04 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 1.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: hiren@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jan 2017 07:55:05 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D183148 Hiren Panchasara changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-net@FreeBSD.org --- Comment #1 from Hiren Panchasara --- Is this still valid/useful? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Mon Jan 9 11:38:29 2017 Return-Path: Delivered-To: freebsd-net@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 BD7E4CA6AE3; Mon, 9 Jan 2017 11:38:29 +0000 (UTC) (envelope-from bz@FreeBSD.org) Received: from mx1.sbone.de (bird.sbone.de [46.4.1.90]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mx1.sbone.de", Issuer "SBone.DE" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 80D651829; Mon, 9 Jan 2017 11:38:29 +0000 (UTC) (envelope-from bz@FreeBSD.org) Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:31::2013:587]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.sbone.de (Postfix) with ESMTPS id 35CCC25D37C2; Mon, 9 Jan 2017 11:38:21 +0000 (UTC) Received: from content-filter.sbone.de (content-filter.sbone.de [IPv6:fde9:577b:c1a9:31::2013:2742]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id 7128FD1F825; Mon, 9 Jan 2017 11:38:20 +0000 (UTC) X-Virus-Scanned: amavisd-new at sbone.de Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:31::2013:587]) by content-filter.sbone.de (content-filter.sbone.de [fde9:577b:c1a9:31::2013:2742]) (amavisd-new, port 10024) with ESMTP id e5dV4mor1r4L; Mon, 9 Jan 2017 11:38:19 +0000 (UTC) Received: from [10.111.64.116] (unknown [IPv6:fde9:577b:c1a9:4410:69da:881:ae95:a80a]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id 1C78FD1F7F9; Mon, 9 Jan 2017 11:38:17 +0000 (UTC) From: "Bjoern A. Zeeb" To: "Andrey V. Elsukov" Cc: freebsd-current@FreeBSD.org, freebsd-net@FreeBSD.org, "George Neville-Neil" Subject: Re: [RFC/RFT] projects/ipsec Date: Mon, 09 Jan 2017 11:38:15 +0000 Message-ID: In-Reply-To: References: <2bd32791-944f-2417-41e9-e0fe1c705502@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; format=flowed X-Mailer: MailMate (2.0BETAr6072) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jan 2017 11:38:29 -0000 On 27 Dec 2016, at 10:18, Andrey V. Elsukov wrote: > So, if there will no objection, I'll merge projects/ipsec into head/ > within two weeks. I still keep seeing almost daily changes to the branch and am having a hard time to convince myself to do a proper review that way. I would very much prefer this to be (a) either become stable first and then give people a chance, or (b) see if you can break out small self-contained changes put them up into review and merge them piece by piece making it a lot easier to convince ourselves that things still look good. /bz From owner-freebsd-net@freebsd.org Mon Jan 9 13:15:00 2017 Return-Path: Delivered-To: freebsd-net@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 0DBC7CA629B; Mon, 9 Jan 2017 13:15:00 +0000 (UTC) (envelope-from ae@FreeBSD.org) Received: from butcher-nb.yandex.net (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) by mx1.freebsd.org (Postfix) with ESMTP id D1CB914CC; Mon, 9 Jan 2017 13:14:58 +0000 (UTC) (envelope-from ae@FreeBSD.org) Subject: Re: [RFC/RFT] projects/ipsec To: "Bjoern A. Zeeb" References: <2bd32791-944f-2417-41e9-e0fe1c705502@FreeBSD.org> Cc: freebsd-current@FreeBSD.org, freebsd-net@FreeBSD.org, George Neville-Neil From: "Andrey V. Elsukov" Message-ID: <7d2366eb-caca-e9b1-174c-3b7cde96e45f@FreeBSD.org> Date: Mon, 9 Jan 2017 16:14:16 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jan 2017 13:15:00 -0000 On 09.01.2017 14:38, Bjoern A. Zeeb wrote: > On 27 Dec 2016, at 10:18, Andrey V. Elsukov wrote: > >> So, if there will no objection, I'll merge projects/ipsec into head/ >> within two weeks. > > I still keep seeing almost daily changes to the branch and am having a > hard time to convince myself to do a proper review that way. I would > very much prefer this to be (a) either become stable first and then give > people a chance, or (b) see if you can break out small self-contained > changes put them up into review and merge them piece by piece making it > a lot easier to convince ourselves that things still look good. Hi, yes, I hope I have fixed all found issues, now I will test the changes in our environment. I prefer the first way (a), because another splitting into small pieces requires a lot of time that I don't have. So, if you want to do a review, you are welcome :) Now I'll be focused on testing with different IKEd, documenting the changes, and fixing possible NO_INET/NO_INET6 related build issues. -- WBR, Andrey V. Elsukov From owner-freebsd-net@freebsd.org Mon Jan 9 15:38:35 2017 Return-Path: Delivered-To: freebsd-net@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 0F1B0CA7233 for ; Mon, 9 Jan 2017 15:38:35 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 F314B1684 for ; Mon, 9 Jan 2017 15:38:34 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v09FcYu8039608 for ; Mon, 9 Jan 2017 15:38:34 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 183148] [patch] add getaddrinfo(1) tool from NetBSD Date: Mon, 09 Jan 2017 15:38:35 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 1.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: vangyzen@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jan 2017 15:38:35 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D183148 Eric van Gyzen changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vangyzen@FreeBSD.org --- Comment #2 from Eric van Gyzen --- I have wanted a tool like this a few times over the years. This should sti= ll be considered. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Mon Jan 9 17:29:12 2017 Return-Path: Delivered-To: freebsd-net@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 2B06DCA7C64 for ; Mon, 9 Jan 2017 17:29:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 1AA711DCF for ; Mon, 9 Jan 2017 17:29:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v09HTB9H094882 for ; Mon, 9 Jan 2017 17:29:11 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 183148] [patch] add getaddrinfo(1) tool from NetBSD Date: Mon, 09 Jan 2017 17:29:12 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 1.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: lohithbsd@gmail.com X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jan 2017 17:29:12 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D183148 Lohith Bellad changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lohithbsd@gmail.com --- Comment #3 from Lohith Bellad --- I will adapt the patch to HEAD and test it. Thanks, Lohith --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Mon Jan 9 17:34:49 2017 Return-Path: Delivered-To: freebsd-net@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 A90F4CA7FF4 for ; Mon, 9 Jan 2017 17:34:49 +0000 (UTC) (envelope-from punasipuli@t-online.de) Received: from mailout01.t-online.de (mailout01.t-online.de [194.25.134.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mailout00.t-online.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7073F15F9 for ; Mon, 9 Jan 2017 17:34:48 +0000 (UTC) (envelope-from punasipuli@t-online.de) Received: from fwd25.aul.t-online.de (fwd25.aul.t-online.de [172.20.26.130]) by mailout01.t-online.de (Postfix) with SMTP id 5BB5D4325785 for ; Mon, 9 Jan 2017 18:34:39 +0100 (CET) Received: from [192.168.10.43] (VyLPvEZ1ohJzDufIbzI1fhfZxuP0xV2lBYaLjuRFL5f5ccKkKdMPZk3PI8OLkRGwfh@[86.56.56.128]) by fwd25.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-SHA encrypted) esmtp id 1cQdqB-1Wrb4y0; Mon, 9 Jan 2017 18:34:39 +0100 Subject: Re: Gigabit USB NIC for RPi References: <03145169-f546-01f7-e701-c76118b76bb9@t-online.de> <1cddb94bf7aed5c3eb49785959b34251@ijs.si> To: freebsd-net@freebsd.org From: diffusae Message-ID: Date: Mon, 9 Jan 2017 18:34:38 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: <1cddb94bf7aed5c3eb49785959b34251@ijs.si> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-ID: VyLPvEZ1ohJzDufIbzI1fhfZxuP0xV2lBYaLjuRFL5f5ccKkKdMPZk3PI8OLkRGwfh X-TOI-MSGID: 49f71a00-4362-436e-8ee0-56429c7b3296 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jan 2017 17:34:49 -0000 Hello again, thanks a lot for you reply. On 08.01.2017 22:57, Mark Martinec wrote: > 2017-01-08 20:33, diffusae wrote: >> Hi! >> >> I am looking for an compatible USB2Gigabit ethernet adapter for a RPi. >> That should work with the ISO Images of FreeBSD 11 stable (armv6). >> >> Do you have any suggestions? > > Raspberry Pi model 3 B and its predecessors only have USB 2.0 (not 3.0), > which (according to Wikipedia) only goes up to about 280 Mbit/s, > so an adapter to a gigabit ethernet is not particularly useful. > > You are not the only one to regret that RPi 3 did not introduce > a proper Gb ethernet interface. > > Mark Yes, I know this and it's a pity. You're right, it isn't really useful. But I also have a Linux Box (RPi 2) with a Gigabit WLAN Interface. It has a bandwidth about 200 Mbit/s or more, this is a bit higher than the internal USB NIC (100 Mbit/s). Especially if you stream HD videos, you could measure this difference. So, I only like to know which gigabit ethernet USB NIC would work with FreeBSD 11 and the Raspberry Pi? Thanks again Regards, Reiner From owner-freebsd-net@freebsd.org Mon Jan 9 20:52:28 2017 Return-Path: Delivered-To: freebsd-net@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 89D3FCA788C for ; Mon, 9 Jan 2017 20:52:28 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 7908810A2 for ; Mon, 9 Jan 2017 20:52:28 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v09KqSu9068429 for ; Mon, 9 Jan 2017 20:52:28 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 189219] [dummynet] [patch] using dummynet on sparc64 and configuring a pipe is an insta-panic Date: Mon, 09 Jan 2017 20:52:28 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: crash, needs-qa, patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: commit-hook@freebsd.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jan 2017 20:52:28 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D189219 --- Comment #9 from commit-hook@freebsd.org --- A commit references this bug: Author: marius Date: Mon Jan 9 20:51:51 UTC 2017 New revision: 311817 URL: https://svnweb.freebsd.org/changeset/base/311817 Log: In dummynet(4), random chunks of memory are casted to struct dn_*, potentially leading to fatal unaligned accesses on architectures with strict alignment requirements. This change fixes dummynet(4) as far as accesses to 64-bit members of struct dn_* are concerned, tripping up on sparc64 with accesses to 32-bit members happening to be correctly aligned there. In other words, this only fixes the tip of the iceberg; larger parts of dummynet(4) still need to be rewritten in order to properly work on all of !x86. In principle, considering the amount of code in dummynet(4) that needs this erroneous pattern corrected, an acceptable workaround would be to declare all struct dn_* packed, forcing compilers to do byte-accesses as a side-effect. However, given that the structs in question aren't laid out well either, this would break ABI/KBI. While at it, replace all existing bcopy(9) calls with memcpy(9) for performance reasons, as there is no need to check for overlap in these cases. PR: 189219 MFC after: 5 days Changes: head/sys/netpfil/ipfw/ip_dummynet.c --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Tue Jan 10 02:04:14 2017 Return-Path: Delivered-To: freebsd-net@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 4E966CA4435 for ; Tue, 10 Jan 2017 02:04:14 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 3DC911966 for ; Tue, 10 Jan 2017 02:04:14 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v0A24ExS024371 for ; Tue, 10 Jan 2017 02:04:14 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 215874] [patch] [icmp] [mbuf_tags] teach icmp_error() optionally keep original packet's mbuf_tags Date: Tue, 10 Jan 2017 02:04:14 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: mfc-stable10? mfc-stable11? X-Bugzilla-Changed-Fields: assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jan 2017 02:04:14 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D215874 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-net@FreeBSD.org --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Tue Jan 10 03:32:15 2017 Return-Path: Delivered-To: freebsd-net@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 B9439CA8FF2 for ; Tue, 10 Jan 2017 03:32:15 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from mail.ignoranthack.me (ignoranthack.me [199.102.79.106]) (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 89440123B for ; Tue, 10 Jan 2017 03:32:15 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from [192.168.0.6] (67-0-248-244.albq.qwest.net [67.0.248.244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: sbruno@ignoranthack.me) by mail.ignoranthack.me (Postfix) with ESMTPSA id BF4A41928BA for ; Tue, 10 Jan 2017 03:32:14 +0000 (UTC) Subject: Re: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb pending To: freebsd-net@freebsd.org References: From: Sean Bruno Message-ID: <092ad9f7-b04c-292f-c626-6ce1956580a8@freebsd.org> Date: Mon, 9 Jan 2017 20:32:14 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="uqsodBtGVRUjL69TwrmALMIANC8p2grvm" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jan 2017 03:32:15 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --uqsodBtGVRUjL69TwrmALMIANC8p2grvm Content-Type: multipart/mixed; boundary="T6P2bXbVQxhlvbCNW7XHmKMI5vwSVrEw0"; protected-headers="v1" From: Sean Bruno To: freebsd-net@freebsd.org Message-ID: <092ad9f7-b04c-292f-c626-6ce1956580a8@freebsd.org> Subject: Re: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb pending References: In-Reply-To: --T6P2bXbVQxhlvbCNW7XHmKMI5vwSVrEw0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable tl;dir --> you get to keep your igbX devices(thanks jhb), no POLA violations this week. I've updated sys/dev/e1000 at svn R311849 to match Matt Macy's work on IFLIB in the kernel. At this point, the driver deviates from Intel's code dramatically and you now get to yell directly into the freebsd-net@ megaphone for things that I may have broken. man page updates are coming up next. Please let us know if this revision has made things better, worse or none-of-the above on whatever Intel Gigabit NIC you happen to have lying around. sean On 01/05/17 20:18, Sean Bruno wrote: > tl;dr --> igbX devices will become emX devices >=20 > We're about to commit an update to sys/dev/e1000 that will implement an= d > activate IFLIB for em(4), lem(4) & igb(4) and would appreciate all folk= s > who can test and poke at the drivers to do so this week. This will hav= e > some really great changes for performance and standardization that have= > been bouncing around inside of various FreeBSD shops that have been > collaborating with Matt Macy over the last year. >=20 > This will implement multiple queues for certain em(4) devices that are > capable of such things and add some new sysctl's for you to poke at in > your monitoring tools. >=20 > Due to limitations of device registration, igbX devices will become emX= > devices. So, you'll need to make a minor update to your rc.conf and > scripts that manipulate the network devices. >=20 > UPDATING will be bumped to reflect these changes. >=20 > MFC to stable/11 will have a legacy implementation that doesn't use > IFLIB for compatibility reasons. >=20 > A documentation and man page update will follow in the next few days > explaining how to work with the changed driver. >=20 > sean >=20 > bcc net@ current@ re@ >=20 >=20 >=20 >=20 >=20 --T6P2bXbVQxhlvbCNW7XHmKMI5vwSVrEw0-- --uqsodBtGVRUjL69TwrmALMIANC8p2grvm Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEEuq1GMucSHejSCZfdEgHvyh5yfmQFAlh0Vb5fFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEJB QUQ0NjMyRTcxMjFERThEMjA5OTdERDEyMDFFRkNBMUU3MjdFNjQACgkQEgHvyh5y fmSLuAf/b3KeS9ogR6Ma8yhb0+0M/zcmCMSToMviDeGmG5snhIdfhexgbfsIsp43 tfwapfBPHnkBA35ePO8wOEt/TeKYeYZ3fLbv5jR83asRywpLtgNDz9H44rbyXidi 6CT6Oi543mQk4bF4Qt4qBwimH7ZreUNynHBXRPLlqK9s4VFIJYygHYRA0l/jvbaN PCzCmfFC0fzFBl7RXJivX192D/g2xgHM+0V6r9NuYQ5KaYMNG4m9bC1PLTMnIGHS sfKacxk4O69VV22psFBt5qUDgfl1IdWPHbmE4hZfxdqrWOcmqXS9CTGi/YEYVT5M yWxawt2OAFxjEF4Tc+cdWRXcps6H2Q== =88Zl -----END PGP SIGNATURE----- --uqsodBtGVRUjL69TwrmALMIANC8p2grvm-- From owner-freebsd-net@freebsd.org Tue Jan 10 09:03:32 2017 Return-Path: Delivered-To: freebsd-net@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 040BFCA7F65 for ; Tue, 10 Jan 2017 09:03:32 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 E1118151E for ; Tue, 10 Jan 2017 09:03:31 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v0A93Vrl047939 for ; Tue, 10 Jan 2017 09:03:31 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 213115] ifconfig ipfw create inside a VNET jail leads to kernel Panic Date: Tue, 10 Jan 2017 09:03:31 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-STABLE X-Bugzilla-Keywords: vimage X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: matthias+freebsd+bugzilla@harz.de X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jan 2017 09:03:32 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213115 --- Comment #4 from matthias+freebsd+bugzilla@harz.de --- (In reply to Ed Maste from comment #3) tested with 11.0 It works as expected. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Tue Jan 10 10:28:38 2017 Return-Path: Delivered-To: freebsd-net@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 AE7EACA95E7 for ; Tue, 10 Jan 2017 10:28:38 +0000 (UTC) (envelope-from freebsd@omnilan.de) Received: from mx0.gentlemail.de (mx0.gentlemail.de [IPv6:2a00:e10:2800::a130]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 43F0C1C47; Tue, 10 Jan 2017 10:28:38 +0000 (UTC) (envelope-from freebsd@omnilan.de) Received: from mh0.gentlemail.de (ezra.dcm1.omnilan.net [IPv6:2a00:e10:2800::a135]) by mx0.gentlemail.de (8.14.5/8.14.5) with ESMTP id v0AASYve062105; Tue, 10 Jan 2017 11:28:34 +0100 (CET) (envelope-from freebsd@omnilan.de) Received: from titan.inop.mo1.omnilan.net (titan.inop.mo1.omnilan.net [IPv6:2001:a60:f0bb:1::3:1]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mh0.gentlemail.de (Postfix) with ESMTPSA id 88DD843; Tue, 10 Jan 2017 11:28:34 +0100 (CET) Message-ID: <5874B751.4000808@omnilan.de> Date: Tue, 10 Jan 2017 11:28:33 +0100 From: Harry Schmalzbauer Organization: OmniLAN User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; de-DE; rv:1.9.2.8) Gecko/20100906 Lightning/1.0b2 Thunderbird/3.1.2 MIME-Version: 1.0 To: Sean Bruno CC: freebsd-net@freebsd.org Subject: Re: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb pending References: <092ad9f7-b04c-292f-c626-6ce1956580a8@freebsd.org> In-Reply-To: <092ad9f7-b04c-292f-c626-6ce1956580a8@freebsd.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (mx0.gentlemail.de [IPv6:2a00:e10:2800::a130]); Tue, 10 Jan 2017 11:28:34 +0100 (CET) X-Milter: Spamilter (Reciever: mx0.gentlemail.de; Sender-ip: ; Sender-helo: mh0.gentlemail.de; ) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jan 2017 10:28:38 -0000 Bezüglich Sean Bruno's Nachricht vom 10.01.2017 04:32 (localtime): > tl;dir --> you get to keep your igbX devices(thanks jhb), no POLA > violations this week. > > I've updated sys/dev/e1000 at svn R311849 to match Matt Macy's work on > IFLIB in the kernel. > > At this point, the driver deviates from Intel's code dramatically and > you now get to yell directly into the freebsd-net@ megaphone for things > that I may have broken. > > man page updates are coming up next. Please let us know if this > revision has made things better, worse or none-of-the above on whatever > Intel Gigabit NIC you happen to have lying around. > > sean > > On 01/05/17 20:18, Sean Bruno wrote: >> tl;dr --> igbX devices will become emX devices >> >> We're about to commit an update to sys/dev/e1000 that will implement and >> activate IFLIB for em(4), lem(4) & igb(4) and would appreciate all folks >> who can test and poke at the drivers to do so this week. This will have >> some really great changes for performance and standardization that have >> been bouncing around inside of various FreeBSD shops that have been >> collaborating with Matt Macy over the last year. >> >> This will implement multiple queues for certain em(4) devices that are >> capable of such things and add some new sysctl's for you to poke at in >> your monitoring tools. >> >> Due to limitations of device registration, igbX devices will become emX >> devices. So, you'll need to make a minor update to your rc.conf and >> scripts that manipulate the network devices. >> >> UPDATING will be bumped to reflect these changes. >> >> MFC to stable/11 will have a legacy implementation that doesn't use >> IFLIB for compatibility reasons. Thank you very much for your work! I'm unsure if I got it right: stabe/11 won't benefit from IFLIB (not that I know waht IFLIB is all about, yet), but driver changes will be merged? I'm already using MULTIQUEUE support for em(4) (Hartwell, 82547) since 10.2-stable without problems on high saturated single links and noticable better performance. Currently I could test a pre-productive igb(4)/Kawela (82576) machine utilizing LACP+VLANs to chekck for regression (improvement regarding »igb stopped distributiong, possible flapping?«), but it's stable/11. Simply merging r311849 doesn't work, most likely due to the IFLIB compatibility reasons you mentioned. Have you already prepared a MFC verison? What should igb(4) users expect after MFC? (Christmas is over and I didn't get SR-IOV for igb(4)/82576, so this its still on my wish list ;-)) Thnaks, -harry From owner-freebsd-net@freebsd.org Tue Jan 10 11:28:47 2017 Return-Path: Delivered-To: freebsd-net@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 C9438CA8DF6 for ; Tue, 10 Jan 2017 11:28:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 B45D6115F for ; Tue, 10 Jan 2017 11:28:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v0ABSlVe052675 for ; Tue, 10 Jan 2017 11:28:47 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 200420] [igb] igb0: Watchdog timeout -- resetting Date: Tue, 10 Jan 2017 11:28:47 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.1-RELEASE X-Bugzilla-Keywords: IntelNetworking X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: kbowling@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jan 2017 11:28:47 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D200420 Kevin Bowling changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kbowling@freebsd.org --- Comment #10 from Kevin Bowling --- For the original submitter with the ASRock board, can you retry with -CURRE= NT? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Tue Jan 10 11:29:14 2017 Return-Path: Delivered-To: freebsd-net@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 EEF0DCA8E5C for ; Tue, 10 Jan 2017 11:29:14 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 D80531217 for ; Tue, 10 Jan 2017 11:29:14 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v0ABTDr8053275 for ; Tue, 10 Jan 2017 11:29:14 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 210417] Reproducible igb related panic 11.0-ALPHA4 Date: Tue, 10 Jan 2017 11:29:14 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: IntelNetworking X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: kbowling@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jan 2017 11:29:15 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D210417 Kevin Bowling changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kbowling@freebsd.org --- Comment #3 from Kevin Bowling --- Can you retry with 12-CURRENT? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Tue Jan 10 11:30:06 2017 Return-Path: Delivered-To: freebsd-net@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 5FA4ACA8F14 for ; Tue, 10 Jan 2017 11:30:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 4F3E412FE for ; Tue, 10 Jan 2017 11:30:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v0ABU658054463 for ; Tue, 10 Jan 2017 11:30:06 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 210901] em0 stores packets somewhere and lets them out slowly under load. Date: Tue, 10 Jan 2017 11:30:06 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-RELEASE X-Bugzilla-Keywords: IntelNetworking X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: kbowling@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jan 2017 11:30:06 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D210901 Kevin Bowling changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kbowling@freebsd.org --- Comment #2 from Kevin Bowling --- Can you retry with 12-CURRENT? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Tue Jan 10 11:33:47 2017 Return-Path: Delivered-To: freebsd-net@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 203ACCA90CC for ; Tue, 10 Jan 2017 11:33:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 0FEB816D5 for ; Tue, 10 Jan 2017 11:33:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v0ABXjJo067877 for ; Tue, 10 Jan 2017 11:33:46 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 202680] Silent data corruption on em(4) interfaces Date: Tue, 10 Jan 2017 11:33:46 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.2-STABLE X-Bugzilla-Keywords: IntelNetworking X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: kbowling@freebsd.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jan 2017 11:33:47 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D202680 Kevin Bowling changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kbowling@freebsd.org --- Comment #25 from Kevin Bowling --- Can you retest with 12-CURRENT? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Tue Jan 10 14:43:20 2017 Return-Path: Delivered-To: freebsd-net@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 7C58CCA9D5A for ; Tue, 10 Jan 2017 14:43:20 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from mail.ignoranthack.me (ignoranthack.me [199.102.79.106]) (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 4E4471CDE for ; Tue, 10 Jan 2017 14:43:19 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from [192.168.0.6] (67-0-248-244.albq.qwest.net [67.0.248.244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: sbruno@ignoranthack.me) by mail.ignoranthack.me (Postfix) with ESMTPSA id 9F7FC1928BA; Tue, 10 Jan 2017 14:43:18 +0000 (UTC) Subject: Re: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb pending To: Harry Schmalzbauer References: <092ad9f7-b04c-292f-c626-6ce1956580a8@freebsd.org> <5874B751.4000808@omnilan.de> Cc: freebsd-net@freebsd.org From: Sean Bruno Message-ID: <7b048fa1-13bc-2a79-4fbe-6f049b30d65f@freebsd.org> Date: Tue, 10 Jan 2017 07:43:15 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: <5874B751.4000808@omnilan.de> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="TUhu1uw9kkfiAacp9X6jUMRiq8TtpJCRI" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jan 2017 14:43:20 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --TUhu1uw9kkfiAacp9X6jUMRiq8TtpJCRI Content-Type: multipart/mixed; boundary="WQXCrKxk9r8kshjXet5Udnoqojabh7Mge"; protected-headers="v1" From: Sean Bruno To: Harry Schmalzbauer Cc: freebsd-net@freebsd.org Message-ID: <7b048fa1-13bc-2a79-4fbe-6f049b30d65f@freebsd.org> Subject: Re: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb pending References: <092ad9f7-b04c-292f-c626-6ce1956580a8@freebsd.org> <5874B751.4000808@omnilan.de> In-Reply-To: <5874B751.4000808@omnilan.de> --WQXCrKxk9r8kshjXet5Udnoqojabh7Mge Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable >=20 > Thank you very much for your work! > I'm unsure if I got it right: stabe/11 won't benefit from IFLIB (not > that I know waht IFLIB is all about, yet), but driver changes will be > merged? Yes, we intend on pulling back IFLIB and the IFLIB'd drivers to stable/11 for people's use. The difference will be that the IFLIB implementation will not be the default here, it will be a KERNCONF option that you will be able to add during your upgrade process. >=20 > I'm already using MULTIQUEUE support for em(4) (Hartwell, 82547) since > 10.2-stable without problems on high saturated single links and > noticable better performance. >=20 > Currently I could test a pre-productive igb(4)/Kawela (82576) machine > utilizing LACP+VLANs to chekck for regression (improvement regarding > =C2=BBigb stopped distributiong, possible flapping?=C2=AB), but it's st= able/11. >=20 > Simply merging r311849 doesn't work, most likely due to the IFLIB > compatibility reasons you mentioned. > Have you already prepared a MFC verison? > What should igb(4) users expect after MFC? (Christmas is over and I > didn't get SR-IOV for igb(4)/82576, so this its still on my wish list ;= -)) >=20 > Thnaks, >=20 > -harry I suspect end of month for an MFC with all the IFLIB bits. sean --WQXCrKxk9r8kshjXet5Udnoqojabh7Mge-- --TUhu1uw9kkfiAacp9X6jUMRiq8TtpJCRI Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEEuq1GMucSHejSCZfdEgHvyh5yfmQFAlh08wNfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEJB QUQ0NjMyRTcxMjFERThEMjA5OTdERDEyMDFFRkNBMUU3MjdFNjQACgkQEgHvyh5y fmT6rQf+LLcY+hXoaUbX5pPoGaN1X47q//NRMoj5MHpmWv1uPXZub+qAwdHv5pcx 2XpUk4wXYzW9aTQTaszx8ff94ttiJsGH1u7HH0P0v6qoYYlR4tPWASgs9qnnbp7x luOnEOu1KQ+xfzpWvsSWygrkSdzLXaQ0EBXAqyDFBQWoDoHljLGCcQdiwSXj8eHB USH9NgdUNnhDVepDf1mhucY105BN3IVJqm1RCHh78zfE71YXIGUUUlHBxr0Ky+vW lZ8h72R9cVTrcJ4+XFKZAAmMq5oHGzCeScnplnbrwWI3vrpMQahaJSH1lq29CsXi Bv2JKnsSjxU4blTLLjJXEx2H0vr0DQ== =1Og1 -----END PGP SIGNATURE----- --TUhu1uw9kkfiAacp9X6jUMRiq8TtpJCRI-- From owner-freebsd-net@freebsd.org Tue Jan 10 16:27:04 2017 Return-Path: Delivered-To: freebsd-net@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 3EED5CA95E8 for ; Tue, 10 Jan 2017 16:27:04 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 2EA4F1338 for ; Tue, 10 Jan 2017 16:27:04 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v0AGR25K053572 for ; Tue, 10 Jan 2017 16:27:04 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 202680] Silent data corruption on em(4) interfaces Date: Tue, 10 Jan 2017 16:27:02 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.2-STABLE X-Bugzilla-Keywords: IntelNetworking X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: KOT@MATPOCKuH.Ru X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jan 2017 16:27:04 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D202680 --- Comment #26 from Dmitry Afanasiev --- (In reply to Kevin Bowling from comment #25) I started to recheck this problem on stable/10 r306961, and currently have = no problems. I need more time to more tests, but may be problem is already solved in r29= 4958 (or next changes?). I will report later. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Tue Jan 10 19:49:46 2017 Return-Path: Delivered-To: freebsd-net@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 8313BCAA92D; Tue, 10 Jan 2017 19:49:46 +0000 (UTC) (envelope-from ae@FreeBSD.org) Received: from butcher-nb.yandex.net (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) by mx1.freebsd.org (Postfix) with ESMTP id 80B631334; Tue, 10 Jan 2017 19:49:45 +0000 (UTC) (envelope-from ae@FreeBSD.org) Subject: Re: [RFC/RFT] projects/ipsec To: freebsd-current@FreeBSD.org, freebsd-net@FreeBSD.org, freebsd-stable@freebsd.org References: <2bd32791-944f-2417-41e9-e0fe1c705502@FreeBSD.org> From: "Andrey V. Elsukov" Message-ID: <3caafac9-d7ff-89bb-6fca-8968191ebb0a@FreeBSD.org> Date: Tue, 10 Jan 2017 22:48:59 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: <2bd32791-944f-2417-41e9-e0fe1c705502@FreeBSD.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jan 2017 19:49:46 -0000 Hi All, I ported the changes from projects/ipsec to stable/11 branch. So, if it is more suitable for testing, please, welcome. You can checkout the sources from github: https://github.com/bu7cher/freebsd/tree/stable/11 Also I made the standalone patch: https://people.freebsd.org/~ae/ipsec.diff Unfortunately, I did only compile test for stable branch. > I am pleased to announce that projects/ipsec, that I started several > months ago is ready for testing and review. > The main goals were: > * rework locking to make IPsec code more friendly for concurrent > processing; > * make lookup in SADB/SPDB faster; > * revise PFKEY implementation, remove stale code, make it closer > to RFC; > * implement IPsec VTI (virtual tunneling interface); > * make IPsec code loadable as kernel module. > > Currently all, except the last one is mostly done. So, I decided ask for > a help to test the what already done, while I will work on the last task. > > How to try? There are no patches, you need to checkout the full > projects/ipsec source tree, and build the kernel and the base system. > There are very few changes in the base system, mostly the kernel > changes. Thus for testing that old configuration is still work, it is > enough to build only the kernel. > > The approximate list of changes that may be visible to users: > * SA bundles now can have only 4 items in the chain. I think it is > enough, I can't imagine configurations when needed more. Also now SA > bundles supported for IPv6 too. > * due to changes in SPDB/SADB, systems where large number of SPs and SAs > are in use should get significant performance benefits. > * the memory consumption should slightly increase. There are several > hash tables and SP cache appeared. > * INPCB SP cache should noticeable increase network performance of > application when security policies are presence. > https://lists.freebsd.org/pipermail/freebsd-net/2015-April/042121.html > * use transport mode IPsec for forwarded IPv4 packets now unsupported. > This matches the IPv6 behavior, and since we can handle the replies, I > think it is useless. > * Added net.inet.ipsec.check_policy_history sysctl variable. When it is > set, each inbound packet that was handled by IPsec will be checked > according to matching security policy. If not all IPsec transforms were > applied, the check will fail, and packet will be dropped. > * Many PF_KEY messages handlers was updated, probably some IKEd now may > fail due to stricter checks. > * SPI now unique for each SA. This also can break something. > * Added if_ipsec interface. For more info look at > https://svnweb.freebsd.org/base?view=revision&revision=309115 > https://reviews.freebsd.org/P112 > * TCP_SIGNATURE code was reworked and now it behaves closer to RFC > https://svnweb.freebsd.org/base?view=revision&revision=309610 > * NAT-T support was reworked. > https://svnweb.freebsd.org/base?view=revision&revision=309808 > Also I made the patch to racoon that adds better support of NAT-T, > you can use this port to build patched racoon: > https://people.freebsd.org/~ae/ipsec-tools.tgz > > What results is interesting to me? > If you have some nontrivial configuration, please test. > If you have some configuration, that did't work, please test this branch. > If you have performance problems, please test. But don't forget that > this is head/ branch, you need to disable all debugging first. > If you just want to test, pay attention to the output of > `vmstat -m | egrep "sec|sah|pol|crypt"`. > If you have used TCP_SIGNATURE, IPSEC_NAT_T options, please test, this > support was significantly changed. IPsec as kernel modules was reported here: https://lists.freebsd.org/pipermail/freebsd-net/2016-December/046762.html Some additional testing also needed with this... -- WBR, Andrey V. Elsukov From owner-freebsd-net@freebsd.org Tue Jan 10 19:56:56 2017 Return-Path: Delivered-To: freebsd-net@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 C3E03CA9419 for ; Tue, 10 Jan 2017 19:56:56 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 B32FC1CAD for ; Tue, 10 Jan 2017 19:56:56 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v0AJuuZ1003509 for ; Tue, 10 Jan 2017 19:56:56 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 202680] Silent data corruption on em(4) interfaces Date: Tue, 10 Jan 2017 19:56:56 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.2-STABLE X-Bugzilla-Keywords: IntelNetworking X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: kbowling@freebsd.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jan 2017 19:56:56 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D202680 --- Comment #27 from Kevin Bowling --- It's possible things were fixed in past versions, but r311849 in -CURRENT h= as a large cleanup and optimization of the FreeBSD part of the driver. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Tue Jan 10 22:22:46 2017 Return-Path: Delivered-To: freebsd-net@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 7F3DFCAAD09 for ; Tue, 10 Jan 2017 22:22:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 6ECCD143B for ; Tue, 10 Jan 2017 22:22:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v0AMMksY051218 for ; Tue, 10 Jan 2017 22:22:46 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 210901] em0 stores packets somewhere and lets them out slowly under load. Date: Tue, 10 Jan 2017 22:22:46 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-RELEASE X-Bugzilla-Keywords: IntelNetworking X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: dgilbert@eicat.ca X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jan 2017 22:22:46 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D210901 --- Comment #3 from dgilbert@eicat.ca --- This was finally shown to be due to jumbo allocation for >4k (greater-than-page-size) mbufs failing. As such, it would still happen if = this still happens. That said, I don't have a means to test on 12-CURRENT. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Tue Jan 10 23:27:50 2017 Return-Path: Delivered-To: freebsd-net@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 C8306CAA0A3; Tue, 10 Jan 2017 23:27:50 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:201:6350::2]) by mx1.freebsd.org (Postfix) with ESMTP id 920A01BB1; Tue, 10 Jan 2017 23:27:50 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from [IPv6:2001:470:923f:2:45dc:b573:f9f6:3f1e] (unknown [IPv6:2001:470:923f:2:45dc:b573:f9f6:3f1e]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPSA id 6AF39BF1; Wed, 11 Jan 2017 02:27:40 +0300 (MSK) Reply-To: lev@FreeBSD.org To: freebsd-net@freebsd.org, freebsd-stable@freebsd.org From: Lev Serebryakov Subject: IPv6 works on em0 () but not on em1 () - what's wrong? Organization: FreeBSD Message-ID: <58756DDE.5000503@FreeBSD.org> Date: Wed, 11 Jan 2017 02:27:26 +0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="OSQIEdTTTT9av1bFQMCCaJmchsQ79ETgb" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jan 2017 23:27:50 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --OSQIEdTTTT9av1bFQMCCaJmchsQ79ETgb Content-Type: multipart/mixed; boundary="7cBXNCGcc6249uUSx8mBLvafUtq8sGafB"; protected-headers="v1" From: Lev Serebryakov Reply-To: lev@FreeBSD.org To: freebsd-net@freebsd.org, freebsd-stable@freebsd.org Message-ID: <58756DDE.5000503@FreeBSD.org> Subject: IPv6 works on em0 () but not on em1 () - what's wrong? --7cBXNCGcc6249uUSx8mBLvafUtq8sGafB Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable I have MoBo (Supermicro X9SCL-F) with two 1G NICs, first one (em0) is based on 82579LM, and second one (em1) is based on 82574L. When I'm using em0 with simple config: ifconfig_em0=3D"inet 192.168.134.2 netmask 255.255.255.0 mtu 9000" ifconfig_em0_ipv6=3D"inet6 accept_rtadv" everything works fine - em0 get IPv6 prefix from rtadvd of my router and "tspdump -n -i em0 icmp6" shows some traffic, like router and prefix announcements. So far so good. I want to use em1 (and don't use em0 at all), because 82579LM has some known bugs according to SuperMicro support and someties hangs whole syste= m. So, I change config to ifconfig_em1=3D"inet 192.168.134.2 netmask 255.255.255.0 mtu 9000" ifconfig_em1_ipv6=3D"inet6 accept_rtadv" connect em1 instead of em0 to the switch and reboot. And after that interface (em1) can not get IPv6 prefix, don't get global address (and shows only link-local one)and "tcpdump -n -i em1 icmp6" shows nothing at all! IPv4 works fine, though. What do I do wrong? Is it known issue of 82574L? I'm running 10-STABLE r311462. --=20 // Lev Serebryakov AKA Black Lion --7cBXNCGcc6249uUSx8mBLvafUtq8sGafB-- --OSQIEdTTTT9av1bFQMCCaJmchsQ79ETgb Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQJ8BAEBCgBmBQJYdW3qXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRGOTZEMUNBMEI1RjQzMThCNjc0QjMzMEFF QUIwM0M1OEJGREM0NzhGAAoJEOqwPFi/3EePTYsQAKXgwFax2jAIyW2KyfPMRU47 wV2jlqSyAbuPQEY5WuNWspalRpUF/JfFLmDrbOfJudgTAsw/jZhFf5r04tbafcv+ njcy5vST3xqToqmpZzcWMjAJ61z+XOEGYN/+DYsu+GjZjBi5lJptEVuv5HRYS0ZR E+ZPRrPoBT4nJ3XV0nZzBVb5/I0Gg3sDg7zaqUF4BBgHUDVWQlOZfFwbEosUgFbg XEnDI2EVXNBpX99ES3dd8oyU6VPmt5VORw8m8kTUtIaxV7j/TuFXZ37N4P6UJ+u5 KCN3WAIQbcHrpLREb6oJ+v9JwRu/eGOjMsxFXRHd1oZ1vXN/tUVzpIDx7HWcHGv7 sJALLQIZhCoLV5bey/o2bOt2TtMrJylbamN8xe8mCvkks7EYYRFCBZhSp21leIbp W0VztHvgnJ3thrGRV7i6/e6ACvcOltQN6C0J0fm3NoD4fWhzlt6m5tUCR1cpqo4v a8IXO4VMMX+/CDFZWPYGrrZ8LeZIFkjDfIdA3NEUXoTi8XnVOEsvAY2DDNGRHwBh Cw1zEYhV80yYDyDujiCcnDz2/ff2ABLGLRZ9uyla1DPHGOfRVGCilWXeHk8WWtiC 8OYXcaMSYLodiBSDzj9C6S4ESQgfQdzNKHHSGv1CfLzNdikpnqtpHiCWWq0TtpG1 IUo4Sx9l6o+waj6WZ/Vn =ZW0l -----END PGP SIGNATURE----- --OSQIEdTTTT9av1bFQMCCaJmchsQ79ETgb-- From owner-freebsd-net@freebsd.org Tue Jan 10 23:45:49 2017 Return-Path: Delivered-To: freebsd-net@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 26AF2CAA8F2; Tue, 10 Jan 2017 23:45:49 +0000 (UTC) (envelope-from hrs@FreeBSD.org) Received: from mail.allbsd.org (gatekeeper.allbsd.org [IPv6:2001:2f0:104:e001::32]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.allbsd.org", Issuer "RapidSSL SHA256 CA - G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 87E5616E0; Tue, 10 Jan 2017 23:45:48 +0000 (UTC) (envelope-from hrs@FreeBSD.org) Received: from mail-d.allbsd.org (p2027-ipbf1605funabasi.chiba.ocn.ne.jp [123.225.191.27]) (authenticated bits=56) by mail.allbsd.org (8.15.2/8.15.2) with ESMTPSA id v0ANjP83072743 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) (Client CN "/OU=GT07882699/OU=See+20www.rapidssl.com/resources/cps+20+28c+2915/OU=Domain+20Control+20Validated+20-+20RapidSSL+28R+29/CN=*.allbsd.org", Issuer "/C=US/O=GeoTrust+20Inc./CN=RapidSSL+20SHA256+20CA+20-+20G3"); Wed, 11 Jan 2017 08:45:44 +0900 (JST) (envelope-from hrs@FreeBSD.org) Received: from alph.allbsd.org (alph.allbsd.org [192.168.0.10]) by mail-d.allbsd.org (8.15.2/8.15.2) with ESMTPS id v0ANi959076580 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 11 Jan 2017 08:44:09 +0900 (JST) (envelope-from hrs@FreeBSD.org) Received: from localhost (localhost [IPv6:::1]) (authenticated bits=0) by alph.allbsd.org (8.15.2/8.15.2) with ESMTPA id v0ANi7Ic076576; Wed, 11 Jan 2017 08:44:09 +0900 (JST) (envelope-from hrs@FreeBSD.org) Date: Wed, 11 Jan 2017 08:43:28 +0900 (JST) Message-Id: <20170111.084328.1155081177427359974.hrs@allbsd.org> To: lev@FreeBSD.org Cc: freebsd-net@freebsd.org, freebsd-stable@freebsd.org Subject: Re: IPv6 works on em0 () but not on em1 () - what's wrong?,IPv6 works on em0 () but not on em1 () - what's wrong? From: Hiroki Sato In-Reply-To: <58756DDE.5000503@FreeBSD.org> References: <58756DDE.5000503@FreeBSD.org> X-PGPkey-fingerprint: BDB3 443F A5DD B3D0 A530 FFD7 4F2C D3D8 2793 CF2D X-Mailer: Mew version 6.7 on Emacs 25.1 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Multipart/Signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="--Security_Multipart(Wed_Jan_11_08_43_28_2017_181)--" Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamav-milter 0.99 at gatekeeper.allbsd.org X-Virus-Status: Clean X-Greylist: Sender DNS name whitelisted, not delayed by milter-greylist-4.4.3 (mail.allbsd.org [133.31.130.32]); Wed, 11 Jan 2017 08:45:45 +0900 (JST) X-Spam-Status: No, score=-98.9 required=13.0 tests=CONTENT_TYPE_PRESENT, FAKEDWORD_ONE,FAKEDWORD_VERTICALLINE,QENCPTR1,USER_IN_WHITELIST autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on gatekeeper.allbsd.org X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jan 2017 23:45:49 -0000 ----Security_Multipart(Wed_Jan_11_08_43_28_2017_181)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Lev Serebryakov wrote in <58756DDE.5000503@FreeBSD.org>,<58756DDE.5000503@FreeBSD.org>: le> le> I have MoBo (Supermicro X9SCL-F) with two 1G NICs, first one (em0) is le> based on 82579LM, and second one (em1) is based on 82574L. le> le> When I'm using em0 with simple config: le> le> ifconfig_em0="inet 192.168.134.2 netmask 255.255.255.0 mtu 9000" le> ifconfig_em0_ipv6="inet6 accept_rtadv" le> le> everything works fine - em0 get IPv6 prefix from rtadvd of my router le> and "tspdump -n -i em0 icmp6" shows some traffic, like router and prefix le> announcements. So far so good. le> le> I want to use em1 (and don't use em0 at all), because 82579LM has some le> known bugs according to SuperMicro support and someties hangs whole system. le> le> So, I change config to le> le> ifconfig_em1="inet 192.168.134.2 netmask 255.255.255.0 mtu 9000" le> ifconfig_em1_ipv6="inet6 accept_rtadv" le> le> connect em1 instead of em0 to the switch and reboot. And after that le> interface (em1) can not get IPv6 prefix, don't get global address (and le> shows only link-local one)and "tcpdump -n -i em1 icmp6" shows nothing at le> all! IPv4 works fine, though. le> le> What do I do wrong? Is it known issue of 82574L? le> le> I'm running 10-STABLE r311462. What happens by typing the following command? % ping6 ff02::1%em1 -- Hiroki ----Security_Multipart(Wed_Jan_11_08_43_28_2017_181)-- Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEABECAAYFAlh1caAACgkQTyzT2CeTzy0JSwCgqt5XrlsxqIO9wDWtEsJ4Gdnv d+wAniNiFLYgtmVop7U53AzogMHR2pI3 =iqLm -----END PGP SIGNATURE----- ----Security_Multipart(Wed_Jan_11_08_43_28_2017_181)---- From owner-freebsd-net@freebsd.org Tue Jan 10 23:49:29 2017 Return-Path: Delivered-To: freebsd-net@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 E53C0CAAC3F for ; Tue, 10 Jan 2017 23:49:29 +0000 (UTC) (envelope-from leeb@ratnaling.org) Received: from mail-ua0-x241.google.com (mail-ua0-x241.google.com [IPv6:2607:f8b0:400c:c08::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A540D1ADA for ; Tue, 10 Jan 2017 23:49:29 +0000 (UTC) (envelope-from leeb@ratnaling.org) Received: by mail-ua0-x241.google.com with SMTP id d5so46658097uag.0 for ; Tue, 10 Jan 2017 15:49:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ratnaling-org.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to:cc; bh=7TN/3hviHONgBAts3kSPsH/e5OyMOnAqYi657hSsPMo=; b=NBkTRUvX66fhyaZh2Q792JvN4ooQ6XPBhATAZXavFPr+zXEtPS3hlN8ZFCST4HL6hK 0QZezUKSdc5xdznaakVmnT4u2GupkQ3lzOUt2YW3aMteFmU5sMrg/AQgUUE4IqdApKJj GtbhVnb9HzAdPn4V31QixJl1ep6L7UnW9H7XEUaDdTc4UErigBeESCGs003jV0P0vDn1 GKRHglFCRqljZirueQBXfJpEGz95uqgWvruvR9nR3AAA3+ex+mFyt6KLU+zcthOtPPoL daL0XTB/tBZLN1MLhpCEECTTEPsN9Yf6720fzNlQcICXdOPgv5irxFBSFzsSwLb+yEqY s47w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=7TN/3hviHONgBAts3kSPsH/e5OyMOnAqYi657hSsPMo=; b=pogZWksmUOgsetNcHIC2Px5rUKZh/kzTwGPQ64eZXyXhoYSbYYE5QGUXrKxz8BG8SC IqIgKFpsiXlPLxG8Q/xmWFSfPAM+sjlEKS+s8MzBJyVFNgHbB2iYOBjcgYFKVvQn7xoK zcgwQY5SoA54et5v66QfuJUn0r7ZQEMra0nia2Co8mxI9AZovAC2qnLhfNzHZxzehNAA w2QmWuKRo5pWtdd7t6kfyrb7Z6ji9w4EyG3KPyM9v6UIlgXmrUm6vedcfJ9dCFR7zq9l ant4TVEsvAeredpCLOt13UaZmjt7LbixJaBZzDV3xYjsOUDHc1jTxPlUVda1XRVNMgOO gQoQ== X-Gm-Message-State: AIkVDXKiSwZnVqwPbEcipjGbNuNPrZWmlP1u4WlFbo5FKlSphNNpPQ4Nfpi1sfCoGG1bBM7i/qioIExmuE2ReQ== X-Received: by 10.159.51.18 with SMTP id o18mr2616104uab.14.1484092168828; Tue, 10 Jan 2017 15:49:28 -0800 (PST) MIME-Version: 1.0 Received: by 10.176.74.150 with HTTP; Tue, 10 Jan 2017 15:49:28 -0800 (PST) From: Lee Brown Date: Tue, 10 Jan 2017 15:49:28 -0800 Message-ID: Subject: General question about 1GB vs 10GB NIC's To: lev@freebsd.org Cc: freebsd-net , freebsd-stable@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jan 2017 23:49:30 -0000 I want to build a router that has 2 x 500mb/s radio ISP facing, 2 x 500mb/s radio's facing another site, plus a 1gb/s link to the LAN. I plan to plug everything into a switch so I can have redundant routers. So my question is should I go with 5 x 1GB NIC's or 2x10GB NIC's on the motherboard. Assume NIC's will be Intel or IBM. Going 10GB pushes the switch price ten-times, so I'd like to avoid that if possible. I'm planning to get a 4 core Xeon @3.4GHz and it would be nice to know if this is a moot point or not. Thanks -- lee From owner-freebsd-net@freebsd.org Tue Jan 10 23:58:32 2017 Return-Path: Delivered-To: freebsd-net@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 70FE9CAA48A; Tue, 10 Jan 2017 23:58:32 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:201:6350::2]) by mx1.freebsd.org (Postfix) with ESMTP id 3FC8F136F; Tue, 10 Jan 2017 23:58:32 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:e0f4:994:662:862]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPSA id 2EBF2C04; Wed, 11 Jan 2017 02:58:31 +0300 (MSK) Date: Wed, 11 Jan 2017 02:58:33 +0300 From: Lev Serebryakov Reply-To: Lev Serebryakov Organization: FreeBSD X-Priority: 3 (Normal) Message-ID: <13626377.20170111025833@serebryakov.spb.ru> To: Hiroki Sato CC: freebsd-net@freebsd.org, freebsd-stable@freebsd.org Subject: Re: IPv6 works on em0 () but not on em1 () - what's wrong?,IPv6 works on em0 () but not on em1 () - what's wrong? In-Reply-To: <20170111.084328.1155081177427359974.hrs@allbsd.org> References: <58756DDE.5000503@FreeBSD.org> <20170111.084328.1155081177427359974.hrs@allbsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jan 2017 23:58:32 -0000 Hello Hiroki, Wednesday, January 11, 2017, 2:43:28 AM, you wrote: > What happens by typing the following command? > % ping6 ff02::1%em1 % ping6 ff02::1%em1 PING6(56=40+8+8 bytes) fe80::225:90ff:fe24:6bf8%em1 --> ff02::1%em1 16 bytes from fe80::225:90ff:fe24:6bf8%em1, icmp_seq=0 hlim=64 time=0.163 ms 16 bytes from fe80::222:4dff:fe9d:e093%em1, icmp_seq=0 hlim=64 time=0.737 ms(DUP!) 16 bytes from fe80::225:90ff:fe24:6bf8%em1, icmp_seq=1 hlim=64 time=0.132 ms 16 bytes from fe80::222:4dff:fe9d:e093%em1, icmp_seq=1 hlim=64 time=0.766 ms(DUP!) 16 bytes from fe80::225:90ff:fe24:6bf8%em1, icmp_seq=2 hlim=64 time=0.086 ms 16 bytes from fe80::222:4dff:fe9d:e093%em1, icmp_seq=2 hlim=64 time=0.713 ms(DUP!) ... BTW, when I add address and default route by hands, everything starts to work. So, this NIC doesn't have problems with IPv6 per se! Looks like some weird configuration problem. -- Best regards, Lev mailto:lev@FreeBSD.org From owner-freebsd-net@freebsd.org Wed Jan 11 06:19:51 2017 Return-Path: Delivered-To: freebsd-net@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 99296CAA5E7 for ; Wed, 11 Jan 2017 06:19:51 +0000 (UTC) (envelope-from BM-2cWfdfG5CJsquqkJyry7hZT9LypbSEWEkQ@bitmessage.ch) Received: from mail.bitmessage.ch (mail.bitmessage.ch [146.228.112.252]) (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 D6873155E; Wed, 11 Jan 2017 06:19:50 +0000 (UTC) (envelope-from BM-2cWfdfG5CJsquqkJyry7hZT9LypbSEWEkQ@bitmessage.ch) dkim-signature: v=1; a=rsa-sha256; d=bitmessage.ch; s=mail; c=relaxed/relaxed; q=dns/txt; h=From:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type:Content-Transfer-Encoding:In-Reply-To:References; bh=wBVdRfEH53e7QEi0/y3f4hmcGD+nuEd9Nnie4HozqTI=; b=jy8LtbgLKDyzfJbPr2f2NZje7w1bd7/A6YzgHX1IUzmw3k2SPJF/c2qlNqRexikhgZ+donHb2oCFJpMTjTFDWWKS8YpJGn1FIxqG0SQx6Mgz14BcOBRbmTKo7EDlcwT0SfRtxObgdEbiTnttzocolkgE20Th6szfzc7Z7JzApeo= Received: from lion.3 (46-227-67-181.pool.ovpn.se [46.227.67.181]) by mail.bitmessage.ch with ESMTPSA (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256) ; Wed, 11 Jan 2017 07:19:11 +0100 Date: Wed, 11 Jan 2017 07:19:39 +0100 From: Jim To: Mark Johnston Cc: freebsd-net@freebsd.org Subject: Re: Panic in nd6_prefix_offlink() Message-Id: <20170111071939.9e3983da5cc61cfe658201da@bitmessage.ch> In-Reply-To: <20170108184815.GB34440@raichu> References: <20170107201119.22d9ceff88e935c2b3f072a1@bitmessage.ch> <20170108184815.GB34440@raichu> X-Mailer: Sylpheed 3.5.1 (GTK+ 2.24.29; amd64-portbld-freebsd10.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2017 06:19:51 -0000 On Sun, 8 Jan 2017 10:48:15 -0800 Mark Johnston wrote: > On Sat, Jan 07, 2017 at 08:11:19PM +0100, Jim wrote: > > Hello, > > > > I observe frequent crashes on Beagle Bone Black running CURRENT r311106 at home. > > My home LAN is connected to DSL provider. The CPE router gets assigned IPv6 address (ds-lite) and advertises prefix/route to the LAN. > > Every night the DSL connection is terminated by provider. Upon connection is reestablished the new IPv6 prefix is assigned to router and then advertised to LAN. > > This event seems to cause kernel panic on Beagelebone board which goes to db> prompt. > > > > Backtrace shows: nd6_timer() -> nd6_prefix_offlink() -> witness_assert() -> vpanic() > > Here is the backtrace: > > Thanks for the report. This should be addressed by r311695. Confirm that the problem is resolved. Thank you. -- Jim From owner-freebsd-net@freebsd.org Wed Jan 11 09:24:08 2017 Return-Path: Delivered-To: freebsd-net@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 47BBCCAA793; Wed, 11 Jan 2017 09:24:08 +0000 (UTC) (envelope-from cochard@gmail.com) Received: from mail-qk0-x243.google.com (mail-qk0-x243.google.com [IPv6:2607:f8b0:400d:c09::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 01B1D1BF5; Wed, 11 Jan 2017 09:24:08 +0000 (UTC) (envelope-from cochard@gmail.com) Received: by mail-qk0-x243.google.com with SMTP id 11so14521926qkl.0; Wed, 11 Jan 2017 01:24:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=qHk+1HQQXMNJmCEne6ErGzm6iHqTjvN06ucD40zRCk0=; b=vK+DTbKcV5WpgSd/4bN/9+pDPYUlfIJkISQDquMckKU+0XSqt87FpWsHLxTekLVCui IAHQep8s+KVFohS9bs8wc8VTXDEpLzHp751nVZtdQH5v6Y+wztmhk9x+zYl+LJT2lqxr YVxKkB3k028beWz4M6s0OKq8aF4phG8xq8Xjzo2n+umR+zussQpIonNY4dHQ2lvFYEBw pcnYSzJeacvy6qbmJURMel1CiR7S6VM/6wiMjT4piFVW641oHpLxfHhwC0uO9VD8vuhC AEOhygGdiBKvtB1+JNWrkufIMv703JAPC5AMgjl7Rmsurj6CAd5ZWncfF8a0YpHTom2q GcQQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=qHk+1HQQXMNJmCEne6ErGzm6iHqTjvN06ucD40zRCk0=; b=IQlNczWsARa6VeSgLY/kxA0CIrwsTXnX0LJoqrvGmJ7IHnQTdy7TQ4kS4YCi8KFcFD SUyjZwbtiijPxqAvgZxaoW3ylxlJfOShXHFufYNZXTkqLsAwdN/SlFCsL1ATvF6Raa2g f8w8HKGqwanZj4PEQmCvxTWtgvUO+LgXxflX7h/dUvLrCPnPZ8UVCCiXK1+xCSLMvL4k Aibq1fwJNVkR6su1IZPyzs9988Wj90q6l2WPkixYVRvnLNXa1VOl6nsNdHae/xPvnK8f SxveLs6YAc5jSQSsz2L/vuP376IKnLNlAhRZwQ0SMH3Bw1y0xY8mWku6V5g8Vd7Lj9lJ C26w== X-Gm-Message-State: AIkVDXLXDHLRxBmDiLbyXU/8LvsgHd2ym9BJCATg31DJSH24kaQeS+8r0/rpeOR0JHRl0SNuXkpmN46+hh+m4w== X-Received: by 10.55.151.199 with SMTP id z190mr7599149qkd.166.1484126647057; Wed, 11 Jan 2017 01:24:07 -0800 (PST) MIME-Version: 1.0 Sender: cochard@gmail.com Received: by 10.237.34.248 with HTTP; Wed, 11 Jan 2017 01:23:46 -0800 (PST) In-Reply-To: References: <30f21c75-d3a2-edcd-1999-d5ed9f970c06@freebsd.org> From: =?UTF-8?Q?Olivier_Cochard=2DLabb=C3=A9?= Date: Wed, 11 Jan 2017 10:23:46 +0100 X-Google-Sender-Auth: eyUA-q2jh4dSxdpfolN-B8JC0WY Message-ID: Subject: Re: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb pending To: Sean Bruno , "freebsd-net@freebsd.org" Cc: "freebsd-current@freebsd.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2017 09:24:08 -0000 On Tue, Jan 10, 2017 at 4:31 AM, Sean Bruno wrote: > > I've updated sys/dev/e1000 at svn R311849 to match Matt Macy's work on > IFLIB in the kernel. > > At this point, the driver deviates from Intel's code dramatically and > you now get to yell directly into the freebsd-net@ megaphone for things > that I may have broken. > > > =E2=80=8BI've got problem with this new drivers regarding number of queues = used on a Netgate RCC-VE 4860 (Intel i354 NIC). =E2=80=8BOnly one queue in place of 4 (on a 4 cores proc) previously: Perfo= rmance drops dramatically. BEFORE (r311848) : igb2: port 0x3000-0x301f mem 0xdfea0000-0xdfebffff,0xdff24000-0xdff27fff irq 18 at device 20.0 on pci0 igb2: Using MSIX interrupts with 5 vectors igb2: Ethernet address: 00:08:a2:09:33:da igb2: Bound queue 0 to cpu 0 igb2: Bound queue 1 to cpu 1 igb2: Bound queue 2 to cpu 2 igb2: Bound queue 3 to cpu 3 igb2: netmap queues/slots: TX 4/2048, RX 4/2048 AFTER (r3118489): igb2: port 0x3000-0x301f mem 0xdfea0000-0xdfebffff,0xdff24000-0xdff27fff irq 18 at device 20.0 on pci0 igb2: attach_pre capping queues at 8 igb2: using 1024 tx descriptors and 1024 rx descriptors igb2: msix_init qsets capped at 8 igb2: Unable to map MSIX table igb2: Using an MSI interrupt igb2: allocated for 1 tx_queues igb2: allocated for 1 rx_queues igb2: Ethernet address: 00:08:a2:09:33:da igb2: netmap queues/slots: TX 1/1024, RX 1/1024 =E2=80=8BNIC information:=E2=80=8B =E2=80=8Bigb2@pci0:0:20:0: class=3D0x020000 card=3D0x1f418086 chip=3D= 0x1f418086 rev=3D0x03 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D 'Ethernet Connection I354' class =3D network subclass =3D ethernet bar [10] =3D type Memory, range 64, base 0xdfea0000, size 131072, enabled bar [18] =3D type I/O Port, range 32, base 0x3000, size 32, enabled bar [20] =3D type Memory, range 64, base 0xdff24000, size 16384, enab= led cap 01[40] =3D powerspec 3 supports D0 D3 current D0 cap 05[50] =3D MSI supports 1 message, 64 bit, vector masks cap 11[70] =3D MSI-X supports 10 messages, enabled Table in map 0x20[0x0], PBA in map 0x20[0x2000] cap 10[a0] =3D PCI-Express 2 root endpoint max data 128(512) FLR RO NS ecap 0001[100] =3D AER 2 0 fatal 0 non-fatal 0 corrected ecap 0003[140] =3D Serial 1 0008a2ffff0933da ecap 0017[1a0] =3D TPH Requester 1 ecap 000d[1d0] =3D ACS 1 igb3@pci0:0:20:1: class=3D0x020000 card=3D0x1f4 From owner-freebsd-net@freebsd.org Wed Jan 11 09:43:18 2017 Return-Path: Delivered-To: freebsd-net@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 B9676CAAF1B for ; Wed, 11 Jan 2017 09:43:18 +0000 (UTC) (envelope-from jpa@semihalf.com) Received: from mail-vk0-x22f.google.com (mail-vk0-x22f.google.com [IPv6:2607:f8b0:400c:c05::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 81E1D16DD for ; Wed, 11 Jan 2017 09:43:18 +0000 (UTC) (envelope-from jpa@semihalf.com) Received: by mail-vk0-x22f.google.com with SMTP id 137so376661419vkl.0 for ; Wed, 11 Jan 2017 01:43:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=semihalf-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=3dEYdjvlSIL0IyVYGffTD2Zx20SuxV2WnHKdPRyg95Y=; b=YrN0yV5cqEB/8Tf4EqXCbCvNoBZLlfq5vPledTgmysztgGNaPg/qfosB3Hz6etRaZt Sr9n4RVJRNs0TbUJAFaWcXc77Ic+aZOhgk4CzS23nzJuD/mgZsgfkArJqv+zySA1Wqnm H4NKRKIxUd1KX647iORVHd3HJN6tUUzC6HRR359aEv43G8CrXz86mwXOdre+szUUSKvK 9xC3N+96YaXXE+wx9/9GPQ/MIHDEOZej8nlJt7upDoMqHVA3ZWjrjb4uKmpTmA8iZGMF iexl5EdEmd5Srh+2RBATQlDGR5lUllucqeYDEGNb190vf1BX9Tg84+2FqENEyawmvDSY kesQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=3dEYdjvlSIL0IyVYGffTD2Zx20SuxV2WnHKdPRyg95Y=; b=lQTfLpbljr9Mzv2I88jFIHtcd4EyamjBEvlo83i/PU6AiBBwjYsVeiBF005ySanLU3 ksFnD6Oy6fxoxnPzrGVIi8gFgwhe/e+CVHe42tEbQkWkDI7KO2iQVircwOEgLhpBWRwn deD+8wkZSdq8zyM7D2n2A/v7O/R11/gzjD4gpmnY4fERNjgM6zjm6SF+4YjUPq6kVaTV jmDxDEuqBVeM/G0BfdOX2vtlY3nDpgPc2eyWv/DJdKM2E6W0qfBIudK6YyOKF5M/WE9e iypM5Lr4gs04zj2hDHlSSd29AYSETIgvYFkrxpt5v5/a9Eu8UoId8dJ1GpYpCI3A3cBX mN3A== X-Gm-Message-State: AIkVDXJ4WCSLktc91nKLActm2TwbqXjeYTBjZZWqyiL6dtySP8cRK+GcnsOiP7NxSkSYVuem/0xbT1hMHRPomg== X-Received: by 10.31.87.6 with SMTP id l6mr3056312vkb.116.1484127797554; Wed, 11 Jan 2017 01:43:17 -0800 (PST) MIME-Version: 1.0 Received: by 10.31.46.18 with HTTP; Wed, 11 Jan 2017 01:42:47 -0800 (PST) In-Reply-To: <20161129190509.GO27748@FreeBSD.org> References: <20161128221033.GM55731@strugglingcoder.info> <20161129190509.GO27748@FreeBSD.org> From: Jakub Palider Date: Wed, 11 Jan 2017 10:42:47 +0100 Message-ID: Subject: Re: FLOWTABLE aka TCP route caching panic To: Gleb Smirnoff Cc: hiren panchasara , freebsd-net@freebsd.org, karels@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2017 09:43:18 -0000 On Tue, 29 Nov 2016 11:05:09 -0800 Gleb Smirnoff wrote: > On Mon, Nov 28, 2016 at 02:10:33PM -0800, hiren panchasara wrote: > h> > Hi, > h> > I have found that last month (19 Oct) the problem appeared on this list, > h> > and to my experience it persists, both on VM and bare metal installation > h> > (HEAD from yesterday). I looks that enabling FLOWTABLE option is the only > h> > source of this fault happening. It appears on our setup in 80% cases within > h> > one hour from boot up. > h> > From our debugging, it is caused by lock on DESTROYED lock. Did you find a > h> > solution to this problem? > > Not yet. > > I'm pretty sure that reverting my r307234 will fix your crashes. However, I still > believe that r307234 is a proper way of fixing things, not r300854 which just > plugged the problem in the nearest place to the crash. But as we all see r307234 > is definitely missing some code path, which still allows for stale route to be > referenced. > > -- > Totus tuus, Glebius. Thank you for your pointer, in helped at some point. The problem however returned, especially when under heavy, continuous load. We are running 4 iperf3 processes, each having 4 threads, and the machine dies after 30-60 minutes of TCP traffic. I am running rS30911112 from Nov 24. On FreeBSD 11.0-RELEASE this problem (1 full day of testing) was not noticed. Could you point to related commits that might also influence this behaviour? Thanks, Jakub From owner-freebsd-net@freebsd.org Wed Jan 11 12:54:15 2017 Return-Path: Delivered-To: freebsd-net@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 2A07FCA8D53; Wed, 11 Jan 2017 12:54:15 +0000 (UTC) (envelope-from mmacy@nextbsd.org) Received: from sender163-mail.zoho.com (sender163-mail.zoho.com [74.201.84.163]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 19B851821; Wed, 11 Jan 2017 12:54:14 +0000 (UTC) (envelope-from mmacy@nextbsd.org) Received: from mail.zoho.com by mx.zohomail.com with SMTP id 1484139249456444.98438677326976; Wed, 11 Jan 2017 04:54:09 -0800 (PST) Date: Wed, 11 Jan 2017 04:54:09 -0800 From: Matthew Macy To: =?UTF-8?Q?=22Olivier_Cochard-Labb=C3=A9=22?= Cc: "Sean Bruno" , "freebsd-net@freebsd.org" , "freebsd-current@freebsd.org" Message-ID: <1598d97bf2a.c6bcb76838987.6501340920645175463@nextbsd.org> In-Reply-To: References: <30f21c75-d3a2-edcd-1999-d5ed9f970c06@freebsd.org> Subject: Re: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb pending MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Priority: Medium User-Agent: Zoho Mail X-Mailer: Zoho Mail X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2017 12:54:15 -0000 ---- On Wed, 11 Jan 2017 01:23:46 -0800 Olivier Cochard-Labb=C3=A9 wrote ----=20 > On Tue, Jan 10, 2017 at 4:31 AM, Sean Bruno wrote: >=20 > > > > I've updated sys/dev/e1000 at svn R311849 to match Matt Macy's work on > > IFLIB in the kernel. > > > > At this point, the driver deviates from Intel's code dramatically and > > you now get to yell directly into the freebsd-net@ megaphone for thing= s > > that I may have broken. > > > > > > > =E2=80=8BI've got problem with this new drivers regarding number of queu= es used on > a Netgate RCC-VE 4860 (Intel i354 NIC). > =E2=80=8BOnly one queue in place of 4 (on a 4 cores proc) previously: Pe= rformance > drops dramatically. >=20 > BEFORE (r311848) : >=20 > igb2: port > 0x3000-0x301f mem 0xdfea0000-0xdfebffff,0xdff24000-0xdff27fff irq 18 at > device 20.0 on pci0 > igb2: Using MSIX interrupts with 5 vectors > igb2: Ethernet address: 00:08:a2:09:33:da > igb2: Bound queue 0 to cpu 0 > igb2: Bound queue 1 to cpu 1 > igb2: Bound queue 2 to cpu 2 > igb2: Bound queue 3 to cpu 3 > igb2: netmap queues/slots: TX 4/2048, RX 4/2048 >=20 > AFTER (r3118489): >=20 > igb2: port 0x3000-0x301f = mem > 0xdfea0000-0xdfebffff,0xdff24000-0xdff27fff irq 18 at device 20.0 on pci= 0 > igb2: attach_pre capping queues at 8 > igb2: using 1024 tx descriptors and 1024 rx descriptors > igb2: msix_init qsets capped at 8 > igb2: Unable to map MSIX table It has the wrong msix bar for your device. I'll look in to it. -M > igb2: Using an MSI interrupt > igb2: allocated for 1 tx_queues > igb2: allocated for 1 rx_queues > igb2: Ethernet address: 00:08:a2:09:33:da > igb2: netmap queues/slots: TX 1/1024, RX 1/1024 >=20 > =E2=80=8BNIC information:=E2=80=8B >=20 > =E2=80=8Bigb2@pci0:0:20:0: class=3D0x020000 card=3D0x1f418086 chip= =3D0x1f418086 > rev=3D0x03 hdr=3D0x00 > vendor =3D 'Intel Corporation' > device =3D 'Ethernet Connection I354' > class =3D network > subclass =3D ethernet > bar [10] =3D type Memory, range 64, base 0xdfea0000, size 131072, > enabled > bar [18] =3D type I/O Port, range 32, base 0x3000, size 32, enable= d > bar [20] =3D type Memory, range 64, base 0xdff24000, size 16384, e= nabled > cap 01[40] =3D powerspec 3 supports D0 D3 current D0 > cap 05[50] =3D MSI supports 1 message, 64 bit, vector masks > cap 11[70] =3D MSI-X supports 10 messages, enabled > Table in map 0x20[0x0], PBA in map 0x20[0x2000] > cap 10[a0] =3D PCI-Express 2 root endpoint max data 128(512) FLR RO = NS > ecap 0001[100] =3D AER 2 0 fatal 0 non-fatal 0 corrected > ecap 0003[140] =3D Serial 1 0008a2ffff0933da > ecap 0017[1a0] =3D TPH Requester 1 > ecap 000d[1d0] =3D ACS 1 > igb3@pci0:0:20:1: class=3D0x020000 card=3D0x1f4 > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.or= g" From owner-freebsd-net@freebsd.org Wed Jan 11 15:17:39 2017 Return-Path: Delivered-To: freebsd-net@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 2427FCAA62B; Wed, 11 Jan 2017 15:17:39 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from mail.ignoranthack.me (ignoranthack.me [199.102.79.106]) (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 F3DF01C4A; Wed, 11 Jan 2017 15:17:38 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from [192.168.0.6] (67-0-248-244.albq.qwest.net [67.0.248.244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: sbruno@ignoranthack.me) by mail.ignoranthack.me (Postfix) with ESMTPSA id E0B301928BA; Wed, 11 Jan 2017 15:17:36 +0000 (UTC) Subject: Re: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb pending To: Matthew Macy , =?UTF-8?Q?Olivier_Cochard-Labb=c3=a9?= References: <30f21c75-d3a2-edcd-1999-d5ed9f970c06@freebsd.org> <1598d97bf2a.c6bcb76838987.6501340920645175463@nextbsd.org> Cc: "freebsd-net@freebsd.org" , "freebsd-current@freebsd.org" From: Sean Bruno Message-ID: <574a7ac7-4842-9518-8286-a4d89a9f7a27@freebsd.org> Date: Wed, 11 Jan 2017 08:17:33 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: <1598d97bf2a.c6bcb76838987.6501340920645175463@nextbsd.org> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="3xRIfR4hHTsqOg8lK9xvHtQsBq0dsLW7a" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2017 15:17:39 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --3xRIfR4hHTsqOg8lK9xvHtQsBq0dsLW7a Content-Type: multipart/mixed; boundary="jOcuW0rdPk7diIb8EiUt34UHcmCK2AQmC"; protected-headers="v1" From: Sean Bruno To: Matthew Macy , =?UTF-8?Q?Olivier_Cochard-Labb=c3=a9?= Cc: "freebsd-net@freebsd.org" , "freebsd-current@freebsd.org" Message-ID: <574a7ac7-4842-9518-8286-a4d89a9f7a27@freebsd.org> Subject: Re: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb pending References: <30f21c75-d3a2-edcd-1999-d5ed9f970c06@freebsd.org> <1598d97bf2a.c6bcb76838987.6501340920645175463@nextbsd.org> In-Reply-To: <1598d97bf2a.c6bcb76838987.6501340920645175463@nextbsd.org> --jOcuW0rdPk7diIb8EiUt34UHcmCK2AQmC Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 01/11/17 05:54, Matthew Macy wrote: >=20 >=20 >=20 > ---- On Wed, 11 Jan 2017 01:23:46 -0800 Olivier Cochard-Labb=C3=A9 wrote ----=20 > > On Tue, Jan 10, 2017 at 4:31 AM, Sean Bruno wro= te: > >=20 > > > > > > I've updated sys/dev/e1000 at svn R311849 to match Matt Macy's wor= k on > > > IFLIB in the kernel. > > > > > > At this point, the driver deviates from Intel's code dramatically = and > > > you now get to yell directly into the freebsd-net@ megaphone for t= hings > > > that I may have broken. > > > > > > > > > > > =E2=80=8BI've got problem with this new drivers regarding number of = queues used on > > a Netgate RCC-VE 4860 (Intel i354 NIC). > > =E2=80=8BOnly one queue in place of 4 (on a 4 cores proc) previously= : Performance > > drops dramatically. > >=20 > > igb2: port 0x3000-0x3= 01f mem > > 0xdfea0000-0xdfebffff,0xdff24000-0xdff27fff irq 18 at device 20.0 on= pci0 > > igb2: attach_pre capping queues at 8 > > igb2: using 1024 tx descriptors and 1024 rx descriptors > > igb2: msix_init qsets capped at 8 > > igb2: Unable to map MSIX table >=20 > It has the wrong msix bar for your device. I'll look in to it. >=20 Olivier: Give this a quick try. This isn't the correct way to do this, but I want to see if I'm on the right path: Index: sys/net/iflib.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- sys/net/iflib.c (revision 311875) +++ sys/net/iflib.c (working copy) @@ -4721,7 +4721,7 @@ if_softc_ctx_t scctx =3D &ctx->ifc_softc_ctx; int vectors, queues, rx_queues, tx_queues, queuemsgs, msgs; int iflib_num_tx_queues, iflib_num_rx_queues; - int err, admincnt, bar; + int err, admincnt, bar, use_different_bar; iflib_num_tx_queues =3D scctx->isc_ntxqsets; iflib_num_rx_queues =3D scctx->isc_nrxqsets; @@ -4729,6 +4729,16 @@ device_printf(dev, "msix_init qsets capped at %d\n", iflib_num_tx_queue= s); =09 bar =3D ctx->ifc_softc_ctx.isc_msix_bar; + + /* + ** Some new devices, as with ixgbe, now may + ** use a different BAR, so we need to keep + ** track of which is used. + */ + use_different_bar =3D pci_read_config(dev, bar, 4); + if (use_different_bar =3D=3D 0) + bar +=3D 4; + admincnt =3D sctx->isc_admin_intrcnt; /* Override by tuneable */ if (enable_msix =3D=3D 0) --jOcuW0rdPk7diIb8EiUt34UHcmCK2AQmC-- --3xRIfR4hHTsqOg8lK9xvHtQsBq0dsLW7a Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEEuq1GMucSHejSCZfdEgHvyh5yfmQFAlh2TI1fFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEJB QUQ0NjMyRTcxMjFERThEMjA5OTdERDEyMDFFRkNBMUU3MjdFNjQACgkQEgHvyh5y fmTrTwf/bVWrOFm8VV+v/QmGEIJYfhUCKaSRVx/4l7hKIXYf6ImPGMhDb7YC4Bmp kKXdG1RenZwmwogOzRfsyCFDZFZmjv42NIuuFwl6AFh2u3sYuWWaYjXLw15S5jea u7fOzTfMdxPs9BeBZzaKSZtOqHJHHV46u9z6gL3Aimg5+a4XouuFo3Zhfvgeqegi 7+l08gL21LEgQ/3pQPfQ5xIcP7nyBTxWJGDwlLW6DZREst/uahRvl5akDC/lfhgF cF1rinUZDqVXTkJTh6iS7SEsPFI6r+szkfjVZz5LMIyTkGqg6GteqbOwQtRsTEaZ S9e0CN7n7iTsU6XftMwj5VyjAqGbag== =GdV1 -----END PGP SIGNATURE----- --3xRIfR4hHTsqOg8lK9xvHtQsBq0dsLW7a-- From owner-freebsd-net@freebsd.org Wed Jan 11 15:23:37 2017 Return-Path: Delivered-To: freebsd-net@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 16274CAAA71 for ; Wed, 11 Jan 2017 15:23:37 +0000 (UTC) (envelope-from citrin+bsd@citrin.ru) Received: from hz.citrin.ru (hz.citrin.ru [88.198.212.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D52291164 for ; Wed, 11 Jan 2017 15:23:36 +0000 (UTC) (envelope-from citrin+bsd@citrin.ru) Received: from x220.lan (c-24-60-168-172.hsd1.ct.comcast.net [24.60.168.172]) by hz.citrin.ru (Postfix) with ESMTPSA id 426C829A309 for ; Wed, 11 Jan 2017 15:23:28 +0000 (UTC) From: Anton Yuzhaninov Subject: fe80::1%lo0 To: freebsd-net@FreeBSD.org Message-ID: <94a99b96-808b-8f50-a4a3-eec8659737cd@citrin.ru> Date: Wed, 11 Jan 2017 10:23:26 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=citrin.ru; s=s0; t=1484148208; bh=1By8mEZqAktq8BSs2/QNN8ZPz9oE6VHEacWgv0Cv7H0=; h=From:Subject:To:Message-ID:Date:MIME-Version:Content-Type:Content-Transfer-Encoding; b=5xIUL68sS7ldS5aHhtDtWu3ANocbjyamePkfeDY2KtJvHJi5U10tRPr6ykCI/XM3uAdoXzwHvyl2UEbE7C0nyNsipz5qHjVWNZjYmZxYDtsi62IoT5VAUUQWAIexAf1QUbr0WfMeFgLjwwx4L4MXsCWjaLlPgHcIAyNKGeEFFC0= X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2017 15:23:37 -0000 Hello, Why FreeBSD adds fe80::1%lo0 to the loopback interface? I know, that in IPv6 each interface should have a link-local address, but ::1 can be considered as link-local: https://tools.ietf.org/html/rfc4291#section-2.5.3 I think fe80::1 is unnecessary can be removed. For all practical purposes ::1 should be enough. BTW Linux has only ::1 on the loopback interface. From owner-freebsd-net@freebsd.org Wed Jan 11 15:51:39 2017 Return-Path: Delivered-To: freebsd-net@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 540BBCAB3E6 for ; Wed, 11 Jan 2017 15:51:39 +0000 (UTC) (envelope-from hrs@FreeBSD.org) Received: from mail.allbsd.org (gatekeeper.allbsd.org [IPv6:2001:2f0:104:e001::32]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.allbsd.org", Issuer "RapidSSL SHA256 CA - G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D78311FD5 for ; Wed, 11 Jan 2017 15:51:38 +0000 (UTC) (envelope-from hrs@FreeBSD.org) Received: from mail-d.allbsd.org (p2027-ipbf1605funabasi.chiba.ocn.ne.jp [123.225.191.27]) (authenticated bits=56) by mail.allbsd.org (8.15.2/8.15.2) with ESMTPSA id v0BFp5ch055069 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) (Client CN "/OU=GT07882699/OU=See+20www.rapidssl.com/resources/cps+20+28c+2915/OU=Domain+20Control+20Validated+20-+20RapidSSL+28R+29/CN=*.allbsd.org", Issuer "/C=US/O=GeoTrust+20Inc./CN=RapidSSL+20SHA256+20CA+20-+20G3"); Thu, 12 Jan 2017 00:51:25 +0900 (JST) (envelope-from hrs@FreeBSD.org) Received: from alph.allbsd.org (alph.allbsd.org [192.168.0.10]) by mail-d.allbsd.org (8.15.2/8.15.2) with ESMTPS id v0BFnnP1013784 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 12 Jan 2017 00:49:49 +0900 (JST) (envelope-from hrs@FreeBSD.org) Received: from localhost (localhost [IPv6:::1]) (authenticated bits=0) by alph.allbsd.org (8.15.2/8.15.2) with ESMTPA id v0BFnlIr013781; Thu, 12 Jan 2017 00:49:49 +0900 (JST) (envelope-from hrs@FreeBSD.org) Date: Thu, 12 Jan 2017 00:49:30 +0900 (JST) Message-Id: <20170112.004930.1372286639994163593.hrs@allbsd.org> To: citrin+bsd@citrin.ru Cc: freebsd-net@FreeBSD.org Subject: Re: fe80::1%lo0 From: Hiroki Sato In-Reply-To: <94a99b96-808b-8f50-a4a3-eec8659737cd@citrin.ru> References: <94a99b96-808b-8f50-a4a3-eec8659737cd@citrin.ru> X-PGPkey-fingerprint: BDB3 443F A5DD B3D0 A530 FFD7 4F2C D3D8 2793 CF2D X-Mailer: Mew version 6.7 on Emacs 25.1 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Multipart/Signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="--Security_Multipart(Thu_Jan_12_00_49_30_2017_204)--" Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamav-milter 0.99 at gatekeeper.allbsd.org X-Virus-Status: Clean X-Greylist: Sender DNS name whitelisted, not delayed by milter-greylist-4.4.3 (mail.allbsd.org [133.31.130.32]); Thu, 12 Jan 2017 00:51:26 +0900 (JST) X-Spam-Status: No, score=-99.9 required=13.0 tests=CONTENT_TYPE_PRESENT, QENCPTR1,USER_IN_WHITELIST autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on gatekeeper.allbsd.org X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2017 15:51:39 -0000 ----Security_Multipart(Thu_Jan_12_00_49_30_2017_204)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Anton Yuzhaninov wrote in <94a99b96-808b-8f50-a4a3-eec8659737cd@citrin.ru>: ci> Hello, ci> ci> Why FreeBSD adds fe80::1%lo0 to the loopback interface? ci> ci> I know, that in IPv6 each interface should have a link-local address, ci> but ::1 can be considered as link-local: ci> https://tools.ietf.org/html/rfc4291#section-2.5.3 FreeBSD's IPv6 stack was written before RFC 4291 clarifies whether ::1 is a link-local address or not---currently the implementation does not recognize ::1 as an address with link-local scope. ci> I think fe80::1 is unnecessary can be removed. For all practical ci> purposes ::1 should be enough. No. It may work with no link-local address but an unexpected behavior can happen in the kernel even if it is not harmful actually. If we really want to remove it, address scope of ::1 needs to be changed throughout the kernel in a consistent manner first. -- Hiroki ----Security_Multipart(Thu_Jan_12_00_49_30_2017_204)-- Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEABECAAYFAlh2VAoACgkQTyzT2CeTzy0vTwCfSYMvmIenswh4+qf8DcI2qPu7 hD8AnjX6EZpQta8Vk4GGu1bvQ8rzetvt =dink -----END PGP SIGNATURE----- ----Security_Multipart(Thu_Jan_12_00_49_30_2017_204)---- From owner-freebsd-net@freebsd.org Wed Jan 11 17:24:53 2017 Return-Path: Delivered-To: freebsd-net@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 40C5DCAB091 for ; Wed, 11 Jan 2017 17:24:53 +0000 (UTC) (envelope-from Michael.Tuexen@lurchi.franken.de) Received: from drew.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.franken.de", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BD3761F72; Wed, 11 Jan 2017 17:24:52 +0000 (UTC) (envelope-from Michael.Tuexen@lurchi.franken.de) Received: from [IPv6:2003:cd:6bc9:5900:6d10:a969:52d7:de0f] (p200300CD6BC959006D10A96952D7DE0F.dip0.t-ipconnect.de [IPv6:2003:cd:6bc9:5900:6d10:a969:52d7:de0f]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTPSA id 7BBE4721E281A; Wed, 11 Jan 2017 18:24:48 +0100 (CET) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: Re: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb pending From: Michael Tuexen In-Reply-To: <092ad9f7-b04c-292f-c626-6ce1956580a8@freebsd.org> Date: Wed, 11 Jan 2017 18:24:46 +0100 Cc: freebsd-net@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <44D9E8B2-1045-4B01-9EB5-B2F25932D8FB@lurchi.franken.de> References: <092ad9f7-b04c-292f-c626-6ce1956580a8@freebsd.org> To: Sean Bruno X-Mailer: Apple Mail (2.3259) X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=disabled version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail-n.franken.de X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2017 17:24:53 -0000 > On 10 Jan 2017, at 04:32, Sean Bruno wrote: >=20 > tl;dir --> you get to keep your igbX devices(thanks jhb), no POLA > violations this week. >=20 > I've updated sys/dev/e1000 at svn R311849 to match Matt Macy's work on > IFLIB in the kernel. >=20 > At this point, the driver deviates from Intel's code dramatically and > you now get to yell directly into the freebsd-net@ megaphone for = things > that I may have broken. My testing shows that sending SCTP/IPv4, SCTP/IPv6, TCP/IPv6, and = UDP/IPV6 is broken since the checksum offload doesn't work. The following patch fixes the issue: Index: if_em.h =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- if_em.h (revision 311887) +++ if_em.h (working copy) @@ -330,7 +330,7 @@ #define EM_MSIX_LINK 0x01000000 /* For 82574 use */ #define ETH_ZLEN 60 #define ETH_ADDR_LEN 6 -#define CSUM_OFFLOAD 7 /* Offload bits in mbuf flag */ +#define CSUM_OFFLOAD 0xE0F /* Offload bits in mbuf flag */ #define IGB_PKTTYPE_MASK 0x0000FFF0 #define IGB_DMCTLX_DCFLUSH_DIS 0x80000000 /* Disable DMA Coalesce = Flush */ The magic number 7 is CSUM_IP | CSUM_IP_UDP | CSUM_IP_TCP, which means that checksum offloading is working for TCP/IPv4 and UDP/IPv4. It should be 0xE0F, which is CSUM_IP | CSUM_IP_UDP | CSUM_IP_TCP | CSUM_IP_SCTP | CSUM_IP6_UDP | = CSUM_IP6_TCP | CSUM_IP6_SCTP. I have tested the above patch with an igb card which supports all these = offloads. Best regards Michael >=20 > man page updates are coming up next. Please let us know if this > revision has made things better, worse or none-of-the above on = whatever > Intel Gigabit NIC you happen to have lying around. >=20 > sean >=20 > On 01/05/17 20:18, Sean Bruno wrote: >> tl;dr --> igbX devices will become emX devices >>=20 >> We're about to commit an update to sys/dev/e1000 that will implement = and >> activate IFLIB for em(4), lem(4) & igb(4) and would appreciate all = folks >> who can test and poke at the drivers to do so this week. This will = have >> some really great changes for performance and standardization that = have >> been bouncing around inside of various FreeBSD shops that have been >> collaborating with Matt Macy over the last year. >>=20 >> This will implement multiple queues for certain em(4) devices that = are >> capable of such things and add some new sysctl's for you to poke at = in >> your monitoring tools. >>=20 >> Due to limitations of device registration, igbX devices will become = emX >> devices. So, you'll need to make a minor update to your rc.conf and >> scripts that manipulate the network devices. >>=20 >> UPDATING will be bumped to reflect these changes. >>=20 >> MFC to stable/11 will have a legacy implementation that doesn't use >> IFLIB for compatibility reasons. >>=20 >> A documentation and man page update will follow in the next few days >> explaining how to work with the changed driver. >>=20 >> sean >>=20 >> bcc net@ current@ re@ >>=20 >>=20 >>=20 >>=20 >>=20 >=20 From owner-freebsd-net@freebsd.org Wed Jan 11 17:43:08 2017 Return-Path: Delivered-To: freebsd-net@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 6EB7FCAB646 for ; Wed, 11 Jan 2017 17:43:08 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from mail.ignoranthack.me (ignoranthack.me [199.102.79.106]) (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 365AE1C1F for ; Wed, 11 Jan 2017 17:43:07 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from [192.168.0.6] (67-0-248-244.albq.qwest.net [67.0.248.244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: sbruno@ignoranthack.me) by mail.ignoranthack.me (Postfix) with ESMTPSA id B81691928BA; Wed, 11 Jan 2017 17:43:05 +0000 (UTC) Subject: Re: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb pending To: Michael Tuexen References: <092ad9f7-b04c-292f-c626-6ce1956580a8@freebsd.org> <44D9E8B2-1045-4B01-9EB5-B2F25932D8FB@lurchi.franken.de> Cc: freebsd-net@freebsd.org From: Sean Bruno Message-ID: <0d86bda1-e2d7-5df6-6fa2-35409f3ae912@freebsd.org> Date: Wed, 11 Jan 2017 10:43:02 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: <44D9E8B2-1045-4B01-9EB5-B2F25932D8FB@lurchi.franken.de> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="3gBaAjshtnFX9ImwIwnXLuuBmDHwOQiKS" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2017 17:43:08 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --3gBaAjshtnFX9ImwIwnXLuuBmDHwOQiKS Content-Type: multipart/mixed; boundary="dalJa63uu556w9AwMH8QSEBbqxsMHjTAc"; protected-headers="v1" From: Sean Bruno To: Michael Tuexen Cc: freebsd-net@freebsd.org Message-ID: <0d86bda1-e2d7-5df6-6fa2-35409f3ae912@freebsd.org> Subject: Re: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb pending References: <092ad9f7-b04c-292f-c626-6ce1956580a8@freebsd.org> <44D9E8B2-1045-4B01-9EB5-B2F25932D8FB@lurchi.franken.de> In-Reply-To: <44D9E8B2-1045-4B01-9EB5-B2F25932D8FB@lurchi.franken.de> --dalJa63uu556w9AwMH8QSEBbqxsMHjTAc Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 01/11/17 10:24, Michael Tuexen wrote: >> On 10 Jan 2017, at 04:32, Sean Bruno wrote: >> >> tl;dir --> you get to keep your igbX devices(thanks jhb), no POLA >> violations this week. >> >> I've updated sys/dev/e1000 at svn R311849 to match Matt Macy's work on= >> IFLIB in the kernel. >> >> At this point, the driver deviates from Intel's code dramatically and >> you now get to yell directly into the freebsd-net@ megaphone for thing= s >> that I may have broken. > My testing shows that sending SCTP/IPv4, SCTP/IPv6, TCP/IPv6, and UDP/I= PV6 > is broken since the checksum offload doesn't work. >=20 > The following patch fixes the issue: >=20 > Index: if_em.h > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > --- if_em.h (revision 311887) > +++ if_em.h (working copy) > @@ -330,7 +330,7 @@ > #define EM_MSIX_LINK 0x01000000 /* For 82574 use */ > #define ETH_ZLEN 60 > #define ETH_ADDR_LEN 6 > -#define CSUM_OFFLOAD 7 /* Offload bits in mbuf flag */= > +#define CSUM_OFFLOAD 0xE0F /* Offload bits in mbuf flag */= >=20 > #define IGB_PKTTYPE_MASK 0x0000FFF0 > #define IGB_DMCTLX_DCFLUSH_DIS 0x80000000 /* Disable DMA Coalesce Flu= sh */ >=20 > The magic number 7 is CSUM_IP | CSUM_IP_UDP | CSUM_IP_TCP, which means > that checksum offloading is working for TCP/IPv4 and UDP/IPv4. > It should be 0xE0F, which is > CSUM_IP | CSUM_IP_UDP | CSUM_IP_TCP | CSUM_IP_SCTP | CSUM_IP6_UDP | CSU= M_IP6_TCP | CSUM_IP6_SCTP. >=20 > I have tested the above patch with an igb card which supports all these= offloads. >=20 > Best regards > Michael >> >> man page updates are coming up next. Please let us know if this >> revision has made things better, worse or none-of-the above on whateve= r >> Intel Gigabit NIC you happen to have lying around. >> >> sean >> >> On 01/05/17 20:18, Sean Bruno wrote: >>> tl;dr --> igbX devices will become emX devices >>> >>> We're about to commit an update to sys/dev/e1000 that will implement = and >>> activate IFLIB for em(4), lem(4) & igb(4) and would appreciate all fo= lks >>> who can test and poke at the drivers to do so this week. This will h= ave >>> some really great changes for performance and standardization that ha= ve >>> been bouncing around inside of various FreeBSD shops that have been >>> collaborating with Matt Macy over the last year. >>> >>> This will implement multiple queues for certain em(4) devices that ar= e >>> capable of such things and add some new sysctl's for you to poke at i= n >>> your monitoring tools. >>> >>> Due to limitations of device registration, igbX devices will become e= mX >>> devices. So, you'll need to make a minor update to your rc.conf and >>> scripts that manipulate the network devices. >>> >>> UPDATING will be bumped to reflect these changes. >>> >>> MFC to stable/11 will have a legacy implementation that doesn't use >>> IFLIB for compatibility reasons. >>> >>> A documentation and man page update will follow in the next few days >>> explaining how to work with the changed driver. >>> >>> sean >>> >>> bcc net@ current@ re@ >>> >>> >>> >>> >>> >> >=20 >=20 Thanks. What I'll do here is restore the CSUM_OFFLOAD settings in the igb(4) case. How does this work for you? Index: em_txrx.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- em_txrx.c (revision 311875) +++ em_txrx.c (working copy) @@ -304,7 +304,7 @@ if (do_tso) { i =3D em_tso_setup(sc, pi, &txd_upper, &txd_lower); tso_desc =3D TRUE; - } else if (csum_flags & CSUM_OFFLOAD) { + } else if (csum_flags & EM_CSUM_OFFLOAD) { i =3D em_transmit_checksum_setup(sc, pi, &txd_upper, &txd_lower); } Index: if_em.h =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- if_em.h (revision 311875) +++ if_em.h (working copy) @@ -330,7 +330,8 @@ #define EM_MSIX_LINK 0x01000000 /* For 82574 use */ #define ETH_ZLEN 60 #define ETH_ADDR_LEN 6 -#define CSUM_OFFLOAD 7 /* Offload bits in mbuf flag */ +#define EM_CSUM_OFFLOAD 7 /* Offload bits in mbuf flag */ +#define IGB_CSUM_OFFLOAD 0x0E0F7 /* Offload bits in mbuf flag */ #define IGB_PKTTYPE_MASK 0x0000FFF0 #define IGB_DMCTLX_DCFLUSH_DIS 0x80000000 /* Disable DMA Coalesce Flush= */ Index: igb_txrx.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- igb_txrx.c (revision 311875) +++ igb_txrx.c (working copy) @@ -171,7 +171,7 @@ */ if (pi->ipi_mflags & M_VLANTAG) { vlan_macip_lens |=3D (pi->ipi_vtag << E1000_ADVTXD_VLAN_SHIFT); - } else if ((pi->ipi_csum_flags & CSUM_OFFLOAD) =3D=3D 0) { + } else if ((pi->ipi_csum_flags & IGB_CSUM_OFFLOAD) =3D=3D 0) { return (0); } sean --dalJa63uu556w9AwMH8QSEBbqxsMHjTAc-- --3gBaAjshtnFX9ImwIwnXLuuBmDHwOQiKS Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEEuq1GMucSHejSCZfdEgHvyh5yfmQFAlh2bqhfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEJB QUQ0NjMyRTcxMjFERThEMjA5OTdERDEyMDFFRkNBMUU3MjdFNjQACgkQEgHvyh5y fmScbwgAqJWQF1MrqHhJM7oNRxTddIf5EQ9a7ust2ONXISOiofgcANXpzsKCBIaW lGL+k/2UjcS5nKXsqzkdG/cW1OaRpEi5clM4R1bt5ds2plpnscVjx/bHh+I7ZV4q Cvl24Z2K+se3YyO1oPXmE/rbRiGzkCjffuAmBoSOOq8Cli5a9RtsINtqBPoBMlVg T0gP6xh3Owm7g21FELt7FULf9d0OoQvnSE2jnmKFHYcu7oBnJlPBxsf/n5qsXyWa HWl5fwI3zY+MDkfZnA8IwMZcHEeourdbQEfNIP+l1o2Eu8S6XXlgqgPL9DAOX+Jr McdLX6XotTAb3bJeoN/R6Tu1Juo9zg== =YfC2 -----END PGP SIGNATURE----- --3gBaAjshtnFX9ImwIwnXLuuBmDHwOQiKS-- From owner-freebsd-net@freebsd.org Wed Jan 11 17:44:34 2017 Return-Path: Delivered-To: freebsd-net@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 AAC8CCAB6D9 for ; Wed, 11 Jan 2017 17:44:34 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from mail.ignoranthack.me (ignoranthack.me [199.102.79.106]) (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 7C7B21CF6 for ; Wed, 11 Jan 2017 17:44:33 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from [192.168.0.6] (67-0-248-244.albq.qwest.net [67.0.248.244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: sbruno@ignoranthack.me) by mail.ignoranthack.me (Postfix) with ESMTPSA id 94D931928BA; Wed, 11 Jan 2017 17:44:32 +0000 (UTC) Subject: Re: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb pending To: Michael Tuexen References: <092ad9f7-b04c-292f-c626-6ce1956580a8@freebsd.org> <44D9E8B2-1045-4B01-9EB5-B2F25932D8FB@lurchi.franken.de> Cc: freebsd-net@freebsd.org From: Sean Bruno Message-ID: <1eb88092-d9de-e692-4b80-847bd6b71d0f@freebsd.org> Date: Wed, 11 Jan 2017 10:44:31 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: <44D9E8B2-1045-4B01-9EB5-B2F25932D8FB@lurchi.franken.de> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="mi3sCqLqA9HimgkaekCcl67dOH4AjefSu" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2017 17:44:34 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --mi3sCqLqA9HimgkaekCcl67dOH4AjefSu Content-Type: multipart/mixed; boundary="aQVcaUCMiGsQ86WqvuDGf2nsqrAaXnVbo"; protected-headers="v1" From: Sean Bruno To: Michael Tuexen Cc: freebsd-net@freebsd.org Message-ID: <1eb88092-d9de-e692-4b80-847bd6b71d0f@freebsd.org> Subject: Re: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb pending References: <092ad9f7-b04c-292f-c626-6ce1956580a8@freebsd.org> <44D9E8B2-1045-4B01-9EB5-B2F25932D8FB@lurchi.franken.de> In-Reply-To: <44D9E8B2-1045-4B01-9EB5-B2F25932D8FB@lurchi.franken.de> --aQVcaUCMiGsQ86WqvuDGf2nsqrAaXnVbo Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 01/11/17 10:24, Michael Tuexen wrote: >> On 10 Jan 2017, at 04:32, Sean Bruno wrote: >> >> tl;dir --> you get to keep your igbX devices(thanks jhb), no POLA >> violations this week. >> >> I've updated sys/dev/e1000 at svn R311849 to match Matt Macy's work on= >> IFLIB in the kernel. >> >> At this point, the driver deviates from Intel's code dramatically and >> you now get to yell directly into the freebsd-net@ megaphone for thing= s >> that I may have broken. > My testing shows that sending SCTP/IPv4, SCTP/IPv6, TCP/IPv6, and UDP/I= PV6 > is broken since the checksum offload doesn't work. >=20 > The following patch fixes the issue: >=20 > Index: if_em.h > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > --- if_em.h (revision 311887) > +++ if_em.h (working copy) > @@ -330,7 +330,7 @@ > #define EM_MSIX_LINK 0x01000000 /* For 82574 use */ > #define ETH_ZLEN 60 > #define ETH_ADDR_LEN 6 > -#define CSUM_OFFLOAD 7 /* Offload bits in mbuf flag */= > +#define CSUM_OFFLOAD 0xE0F /* Offload bits in mbuf flag */= >=20 > #define IGB_PKTTYPE_MASK 0x0000FFF0 > #define IGB_DMCTLX_DCFLUSH_DIS 0x80000000 /* Disable DMA Coalesce Flu= sh */ >=20 > The magic number 7 is CSUM_IP | CSUM_IP_UDP | CSUM_IP_TCP, which means > that checksum offloading is working for TCP/IPv4 and UDP/IPv4. > It should be 0xE0F, which is > CSUM_IP | CSUM_IP_UDP | CSUM_IP_TCP | CSUM_IP_SCTP | CSUM_IP6_UDP | CSU= M_IP6_TCP | CSUM_IP6_SCTP. >=20 > I have tested the above patch with an igb card which supports all these= offloads. >=20 > Best regards > Michael >> >> man page updates are coming up next. Please let us know if this >> revision has made things better, worse or none-of-the above on whateve= r >> Intel Gigabit NIC you happen to have lying around. >> >> sean >> >> On 01/05/17 20:18, Sean Bruno wrote: >>> tl;dr --> igbX devices will become emX devices >>> >>> We're about to commit an update to sys/dev/e1000 that will implement = and >>> activate IFLIB for em(4), lem(4) & igb(4) and would appreciate all fo= lks >>> who can test and poke at the drivers to do so this week. This will h= ave >>> some really great changes for performance and standardization that ha= ve >>> been bouncing around inside of various FreeBSD shops that have been >>> collaborating with Matt Macy over the last year. >>> >>> This will implement multiple queues for certain em(4) devices that ar= e >>> capable of such things and add some new sysctl's for you to poke at i= n >>> your monitoring tools. >>> >>> Due to limitations of device registration, igbX devices will become e= mX >>> devices. So, you'll need to make a minor update to your rc.conf and >>> scripts that manipulate the network devices. >>> >>> UPDATING will be bumped to reflect these changes. >>> >>> MFC to stable/11 will have a legacy implementation that doesn't use >>> IFLIB for compatibility reasons. >>> >>> A documentation and man page update will follow in the next few days >>> explaining how to work with the changed driver. >>> >>> sean >>> >>> bcc net@ current@ re@ >>> >>> >>> >>> >>> >> >=20 >=20 Bah, last one was wrong bits. Try this one. Index: em_txrx.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- em_txrx.c (revision 311875) +++ em_txrx.c (working copy) @@ -304,7 +304,7 @@ if (do_tso) { i =3D em_tso_setup(sc, pi, &txd_upper, &txd_lower); tso_desc =3D TRUE; - } else if (csum_flags & CSUM_OFFLOAD) { + } else if (csum_flags & EM_CSUM_OFFLOAD) { i =3D em_transmit_checksum_setup(sc, pi, &txd_upper, &txd_lower); } Index: if_em.h =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- if_em.h (revision 311875) +++ if_em.h (working copy) @@ -330,7 +330,8 @@ #define EM_MSIX_LINK 0x01000000 /* For 82574 use */ #define ETH_ZLEN 60 #define ETH_ADDR_LEN 6 -#define CSUM_OFFLOAD 7 /* Offload bits in mbuf flag */ +#define EM_CSUM_OFFLOAD 7 /* Offload bits in mbuf flag */ +#define IGB_CSUM_OFFLOAD 0x0E0F /* Offload bits in mbuf flag */ #define IGB_PKTTYPE_MASK 0x0000FFF0 #define IGB_DMCTLX_DCFLUSH_DIS 0x80000000 /* Disable DMA Coalesce Flush= */ Index: igb_txrx.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- igb_txrx.c (revision 311875) +++ igb_txrx.c (working copy) @@ -171,7 +171,7 @@ */ if (pi->ipi_mflags & M_VLANTAG) { vlan_macip_lens |=3D (pi->ipi_vtag << E1000_ADVTXD_VLAN_SHIFT); - } else if ((pi->ipi_csum_flags & CSUM_OFFLOAD) =3D=3D 0) { + } else if ((pi->ipi_csum_flags & IGB_CSUM_OFFLOAD) =3D=3D 0) { return (0); } =09 --aQVcaUCMiGsQ86WqvuDGf2nsqrAaXnVbo-- --mi3sCqLqA9HimgkaekCcl67dOH4AjefSu Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEEuq1GMucSHejSCZfdEgHvyh5yfmQFAlh2bwBfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEJB QUQ0NjMyRTcxMjFERThEMjA5OTdERDEyMDFFRkNBMUU3MjdFNjQACgkQEgHvyh5y fmSSTQf/bk97GWQKgJqDEKGDG1tRCWVWr1nLPZfHrorVyLN0LbGj2THz11NJTYx9 VyVCPLqtP+7SsF/gbuXxYbBgydQl0zMdImZWX4Xj9g0aQ7l4e4FsXd7v/rSPa71u eQt3uz3an7NWYD5uSC72wT4MblzdKoinZfWoybS6nSXcVXCetCJiT4qFt+2ckdaP yBEoFz9K/V4Vtwd8gwvu0QikIKTZ3DkAYYbGbSiYVbxOmaSY++VyKQTjsh8z5Q2N bHwNPBbiF/nR7lILoy8tTiWccRhTY8//gtyfc4TW+n2fXHC7ajXZy9DVfToGA7Hu CbHcobJFwvVeZTEdPQERsnTyW4MxPg== =QANH -----END PGP SIGNATURE----- --mi3sCqLqA9HimgkaekCcl67dOH4AjefSu-- From owner-freebsd-net@freebsd.org Wed Jan 11 18:45:50 2017 Return-Path: Delivered-To: freebsd-net@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 6F341CABA2B for ; Wed, 11 Jan 2017 18:45:50 +0000 (UTC) (envelope-from Michael.Tuexen@lurchi.franken.de) Received: from drew.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.franken.de", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1C9241E3A; Wed, 11 Jan 2017 18:45:49 +0000 (UTC) (envelope-from Michael.Tuexen@lurchi.franken.de) Received: from [IPv6:2003:cd:6bc9:5900:6d10:a969:52d7:de0f] (p200300CD6BC959006D10A96952D7DE0F.dip0.t-ipconnect.de [IPv6:2003:cd:6bc9:5900:6d10:a969:52d7:de0f]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTPSA id EBC35721E281A; Wed, 11 Jan 2017 19:45:39 +0100 (CET) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: Re: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb pending From: Michael Tuexen In-Reply-To: <1eb88092-d9de-e692-4b80-847bd6b71d0f@freebsd.org> Date: Wed, 11 Jan 2017 19:45:39 +0100 Cc: freebsd-net@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <9A868536-08B0-4F56-B12D-720AD955E8DA@lurchi.franken.de> References: <092ad9f7-b04c-292f-c626-6ce1956580a8@freebsd.org> <44D9E8B2-1045-4B01-9EB5-B2F25932D8FB@lurchi.franken.de> <1eb88092-d9de-e692-4b80-847bd6b71d0f@freebsd.org> To: Sean Bruno X-Mailer: Apple Mail (2.3259) X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=disabled version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail-n.franken.de X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2017 18:45:50 -0000 > On 11 Jan 2017, at 18:44, Sean Bruno wrote: >=20 >=20 >=20 > On 01/11/17 10:24, Michael Tuexen wrote: >>> On 10 Jan 2017, at 04:32, Sean Bruno wrote: >>>=20 >>> tl;dir --> you get to keep your igbX devices(thanks jhb), no POLA >>> violations this week. >>>=20 >>> I've updated sys/dev/e1000 at svn R311849 to match Matt Macy's work = on >>> IFLIB in the kernel. >>>=20 >>> At this point, the driver deviates from Intel's code dramatically = and >>> you now get to yell directly into the freebsd-net@ megaphone for = things >>> that I may have broken. >> My testing shows that sending SCTP/IPv4, SCTP/IPv6, TCP/IPv6, and = UDP/IPV6 >> is broken since the checksum offload doesn't work. >>=20 >> The following patch fixes the issue: >>=20 >> Index: if_em.h >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> --- if_em.h (revision 311887) >> +++ if_em.h (working copy) >> @@ -330,7 +330,7 @@ >> #define EM_MSIX_LINK 0x01000000 /* For 82574 use */ >> #define ETH_ZLEN 60 >> #define ETH_ADDR_LEN 6 >> -#define CSUM_OFFLOAD 7 /* Offload bits in mbuf flag = */ >> +#define CSUM_OFFLOAD 0xE0F /* Offload bits in mbuf flag = */ >>=20 >> #define IGB_PKTTYPE_MASK 0x0000FFF0 >> #define IGB_DMCTLX_DCFLUSH_DIS 0x80000000 /* Disable DMA Coalesce = Flush */ >>=20 >> The magic number 7 is CSUM_IP | CSUM_IP_UDP | CSUM_IP_TCP, which = means >> that checksum offloading is working for TCP/IPv4 and UDP/IPv4. >> It should be 0xE0F, which is >> CSUM_IP | CSUM_IP_UDP | CSUM_IP_TCP | CSUM_IP_SCTP | CSUM_IP6_UDP | = CSUM_IP6_TCP | CSUM_IP6_SCTP. >>=20 >> I have tested the above patch with an igb card which supports all = these offloads. >>=20 >> Best regards >> Michael >>>=20 >>> man page updates are coming up next. Please let us know if this >>> revision has made things better, worse or none-of-the above on = whatever >>> Intel Gigabit NIC you happen to have lying around. >>>=20 >>> sean >>>=20 >>> On 01/05/17 20:18, Sean Bruno wrote: >>>> tl;dr --> igbX devices will become emX devices >>>>=20 >>>> We're about to commit an update to sys/dev/e1000 that will = implement and >>>> activate IFLIB for em(4), lem(4) & igb(4) and would appreciate all = folks >>>> who can test and poke at the drivers to do so this week. This will = have >>>> some really great changes for performance and standardization that = have >>>> been bouncing around inside of various FreeBSD shops that have been >>>> collaborating with Matt Macy over the last year. >>>>=20 >>>> This will implement multiple queues for certain em(4) devices that = are >>>> capable of such things and add some new sysctl's for you to poke at = in >>>> your monitoring tools. >>>>=20 >>>> Due to limitations of device registration, igbX devices will become = emX >>>> devices. So, you'll need to make a minor update to your rc.conf = and >>>> scripts that manipulate the network devices. >>>>=20 >>>> UPDATING will be bumped to reflect these changes. >>>>=20 >>>> MFC to stable/11 will have a legacy implementation that doesn't use >>>> IFLIB for compatibility reasons. >>>>=20 >>>> A documentation and man page update will follow in the next few = days >>>> explaining how to work with the changed driver. >>>>=20 >>>> sean >>>>=20 >>>> bcc net@ current@ re@ >>>>=20 >>>>=20 >>>>=20 >>>>=20 >>>>=20 >>>=20 >>=20 >>=20 >=20 >=20 > Bah, last one was wrong bits. Try this one. >=20 > Index: em_txrx.c > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > --- em_txrx.c (revision 311875) > +++ em_txrx.c (working copy) > @@ -304,7 +304,7 @@ > if (do_tso) { > i =3D em_tso_setup(sc, pi, &txd_upper, &txd_lower); > tso_desc =3D TRUE; > - } else if (csum_flags & CSUM_OFFLOAD) { > + } else if (csum_flags & EM_CSUM_OFFLOAD) { > i =3D em_transmit_checksum_setup(sc, pi, &txd_upper, = &txd_lower); > } >=20 > Index: if_em.h > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > --- if_em.h (revision 311875) > +++ if_em.h (working copy) > @@ -330,7 +330,8 @@ > #define EM_MSIX_LINK 0x01000000 /* For 82574 use */ > #define ETH_ZLEN 60 > #define ETH_ADDR_LEN 6 > -#define CSUM_OFFLOAD 7 /* Offload bits in mbuf flag */ > +#define EM_CSUM_OFFLOAD 7 /* Offload bits in mbuf = flag */ > +#define IGB_CSUM_OFFLOAD 0x0E0F /* Offload bits in mbuf flag */ >=20 > #define IGB_PKTTYPE_MASK 0x0000FFF0 > #define IGB_DMCTLX_DCFLUSH_DIS 0x80000000 /* Disable DMA = Coalesce Flush */ > Index: igb_txrx.c > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > --- igb_txrx.c (revision 311875) > +++ igb_txrx.c (working copy) > @@ -171,7 +171,7 @@ > */ > if (pi->ipi_mflags & M_VLANTAG) { > vlan_macip_lens |=3D (pi->ipi_vtag << = E1000_ADVTXD_VLAN_SHIFT); > - } else if ((pi->ipi_csum_flags & CSUM_OFFLOAD) =3D=3D 0) { > + } else if ((pi->ipi_csum_flags & IGB_CSUM_OFFLOAD) =3D=3D 0) { > return (0); > } Looks good to me... Best regards Michael > =09 >=20 From owner-freebsd-net@freebsd.org Wed Jan 11 19:02:56 2017 Return-Path: Delivered-To: freebsd-net@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 8429BCAA4FD for ; Wed, 11 Jan 2017 19:02:56 +0000 (UTC) (envelope-from j.moyer@student-email.org) Received: from mail-io0-x22b.google.com (mail-io0-x22b.google.com [IPv6:2607:f8b0:4001:c06::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5BF6C1D3E for ; Wed, 11 Jan 2017 19:02:56 +0000 (UTC) (envelope-from j.moyer@student-email.org) Received: by mail-io0-x22b.google.com with SMTP id j18so599077ioe.2 for ; Wed, 11 Jan 2017 11:02:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=student-email.org; s=google; h=mime-version:from:date:message-id:subject:to; bh=z1FAtFGYDhjdXJZfEisLWrOgVg9olmm87mcugYIGQ2E=; b=eRtjW1jxrHddS/MhdNn3O2BaqQgbCGLYyMVxgsNi6LOQ4xHxpi2vIlruZcvb3e4Kpz 2dMkTU8fc+AA+0a1IkJWnTPnOC5cCuhZV3FIGWW/ZikFYXZY8a25Q6ll3NeU+FdPAmfz kXSJ8yDlRzscVX7EGRC8Bxz0gjT92IaeMiBQc= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=z1FAtFGYDhjdXJZfEisLWrOgVg9olmm87mcugYIGQ2E=; b=UfcYPxlKZAG7S/c35fi+G+hxaVeINooCZGdSGPSoN1NrxS6A8GwUbPXpgMblB8kdB2 UXQ5spkSCKo3xdDTLrX0SKrcWKTLydSBPEOw7MtptfUzEToPWUMMSkvD/Fw51R6NHdCe 32MfrE0ROkkYvQ5fVBoLd6/m7LPiYj8i/ObyFnG7l/4u8OwaQAo88B+io33/8RRqhSiT ujc0d0NV8BB9Xa1zWRnUuQXrTWAna3C6YBxKdoGAnIepYQ8rbz5cT7zK3fyOvstQ56QZ Ha2FjUfzdYGwh6wgqyFbSm9+t0EU9V8hfO9SfX2626YT1+IXQupy/PG15yY397YP66dV wUDw== X-Gm-Message-State: AIkVDXLag58XxcHJk/uuynkIze0ET+TKmybnA8p6FqCyv0t/KHRK9fHv0kfzuP8d+gkLx5J5YgaLCNGPyGNJAw== X-Received: by 10.107.175.80 with SMTP id y77mr9062225ioe.12.1484161375516; Wed, 11 Jan 2017 11:02:55 -0800 (PST) MIME-Version: 1.0 Received: by 10.79.144.152 with HTTP; Wed, 11 Jan 2017 11:02:35 -0800 (PST) From: Jennifer Moyer Date: Wed, 11 Jan 2017 20:02:35 +0100 Message-ID: Subject: Resource Links are Broken To: freebsd-net@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2017 19:02:56 -0000 Good morning, Are you the person who maintains the resource page? I was examining your website and clicked on some resource links that didn't work. Let me know who I should send these to. Thanks, Hope this helps. Thanks. -- Jennifer From owner-freebsd-net@freebsd.org Wed Jan 11 19:54:16 2017 Return-Path: Delivered-To: freebsd-net@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 F13E9CABB82; Wed, 11 Jan 2017 19:54:16 +0000 (UTC) (envelope-from mmacy@nextbsd.org) Received: from sender163-mail.zoho.com (sender163-mail.zoho.com [74.201.84.163]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DBD0B1B15; Wed, 11 Jan 2017 19:54:16 +0000 (UTC) (envelope-from mmacy@nextbsd.org) Received: from mail.zoho.com by mx.zohomail.com with SMTP id 1484164449753237.24798839998505; Wed, 11 Jan 2017 11:54:09 -0800 (PST) Date: Wed, 11 Jan 2017 11:54:09 -0800 From: Matthew Macy To: =?UTF-8?Q?=22Olivier_Cochard-Labb=C3=A9=22?= Cc: "Sean Bruno" , "freebsd-net@freebsd.org" , "freebsd-current@freebsd.org" Message-ID: <1598f1845d6.125d30bfe89230.1420530647486361817@nextbsd.org> In-Reply-To: References: <30f21c75-d3a2-edcd-1999-d5ed9f970c06@freebsd.org> <1598d97bf2a.c6bcb76838987.6501340920645175463@nextbsd.org> <574a7ac7-4842-9518-8286-a4d89a9f7a27@freebsd.org> Subject: Re: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb pending MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Priority: Medium User-Agent: Zoho Mail X-Mailer: Zoho Mail X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2017 19:54:17 -0000 > > x head r311848: packets per second > + head r311849 and BAR patch: packets per second > +--------------------------------------------------------------------------+ > |++ ++ + xxx x x| > | |__M__A____| | > | |___AM__| | > +--------------------------------------------------------------------------+ > N Min Max Median Avg Stddev > x 5 924170 943071 927509 931612.1 8096.8269 > + 5 831452 845929.5 840940 838730.5 6413.5602 > Difference at 95.0% confidence > -92881.6 +/- 10652.2 > -9.96999% +/- 1.07481% > (Student's t, pooled s = 7303.85) I apologize. I've only had profiling data for NFLX's read-mostly workload on which it (or at least ixl) is 10% faster. Could you please detail your setup for us so that we can reproduce and get profiling data? Thanks in advance. -M From owner-freebsd-net@freebsd.org Wed Jan 11 19:55:35 2017 Return-Path: Delivered-To: freebsd-net@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 98B10CABD5A for ; Wed, 11 Jan 2017 19:55:35 +0000 (UTC) (envelope-from olivier@freebsd.org) Received: from smtp.smtpout.orange.fr (smtp08.smtpout.orange.fr [80.12.242.130]) by mx1.freebsd.org (Postfix) with ESMTP id EA1C81DF2 for ; Wed, 11 Jan 2017 19:55:34 +0000 (UTC) (envelope-from olivier@freebsd.org) Received: from mail-qt0-f174.google.com ([209.85.216.174]) by mwinf5d43 with ME id X7ns1u0133mLd29037ntgo; Wed, 11 Jan 2017 20:47:56 +0100 X-ME-Helo: mail-qt0-f174.google.com X-ME-Auth: Y29jaGFyZC1sYWJiZS5vbGl2aWVyQG9yYW5nZS5mcg== X-ME-Date: Wed, 11 Jan 2017 20:47:56 +0100 X-ME-IP: 209.85.216.174 Received: by mail-qt0-f174.google.com with SMTP id l7so156702804qtd.1; Wed, 11 Jan 2017 11:47:53 -0800 (PST) X-Gm-Message-State: AIkVDXIe8weV+RtjVyFHKYHbEBr6U+xqaSL8EAEto1egqpuFcm9ZgS0yF/Pm56AFyKrfmXXDJd1HEpmGwqjHOg== X-Received: by 10.200.1.11 with SMTP id e11mr9001087qtg.85.1484164072421; Wed, 11 Jan 2017 11:47:52 -0800 (PST) MIME-Version: 1.0 Received: by 10.237.34.248 with HTTP; Wed, 11 Jan 2017 11:47:31 -0800 (PST) In-Reply-To: <574a7ac7-4842-9518-8286-a4d89a9f7a27@freebsd.org> References: <30f21c75-d3a2-edcd-1999-d5ed9f970c06@freebsd.org> <1598d97bf2a.c6bcb76838987.6501340920645175463@nextbsd.org> <574a7ac7-4842-9518-8286-a4d89a9f7a27@freebsd.org> From: =?UTF-8?Q?Olivier_Cochard=2DLabb=C3=A9?= Date: Wed, 11 Jan 2017 20:47:31 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb pending To: Sean Bruno Cc: Matthew Macy , "freebsd-net@freebsd.org" , "freebsd-current@freebsd.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2017 19:55:35 -0000 On Wed, Jan 11, 2017 at 4:17 PM, Sean Bruno wrote: > > > Olivier: > > Give this a quick try. This isn't the correct way to do this, but I > want to see if I'm on the right path: > =E2=80=8Bthanks, it fix the problem, I've got back the 4 queues:=E2=80=8B =E2=80=8Bigb2: port 0x3000-0= x301f mem 0xdfea0000-0xdfebffff,0xdff24000-0xdff27fff irq 18 at device 20.0 on pci0 igb2: attach_pre capping queues at 8 igb2: using 1024 tx descriptors and 1024 rx descriptors igb2: msix_init qsets capped at 8 igb2: pxm cpus: 4 queue msgs: 9 admincnt: 1 igb2: using 4 rx queues 4 tx queues igb2: Using MSIX interrupts with 5 vectors igb2: allocated for 4 tx_queues igb2: allocated for 4 rx_queues igb2: Ethernet address: 00:08:a2:09:33:da igb2: netmap queues/slots: TX 4/1024, RX 4/1024 =E2=80=8B In forwarding mode, I measure about 10% performance drop with this new drivers on this hardware: x head r311848: packets per second + head r311849 and BAR patch: packets per second +--------------------------------------------------------------------------= + |++ ++ + xxx x x= | | |__M__A____| = | | |___AM__| = | +--------------------------------------------------------------------------= + N Min Max Median Avg Stddev x 5 924170 943071 927509 931612.1 8096.8269 + 5 831452 845929.5 840940 838730.5 6413.5602 Difference at 95.0% confidence -92881.6 +/- 10652.2 -9.96999% +/- 1.07481% (Student's t, pooled s =3D 7303.85) Regards, Olivier From owner-freebsd-net@freebsd.org Wed Jan 11 20:02:12 2017 Return-Path: Delivered-To: freebsd-net@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 1F88ECAB251; Wed, 11 Jan 2017 20:02:12 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from mail.ignoranthack.me (ignoranthack.me [199.102.79.106]) (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 EC7B91B52; Wed, 11 Jan 2017 20:02:11 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from [192.168.0.6] (67-0-248-244.albq.qwest.net [67.0.248.244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: sbruno@ignoranthack.me) by mail.ignoranthack.me (Postfix) with ESMTPSA id 2091F1928BA; Wed, 11 Jan 2017 20:02:10 +0000 (UTC) Subject: Re: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb pending To: =?UTF-8?Q?Olivier_Cochard-Labb=c3=a9?= References: <30f21c75-d3a2-edcd-1999-d5ed9f970c06@freebsd.org> <1598d97bf2a.c6bcb76838987.6501340920645175463@nextbsd.org> <574a7ac7-4842-9518-8286-a4d89a9f7a27@freebsd.org> Cc: Matthew Macy , "freebsd-net@freebsd.org" , "freebsd-current@freebsd.org" From: Sean Bruno Message-ID: <6c6cb534-73c7-464b-8af1-7445a9c0188c@freebsd.org> Date: Wed, 11 Jan 2017 13:02:06 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="2vdJXqMe1gBhPGe7www9f7nJ3gpI1JuMx" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2017 20:02:12 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --2vdJXqMe1gBhPGe7www9f7nJ3gpI1JuMx Content-Type: multipart/mixed; boundary="QS57mcSObCrNIKjmEVANwKR6hUMcA7uqn"; protected-headers="v1" From: Sean Bruno To: =?UTF-8?Q?Olivier_Cochard-Labb=c3=a9?= Cc: Matthew Macy , "freebsd-net@freebsd.org" , "freebsd-current@freebsd.org" Message-ID: <6c6cb534-73c7-464b-8af1-7445a9c0188c@freebsd.org> Subject: Re: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb pending References: <30f21c75-d3a2-edcd-1999-d5ed9f970c06@freebsd.org> <1598d97bf2a.c6bcb76838987.6501340920645175463@nextbsd.org> <574a7ac7-4842-9518-8286-a4d89a9f7a27@freebsd.org> In-Reply-To: --QS57mcSObCrNIKjmEVANwKR6hUMcA7uqn Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 01/11/17 12:47, Olivier Cochard-Labb=C3=A9 wrote: > On Wed, Jan 11, 2017 at 4:17 PM, Sean Bruno > wrote: >=20 >=20 >=20 > Olivier: >=20 > Give this a quick try. This isn't the correct way to do this, but = I > want to see if I'm on the right path: >=20 >=20 > =E2=80=8Bthanks, it fix the problem, I've got back the 4 queues:=E2=80=8B= >=20 > =E2=80=8Bigb2: port 0x30= 00-0x301f > mem 0xdfea0000-0xdfebffff,0xdff24000-0xdff27fff irq 18 at device 20.0 o= n > pci0 > igb2: attach_pre capping queues at 8 > igb2: using 1024 tx descriptors and 1024 rx descriptors > igb2: msix_init qsets capped at 8 > igb2: pxm cpus: 4 queue msgs: 9 admincnt: 1 > igb2: using 4 rx queues 4 tx queues > igb2: Using MSIX interrupts with 5 vectors > igb2: allocated for 4 tx_queues > igb2: allocated for 4 rx_queues > igb2: Ethernet address: 00:08:a2:09:33:da > igb2: netmap queues/slots: TX 4/1024, RX 4/1024 > =E2=80=8B > In forwarding mode, I measure about 10% performance drop with this new > drivers on this hardware: >=20 > x head r311848: packets per second > + head r311849 and BAR patch: packets per second > +----------------------------------------------------------------------= ----+ > |++ ++ + xxx x= x| > | |__M__A___= _| | > | |___AM__| = | > +----------------------------------------------------------------------= ----+ > N Min Max Median Avg St= ddev > x 5 924170 943071 927509 931612.1 8096.= 8269 > + 5 831452 845929.5 840940 838730.5 6413.= 5602 > Difference at 95.0% confidence > -92881.6 +/- 10652.2 > -9.96999% +/- 1.07481% > (Student's t, pooled s =3D 7303.85) >=20 > Regards, >=20 > Olivier >=20 Hmmm ... did your old tests do 4 or 8 queues on this hardware? Did the old tests run 1024 tx/rx slots or the max 4096? sean --QS57mcSObCrNIKjmEVANwKR6hUMcA7uqn-- --2vdJXqMe1gBhPGe7www9f7nJ3gpI1JuMx Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEEuq1GMucSHejSCZfdEgHvyh5yfmQFAlh2jz5fFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEJB QUQ0NjMyRTcxMjFERThEMjA5OTdERDEyMDFFRkNBMUU3MjdFNjQACgkQEgHvyh5y fmTW1Af/ev4/sYMZG4173M8OKsh0iJgHojq837uThv2pQUWGjzTlxQgtn0fS8u9Y WFFOSP8cKqGugrwf9rup816GKk57bohmcSGs0He9rJRcszzocwExhWCiCwidk+aT LLqSG6U/DfMU9C4O8yzWrnZ+OM2vlnLKegxPBONSrJapQQIOPeHlWuL0Eb5gIItA mzT0s0owzdrozHazIGpNMaf5KU27nKtcPpeGgLbV1amVqp7lPM1nA8TQ6L7uvtha LNWpvDFqlvRctBHc3iYm+ZWwba25EcSNqgiR006uQeTfGDxaHV6Tk3qX5HLeSTK6 3kkjvsAS0OH0/bcUpXY7IHxjfwYTHQ== =e2yN -----END PGP SIGNATURE----- --2vdJXqMe1gBhPGe7www9f7nJ3gpI1JuMx-- From owner-freebsd-net@freebsd.org Wed Jan 11 20:13:12 2017 Return-Path: Delivered-To: freebsd-net@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 037CECAB9A2 for ; Wed, 11 Jan 2017 20:13:12 +0000 (UTC) (envelope-from ml@my.gd) Received: from mail-vk0-x22d.google.com (mail-vk0-x22d.google.com [IPv6:2607:f8b0:400c:c05::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B905517AD for ; Wed, 11 Jan 2017 20:13:11 +0000 (UTC) (envelope-from ml@my.gd) Received: by mail-vk0-x22d.google.com with SMTP id x75so63200688vke.2 for ; Wed, 11 Jan 2017 12:13:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=my-gd.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to:cc; bh=8QNI5aRwiCSrH8T3+dFooY58Qq4/GX0gTpKHdKzYxh8=; b=dUgknhtmHhy7kuv3URvmNzAQWhczDmWz3KZ83rfqUzSgUWvi9UDIBnC30dHoOPMtUT SgTVkOZcoeXCAqSHM4F0SitGMi3QJ1o/7FSUAtmHvT/Ju7iefp8C5oTqXUs9WRiEwOZR M9dtoJdpFQ183N9zYkAiHsdkP0v4AYMK26OYnJEmZus1IpqcuZgXAw8wiWMna+2NR5/m q/lqSTV/FXjZl7UnagKyqBHNZOue7M5uTyduz/7B757EFI81NYpOswRnIGiSI909uP5v o+oPUhx+7elnIH9B4+8uCVAs7ydCrbUNNIjC3TA+OcveJxPYt7CcD1Txps3Q2EKyEZ1e kBaA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=8QNI5aRwiCSrH8T3+dFooY58Qq4/GX0gTpKHdKzYxh8=; b=eZqMS6N4zKFtSvD5SNxwSIDDa+f1EgyIRDyE2pMnFJacN5/1CyFZkTt+G2xnqKfcqT uHBlmb3sDqvvkCP0/8AJaTvyKIaL0g9Xm2fg2TcMOnDp+fAi4/qR4Riz/6jqVT+uVmcz OI08enkfhV2FW5XeNzP5joTxTbROivu0sFlrv63gPF4eb7TcmB2oePkkTTZbmFOenk1f D4kNAhL/qTycg+gB2qx98+etA8DMnoJokujC/ygZo3Tz4eo4RYxRS1CoVisH2bbc/e7g g/bLbvEukMUAcDHcdEPqfsLdPB7/Pv5r8Rz0IJww/uHvT5TyVUF4//zFVUxS4uQJo6AS 7UQw== X-Gm-Message-State: AIkVDXJNaxK/vub8pAHYREDwhqSB61gfB9HZ4s59mBPzSo2eImLgjrsRQA1FgbhoVdAtwyty5VltfksKTO42Pg== X-Received: by 10.31.205.129 with SMTP id d123mr5107213vkg.166.1484165590669; Wed, 11 Jan 2017 12:13:10 -0800 (PST) MIME-Version: 1.0 Received: by 10.103.48.213 with HTTP; Wed, 11 Jan 2017 12:13:10 -0800 (PST) From: Damien Fleuriot Date: Wed, 11 Jan 2017 21:13:10 +0100 Message-ID: Subject: [CARP] BUG #202510 - advertisements sourced from CARP IP cause double master situation To: "freebsd-net@freebsd.org" Cc: dfl@hipay.com Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2017 20:13:12 -0000 Hello list, When using (legacy ?) syntax ipv4_addrs_$interf="1.2.3.4/32" in /etc/rc.conf, CARP advertisements are sent from subsequent addresses defined using ifconfig_$interf_aliasN="2.3.4.5/32" This causes master-master situations and, obviously, network problems. I have attached a patch to the PR [1] which moves ipv4_addrs_$interf processing higher up the chain in /etc/network.subr Despite dating back from 2015 the patch applies just fine here on 10-STABLE and corrects the behaviour without any noticeable side effects. Seeking people running 9.x and 11.x to help close this PR [2]. Would anyone kindly check and report ? [1] https://bugs.freebsd.org/bugzilla/attachment.cgi?id=160307&action=diff [2] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202510 From owner-freebsd-net@freebsd.org Wed Jan 11 20:13:25 2017 Return-Path: Delivered-To: freebsd-net@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 5B07BCAB9C5; Wed, 11 Jan 2017 20:13:25 +0000 (UTC) (envelope-from mmacy@nextbsd.org) Received: from sender163-mail.zoho.com (sender163-mail.zoho.com [74.201.84.163]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3A9A21863; Wed, 11 Jan 2017 20:13:24 +0000 (UTC) (envelope-from mmacy@nextbsd.org) Received: from mail.zoho.com by mx.zohomail.com with SMTP id 1484165600128352.09294656141446; Wed, 11 Jan 2017 12:13:20 -0800 (PST) Date: Wed, 11 Jan 2017 12:13:20 -0800 From: Matthew Macy To: "Sean Bruno" Cc: =?UTF-8?Q?=22Olivier_Cochard-Labb=C3=A9=22?= , "freebsd-net@freebsd.org" , "freebsd-current@freebsd.org" Message-ID: <1598f29d379.ea6360351471.8752933472741761813@nextbsd.org> In-Reply-To: <6c6cb534-73c7-464b-8af1-7445a9c0188c@freebsd.org> References: <30f21c75-d3a2-edcd-1999-d5ed9f970c06@freebsd.org> <1598d97bf2a.c6bcb76838987.6501340920645175463@nextbsd.org> <574a7ac7-4842-9518-8286-a4d89a9f7a27@freebsd.org> <6c6cb534-73c7-464b-8af1-7445a9c0188c@freebsd.org> Subject: Re: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb pending MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Priority: Medium User-Agent: Zoho Mail X-Mailer: Zoho Mail X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2017 20:13:25 -0000 ---- On Wed, 11 Jan 2017 12:02:06 -0800 Sean Bruno wr= ote ----=20 > =20 > =20 > On 01/11/17 12:47, Olivier Cochard-Labb=C3=A9 wrote:=20 > > On Wed, Jan 11, 2017 at 4:17 PM, Sean Bruno > > wrote:=20 > > =20 > > =20 > > =20 > > Olivier:=20 > > =20 > > Give this a quick try. This isn't the correct way to do this, but= I=20 > > want to see if I'm on the right path:=20 > > =20 > > =20 > > =E2=80=8Bthanks, it fix the problem, I've got back the 4 queues:=E2=80= =8B=20 > > =20 > > =E2=80=8Bigb2: port 0x3= 000-0x301f=20 > > mem 0xdfea0000-0xdfebffff,0xdff24000-0xdff27fff irq 18 at device 20.0 = on=20 > > pci0=20 > > igb2: attach_pre capping queues at 8=20 > > igb2: using 1024 tx descriptors and 1024 rx descriptors=20 > > igb2: msix_init qsets capped at 8=20 > > igb2: pxm cpus: 4 queue msgs: 9 admincnt: 1=20 > > igb2: using 4 rx queues 4 tx queues=20 > > igb2: Using MSIX interrupts with 5 vectors=20 > > igb2: allocated for 4 tx_queues=20 > > igb2: allocated for 4 rx_queues=20 > > igb2: Ethernet address: 00:08:a2:09:33:da=20 > > igb2: netmap queues/slots: TX 4/1024, RX 4/1024=20 > > =E2=80=8B=20 > > In forwarding mode, I measure about 10% performance drop with this new= =20 > > drivers on this hardware:=20 > > =20 > > x head r311848: packets per second=20 > > + head r311849 and BAR patch: packets per second=20 > > +---------------------------------------------------------------------= -----+=20 > > |++ ++ + xxx = x x|=20 > > | |__M__A__= __| |=20 > > | |___AM__| = |=20 > > +---------------------------------------------------------------------= -----+=20 > > N Min Max Median Avg S= tddev=20 > > x 5 924170 943071 927509 931612.1 8096= .8269=20 > > + 5 831452 845929.5 840940 838730.5 6413= .5602=20 > > Difference at 95.0% confidence=20 > > -92881.6 +/- 10652.2=20 > > -9.96999% +/- 1.07481%=20 > > (Student's t, pooled s =3D 7303.85)=20 > > =20 > > Regards,=20 > > =20 > > Olivier=20 > > =20 > =20 > =20 > Hmmm ... did your old tests do 4 or 8 queues on this hardware?=20 > =20 > Did the old tests run 1024 tx/rx slots or the max 4096?=20 That's a great point, only having one thread per core could easily account = for this. I'm hoping Sean can make txq !=3D rxq work so that you can have 8= txqs and 4 rxqs. -M From owner-freebsd-net@freebsd.org Wed Jan 11 20:37:06 2017 Return-Path: Delivered-To: freebsd-net@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 BD9CECAB167; Wed, 11 Jan 2017 20:37:06 +0000 (UTC) (envelope-from mmacy@nextbsd.org) Received: from sender163-mail.zoho.com (sender163-mail.zoho.com [74.201.84.163]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9F0B418D3; Wed, 11 Jan 2017 20:37:06 +0000 (UTC) (envelope-from mmacy@nextbsd.org) Received: from mail.zoho.com by mx.zohomail.com with SMTP id 1484167021964143.00894341522314; Wed, 11 Jan 2017 12:37:01 -0800 (PST) Date: Wed, 11 Jan 2017 12:37:01 -0800 From: Matthew Macy To: =?UTF-8?Q?=22Olivier_Cochard-Labb=C3=A9=22?= Cc: "Sean Bruno" , "freebsd-net@freebsd.org" , "freebsd-current@freebsd.org" Message-ID: <1598f3f8588.d20017893749.339651164872952258@nextbsd.org> In-Reply-To: References: <30f21c75-d3a2-edcd-1999-d5ed9f970c06@freebsd.org> <1598d97bf2a.c6bcb76838987.6501340920645175463@nextbsd.org> <574a7ac7-4842-9518-8286-a4d89a9f7a27@freebsd.org> <6c6cb534-73c7-464b-8af1-7445a9c0188c@freebsd.org> <1598f29d379.ea6360351471.8752933472741761813@nextbsd.org> Subject: Re: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb pending MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Priority: Medium User-Agent: Zoho Mail X-Mailer: Zoho Mail X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2017 20:37:06 -0000 You can still explicitly set the number of descriptors. It is now reported = under the dev sysctl tree. dev... -M ---- On Wed, 11 Jan 2017 12:34:23 -0800 Olivier Cochard-Labb=C3=A9 wrote ----=20 >=20 > On Wed, Jan 11, 2017 at 9:13 PM, Matthew Macy wrote: >=20 > > Hmmm ... did your old tests do 4 or 8 queues on this hardware? > > > > Did the old tests run 1024 tx/rx slots or the max 4096? > =20 > That's a great point, only having one thread per core could easily acco= unt for this. I'm hoping Sean can make txq !=3D rxq work so that you can ha= ve 8txqs and 4 rxqs. > =20 >=20 > =E2=80=8BThe netgate RCC-VE 4860 is a 4 cores atom C2558E, and I'm using= 2 of the 4 Gigabit Intel i350 ports. > Lab detail: > https://bsdrp.net/documentation/examples/forwarding_performance_lab_of_a= _netgate_rcc-ve_4860 >=20 > My tunning are (same for both test): > hw.igb.rxd=3D"2048" (it should be useless now) > hw.igb.txd=3D"2048" (it should be useless now) > hw.em.rxd=3D"2048" > hw.em.txd=3D"2048" > hw.igb.rx_process_limit=3D"-1" (It should be useless now too) > hw.em.rx_process_limit=3D"-1" >=20 > dev.igb.2.fc=3D0 > dev.igb.3.fc=3D0 >=20 > I can generate profiling data for you: what kind of data do you want ? > =20 From owner-freebsd-net@freebsd.org Wed Jan 11 20:40:31 2017 Return-Path: Delivered-To: freebsd-net@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 AA3A3CAB2EE; Wed, 11 Jan 2017 20:40:31 +0000 (UTC) (envelope-from mmacy@nextbsd.org) Received: from sender163-mail.zoho.com (sender163-mail.zoho.com [74.201.84.163]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 959BB1B4C; Wed, 11 Jan 2017 20:40:31 +0000 (UTC) (envelope-from mmacy@nextbsd.org) Received: from mail.zoho.com by mx.zohomail.com with SMTP id 14841672287931008.6866462705742; Wed, 11 Jan 2017 12:40:28 -0800 (PST) Date: Wed, 11 Jan 2017 12:40:28 -0800 From: Matthew Macy To: "Matthew Macy" Cc: =?UTF-8?Q?=22Olivier_Cochard-Labb=C3=A9=22?= , "Sean Bruno" , "freebsd-net@freebsd.org" , "freebsd-current@freebsd.org" Message-ID: <1598f42ad77.eeec05be4113.9201780237587761460@nextbsd.org> In-Reply-To: <1598f3f8588.d20017893749.339651164872952258@nextbsd.org> References: <30f21c75-d3a2-edcd-1999-d5ed9f970c06@freebsd.org> <1598d97bf2a.c6bcb76838987.6501340920645175463@nextbsd.org> <574a7ac7-4842-9518-8286-a4d89a9f7a27@freebsd.org> <6c6cb534-73c7-464b-8af1-7445a9c0188c@freebsd.org> <1598f29d379.ea6360351471.8752933472741761813@nextbsd.org> <1598f3f8588.d20017893749.339651164872952258@nextbsd.org> Subject: Re: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb pending MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Priority: Medium User-Agent: Zoho Mail X-Mailer: Zoho Mail X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2017 20:40:31 -0000 > > I can generate profiling data for you: what kind of data do you want ? > > > A flame graph for the core cycle count and a flame graph with cache miss stats from pmc would be a great start. From owner-freebsd-net@freebsd.org Wed Jan 11 20:42:24 2017 Return-Path: Delivered-To: freebsd-net@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 E30E7CAB54D for ; Wed, 11 Jan 2017 20:42:24 +0000 (UTC) (envelope-from olivier@freebsd.org) Received: from smtp.smtpout.orange.fr (smtp02.smtpout.orange.fr [80.12.242.124]) by mx1.freebsd.org (Postfix) with ESMTP id 521EC1FE0 for ; Wed, 11 Jan 2017 20:42:23 +0000 (UTC) (envelope-from olivier@freebsd.org) Received: from mail-qt0-f171.google.com ([209.85.216.171]) by mwinf5d56 with ME id X8ak1u00E3iTc1M038akSX; Wed, 11 Jan 2017 21:34:45 +0100 X-ME-Helo: mail-qt0-f171.google.com X-ME-Auth: Y29jaGFyZC1sYWJiZS5vbGl2aWVyQG9yYW5nZS5mcg== X-ME-Date: Wed, 11 Jan 2017 21:34:45 +0100 X-ME-IP: 209.85.216.171 Received: by mail-qt0-f171.google.com with SMTP id l7so157935477qtd.1; Wed, 11 Jan 2017 12:34:44 -0800 (PST) X-Gm-Message-State: AIkVDXJpXBvUv2MdGyu9rGa7bwduCJgpE7qEoseenj/GBkoACx+7IDLUJpS6aYeFTaSagdLlnmUYFZKZU56NOg== X-Received: by 10.200.41.198 with SMTP id 6mr10201420qtt.130.1484166883894; Wed, 11 Jan 2017 12:34:43 -0800 (PST) MIME-Version: 1.0 Received: by 10.237.34.248 with HTTP; Wed, 11 Jan 2017 12:34:23 -0800 (PST) In-Reply-To: <1598f29d379.ea6360351471.8752933472741761813@nextbsd.org> References: <30f21c75-d3a2-edcd-1999-d5ed9f970c06@freebsd.org> <1598d97bf2a.c6bcb76838987.6501340920645175463@nextbsd.org> <574a7ac7-4842-9518-8286-a4d89a9f7a27@freebsd.org> <6c6cb534-73c7-464b-8af1-7445a9c0188c@freebsd.org> <1598f29d379.ea6360351471.8752933472741761813@nextbsd.org> From: =?UTF-8?Q?Olivier_Cochard=2DLabb=C3=A9?= Date: Wed, 11 Jan 2017 21:34:23 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb pending To: Matthew Macy Cc: Sean Bruno , "freebsd-net@freebsd.org" , "freebsd-current@freebsd.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2017 20:42:25 -0000 On Wed, Jan 11, 2017 at 9:13 PM, Matthew Macy wrote: > > > Hmmm ... did your old tests do 4 or 8 queues on this hardware? > > > > Did the old tests run 1024 tx/rx slots or the max 4096? > > That's a great point, only having one thread per core could easily accoun= t > for this. I'm hoping Sean can make txq !=3D rxq work so that you can have > 8txqs and 4 rxqs. > > > =E2=80=8BThe netgate RCC-VE 4860 is a 4 cores atom C2558E, and I'm using = 2 of the 4 Gigabit Intel i350 ports. Lab detail: https://bsdrp.net/documentation/examples/forwarding_performance_lab_of_a_ne= tgate_rcc-ve_4860 My tunning are (same for both test): hw.igb.rxd=3D"2048" (it should be useless now) hw.igb.txd=3D"2048" (it should be useless now) hw.em.rxd=3D"2048" hw.em.txd=3D"2048" hw.igb.rx_process_limit=3D"-1" (It should be useless now too) hw.em.rx_process_limit=3D"-1" dev.igb.2.fc=3D0 dev.igb.3.fc=3D0 I can generate profiling data for you: what kind of data do you want ? From owner-freebsd-net@freebsd.org Wed Jan 11 22:29:36 2017 Return-Path: Delivered-To: freebsd-net@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 C7D24CAB6C1 for ; Wed, 11 Jan 2017 22:29:36 +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 8C6651A18 for ; Wed, 11 Jan 2017 22:29:36 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1cRR46-000JZq-9F for freebsd-net@freebsd.org; Thu, 12 Jan 2017 01:08:18 +0300 Date: Thu, 12 Jan 2017 01:08:18 +0300 From: Slawa Olhovchenkov To: freebsd-net@freebsd.org Subject: NFSv4 stuck Message-ID: <20170111220818.GD30374@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2017 22:29:36 -0000 I am have NFSv4 mount dir and some time got stucked after access. Mounted by automount: # cat /etc/nfs.map /NFS -nfsv4,intr,soft,sec=krb5i,gssname=host stat:/ # mount -v map -hosts on /net (autofs, fsid 01ff00cfcf000000) map nfs.map on /NFS (autofs, fsid 02ff00cfcf000000) map nfs.map on /NFS (autofs, fsid 03ff00cfcf000000) map nfs.map on /NFS (autofs, fsid 04ff00cfcf000000) map nfs.map on /NFS (autofs, fsid 05ff00cfcf000000) stat:/ on /NFS (nfs, nfsv4acls, automounted, fsid 0aff003a3a000000) # procstat -a | grep -e rpc -e gss -e nfs 840 1 840 840 0 1 root select FreeBSD ELF64 rpcbind 956 1 956 956 0 1 root pause FreeBSD ELF64 nfsuserd 957 956 956 956 0 1 root sbwait FreeBSD ELF64 nfsuserd 958 956 956 956 0 1 root select FreeBSD ELF64 nfsuserd 960 956 956 956 0 1 root select FreeBSD ELF64 nfsuserd 961 956 956 956 0 1 root sbwait FreeBSD ELF64 nfsuserd 969 1 969 969 0 1 root select FreeBSD ELF64 rpc.statd 972 1 972 972 0 1 root rpcsvc FreeBSD ELF64 rpc.lockd 10629 1098 10629 10629 0 1 root gssstate FreeBSD ELF64 sshd 10687 10652 10687 10647 10647 1 admin gssstate FreeBSD ELF64 csh 14521 1098 14521 14521 0 1 root gssstate FreeBSD ELF64 sshd 14924 14896 14924 14892 14892 1 admin nfs FreeBSD ELF64 automount 45455 45454 45455 45455 45455 1 slw gssstate FreeBSD ELF64 tcsh 63495 63481 42791 42791 0 1 root rpccon FreeBSD ELF64 find 79451 0 0 0 0 1 - rpccon - nfscl 79452 79450 79452 79452 79452 1 slw rpccon FreeBSD ELF64 tcsh How to unlock system w/o reboot? automount -u don't work From owner-freebsd-net@freebsd.org Wed Jan 11 22:32:45 2017 Return-Path: Delivered-To: freebsd-net@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 772B5CAB93E for ; Wed, 11 Jan 2017 22:32:45 +0000 (UTC) (envelope-from olivier@freebsd.org) Received: from smtp.smtpout.orange.fr (smtp05.smtpout.orange.fr [80.12.242.127]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "Bizanga Labs SMTP Client Certificate", Issuer "Bizanga Labs CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id D8A8D1FBF for ; Wed, 11 Jan 2017 22:32:44 +0000 (UTC) (envelope-from olivier@freebsd.org) Received: from mail-qk0-f170.google.com ([209.85.220.170]) by mwinf5d28 with ME id XAYf1u00f3hB8W903AYgKf; Wed, 11 Jan 2017 23:32:41 +0100 X-ME-Helo: mail-qk0-f170.google.com X-ME-Auth: Y29jaGFyZC1sYWJiZS5vbGl2aWVyQG9yYW5nZS5mcg== X-ME-Date: Wed, 11 Jan 2017 23:32:41 +0100 X-ME-IP: 209.85.220.170 Received: by mail-qk0-f170.google.com with SMTP id u25so2285336qki.2; Wed, 11 Jan 2017 14:32:40 -0800 (PST) X-Gm-Message-State: AIkVDXKw50aXyPBIBg0BII+MeP3K1oad5Ngx+arWEXFs/Z9sZmgxUJjfBdwFCQ7Ubbr35GrZCXJkd67f8Klp/g== X-Received: by 10.55.67.68 with SMTP id q65mr11423072qka.65.1484173959472; Wed, 11 Jan 2017 14:32:39 -0800 (PST) MIME-Version: 1.0 Received: by 10.237.34.248 with HTTP; Wed, 11 Jan 2017 14:32:18 -0800 (PST) In-Reply-To: <1598f42ad77.eeec05be4113.9201780237587761460@nextbsd.org> References: <30f21c75-d3a2-edcd-1999-d5ed9f970c06@freebsd.org> <1598d97bf2a.c6bcb76838987.6501340920645175463@nextbsd.org> <574a7ac7-4842-9518-8286-a4d89a9f7a27@freebsd.org> <6c6cb534-73c7-464b-8af1-7445a9c0188c@freebsd.org> <1598f29d379.ea6360351471.8752933472741761813@nextbsd.org> <1598f3f8588.d20017893749.339651164872952258@nextbsd.org> <1598f42ad77.eeec05be4113.9201780237587761460@nextbsd.org> From: =?UTF-8?Q?Olivier_Cochard=2DLabb=C3=A9?= Date: Wed, 11 Jan 2017 23:32:18 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb pending To: Matthew Macy Cc: Sean Bruno , "freebsd-net@freebsd.org" , "freebsd-current@freebsd.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2017 22:32:45 -0000 On Wed, Jan 11, 2017 at 9:40 PM, Matthew Macy wrote: > > > > I can generate profiling data for you: what kind of data do you wan= t > ? > > > > > > > A flame graph for the core cycle count and a flame graph with cache miss > stats from pmc would be a great start. > > =E2=80=8BI didn't know the exact event name to use for cache miss stats, bu= t here are the flame graphs for CPU_CLK_UNHALTED_CORE: http://dev.bsdrp.net/netgate.r311848.CPU_CLK_UNHALTED_CORE.svg http://dev.bsdrp.net/netgate.r311849.CPU_CLK_UNHALTED_CORE.svg From owner-freebsd-net@freebsd.org Wed Jan 11 22:39:44 2017 Return-Path: Delivered-To: freebsd-net@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 A1C1FCABE00 for ; Wed, 11 Jan 2017 22:39:44 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from NAM01-BY2-obe.outbound.protection.outlook.com (mail-by2nam01on0057.outbound.protection.outlook.com [104.47.34.57]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT SSL SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 52A58174F for ; Wed, 11 Jan 2017 22:39:43 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM (10.165.218.133) by YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM (10.165.218.133) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.845.12; Wed, 11 Jan 2017 22:39:42 +0000 Received: from YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM ([10.165.218.133]) by YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM ([10.165.218.133]) with mapi id 15.01.0845.013; Wed, 11 Jan 2017 22:39:42 +0000 From: Rick Macklem To: Slawa Olhovchenkov , "freebsd-net@freebsd.org" Subject: Re: NFSv4 stuck Thread-Topic: NFSv4 stuck Thread-Index: AQHSbFpEjAFIf9ZbxU6pF+N5/AhAH6Ez3cvb Date: Wed, 11 Jan 2017 22:39:42 +0000 Message-ID: References: <20170111220818.GD30374@zxy.spb.ru> In-Reply-To: <20170111220818.GD30374@zxy.spb.ru> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=rmacklem@uoguelph.ca; x-ms-office365-filtering-correlation-id: d833aa65-f02f-4192-8080-08d43a72bc7b x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:YTXPR01MB0189; x-microsoft-exchange-diagnostics: 1; YTXPR01MB0189; 7:TpiFBrrltFe+Bhk712sfucfIrJ/K5S5O1+Kn/BlESS2PHqV9JydA1+TqdfCfsBpM9sXDSUAUdTzduTI0aYtEEMIOyAwXZTzGhst0XvHTGePncNwnUyJGMmO9nY3iG7bd7r0nrhPHHhBJ+9wK/hYoSaHVCDbVfnBYVOCPn5wQkSZ1HIJnRO4xshCiMU+UiNPJ4a2QAnhF6QIuFJ/qG3oxXkQMf+Rt07HPGuJxX5pu9thQEzCqGAA1pbvR/fK+Vseux+T1QHAKSDi63jYcX25LZ+Y0OAQ/aQyX0A6G88wDPdrIMcZXJw0fnpIftiEaEf+t3kr3PB6ZwPiF56lF9C1079ngIeKqy1J8+OIw9BeXiuThnzrkaqdkl8BYYZOvS0OlzeQnwFA3orF2kXCj/YLNZv3cYd+QF8am0yyKJvyBHUJAaeCdAbcHlVzvuQbiAdViRU2Ek8Qn0KeZr7DS4molvw== x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(158342451672863)(75325880899374); x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040375)(2401047)(5005006)(8121501046)(3002001)(10201501046)(6041248)(20161123562025)(20161123555025)(20161123564025)(20161123560025)(6072148); SRVR:YTXPR01MB0189; BCL:0; PCL:0; RULEID:; SRVR:YTXPR01MB0189; x-forefront-prvs: 01842C458A x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(7916002)(39450400003)(377454003)(189002)(199003)(102836003)(7696004)(101416001)(2900100001)(92566002)(81156014)(81166006)(8936002)(8676002)(7116003)(5660300001)(50986999)(76176999)(54356999)(3660700001)(4477795004)(33656002)(97736004)(5001770100001)(2906002)(74316002)(68736007)(9686003)(86362001)(305945005)(107886002)(6436002)(3280700002)(189998001)(6506006)(122556002)(38730400001)(74482002)(2501003)(77096006)(106116001)(229853002)(105586002)(6306002)(106356001)(55016002)(2950100002); DIR:OUT; SFP:1101; SCL:1; SRVR:YTXPR01MB0189; H:YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; received-spf: None (protection.outlook.com: uoguelph.ca does not designate permitted sender hosts) spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: uoguelph.ca X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Jan 2017 22:39:42.8044 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: be62a12b-2cad-49a1-a5fa-85f4f3156a7d X-MS-Exchange-Transport-CrossTenantHeadersStamped: YTXPR01MB0189 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2017 22:39:44 -0000 "umount -f" is your only chance. However, if there is already a non-forced dismount stuck, it won't work because the non-forced dismount will have the mounted-on vnode locked. Btw, the processes waiting on "rpccon" are trying to make a new TCP connection to the server. Are you sure the client can talk to the server over your net? rick ________________________________________ From: owner-freebsd-net@freebsd.org on beha= lf of Slawa Olhovchenkov Sent: Wednesday, January 11, 2017 5:08:18 PM To: freebsd-net@freebsd.org Subject: NFSv4 stuck I am have NFSv4 mount dir and some time got stucked after access. Mounted by automount: # cat /etc/nfs.map /NFS -nfsv4,intr,soft,sec=3Dkrb5i,gssname=3Dhost stat:/ # mount -v map -hosts on /net (autofs, fsid 01ff00cfcf000000) map nfs.map on /NFS (autofs, fsid 02ff00cfcf000000) map nfs.map on /NFS (autofs, fsid 03ff00cfcf000000) map nfs.map on /NFS (autofs, fsid 04ff00cfcf000000) map nfs.map on /NFS (autofs, fsid 05ff00cfcf000000) stat:/ on /NFS (nfs, nfsv4acls, automounted, fsid 0aff003a3a000000) # procstat -a | grep -e rpc -e gss -e nfs 840 1 840 840 0 1 root select FreeBSD ELF64 rpcbind 956 1 956 956 0 1 root pause FreeBSD ELF64 nfsuserd 957 956 956 956 0 1 root sbwait FreeBSD ELF64 nfsuserd 958 956 956 956 0 1 root select FreeBSD ELF64 nfsuserd 960 956 956 956 0 1 root select FreeBSD ELF64 nfsuserd 961 956 956 956 0 1 root sbwait FreeBSD ELF64 nfsuserd 969 1 969 969 0 1 root select FreeBSD ELF64 rpc.stat= d 972 1 972 972 0 1 root rpcsvc FreeBSD ELF64 rpc.lock= d 10629 1098 10629 10629 0 1 root gssstate FreeBSD ELF64 sshd 10687 10652 10687 10647 10647 1 admin gssstate FreeBSD ELF64 csh 14521 1098 14521 14521 0 1 root gssstate FreeBSD ELF64 sshd 14924 14896 14924 14892 14892 1 admin nfs FreeBSD ELF64 automoun= t 45455 45454 45455 45455 45455 1 slw gssstate FreeBSD ELF64 tcsh 63495 63481 42791 42791 0 1 root rpccon FreeBSD ELF64 find 79451 0 0 0 0 1 - rpccon - nfscl 79452 79450 79452 79452 79452 1 slw rpccon FreeBSD ELF64 tcsh How to unlock system w/o reboot? automount -u don't work _______________________________________________ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-net@freebsd.org Wed Jan 11 22:44:36 2017 Return-Path: Delivered-To: freebsd-net@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 68C27CAB1B7; Wed, 11 Jan 2017 22:44:36 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from mail.ignoranthack.me (ignoranthack.me [199.102.79.106]) (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 3188B1DDE; Wed, 11 Jan 2017 22:44:35 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from [192.168.0.6] (67-0-248-244.albq.qwest.net [67.0.248.244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: sbruno@ignoranthack.me) by mail.ignoranthack.me (Postfix) with ESMTPSA id 625A91928BA; Wed, 11 Jan 2017 22:44:29 +0000 (UTC) Subject: Re: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb pending To: =?UTF-8?Q?Olivier_Cochard-Labb=c3=a9?= , Matthew Macy References: <30f21c75-d3a2-edcd-1999-d5ed9f970c06@freebsd.org> <1598d97bf2a.c6bcb76838987.6501340920645175463@nextbsd.org> <574a7ac7-4842-9518-8286-a4d89a9f7a27@freebsd.org> <6c6cb534-73c7-464b-8af1-7445a9c0188c@freebsd.org> <1598f29d379.ea6360351471.8752933472741761813@nextbsd.org> Cc: "freebsd-net@freebsd.org" , "freebsd-current@freebsd.org" From: Sean Bruno Message-ID: <000deaa1-65f0-58b6-e322-5e9ec0081644@freebsd.org> Date: Wed, 11 Jan 2017 15:44:26 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="BQft3SddK6t4MuG81v2jeu42SPeiMDt9D" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2017 22:44:36 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --BQft3SddK6t4MuG81v2jeu42SPeiMDt9D Content-Type: multipart/mixed; boundary="GMFUMIp3wa6oPH7FfPsAtUvwS2bFBtKiJ"; protected-headers="v1" From: Sean Bruno To: =?UTF-8?Q?Olivier_Cochard-Labb=c3=a9?= , Matthew Macy Cc: "freebsd-net@freebsd.org" , "freebsd-current@freebsd.org" Message-ID: <000deaa1-65f0-58b6-e322-5e9ec0081644@freebsd.org> Subject: Re: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb pending References: <30f21c75-d3a2-edcd-1999-d5ed9f970c06@freebsd.org> <1598d97bf2a.c6bcb76838987.6501340920645175463@nextbsd.org> <574a7ac7-4842-9518-8286-a4d89a9f7a27@freebsd.org> <6c6cb534-73c7-464b-8af1-7445a9c0188c@freebsd.org> <1598f29d379.ea6360351471.8752933472741761813@nextbsd.org> In-Reply-To: --GMFUMIp3wa6oPH7FfPsAtUvwS2bFBtKiJ Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable > My tunning are (same for both test): > hw.igb.rxd=3D"2048" (it should be useless now) > hw.igb.txd=3D"2048" (it should be useless now) > hw.em.rxd=3D"2048" > hw.em.txd=3D"2048" > hw.igb.rx_process_limit=3D"-1" (It should be useless now too) > hw.em.rx_process_limit=3D"-1" >=20 > dev.igb.2.fc=3D0 > dev.igb.3.fc=3D0 >=20 > I can generate profiling data for you: what kind of data do you want ? Specifically, you may want to adjust these: dev.em.0.iflib.override_nrxds: 0 dev.em.0.iflib.override_ntxds: 0 dev.em.0.iflib.override_nrxqs: 0 dev.em.0.iflib.override_ntxqs: 0 sean --GMFUMIp3wa6oPH7FfPsAtUvwS2bFBtKiJ-- --BQft3SddK6t4MuG81v2jeu42SPeiMDt9D Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEEuq1GMucSHejSCZfdEgHvyh5yfmQFAlh2tUpfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEJB QUQ0NjMyRTcxMjFERThEMjA5OTdERDEyMDFFRkNBMUU3MjdFNjQACgkQEgHvyh5y fmS6CAf+I/lN/Q5awnm3DEI23xCHjVendr/t0cjXxNbGtr5Ne6IT3u4lWjwFkEGU UY5UQm7jiIOSPwgli+43xJBdsRkdED3REa+/pDoF47iiq15hifK4LelbhXPG8hsh kFsQxW0jzNqRQsjY95bbjZSjH0hNmt3W77JG+4d2BgNSE6ExxAxzG1BeM/JdL2lK lrLfTtIZPsGzBWAUkb7etdSdo3DpDX+iPCFK1OqlpCjkn2+5k1GO6wRqFLcolSD9 mnA0eIozs6ZeA7ipnc5MmRD6LfQZibhfpEF5J8NDVBJTSvZRUHKO1KXSZaXfS/O0 jjnnUhBo0cDGgv+th4CjZmU+jXsMMA== =ldlj -----END PGP SIGNATURE----- --BQft3SddK6t4MuG81v2jeu42SPeiMDt9D-- From owner-freebsd-net@freebsd.org Wed Jan 11 22:50:51 2017 Return-Path: Delivered-To: freebsd-net@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 38D71CAB688; Wed, 11 Jan 2017 22:50:51 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from mail.ignoranthack.me (ignoranthack.me [199.102.79.106]) (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 0625E1309; Wed, 11 Jan 2017 22:50:50 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from [192.168.0.6] (67-0-248-244.albq.qwest.net [67.0.248.244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: sbruno@ignoranthack.me) by mail.ignoranthack.me (Postfix) with ESMTPSA id 506041928BA; Wed, 11 Jan 2017 22:50:49 +0000 (UTC) Subject: Re: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb pending To: =?UTF-8?Q?Olivier_Cochard-Labb=c3=a9?= , Matthew Macy References: <30f21c75-d3a2-edcd-1999-d5ed9f970c06@freebsd.org> <1598d97bf2a.c6bcb76838987.6501340920645175463@nextbsd.org> <574a7ac7-4842-9518-8286-a4d89a9f7a27@freebsd.org> <6c6cb534-73c7-464b-8af1-7445a9c0188c@freebsd.org> <1598f29d379.ea6360351471.8752933472741761813@nextbsd.org> <000deaa1-65f0-58b6-e322-5e9ec0081644@freebsd.org> Cc: "freebsd-net@freebsd.org" , "freebsd-current@freebsd.org" From: Sean Bruno Message-ID: <91cb25c4-074e-f37b-84a6-8e41a89ea10f@freebsd.org> Date: Wed, 11 Jan 2017 15:50:46 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: <000deaa1-65f0-58b6-e322-5e9ec0081644@freebsd.org> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="5Hu6ie2nMlpNVFOmD25ijkHV0iCLTQm6k" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2017 22:50:51 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --5Hu6ie2nMlpNVFOmD25ijkHV0iCLTQm6k Content-Type: multipart/mixed; boundary="HPX50KJM6ISKV7A00PEKtXK4jeCBbxwig"; protected-headers="v1" From: Sean Bruno To: =?UTF-8?Q?Olivier_Cochard-Labb=c3=a9?= , Matthew Macy Cc: "freebsd-net@freebsd.org" , "freebsd-current@freebsd.org" Message-ID: <91cb25c4-074e-f37b-84a6-8e41a89ea10f@freebsd.org> Subject: Re: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb pending References: <30f21c75-d3a2-edcd-1999-d5ed9f970c06@freebsd.org> <1598d97bf2a.c6bcb76838987.6501340920645175463@nextbsd.org> <574a7ac7-4842-9518-8286-a4d89a9f7a27@freebsd.org> <6c6cb534-73c7-464b-8af1-7445a9c0188c@freebsd.org> <1598f29d379.ea6360351471.8752933472741761813@nextbsd.org> <000deaa1-65f0-58b6-e322-5e9ec0081644@freebsd.org> In-Reply-To: <000deaa1-65f0-58b6-e322-5e9ec0081644@freebsd.org> --HPX50KJM6ISKV7A00PEKtXK4jeCBbxwig Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 01/11/17 15:44, Sean Bruno wrote: >=20 >> My tunning are (same for both test): >> hw.igb.rxd=3D"2048" (it should be useless now) >> hw.igb.txd=3D"2048" (it should be useless now) >> hw.em.rxd=3D"2048" >> hw.em.txd=3D"2048" >> hw.igb.rx_process_limit=3D"-1" (It should be useless now too) >> hw.em.rx_process_limit=3D"-1" >> >> dev.igb.2.fc=3D0 >> dev.igb.3.fc=3D0 >> >> I can generate profiling data for you: what kind of data do you want ?= >=20 >=20 > Specifically, you may want to adjust these: >=20 > dev.em.0.iflib.override_nrxds: 0 > dev.em.0.iflib.override_ntxds: 0 >=20 > dev.em.0.iflib.override_nrxqs: 0 > dev.em.0.iflib.override_ntxqs: 0 >=20 > sean >=20 dev.igb.0 .... but you get the point. sean --HPX50KJM6ISKV7A00PEKtXK4jeCBbxwig-- --5Hu6ie2nMlpNVFOmD25ijkHV0iCLTQm6k Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEEuq1GMucSHejSCZfdEgHvyh5yfmQFAlh2tsZfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEJB QUQ0NjMyRTcxMjFERThEMjA5OTdERDEyMDFFRkNBMUU3MjdFNjQACgkQEgHvyh5y fmSvkwf/U+9TOSHltNdEcVDMpmH14wUwddEY/ysIzGSe3Sa1Js7Wee1X7SFxewzy WFKOikAMV5oT1aAmikFoH2Hy/BWIp4wfl1/WmoNAHd6o+LzlWtfRC8KyIt/P6NnT 9+y/E8auRYu+b5xuHYGWe9+DURW135gIrfBJIWuRGQT7AW4zwmLAeltVjZRhfCoH oS46AwgStMZ6PFl9hMa6N4eRQvb5QyLvlYwd3lLccnd4cnSUCOlmW7wh0KvSnHrj UrlaUixIG2cPMe532D9X6U2T5vJMUvYPbu1gmdxXazLaaeH3uHyj0olPFUCmQMzu orwCnXkmnyoG02YDlBZV82URJ4IpDg== =tmft -----END PGP SIGNATURE----- --5Hu6ie2nMlpNVFOmD25ijkHV0iCLTQm6k-- From owner-freebsd-net@freebsd.org Wed Jan 11 22:59:26 2017 Return-Path: Delivered-To: freebsd-net@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 3299ACABAE1 for ; Wed, 11 Jan 2017 22:59:26 +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 E9C981D91 for ; Wed, 11 Jan 2017 22:59:25 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1cRRrW-000LE0-V1; Thu, 12 Jan 2017 01:59:22 +0300 Date: Thu, 12 Jan 2017 01:59:22 +0300 From: Slawa Olhovchenkov To: Rick Macklem Cc: "freebsd-net@freebsd.org" Subject: Re: NFSv4 stuck Message-ID: <20170111225922.GE30374@zxy.spb.ru> References: <20170111220818.GD30374@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2017 22:59:26 -0000 On Wed, Jan 11, 2017 at 10:39:42PM +0000, Rick Macklem wrote: > "umount -f" is your only chance. However, if there is already a non-forced > dismount stuck, it won't work because the non-forced dismount will have > the mounted-on vnode locked. I am use 'intr,soft' flags -- why ignored? > Btw, the processes waiting on "rpccon" are trying to make a new TCP > connection to the server. Are you sure the client can talk to the server > over your net? root@edge16:/home/admin # ping stat PING stat.int.integros.com (185.38.13.26): 56 data bytes 64 bytes from 185.38.13.26: icmp_seq=0 ttl=63 time=0.103 ms # netstat -an | grep 185.38.13 tcp4 0 0 185.38.12.42.709 185.38.13.26.2049 CLOSE_WAIT tcp4 0 0 185.38.12.42.1006 185.38.13.26.2049 CLOSED root@edge16:/home/admin # telnet -NK 185.38.13.26 2049 Trying 185.38.13.26... Connected to 185.38.13.26. Escape character is '^]'. ^C^] telnet> q I am don't know how to check more -- currently no sockets try > ________________________________________ > From: owner-freebsd-net@freebsd.org on behalf of Slawa Olhovchenkov > Sent: Wednesday, January 11, 2017 5:08:18 PM > To: freebsd-net@freebsd.org > Subject: NFSv4 stuck > > I am have NFSv4 mount dir and some time got stucked after access. > > Mounted by automount: > > # cat /etc/nfs.map > /NFS -nfsv4,intr,soft,sec=krb5i,gssname=host stat:/ > > # mount -v > map -hosts on /net (autofs, fsid 01ff00cfcf000000) > map nfs.map on /NFS (autofs, fsid 02ff00cfcf000000) > map nfs.map on /NFS (autofs, fsid 03ff00cfcf000000) > map nfs.map on /NFS (autofs, fsid 04ff00cfcf000000) > map nfs.map on /NFS (autofs, fsid 05ff00cfcf000000) > stat:/ on /NFS (nfs, nfsv4acls, automounted, fsid 0aff003a3a000000) > > # procstat -a | grep -e rpc -e gss -e nfs > 840 1 840 840 0 1 root select FreeBSD ELF64 rpcbind > 956 1 956 956 0 1 root pause FreeBSD ELF64 nfsuserd > 957 956 956 956 0 1 root sbwait FreeBSD ELF64 nfsuserd > 958 956 956 956 0 1 root select FreeBSD ELF64 nfsuserd > 960 956 956 956 0 1 root select FreeBSD ELF64 nfsuserd > 961 956 956 956 0 1 root sbwait FreeBSD ELF64 nfsuserd > 969 1 969 969 0 1 root select FreeBSD ELF64 rpc.statd > 972 1 972 972 0 1 root rpcsvc FreeBSD ELF64 rpc.lockd > 10629 1098 10629 10629 0 1 root gssstate FreeBSD ELF64 sshd > 10687 10652 10687 10647 10647 1 admin gssstate FreeBSD ELF64 csh > 14521 1098 14521 14521 0 1 root gssstate FreeBSD ELF64 sshd > 14924 14896 14924 14892 14892 1 admin nfs FreeBSD ELF64 automount > 45455 45454 45455 45455 45455 1 slw gssstate FreeBSD ELF64 tcsh > 63495 63481 42791 42791 0 1 root rpccon FreeBSD ELF64 find > 79451 0 0 0 0 1 - rpccon - nfscl > 79452 79450 79452 79452 79452 1 slw rpccon FreeBSD ELF64 tcsh > > How to unlock system w/o reboot? > > automount -u don't work > _______________________________________________ > freebsd-net@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-net@freebsd.org Wed Jan 11 23:20:33 2017 Return-Path: Delivered-To: freebsd-net@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 42F70CAB1C5 for ; Wed, 11 Jan 2017 23:20:33 +0000 (UTC) (envelope-from michael+lists@burnttofu.net) Received: from burnttofu.net (burnttofu.net [IPv6:2607:fc50:1:9d00::9977]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "burnttofu.net", Issuer "burnttofu.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 07C55190E for ; Wed, 11 Jan 2017 23:20:32 +0000 (UTC) (envelope-from michael+lists@burnttofu.net) Received: from elwha.brokendns.net (elwha.brokendns.net [IPv6:2607:f2f8:a544::2]) by burnttofu.net (8.15.2/8.15.2) with ESMTPS id v0BNKTes001255 (version=TLSv1.2 cipher=DHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Wed, 11 Jan 2017 18:20:30 -0500 (EST) (envelope-from michael+lists@burnttofu.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=burnttofu.net; s=bt; t=1484176831; bh=30w/b42SRF+xlF4S0kI6lSY33ZhAHqFqG/cPnaDtIkg=; h=Subject:To:References:Cc:From:Date:In-Reply-To; b=aoJwa5YS8YWfmCmixJDrWsXBGJLItjhL2jQg+GTSbZZ1u6+ROGrYvTVC1GAu/Dfqb mvXp/UD72LaLxoERI9sSq2qTutnp6GhyxiimdQtpHlaSJYmprFsmVWUxSou7Y1xsHB Tuc04lygEFWJTIQatiKjXvCMyId+gBt9178i4BLCCw94QUlMr2rE/c3f+7igY/oAop VSMVtaeabHQzjN2H7lojiaf4avlLCwCUE8wwj708ZZezNAfsmKoNqikmE70JQDYJkI g6yCjVFdDSV1vuzlnrtsKnsiDofMXxLJPEGuPHk99DzZEDLzIgHX89xc0gjaABlQH9 K8BZ3v9uAdiPw== Received: from kimberton.burnttofu.net (unknown [IPv6:2601:643:8400:3e00::7777]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elwha.brokendns.net (5.65c/IDA-1.4.4/5.63) with ESMTPSA id 316AB7C8B; Wed, 11 Jan 2017 15:20:29 -0800 (PST) Subject: Re: NFSv4 stuck To: Slawa Olhovchenkov , Rick Macklem References: <20170111220818.GD30374@zxy.spb.ru> <20170111225922.GE30374@zxy.spb.ru> Cc: "freebsd-net@freebsd.org" From: Michael Sinatra Message-ID: Date: Wed, 11 Jan 2017 15:20:22 -0800 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: <20170111225922.GE30374@zxy.spb.ru> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Default is to whitelist mail, not delayed by milter-greylist-4.6.1 (burnttofu.net [IPv6:2607:fc50:1:9d00::9977]); Wed, 11 Jan 2017 18:20:31 -0500 (EST) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2017 23:20:33 -0000 On 01/11/17 14:59, Slawa Olhovchenkov wrote: > On Wed, Jan 11, 2017 at 10:39:42PM +0000, Rick Macklem wrote: > >> "umount -f" is your only chance. However, if there is already a non-forced >> dismount stuck, it won't work because the non-forced dismount will have >> the mounted-on vnode locked. > > I am use 'intr,soft' flags -- why ignored? intr and soft are considered dangerous with nfsv4. See the "BUGS" section of the mount_nfs(8) man page. michael From owner-freebsd-net@freebsd.org Wed Jan 11 23:50:26 2017 Return-Path: Delivered-To: freebsd-net@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 C3BAFCABBD4 for ; Wed, 11 Jan 2017 23:50:26 +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 8707118A8 for ; Wed, 11 Jan 2017 23:50:26 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1cRSeq-000Mro-Ar; Thu, 12 Jan 2017 02:50:20 +0300 Date: Thu, 12 Jan 2017 02:50:20 +0300 From: Slawa Olhovchenkov To: Michael Sinatra Cc: Rick Macklem , "freebsd-net@freebsd.org" Subject: Re: NFSv4 stuck Message-ID: <20170111235020.GF30374@zxy.spb.ru> References: <20170111220818.GD30374@zxy.spb.ru> <20170111225922.GE30374@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2017 23:50:26 -0000 On Wed, Jan 11, 2017 at 03:20:22PM -0800, Michael Sinatra wrote: > On 01/11/17 14:59, Slawa Olhovchenkov wrote: > > On Wed, Jan 11, 2017 at 10:39:42PM +0000, Rick Macklem wrote: > > > >> "umount -f" is your only chance. However, if there is already a non-forced > >> dismount stuck, it won't work because the non-forced dismount will have > >> the mounted-on vnode locked. > > > > I am use 'intr,soft' flags -- why ignored? > > intr and soft are considered dangerous with nfsv4. See the "BUGS" > section of the mount_nfs(8) man page. Currently I am see dangerous w/o intr: system need reboot, application don't killable. From owner-freebsd-net@freebsd.org Thu Jan 12 00:54:52 2017 Return-Path: Delivered-To: freebsd-net@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 ED849CA987A; Thu, 12 Jan 2017 00:54:52 +0000 (UTC) (envelope-from mmacy@nextbsd.org) Received: from sender163-mail.zoho.com (sender163-mail.zoho.com [74.201.84.163]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D7C06131D; Thu, 12 Jan 2017 00:54:52 +0000 (UTC) (envelope-from mmacy@nextbsd.org) Received: from mail.zoho.com by mx.zohomail.com with SMTP id 1484182483952176.91086989048313; Wed, 11 Jan 2017 16:54:43 -0800 (PST) Date: Wed, 11 Jan 2017 16:54:43 -0800 From: Matthew Macy To: =?UTF-8?Q?=22Olivier_Cochard-Labb=C3=A9=22?= Cc: "Sean Bruno" , "freebsd-net@freebsd.org" , "freebsd-current@freebsd.org" Message-ID: <159902b73ed.10775291e21533.7488368455500235608@nextbsd.org> In-Reply-To: References: <30f21c75-d3a2-edcd-1999-d5ed9f970c06@freebsd.org> <1598d97bf2a.c6bcb76838987.6501340920645175463@nextbsd.org> <574a7ac7-4842-9518-8286-a4d89a9f7a27@freebsd.org> <6c6cb534-73c7-464b-8af1-7445a9c0188c@freebsd.org> <1598f29d379.ea6360351471.8752933472741761813@nextbsd.org> <1598f3f8588.d20017893749.339651164872952258@nextbsd.org> <1598f42ad77.eeec05be4113.9201780237587761460@nextbsd.org> Subject: Re: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb pending MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Priority: Medium User-Agent: Zoho Mail X-Mailer: Zoho Mail X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 12 Jan 2017 00:54:53 -0000 > A flame graph for the core cycle count and a flame graph with cache mis= s stats from pmc would be a great start. > =20 >=20 > =E2=80=8BI didn't know the exact event name to use for cache miss stats,= but here are the flame graphs for CPU_CLK_UNHALTED_CORE: > http://dev.bsdrp.net/netgate.r311848.CPU_CLK_UNHALTED_CORE.svg > http://dev.bsdrp.net/netgate.r311849.CPU_CLK_UNHALTED_CORE.svg Thanks. Having twice as many txqs would definitely help. It's also clear th= at there may be some sort of peformance issue in iflib_txq_drain. Although = it could just be non-stop cache misses on the packet headers. -M From owner-freebsd-net@freebsd.org Thu Jan 12 04:14:32 2017 Return-Path: Delivered-To: freebsd-net@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 3D4A3CAC1E6 for ; Thu, 12 Jan 2017 04:14:32 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wm0-x236.google.com (mail-wm0-x236.google.com [IPv6:2a00:1450:400c:c09::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C091D1654 for ; Thu, 12 Jan 2017 04:14:31 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-wm0-x236.google.com with SMTP id c206so5637993wme.0 for ; Wed, 11 Jan 2017 20:14:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=uVVJPEiQS1wQom6a/TQdxJlilzcwHH9Ys9R8sJdrOjg=; b=YqJ4EldkVzGr4vlCxb5Y5g0wzjPyPUlEjxMUXpYdacLq3s+W/O55UadsIa8rBnmVmP P/uLQP6ijzbgb8pYIcdQrt6nCRx5u6BHDNt6p3Wqo9m2MKi8mZUrLx/tu8QW53Mlvrdt +9Nq3H0/wwz4r/WrOR+qiMTD1hRiWcUe9JbqwS3mEag67RopS2Fxw9FzcHbkvSdkzNn9 O6LQjYC/LiyOovXQzSTNrAE+TLp/YSD4NdLdI1YGPfTNOOH2UqDNL7gOaMqmM6dssrby XiXpL9Rzs3u63NqR5FslgG5SpUGHGMgfxPzl7dJjeFzU/po+LLxuDvkgFPXjgqKuGJgr mfSg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=uVVJPEiQS1wQom6a/TQdxJlilzcwHH9Ys9R8sJdrOjg=; b=lp5kTTYHtST6pzw2+bS9HgX5yAsSX37Tp9ElhwOvq67LvtdlmNjJrn2YTnJMmJ/1+/ MkUEagXVf73XhwOuw73ehRaBYC75U8KK/VlF7xYLGzfauPM+JT9tOepEoVPpW68mFOSP DzYjijCScnRctYrx4wuDGSqw7cHu3Sn+XcDFZF+XVQKREA9k81OfiACet11UXRz09Wq3 E0rPSgmWvjaxqrMN1mvYG9jPrZn4tNHi7n0njgoEEUIv8dpcvVbhv+gZ9EhR+ZXT91Gs kqYpKhTuNvcnFd/mFk4Dj4XzU6dwiPMR8NPS2+I1oUWi40EvaOIC5Ccv/I0RYuL+Y3ny b0iw== X-Gm-Message-State: AIkVDXLwyzGEnsGdpjOEBcPjrCl0LrH/AOkJ3CGlrMKF08rNgQfHku0RClw7+PXdfMrJ5Msmuzqu54ArMHF9vQ== X-Received: by 10.223.173.181 with SMTP id w50mr5560109wrc.177.1484194469104; Wed, 11 Jan 2017 20:14:29 -0800 (PST) MIME-Version: 1.0 Sender: adrian.chadd@gmail.com Received: by 10.194.82.162 with HTTP; Wed, 11 Jan 2017 20:14:27 -0800 (PST) In-Reply-To: References: From: Adrian Chadd Date: Wed, 11 Jan 2017 20:14:27 -0800 X-Google-Sender-Auth: K2NWmqpqjOtNMzPspJ0iYvv2SdQ Message-ID: Subject: Re: Changing NIC ring weight in indirection table To: Sepherosa Ziehau Cc: David Belle-Isle , "freebsd-net@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 12 Jan 2017 04:14:32 -0000 yeah, adrian is currently busy doing non-paid wifi work, so getting onto non-paid RSS configuration work is taking a backburner. Patches gratefully accepted though! -a On 3 January 2017 at 17:19, Sepherosa Ziehau wrote: > On Fri, Dec 30, 2016 at 11:34 PM, David Belle-Isle wrote: >> Hi, >> >> Can anyone tell me how to set the weight of a ring from the indirection >> table on FreeBSD? My plan is to yank out a TX ring and to use it solely >> with netmap to receive packets but want to make sure the kernel won't be >> receiving any packets on this ring. > > TX side is not related to the RSS's indirect table at all. I believe > you need to modify the drivers you are using. > >> >> Based on a quick search this is something that ethtool would be able to do >> on Linux but I doubt this can be done on FreeBSD using the same tool? > > adrian@ has proposed something in this area, RSS key and RSS indirect > table, though not much happens yet. I have implemented the indirect > table changes through a driver specific sysctl for hn(4), you probably > could do the same for the drivers that you are using. But again, you > will have to change the code. > > Thanks, > sephe From owner-freebsd-net@freebsd.org Thu Jan 12 06:14:36 2017 Return-Path: Delivered-To: freebsd-net@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 CEE61CACCEB for ; Thu, 12 Jan 2017 06:14:36 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [78.47.246.247]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 6B1BB1FC7 for ; Thu, 12 Jan 2017 06:14:35 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221]) by hz.grosbein.net (8.15.2/8.15.2) with ESMTPS id v0C6EBJ5023930 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 12 Jan 2017 07:14:12 +0100 (CET) (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: slw@zxy.spb.ru Received: from [10.58.0.10] (dadvw [10.58.0.10]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTPS id v0C6E3HF078345 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 12 Jan 2017 13:14:03 +0700 (KRAT) (envelope-from eugen@grosbein.net) Subject: Re: NFSv4 stuck To: Slawa Olhovchenkov , Michael Sinatra References: <20170111220818.GD30374@zxy.spb.ru> <20170111225922.GE30374@zxy.spb.ru> <20170111235020.GF30374@zxy.spb.ru> Cc: "freebsd-net@freebsd.org" , Rick Macklem From: Eugene Grosbein Message-ID: <58771EA6.1020104@grosbein.net> Date: Thu, 12 Jan 2017 13:13:58 +0700 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: <20170111235020.GF30374@zxy.spb.ru> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=0.3 required=5.0 tests=BAYES_00,LOCAL_FROM autolearn=no autolearn_force=no version=3.4.1 X-Spam-Report: * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 2.6 LOCAL_FROM From my domains X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on hz.grosbein.net X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 12 Jan 2017 06:14:36 -0000 12.01.2017 6:50, Slawa Olhovchenkov пишет: > On Wed, Jan 11, 2017 at 03:20:22PM -0800, Michael Sinatra wrote: > >> On 01/11/17 14:59, Slawa Olhovchenkov wrote: >>> On Wed, Jan 11, 2017 at 10:39:42PM +0000, Rick Macklem wrote: >>> >>>> "umount -f" is your only chance. However, if there is already a non-forced >>>> dismount stuck, it won't work because the non-forced dismount will have >>>> the mounted-on vnode locked. >>> >>> I am use 'intr,soft' flags -- why ignored? >> >> intr and soft are considered dangerous with nfsv4. See the "BUGS" >> section of the mount_nfs(8) man page. > > Currently I am see dangerous w/o intr: system need reboot, application > don't killable. NFSv4 confiders "intr,soft" dangerous for data generated by poorly written applications, not for a OS. Just switch back to NFSv3 if you value reliability of your machines more. NFSv3 processes "intr,soft" just fine. From owner-freebsd-net@freebsd.org Thu Jan 12 10:51:58 2017 Return-Path: Delivered-To: freebsd-net@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 94AD2CACE0B for ; Thu, 12 Jan 2017 10:51:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 83FB11078 for ; Thu, 12 Jan 2017 10:51:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v0CApw3V059872 for ; Thu, 12 Jan 2017 10:51:58 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 215933] SCM_RIGHTS messages being lost, socket data being lost as well, with example code Date: Thu, 12 Jan 2017 10:51:58 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: short_desc assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 12 Jan 2017 10:51:58 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D215933 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|SCM_RIGHTS messages being |SCM_RIGHTS messages being |lost, socket data being |lost, socket data being |lost as well, with example |lost as well, with example |code.. |code Assignee|freebsd-bugs@FreeBSD.org |freebsd-net@FreeBSD.org --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Thu Jan 12 10:52:16 2017 Return-Path: Delivered-To: freebsd-net@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 6E202CACE8D for ; Thu, 12 Jan 2017 10:52:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 5C36F11BE for ; Thu, 12 Jan 2017 10:52:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v0CAqG5l060283 for ; Thu, 12 Jan 2017 10:52:16 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 215933] SCM_RIGHTS messages being lost, socket data being lost as well (with example code) Date: Thu, 12 Jan 2017 10:52:16 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: short_desc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 12 Jan 2017 10:52:16 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D215933 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|SCM_RIGHTS messages being |SCM_RIGHTS messages being |lost, socket data being |lost, socket data being |lost as well, with example |lost as well (with example |code |code) --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Thu Jan 12 13:15:14 2017 Return-Path: Delivered-To: freebsd-net@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 0F7D5CAB679 for ; Thu, 12 Jan 2017 13:15:14 +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 C4D4A11C4 for ; Thu, 12 Jan 2017 13:15:13 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1cRfDc-000N8w-I9; Thu, 12 Jan 2017 16:15:04 +0300 Date: Thu, 12 Jan 2017 16:15:04 +0300 From: Slawa Olhovchenkov To: Eugene Grosbein Cc: Michael Sinatra , "freebsd-net@freebsd.org" , Rick Macklem Subject: Re: NFSv4 stuck Message-ID: <20170112131504.GG30374@zxy.spb.ru> References: <20170111220818.GD30374@zxy.spb.ru> <20170111225922.GE30374@zxy.spb.ru> <20170111235020.GF30374@zxy.spb.ru> <58771EA6.1020104@grosbein.net> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <58771EA6.1020104@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: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 12 Jan 2017 13:15:14 -0000 On Thu, Jan 12, 2017 at 01:13:58PM +0700, Eugene Grosbein wrote: > 12.01.2017 6:50, Slawa Olhovchenkov ÐÉÛÅÔ: > > On Wed, Jan 11, 2017 at 03:20:22PM -0800, Michael Sinatra wrote: > > > >> On 01/11/17 14:59, Slawa Olhovchenkov wrote: > >>> On Wed, Jan 11, 2017 at 10:39:42PM +0000, Rick Macklem wrote: > >>> > >>>> "umount -f" is your only chance. However, if there is already a non-forced > >>>> dismount stuck, it won't work because the non-forced dismount will have > >>>> the mounted-on vnode locked. > >>> > >>> I am use 'intr,soft' flags -- why ignored? > >> > >> intr and soft are considered dangerous with nfsv4. See the "BUGS" > >> section of the mount_nfs(8) man page. > > > > Currently I am see dangerous w/o intr: system need reboot, application > > don't killable. > > NFSv4 confiders "intr,soft" dangerous for data generated by poorly written applications, not for a OS. What data? In may case no data. In may case just root idle tcsh. And I am got dangerous for OS: application stuck, nfs don't unmount, any call to nfs function is stuck (lsof, for example) > Just switch back to NFSv3 if you value reliability of your machines more. > NFSv3 processes "intr,soft" just fine. By implementation, not by designg. NFSv4 have some features need for me. From owner-freebsd-net@freebsd.org Thu Jan 12 14:14:16 2017 Return-Path: Delivered-To: freebsd-net@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 CC3B0CACD5D for ; Thu, 12 Jan 2017 14:14:16 +0000 (UTC) (envelope-from jpa@semihalf.com) Received: from mail-ua0-x22e.google.com (mail-ua0-x22e.google.com [IPv6:2607:f8b0:400c:c08::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7FE041768 for ; Thu, 12 Jan 2017 14:14:16 +0000 (UTC) (envelope-from jpa@semihalf.com) Received: by mail-ua0-x22e.google.com with SMTP id 96so14789989uaq.3 for ; Thu, 12 Jan 2017 06:14:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=semihalf-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=ig06pvn7qzcu0Uu2io3V3i/sVOZzo0s45u/KhRUgHxQ=; b=V//BXZUXaAtukprEP5XTmVslOKbJkLJiuXn/Vbhx3SDS2m9Yqtk27ctnOSCSOcyldr mEd7LlBRYIv06QYMQw8WyzsOUuUi4yhZWjAvLWkvwhFjZcWqQcVzHaRkEwGYdioafLDy TU77LorlOQdOgrySBuHQbwdDJeeeLEzYsRsozuTvY81rShUpWSP/KMdbFk062SjlBCTm bJwOd7JpugI1v5MTEkDjc+Bx9x40jXayO+hE23jCn1q2zn/iryKCKK7z+v4klwPr20A8 tcuqbrectMavRCrQplRSw0b3x8HboHHdaPvZ4rqL5WLiYKpVlymYgrRxdRr10xXrumXu oMEA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=ig06pvn7qzcu0Uu2io3V3i/sVOZzo0s45u/KhRUgHxQ=; b=AO0GsaZk1zR5ffvLSJmverQT2igTnkxfgkBIrD5X/Y2zAFH1oGEwObpCRJvMtcqwKU 2U2EryhuSB1D1X9+WN87yaHqN2u7payb0AthlEDZaEVw139ZXMzI0MUx0/JE6QDe8tI5 i4gs1/uI1tnsXq5g4a3sPwqE2xIom06jB30cIsqPvQQOnC3qD9hJJl/qVxF1LFZgS33O nsZUGf/CJHlZ1Q7DcVlInS3muhstxndvLvwmDAwSGT795zaBzwdzPqYYI2vZl57AtbG/ 038sPhi09LKdLRVVfrmEJh9w+kNXDMGHDgJBjxXnwVhk7CqJWX4jqawL853henJ5Kt5L qh+w== X-Gm-Message-State: AIkVDXLO9wxVSO9T1g/nfCIelOZlfqV+XLEOGHYXl6ynDbJAqLfAfLb0AIOyILPnY/TYWzMU5gjy87ZQhNS6eA== X-Received: by 10.159.48.131 with SMTP id j3mr5982468uab.43.1484230455540; Thu, 12 Jan 2017 06:14:15 -0800 (PST) MIME-Version: 1.0 Received: by 10.31.46.18 with HTTP; Thu, 12 Jan 2017 06:13:45 -0800 (PST) In-Reply-To: References: <20161128221033.GM55731@strugglingcoder.info> <20161129190509.GO27748@FreeBSD.org> From: Jakub Palider Date: Thu, 12 Jan 2017 15:13:45 +0100 Message-ID: Subject: Re: FLOWTABLE aka TCP route caching panic To: Gleb Smirnoff Cc: hiren panchasara , freebsd-net@freebsd.org, karels@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 12 Jan 2017 14:14:16 -0000 An update: eventually, FLOWTABLE option also resulted in crash with __rw_lock_hard on FreeBSD release/11.0.0 (also on VM). This time, however, the backtrace was different, instead of tcp_output->ip_output->ether_output() chain, it happened in flowtable_clean_vnet() On Wed, Jan 11, 2017 at 10:42 AM, Jakub Palider wrote: > On Tue, 29 Nov 2016 11:05:09 -0800 > Gleb Smirnoff wrote: > > > On Mon, Nov 28, 2016 at 02:10:33PM -0800, hiren panchasara wrote: > > h> > Hi, > > h> > I have found that last month (19 Oct) the problem appeared on this > list, > > h> > and to my experience it persists, both on VM and bare metal > installation > > h> > (HEAD from yesterday). I looks that enabling FLOWTABLE option is > the only > > h> > source of this fault happening. It appears on our setup in 80% > cases within > > h> > one hour from boot up. > > h> > From our debugging, it is caused by lock on DESTROYED lock. Did you > find a > > h> > solution to this problem? > > > > Not yet. > > > > I'm pretty sure that reverting my r307234 will fix your crashes. > However, I still > > believe that r307234 is a proper way of fixing things, not r300854 which > just > > plugged the problem in the nearest place to the crash. But as we all see > r307234 > > is definitely missing some code path, which still allows for stale route > to be > > referenced. > > > > -- > > Totus tuus, Glebius. > > Thank you for your pointer, in helped at some point. The problem > however returned, especially when under heavy, continuous load. We are > running 4 iperf3 processes, each having 4 threads, and the machine > dies after 30-60 minutes of TCP traffic. I am running rS30911112 from > Nov 24. > On FreeBSD 11.0-RELEASE this problem (1 full day of testing) was not > noticed. Could you point to related commits that might also influence > this behaviour? > Thanks, > Jakub > From owner-freebsd-net@freebsd.org Thu Jan 12 15:30:38 2017 Return-Path: Delivered-To: freebsd-net@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 E0193CACE74 for ; Thu, 12 Jan 2017 15:30:38 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 D000A10F4 for ; Thu, 12 Jan 2017 15:30:38 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v0CFUcoF019596 for ; Thu, 12 Jan 2017 15:30:38 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 215998] if.c has dependencies on loop and ether Date: Thu, 12 Jan 2017 15:30:39 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: bz@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 12 Jan 2017 15:30:39 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D215998 Bjoern A. Zeeb changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-net@FreeBSD.org CC| |bz@FreeBSD.org --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Thu Jan 12 16:40:52 2017 Return-Path: Delivered-To: freebsd-net@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 18560CAC443 for ; Thu, 12 Jan 2017 16:40:52 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wm0-x232.google.com (mail-wm0-x232.google.com [IPv6:2a00:1450:400c:c09::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AA2C617F6; Thu, 12 Jan 2017 16:40:51 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-wm0-x232.google.com with SMTP id c85so27318415wmi.1; Thu, 12 Jan 2017 08:40:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=TtwQB+IP7KpwgzfYZAyEITasAFeFrtabUELC/qkVWYg=; b=QEy8ZJXrDPJ+d5GnY5wV2MNBY7JS5w97bKWt9d+UYeowLPAZtgb0RMKBHvUTDZipcr 04RCbDfHoQH0np86GhP2kkEd4CqOoF8oAUIa7J8sk9O71IdJh4otDWSaSpCVHdsXwgPE l+KlgPFv6Eo5di9FK7Y4UTwdeiuPbkxTLakGtRDJpdSHw8rX/MtNMPkKFt73/UQQzG+I 4MQGUVbTKUgsLdJSMQggTzjTkWChzMIdw0YWrRuT9okqkeBVToJDUB9zEjRGQ17WKS7W GDg2P896ZC+aSuqeKzrznGn8f3XprDuP/hrqz41qnu2eM4Jc4YDAWjNHPrUEsbJXsggc i59A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=TtwQB+IP7KpwgzfYZAyEITasAFeFrtabUELC/qkVWYg=; b=RmeWSuE1AysLqsaYqPkTMIv16a3SBk3Nz2miXBDxX3MuKKfMiX/8RIt9f7MZrdduMC p737tXBUNF26AWks2GbmJDzFo0UQXeJfZfLdCq2xaQRFYrNVqXkVGTmgeaEWn5ZTUgj5 MQfRKiDpK97LZ9/xuQ+GcNR8eL+1vvfKnRWwVeBLjjd2N5avO77qm4dZqps8k4cyxVNt c332W0bmNElbHcI7JnQIwHORQ5V6YMXS1sVUMlUL+NIaD9II1tbZ77lu19tBRND6clqg /uhwRwmuI38hS1HMDbp/Js7r6e1xb92x2SC1MukztFr4OiMw/lVnqWsJCHgqk/3OuLI1 eICg== X-Gm-Message-State: AIkVDXKpHiGFIgcP0KmH8zo2c54pmiWuJ3GqWuvPaM3mfg3/Vd+YakhfjmVvJhsvwHy90qWqdoRxKu8hZqPwJw== X-Received: by 10.223.151.138 with SMTP id s10mr7860857wrb.65.1484239249398; Thu, 12 Jan 2017 08:40:49 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.82.162 with HTTP; Thu, 12 Jan 2017 08:40:48 -0800 (PST) In-Reply-To: References: <20161128221033.GM55731@strugglingcoder.info> <20161129190509.GO27748@FreeBSD.org> From: Adrian Chadd Date: Thu, 12 Jan 2017 08:40:48 -0800 Message-ID: Subject: Re: FLOWTABLE aka TCP route caching panic To: Jakub Palider Cc: Gleb Smirnoff , FreeBSD Net , hiren panchasara , karels@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 12 Jan 2017 16:40:52 -0000 i can reproduce this daily using flowtable on a wifi enabled PC on -HEAD. -adrian On 12 January 2017 at 06:13, Jakub Palider wrote: > An update: eventually, FLOWTABLE option also resulted in crash with > __rw_lock_hard on FreeBSD release/11.0.0 (also on VM). > This time, however, the backtrace was different, instead of > tcp_output->ip_output->ether_output() chain, it happened in > flowtable_clean_vnet() > > On Wed, Jan 11, 2017 at 10:42 AM, Jakub Palider wrote: > >> On Tue, 29 Nov 2016 11:05:09 -0800 >> Gleb Smirnoff wrote: >> >> > On Mon, Nov 28, 2016 at 02:10:33PM -0800, hiren panchasara wrote: >> > h> > Hi, >> > h> > I have found that last month (19 Oct) the problem appeared on this >> list, >> > h> > and to my experience it persists, both on VM and bare metal >> installation >> > h> > (HEAD from yesterday). I looks that enabling FLOWTABLE option is >> the only >> > h> > source of this fault happening. It appears on our setup in 80% >> cases within >> > h> > one hour from boot up. >> > h> > From our debugging, it is caused by lock on DESTROYED lock. Did you >> find a >> > h> > solution to this problem? >> > >> > Not yet. >> > >> > I'm pretty sure that reverting my r307234 will fix your crashes. >> However, I still >> > believe that r307234 is a proper way of fixing things, not r300854 which >> just >> > plugged the problem in the nearest place to the crash. But as we all see >> r307234 >> > is definitely missing some code path, which still allows for stale route >> to be >> > referenced. >> > >> > -- >> > Totus tuus, Glebius. >> >> Thank you for your pointer, in helped at some point. The problem >> however returned, especially when under heavy, continuous load. We are >> running 4 iperf3 processes, each having 4 threads, and the machine >> dies after 30-60 minutes of TCP traffic. I am running rS30911112 from >> Nov 24. >> On FreeBSD 11.0-RELEASE this problem (1 full day of testing) was not >> noticed. Could you point to related commits that might also influence >> this behaviour? >> Thanks, >> Jakub >> > _______________________________________________ > freebsd-net@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-net@freebsd.org Thu Jan 12 21:45:59 2017 Return-Path: Delivered-To: freebsd-net@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 4D531CAD46A for ; Thu, 12 Jan 2017 21:45:59 +0000 (UTC) (envelope-from matt.joras@gmail.com) Received: from mail-qt0-x234.google.com (mail-qt0-x234.google.com [IPv6:2607:f8b0:400d:c0d::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0D92D18B3 for ; Thu, 12 Jan 2017 21:45:59 +0000 (UTC) (envelope-from matt.joras@gmail.com) Received: by mail-qt0-x234.google.com with SMTP id v23so31265033qtb.0 for ; Thu, 12 Jan 2017 13:45:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=x7W1Vet+t4i3VtPFA1LqDAxPwL1tfDIqv7Gkjzc1OPQ=; b=KJtPNlvP3Jm5Y8y8HT+rksu/QEuuifakrR8nH/NoOP9DLqamWQak7+yfyI0yjx+a1v JdzWQZXv6Xh+02S0Chj3TVLrz0S2AruRY+jWM4jAYM3b90rC7qLG3G865WXTQ3sIqM53 7/FOjjaLSoH/w3io4YzM3cFMABR36EezPwWS8+IMrIFwGvBNZSEdwXaOzPDgVKS8gD+7 CPnfiFGu16shMSVEJevw2JO3lPOX5Yq6zJEIOv5HoT0t/q+6lDZgLQdI/lqB8CzfmUGE Sok8YXFNI733o1g4R0Wm8vSQNO1AxpYZMVLkLpwZP4wIvaqtfTgCi5jcxG3JKro7or12 m7og== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=x7W1Vet+t4i3VtPFA1LqDAxPwL1tfDIqv7Gkjzc1OPQ=; b=fC8Xvz46gWlNO1JH2DlnxzqSV25r3edHRlTQDuxz1g6t1X4XEkTgR+0nRIhAG5GVBj 64/aEFMSTPUXJ7Iu65fqGmK6JVg9u790l7ilQyVYQBch72MN1Vb0lX/kjSL2iH3KF8d8 rEdjxgRRChBVk0dM7mFKrxxwGjY3W/uwqVfRvtxH17LccQCldOlKPjrgA15WLpc1WIDu y8JNZTFpHyVkGrCccmkq063xvP1RWiDpuJH2x+QM3KXdtXLGX2WjMqoaHZ19NnWuuJhL rG+F8elFoouReJx2pXs9A60Nv5GRBs9ui8WzafxcM7SZT65N+9USdNEH15Pi8KgRgvWS 3rQw== X-Gm-Message-State: AIkVDXIKJUo6JILP94yjQ0sRQtdaRgc8Ri7ECcc49WWD16l0F4OZXzrmZ6JvV4g5oNdiWwfw08e0HeK2fZCZvg== X-Received: by 10.200.40.45 with SMTP id 42mr14206849qtq.89.1484257558157; Thu, 12 Jan 2017 13:45:58 -0800 (PST) MIME-Version: 1.0 Received: by 10.12.175.11 with HTTP; Thu, 12 Jan 2017 13:45:57 -0800 (PST) From: Matt Joras Date: Thu, 12 Jan 2017 13:45:57 -0800 Message-ID: Subject: Fix dangling pointer left by ifmedia_removeall To: FreeBSD Net Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 12 Jan 2017 21:45:59 -0000 I thought I'd bring this review to people's attention: https://reviews.freebsd.org/D9164 The problem is fairly straightforward, as is the fix. ixgbe(4) uses ifmedia_removeall in a way that other drivers do not, which ends up leaving a dangling pointer in the ifmedia struct leading to incorrect information displayed by ifconfig(8). Matt From owner-freebsd-net@freebsd.org Thu Jan 12 23:08:21 2017 Return-Path: Delivered-To: freebsd-net@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 85890CAC098 for ; Thu, 12 Jan 2017 23:08:21 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from NAM01-BY2-obe.outbound.protection.outlook.com (mail-by2nam01on0063.outbound.protection.outlook.com [104.47.34.63]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT SSL SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2CD091454 for ; Thu, 12 Jan 2017 23:08:20 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM (10.165.218.133) by YTXPR01MB0191.CANPRD01.PROD.OUTLOOK.COM (10.165.218.135) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.845.12; Thu, 12 Jan 2017 23:08:17 +0000 Received: from YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM ([10.165.218.133]) by YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM ([10.165.218.133]) with mapi id 15.01.0845.014; Thu, 12 Jan 2017 23:08:18 +0000 From: Rick Macklem To: Slawa Olhovchenkov , Eugene Grosbein CC: Michael Sinatra , "freebsd-net@freebsd.org" Subject: Re: NFSv4 stuck Thread-Topic: NFSv4 stuck Thread-Index: AQHSbFpEjAFIf9ZbxU6pF+N5/AhAH6Ez3cvbgAAGMgCAAAXeAIAACF8AgABrMACAAHWnAIAApBHY Date: Thu, 12 Jan 2017 23:08:18 +0000 Message-ID: References: <20170111220818.GD30374@zxy.spb.ru> <20170111225922.GE30374@zxy.spb.ru> <20170111235020.GF30374@zxy.spb.ru> <58771EA6.1020104@grosbein.net>,<20170112131504.GG30374@zxy.spb.ru> In-Reply-To: <20170112131504.GG30374@zxy.spb.ru> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=rmacklem@uoguelph.ca; x-ms-office365-filtering-correlation-id: c55782d7-274e-4490-ede6-08d43b3fe54d x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:YTXPR01MB0191; x-microsoft-exchange-diagnostics: 1; YTXPR01MB0191; 7:Nfr9XMxJXveQS+ela3k1fyiUCVT8b6oBd+/9NIMIfnpkJc/Xobt9sIR7yV6OGXhD7Kmbl0J7AMYL8w0jovQAL+nB8GAMyxXimO+nNKNuUFZ+LKFQVu71liQ5xllAWKOw0JFsacDdIiP2gClFfZO5rAq5/6j0eCX9g8n4oPA9kwM+oyEX2JEIlpJMBsD5QLzmx9+rryHrhUwVMQpME/giRU8uoyr4W/q7FcnHSxsejg7QJBREih1OPP5x2EQJA/di8K61HZqz/QphDKrNGI7j5P5YpCGDbbOoMX/t6PzfBe20VnQ6cW9qouAbr/3zU8jwgGWtuhN55LPTc8bLsj0XbXKCivAWMdQYJBKXd5G4c8infEpq6sZ9cU+o+DO5zTKhCMIxE7cepDN14b5qvVgSiSwA9G+kB7kny760HlTP7jApQzWwEI9A1ysDDm5Tzn6BwrcENWUGvDbjeR8QSyJi3Q== x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(158342451672863)(278428928389397); x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040375)(2401047)(5005006)(8121501046)(10201501046)(3002001)(6041248)(20161123555025)(20161123560025)(20161123564025)(20161123562025)(6072148); SRVR:YTXPR01MB0191; BCL:0; PCL:0; RULEID:; SRVR:YTXPR01MB0191; x-forefront-prvs: 018577E36E x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(7916002)(39450400003)(189002)(24454002)(199003)(5660300001)(3660700001)(92566002)(97736004)(7116003)(3280700002)(106356001)(106116001)(102836003)(4326007)(189998001)(8936002)(74482002)(7696004)(5001770100001)(105586002)(2900100001)(2906002)(74316002)(55016002)(54906002)(68736007)(86362001)(93886004)(77096006)(305945005)(2950100002)(101416001)(8676002)(81156014)(81166006)(9686003)(33656002)(6506006)(6436002)(122556002)(76176999)(38730400001)(229853002)(50986999)(54356999); DIR:OUT; SFP:1101; SCL:1; SRVR:YTXPR01MB0191; H:YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; received-spf: None (protection.outlook.com: uoguelph.ca does not designate permitted sender hosts) spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: uoguelph.ca X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Jan 2017 23:08:18.0319 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: be62a12b-2cad-49a1-a5fa-85f4f3156a7d X-MS-Exchange-Transport-CrossTenantHeadersStamped: YTXPR01MB0191 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 12 Jan 2017 23:08:21 -0000 Slawa Olhovchenkov wrote: >On Thu, Jan 12, 2017 at 01:13:58PM +0700, Eugene Grosbein wrote: > >> 12.01.2017 6:50, Slawa Olhovchenkov =D0=C9=DB=C5=D4: >> > On Wed, Jan 11, 2017 at 03:20:22PM -0800, Michael Sinatra wrote: >> > >> >> On 01/11/17 14:59, Slawa Olhovchenkov wrote: >> >>> On Wed, Jan 11, 2017 at 10:39:42PM +0000, Rick Macklem wrote: >> >>> >> >>>> "umount -f" is your only chance. However, if there is already a non= -forced >> >>>> dismount stuck, it won't work because the non-forced dismount will = have >> >>>> the mounted-on vnode locked. >> >>> >> >>> I am use 'intr,soft' flags -- why ignored? >> >> >> >> intr and soft are considered dangerous with nfsv4. See the "BUGS" >> >> section of the mount_nfs(8) man page. >> > >> > Currently I am see dangerous w/o intr: system need reboot, application >> > don't killable. >> >> NFSv4 confiders "intr,soft" dangerous for data generated by poorly writt= en applications, not for a OS. > >What data? In may case no data. Certain NFSv4 operations (such as open and byte range locking) are strictly= ordered using a seqid#. If you fail an RPC in progress (via a soft timeout or intr via a si= gnal) then this seqid gets out of sync between client and server and your mount is badly broken. I do not believe this caused your hang though, since processes were sleepin= g on rpccon, which means they were trying to do a new TCP connection to the server unsuccessfu= lly. - Which normally indicates a problem with your underlying network fabric. stuff snipped... rick From owner-freebsd-net@freebsd.org Thu Jan 12 23:20:27 2017 Return-Path: Delivered-To: freebsd-net@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 47339CAC994 for ; Thu, 12 Jan 2017 23:20:27 +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 06D961C1D for ; Thu, 12 Jan 2017 23:20:27 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1cRofI-000EKH-Ux; Fri, 13 Jan 2017 02:20:16 +0300 Date: Fri, 13 Jan 2017 02:20:16 +0300 From: Slawa Olhovchenkov To: Rick Macklem Cc: Eugene Grosbein , Michael Sinatra , "freebsd-net@freebsd.org" Subject: Re: NFSv4 stuck Message-ID: <20170112232016.GM30374@zxy.spb.ru> References: <20170111220818.GD30374@zxy.spb.ru> <20170111225922.GE30374@zxy.spb.ru> <20170111235020.GF30374@zxy.spb.ru> <58771EA6.1020104@grosbein.net> <20170112131504.GG30374@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: 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: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 12 Jan 2017 23:20:27 -0000 On Thu, Jan 12, 2017 at 11:08:18PM +0000, Rick Macklem wrote: > Slawa Olhovchenkov wrote: > > >On Thu, Jan 12, 2017 at 01:13:58PM +0700, Eugene Grosbein wrote: > > > >> 12.01.2017 6:50, Slawa Olhovchenkov ÐÉÛÅÔ: > >> > On Wed, Jan 11, 2017 at 03:20:22PM -0800, Michael Sinatra wrote: > >> > > >> >> On 01/11/17 14:59, Slawa Olhovchenkov wrote: > >> >>> On Wed, Jan 11, 2017 at 10:39:42PM +0000, Rick Macklem wrote: > >> >>> > >> >>>> "umount -f" is your only chance. However, if there is already a non-forced > >> >>>> dismount stuck, it won't work because the non-forced dismount will have > >> >>>> the mounted-on vnode locked. > >> >>> > >> >>> I am use 'intr,soft' flags -- why ignored? > >> >> > >> >> intr and soft are considered dangerous with nfsv4. See the "BUGS" > >> >> section of the mount_nfs(8) man page. > >> > > >> > Currently I am see dangerous w/o intr: system need reboot, application > >> > don't killable. > >> > >> NFSv4 confiders "intr,soft" dangerous for data generated by poorly written applications, not for a OS. > > > >What data? In may case no data. > Certain NFSv4 operations (such as open and byte range locking) are strictly ordered using a > seqid#. If you fail an RPC in progress (via a soft timeout or intr via a signal) then this seqid gets > out of sync between client and server and your mount is badly broken. Mount can be droped? Automatic forced unmount? Or application can be manual killed for manual unmount? This is will be perfect for me. This is will be best that current behavior. > I do not believe this caused your hang though, since processes were sleeping on rpccon, which > means they were trying to do a new TCP connection to the server unsuccessfully. > - Which normally indicates a problem with your underlying network fabric. Network can fail always, at any time. This should not cause a blockage of the system. > stuff snipped... > > rick > From owner-freebsd-net@freebsd.org Fri Jan 13 10:22:23 2017 Return-Path: Delivered-To: freebsd-net@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 CAB7FCAD6C1; Fri, 13 Jan 2017 10:22:23 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: from mail-pf0-x243.google.com (mail-pf0-x243.google.com [IPv6:2607:f8b0:400e:c00::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 99F031FFE; Fri, 13 Jan 2017 10:22:23 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: by mail-pf0-x243.google.com with SMTP id b22so7830131pfd.3; Fri, 13 Jan 2017 02:22:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:subject:date:message-id:cc:to:mime-version; bh=BB2SwcYJOIYhak/FtbdOn+kdJMNuB3/ApFTDM8vnGGk=; b=d2HZk80lfFDjN3AicwQx/M4a86tTtWJSv1ZUOoJEfLcnbf/SKG4aDwGyCBuHo2WxVm lZLV9gFiKjCx+2FWoaF+rf1c/2LpwBaZYuDlYbFhgU9XdC29ODALkvMMeq0b3SbvGwi3 GawZiSzk6M2+okYpG/5F5g+fqmMHB7PslcJglu2UWCnu35N5lw+HS7w5IUmzwaHppygV fUAxfuBC9+tJOWv5BzgmVgIpvqHUL4kd921HYPZMd2eVoZaQAqNrauzy9sk1rUmYXa/v FP7hok9qpJWuGCtowZr7im2LkuEg1ztgC5sCHgy/m4vB2xHDUIBvpYIwmDk6sgekWQtp i/AA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:subject:date:message-id:cc:to:mime-version; bh=BB2SwcYJOIYhak/FtbdOn+kdJMNuB3/ApFTDM8vnGGk=; b=I9/FH88bkySBBB8kcV7Ko9HgaS4RcBrwDmC7EETWhxkEq/6Xa4suD/XG3YUmMTdSF8 bpiKTql9PzD1ArgApnXOAii1bkSVvPy4JPuNgRP5sgMgIdTx9/x/EdRjMIiUSJuCSEsY px8qHkGtMaSs1OKPs6Ls04pHeRtQssQ+h7yNRwA1yIaXVYdBDPGZAZooFXP5nj5RCMo5 pB4DPTHtHq7Ly0HQzgN4A/xuWIwfZ9w94QIbfWUugvmF+HQqt+hHdkG4nvWU+W0lta3D WIgxKarUcmATSU29ZmKJT57dVkEwURjlQrUI9DGzIVjkR3Vw1Iw17aj4wxsu43kSWU+z p5yQ== X-Gm-Message-State: AIkVDXLAONg/upmC0KmtJra/YuGYxXxxJdfcf+wY75dSdM4L4p1bjLY/ynmSePXxYeAnYg== X-Received: by 10.99.176.76 with SMTP id z12mr23252924pgo.158.1484302942982; Fri, 13 Jan 2017 02:22:22 -0800 (PST) Received: from pinklady.local (c-73-19-52-228.hsd1.wa.comcast.net. [73.19.52.228]) by smtp.gmail.com with ESMTPSA id l63sm28030951pfl.83.2017.01.13.02.22.21 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 13 Jan 2017 02:22:22 -0800 (PST) From: "Ngie Cooper (yaneurabeya)" X-Pgp-Agent: GPGMail Content-Type: multipart/signed; boundary="Apple-Mail=_B949EFCF-91DD-4FB3-8CE8-E1FFF90DB5E0"; protocol="application/pgp-signature"; micalg=pgp-sha512 Subject: powerpc.LINT* broken in netmap(4) Date: Fri, 13 Jan 2017 02:22:20 -0800 Message-Id: Cc: FreeBSD CURRENT , freebsd-powerpc@FreeBSD.org, Luigi Rizzo To: freebsd-net@FreeBSD.org Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jan 2017 10:22:23 -0000 --Apple-Mail=_B949EFCF-91DD-4FB3-8CE8-E1FFF90DB5E0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hi, I spotted these compilation errors on universe12a.freebsd.org = for both powerpc.LINT and powerpc.LINT64: cc1: warnings being treated as errors /scratch/tmp/ngie/svn/sys/dev/netmap/netmap_generic.c: In function = 'generic_set_tx_event': /scratch/tmp/ngie/svn/sys/dev/netmap/netmap_generic.c:765: warning: the = address of 'generic_mbuf_destructor' will always evaluate as 'true' = [-Waddress] --- netmap_generic.o --- *** [netmap_generic.o] Error code 1 I haven=E2=80=99t yet dug into why this only surfaces on = powerpc, yet=E2=80=A6 Thanks, -Ngie --Apple-Mail=_B949EFCF-91DD-4FB3-8CE8-E1FFF90DB5E0 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJYeKpcAAoJEPWDqSZpMIYVpjEQAKciJGGd2iDNM4s5CNQaaaZt WQMG2gX1fmuluRSWIn1wdgayj7G1lUVEN0vthYJZF+eHYp+8Q4ev/mqFEuX69UFn 9ADtxHdOnbM591HRXMRTPxCOzeMUpbZR2PX0Gk/m+WCc/Zo7gmuN+1YMV1UXl4Od 6onN9D7Trbl7PEB1tDs1g4BfsiccbEekOyTurntE4Ixo39jUfRynM3pvZaEytyr+ HLwyEIVMeAp1vQRj7dHzPsEcjwvU6k3DxpCMPzl0/JEa3Ay1KYUoNlczKs8I2n39 CYjUWmShyBlE530ls7dXDFgejIPNqk6ThpkqPegfZJcHGRzjGUrhiMHXheewvAFr jWXSAimHnP4obMxsLnBpL9msbg6VrUC/CarvQUdaTKc5qrWgCTGxDZLwMb0SC65e YJS+eOH31ePrk0I2Yxl1OdR9Zgx/pC0iAUa045yOOsWtJ/1eR0aAz/o/Ft9I0MEh THwFawLsQTgY8x6YBddxFCRPhEOxML2CwrVOkTbBaZR2CGrs2fU26ii7eKCS4LUo RMd6rqwmoAsOa9BjRV5n4VrQDZOHl+IVG7JvmeC4VocCS17+imer0tXhyn+uVfcr 1u7TaI88+XHzB+YpQ1lYWK5MTLSwQVE9tf+IQHOgSGBR6uIFoWtB7BNzQtWiK69b VnV9/xPu0yc5EUzuKk0j =G382 -----END PGP SIGNATURE----- --Apple-Mail=_B949EFCF-91DD-4FB3-8CE8-E1FFF90DB5E0-- From owner-freebsd-net@freebsd.org Fri Jan 13 10:46:28 2017 Return-Path: Delivered-To: freebsd-net@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 9F219CAC4B0; Fri, 13 Jan 2017 10:46:28 +0000 (UTC) (envelope-from v.maffione@gmail.com) Received: from mail-oi0-x241.google.com (mail-oi0-x241.google.com [IPv6:2607:f8b0:4003:c06::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 60F351286; Fri, 13 Jan 2017 10:46:28 +0000 (UTC) (envelope-from v.maffione@gmail.com) Received: by mail-oi0-x241.google.com with SMTP id j15so6353183oih.0; Fri, 13 Jan 2017 02:46:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=CKCgPaMpvPjuihq4SbZxBPn/gb78dk+rbH4DYPY70t8=; b=ecteEl8TxgR063WtQ8ZXsHwCS108tIWwsyDzALJ7moz4yoB+OM8sOFJpkUJMlkpH5F UXBBS9CVkuUnahW8DnQfLfs+0Sf1PJOlY6zARGCTXgYgVib+9rfzwUoRMmLH483L2LTe MNrimSVNIhkbVKIzR8V8OWHAj3WCn4StbyTdw3VSRWH7ntS+W5Lnpb6m/7jDmTJpkA7X sJM4AiHCySYL5vkDmIzFaADjJnVmH9O1HHt96QkWbyi7VDf6gYfvXfBP3PHhV9jF74rI QoHbn97Ap53AMCT6F4hI/7u8qvWdB+qeUj3QZvl41bwXjvD8UP4+rYF7gh52ttDY+eJY eWAQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=CKCgPaMpvPjuihq4SbZxBPn/gb78dk+rbH4DYPY70t8=; b=Cqsvkem/RwwDHePqoCyVgoGcXES0mzyOJ+ara1DaS/+pQSEgJs7LSfabIvTM545bdh FEOB9kzhCfEHNXCJROvevtMOEC8nCXtaCyYeTn2ZV7PL7Uu9zptnGGI36p58p/V1zKC1 bVOYxscxA8rwSHe1P1lqgGcoKxK1jOBQjwZQy/jrPqe1Y6pdX1ecco+LKqJ66eWCAalQ ESSe9MPDzhHoRBJaKN812+2ENCxbB8c7Be/V1CpF/QWZ0SjD/6MwEAVoE8PQI0UHto4O 3hOu1E1XoLqhrX0F9yCZ747xt9al9Ja6aQo4+Rz/EXcWWMAVCpyHqwzRQGjdCmmfquWZ 92NQ== X-Gm-Message-State: AIkVDXLiXzSl4wTTFtMdRrBMKzJWfodvcTCuvDzYje5Y7cl3S8TfXlw8/kUgD7q7QJZZN9j9MQzmFuP7mJB9yA== X-Received: by 10.202.213.17 with SMTP id m17mr9706157oig.104.1484304387641; Fri, 13 Jan 2017 02:46:27 -0800 (PST) MIME-Version: 1.0 Received: by 10.157.6.166 with HTTP; Fri, 13 Jan 2017 02:46:27 -0800 (PST) In-Reply-To: References: From: Vincenzo Maffione Date: Fri, 13 Jan 2017 11:46:27 +0100 Message-ID: Subject: Re: powerpc.LINT* broken in netmap(4) To: "Ngie Cooper (yaneurabeya)" Cc: "freebsd-net@freebsd.org" , freebsd-powerpc@freebsd.org, FreeBSD CURRENT , Luigi Rizzo Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jan 2017 10:46:28 -0000 Hi, Thanks for reporting. The warning is innocuous, but I'm not sure how to silence it. Maybe diff --git a/sys/dev/netmap/netmap_generic.c b/sys/dev/netmap/netmap_generic.c index cb1cff1f0e7..226a0864fd0 100644 --- a/sys/dev/netmap/netmap_generic.c +++ b/sys/dev/netmap/netmap_generic.c @@ -168,7 +168,7 @@ nm_os_get_mbuf(struct ifnet *ifp, int len) static void void_mbuf_dtor(struct mbuf *m, void *arg1, void *arg2) { } #define SET_MBUF_DESTRUCTOR(m, fn) do { \ - (m)->m_ext.ext_free =3D fn ? (void *)fn : (void *)void_mbuf_dtor; \ + (m)->m_ext.ext_free =3D (fn !=3D NULL) ? (void *)fn : (void *)void_mbuf_dtor; \ } while (0) static inline struct mbuf * or we could turn SET_MBUF_DESTRUCTOR into a real function. Cheers, VIncenzo 2017-01-13 11:22 GMT+01:00 Ngie Cooper (yaneurabeya) : > Hi, > I spotted these compilation errors on universe12a.freebsd.org for > both powerpc.LINT and powerpc.LINT64: > > cc1: warnings being treated as errors > /scratch/tmp/ngie/svn/sys/dev/netmap/netmap_generic.c: In function > 'generic_set_tx_event': > /scratch/tmp/ngie/svn/sys/dev/netmap/netmap_generic.c:765: warning: the > address of 'generic_mbuf_destructor' will always evaluate as 'true' > [-Waddress] > --- netmap_generic.o --- > *** [netmap_generic.o] Error code 1 > > I haven=E2=80=99t yet dug into why this only surfaces on powerpc,= yet=E2=80=A6 > Thanks, > -Ngie > --=20 Vincenzo Maffione From owner-freebsd-net@freebsd.org Fri Jan 13 15:23:42 2017 Return-Path: Delivered-To: freebsd-net@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 9D249CAEBBE; Fri, 13 Jan 2017 15:23:42 +0000 (UTC) (envelope-from shuriku@shurik.kiev.ua) Received: from graal.it-profi.org.ua (graal.shurik.kiev.ua [193.239.74.7]) (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 CBB471597; Fri, 13 Jan 2017 15:23:41 +0000 (UTC) (envelope-from shuriku@shurik.kiev.ua) Received: from mail.lissoft.com.ua ([109.237.91.29] helo=thinkpad.it-profi.org.ua) by graal.it-profi.org.ua with esmtpa (Exim 4.87 (FreeBSD)) (envelope-from ) id 1cS3hT-000EDg-SQ; Fri, 13 Jan 2017 17:23:31 +0200 Subject: Re: [RFC/RFT] projects/ipsec To: "Andrey V. Elsukov" , freebsd-current@FreeBSD.org, freebsd-net@FreeBSD.org References: <2bd32791-944f-2417-41e9-e0fe1c705502@FreeBSD.org> From: Alexandr Krivulya Message-ID: Date: Fri, 13 Jan 2017 17:23:26 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: <2bd32791-944f-2417-41e9-e0fe1c705502@FreeBSD.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-SA-Exim-Connect-IP: 109.237.91.29 X-SA-Exim-Mail-From: shuriku@shurik.kiev.ua X-SA-Exim-Scanned: No (on graal.it-profi.org.ua); SAEximRunCond expanded to false X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jan 2017 15:23:42 -0000 11.12.2016 01:07, Andrey V. Elsukov пишет: > Hi All, > > I am pleased to announce that projects/ipsec, that I started several > months ago is ready for testing and review. > The main goals were: > * rework locking to make IPsec code more friendly for concurrent > processing; > * make lookup in SADB/SPDB faster; > * revise PFKEY implementation, remove stale code, make it closer > to RFC; > * implement IPsec VTI (virtual tunneling interface); > * make IPsec code loadable as kernel module. > > Currently all, except the last one is mostly done. So, I decided ask for > a help to test the what already done, while I will work on the last task. > > How to try? There are no patches, you need to checkout the full > projects/ipsec source tree, and build the kernel and the base system. > There are very few changes in the base system, mostly the kernel > changes. Thus for testing that old configuration is still work, it is > enough to build only the kernel. > > The approximate list of changes that may be visible to users: > * SA bundles now can have only 4 items in the chain. I think it is > enough, I can't imagine configurations when needed more. Also now SA > bundles supported for IPv6 too. > * due to changes in SPDB/SADB, systems where large number of SPs and SAs > are in use should get significant performance benefits. > * the memory consumption should slightly increase. There are several > hash tables and SP cache appeared. > * INPCB SP cache should noticeable increase network performance of > application when security policies are presence. > https://lists.freebsd.org/pipermail/freebsd-net/2015-April/042121.html > * use transport mode IPsec for forwarded IPv4 packets now unsupported. > This matches the IPv6 behavior, and since we can handle the replies, I > think it is useless. > * Added net.inet.ipsec.check_policy_history sysctl variable. When it is > set, each inbound packet that was handled by IPsec will be checked > according to matching security policy. If not all IPsec transforms were > applied, the check will fail, and packet will be dropped. > * Many PF_KEY messages handlers was updated, probably some IKEd now may > fail due to stricter checks. > * SPI now unique for each SA. This also can break something. > * Added if_ipsec interface. For more info look at > https://svnweb.freebsd.org/base?view=revision&revision=309115 > https://reviews.freebsd.org/P112 > * TCP_SIGNATURE code was reworked and now it behaves closer to RFC > https://svnweb.freebsd.org/base?view=revision&revision=309610 > * NAT-T support was reworked. > https://svnweb.freebsd.org/base?view=revision&revision=309808 > Also I made the patch to racoon that adds better support of NAT-T, > you can use this port to build patched racoon: > https://people.freebsd.org/~ae/ipsec-tools.tgz > > What results is interesting to me? > If you have some nontrivial configuration, please test. > If you have some configuration, that did't work, please test this branch. > If you have performance problems, please test. But don't forget that > this is head/ branch, you need to disable all debugging first. > If you just want to test, pay attention to the output of > `vmstat -m | egrep "sec|sah|pol|crypt"`. > If you have used TCP_SIGNATURE, IPSEC_NAT_T options, please test, this > support was significantly changed. > > PS. I just updated the branch to last head/, and it was not tested, sorry :) > Hi, nothing unusual, all works fine. Strangswan in tunnel mode on current: root@thinkpad:/home/shurik # ipsec status Security Associations (1 up, 0 connecting): ikev2-client[1]: ESTABLISHED 3 minutes ago, 10.1.1.183[xxx.xxxx.org.ua]...xxx.yyy.74.7[xxx.xxxx.org.ua] ikev2-client{1}: INSTALLED, TUNNEL, reqid 1, ESP in UDP SPIs: c6f68157_i c6d17c85_o ikev2-client{1}: 10.10.10.2/32 === 0.0.0.0/0 -- From owner-freebsd-net@freebsd.org Fri Jan 13 22:27:55 2017 Return-Path: Delivered-To: freebsd-net@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 2E986CAEC92; Fri, 13 Jan 2017 22:27:55 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: from mail-pf0-x241.google.com (mail-pf0-x241.google.com [IPv6:2607:f8b0:400e:c00::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EDDA41E93; Fri, 13 Jan 2017 22:27:54 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: by mail-pf0-x241.google.com with SMTP id y143so10033940pfb.1; Fri, 13 Jan 2017 14:27:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:mime-version:from:in-reply-to:date:cc:message-id:references :to; bh=xSH0RWQ0Sc5pYUS471PVPmWO761Qjyq9ND9fXOyzgHc=; b=cpoeN0s3FQd0jii2PoZvChtw97kCVjN60A/LE1Ib7lo6sC/EvegWILBldsTR++J5F8 entDwPY/xZHKj0oJeenuEUDoP+MuNBOZSjz2vsmq7D3/wSf8c6KQisHK/2JmDvkS/+jU x3RMyQF0yGpTRSBJGlJD0CbYWVLfrXvVUBKSyCFg4MV816GHjQZkPHDnFql7gE/T0eqE hKZ9j3dX2WbkQnOue66y4xYuR7kWTQl9VJdtmbrAd4lhZ3WjY5UetxQKo4j6RvzkMf/F +W/uUpdiEgRE7hXuA8QSOU1qDvQwkw+ZjTU7AKUjAzAsoZF7QwSD62EFzokuGkgZ8wYA GM5A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:mime-version:from:in-reply-to:date:cc :message-id:references:to; bh=xSH0RWQ0Sc5pYUS471PVPmWO761Qjyq9ND9fXOyzgHc=; b=udCQW0hvZ6dOkY12Q4Ufuwk4/AzdK7jAxSDyvoVHTt9Hy7hEFAq41YfwBBoNOV+mXS icTNuJZ6pFVQ8+22DCvieXSEYvkN27tOVIgU5DbUK4ORQDcWB9FWdSWCkuNTUCXIuo4Q 0tjpeZCg83PC2WJhzm+t0fnhJElSruDqeV7edyVwSXXPLegUvpRMqN0lmmNStQLdNBdr Kai1Z6iylIBleihqbQSavzxXjSAvGza7AbfWSfENoXi1FkkhmkpbYZbFKJuFaXyPt1b/ fiJF/i621aXw7jveZLCrJ4WRLRDS03PMspWF2lzvG1YPzVE11jHu68/3BqQACasn5YGB 5NAw== X-Gm-Message-State: AIkVDXI/FhOg1vlyx6bMM/4nYzAHqW2mdby/cLEhZjdWICpuUan3TJkvaADiVGEmTyIPpg== X-Received: by 10.84.233.193 with SMTP id m1mr32897862pln.126.1484346474334; Fri, 13 Jan 2017 14:27:54 -0800 (PST) Received: from pinklady.local (c-73-19-52-228.hsd1.wa.comcast.net. [73.19.52.228]) by smtp.gmail.com with ESMTPSA id x8sm31655517pge.15.2017.01.13.14.27.53 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 13 Jan 2017 14:27:53 -0800 (PST) Subject: Re: powerpc.LINT* broken in netmap(4) Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Content-Type: multipart/signed; boundary="Apple-Mail=_37801E61-DF34-4A8A-ACD3-5B34951F261D"; protocol="application/pgp-signature"; micalg=pgp-sha512 X-Pgp-Agent: GPGMail From: "Ngie Cooper (yaneurabeya)" In-Reply-To: Date: Fri, 13 Jan 2017 14:27:52 -0800 Cc: FreeBSD CURRENT , Luigi Rizzo Message-Id: <49F36EE5-D3BD-420A-9F16-2219C7C83AC8@gmail.com> References: To: freebsd-net@FreeBSD.org X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jan 2017 22:27:55 -0000 --Apple-Mail=_37801E61-DF34-4A8A-ACD3-5B34951F261D Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On Jan 13, 2017, at 02:22, Ngie Cooper (yaneurabeya) = wrote: >=20 > Hi, > I spotted these compilation errors on universe12a.freebsd.org = for both powerpc.LINT and powerpc.LINT64: >=20 > cc1: warnings being treated as errors > /scratch/tmp/ngie/svn/sys/dev/netmap/netmap_generic.c: In function = 'generic_set_tx_event': > /scratch/tmp/ngie/svn/sys/dev/netmap/netmap_generic.c:765: warning: = the address of 'generic_mbuf_destructor' will always evaluate as 'true' = [-Waddress] > --- netmap_generic.o --- > *** [netmap_generic.o] Error code 1 >=20 > I haven=E2=80=99t yet dug into why this only surfaces on = powerpc, yet=E2=80=A6 (CC -powerpc; BCC +powerpc) Hi, sparc64 has the same issue as powerpc*, so I suspect that gcc is = flagging this as an issue. Thanks, -Ngie PS. Sidenote: why was the SET_MBUF_DESTRUCTOR macro added, but not used = in nm_os_get_mbuf ? --Apple-Mail=_37801E61-DF34-4A8A-ACD3-5B34951F261D Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJYeVRoAAoJEPWDqSZpMIYVzf0QAMZ0TfNkcUpB+9Lksy3BNTSO tZZnO3gI8VpZ+XIBf/tlaoW7sKkwzVtficd1kvqz8iy4HCfapYU5Mf9BjowrQzY+ kPpUE+kckOwIYjS5AkQQHeEHKsr4F99O9Orj7DZBBWP4+9yeqDl48tnNw0N82zFF 4F3FDs9I/tFLyXNOX6K1gs4cJfUah1PwktFFIAXLXpAiqHx+TyxEgGFn0TJKmsVD TcKpW50MNFlc2lJzxKZeVVXCt2GwdjeautkKX+qVt+kbno4J+uJN0lTsJPBp25Tg M3rmgK8bBl7DL0DfreTwsVyQP4Czy9L0FwKkS8AkjPjLa0PZXDUsHJaeR9ITaAFD Tyyh44oIxcTashT20Yp590A0E0EOhuIkt18aEOAKgVuS8KKLl0GnsNsdxv1BtfSD 5H/PSjV7RdfijrzuDH9ChAs/7Z4GeL9MsBQIoNGz3lZ6dRRYq+b5WyPLTsf/ldpI mLm1bNyMuxPoYO+U7lYfK98qQS5fHKn6pO9vzdP4qu6qRfgx19VzfAC3hvzFNPrr tDeF13L8t5J5549rIXVyMEEUvSCQFiDqhwNrN5LIZBVzY3YP23tKM4WqaufAwLTC VctYhfTOCYxv74euyH39iGhW+4ohBtteJ6cV4QVf9DGFZ0+r3jR66vCbB10hBqRW 3845E6ngPZ0o1aGJbpck =8BD3 -----END PGP SIGNATURE----- --Apple-Mail=_37801E61-DF34-4A8A-ACD3-5B34951F261D-- From owner-freebsd-net@freebsd.org Fri Jan 13 23:02:25 2017 Return-Path: Delivered-To: freebsd-net@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 8598FCAE530 for ; Fri, 13 Jan 2017 23:02:25 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from NAM03-BY2-obe.outbound.protection.outlook.com (mail-by2nam03on0058.outbound.protection.outlook.com [104.47.42.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT SSL SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3BBE41361 for ; Fri, 13 Jan 2017 23:02:24 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM (10.165.218.133) by YTXPR01MB0190.CANPRD01.PROD.OUTLOOK.COM (10.165.218.134) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.845.12; Fri, 13 Jan 2017 23:02:22 +0000 Received: from YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM ([10.165.218.133]) by YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM ([10.165.218.133]) with mapi id 15.01.0845.014; Fri, 13 Jan 2017 23:02:22 +0000 From: Rick Macklem To: Slawa Olhovchenkov CC: Eugene Grosbein , Michael Sinatra , "freebsd-net@freebsd.org" Subject: Re: NFSv4 stuck Thread-Topic: NFSv4 stuck Thread-Index: AQHSbFpEjAFIf9ZbxU6pF+N5/AhAH6Ez3cvbgAAGMgCAAAXeAIAACF8AgABrMACAAHWnAIAApBHYgAAFBgCAAYnXdQ== Date: Fri, 13 Jan 2017 23:02:22 +0000 Message-ID: References: <20170111220818.GD30374@zxy.spb.ru> <20170111225922.GE30374@zxy.spb.ru> <20170111235020.GF30374@zxy.spb.ru> <58771EA6.1020104@grosbein.net> <20170112131504.GG30374@zxy.spb.ru> , <20170112232016.GM30374@zxy.spb.ru> In-Reply-To: <20170112232016.GM30374@zxy.spb.ru> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=rmacklem@uoguelph.ca; x-ms-office365-filtering-correlation-id: e7b964a0-0075-43a7-0dc0-08d43c083bc8 x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:YTXPR01MB0190; x-microsoft-exchange-diagnostics: 1; YTXPR01MB0190; 7:lKga5oZ2rLvLJdIZIIQyzFYWei2UmQmXk00FutVX5e2aPKU0k+32R1onFjnktU0T4XWcb3M9txNNi4/SZTYmS4S3YIPlYbo5P1LPFYiB7A4+/2lBfrKurj+JiFYcsbca3mxgJE7MpkIv80IBc7dGFsshPo9WnAwqFNP1mCeue2k/K4FTvlviKLb5XRR1Blr4M2IYIvQdsIXh7VYOUmKwBDv1A4CI5rdADQ9JKWtL3Eh0DfNZ3E+FZP1m5al/qAcP945iAWhzDlxcfop2jh4XtY1cJexXZujUItgqCaPXqhlApIuhNDuqMcDTjnmcUSvfNrrHO93hOohlQb+hrvyZkLiYzd9pwUdeIZM4vMHGOHH9hFdk1PQdA2zkIbq90VLKg0vcA1iI3YEyUG7I3BdlRaGT/+eiCRWFmP8YoSw6hZykv5hc0Z8eAh6f6pkVb/ckFV9N1s1OhUrEGUfd7UBDCA== x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(158342451672863); x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040375)(2401047)(5005006)(8121501046)(3002001)(10201501046)(6041248)(20161123562025)(20161123555025)(20161123564025)(20161123560025)(6072148); SRVR:YTXPR01MB0190; BCL:0; PCL:0; RULEID:; SRVR:YTXPR01MB0190; x-forefront-prvs: 018632C080 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(7916002)(39450400003)(199003)(24454002)(189002)(76176999)(50986999)(54356999)(55016002)(3280700002)(54906002)(102836003)(86362001)(122556002)(101416001)(2900100001)(27001)(74482002)(6916009)(189998001)(7116003)(33656002)(2950100002)(92566002)(5660300001)(110136003)(97736004)(9686003)(7696004)(229853002)(77096006)(6506006)(93886004)(6436002)(38730400001)(81166006)(74316002)(105586002)(106116001)(2906002)(305945005)(8676002)(106356001)(8936002)(3660700001)(81156014)(4326007)(68736007); DIR:OUT; SFP:1101; SCL:1; SRVR:YTXPR01MB0190; H:YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; received-spf: None (protection.outlook.com: uoguelph.ca does not designate permitted sender hosts) spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: uoguelph.ca X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Jan 2017 23:02:22.4532 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: be62a12b-2cad-49a1-a5fa-85f4f3156a7d X-MS-Exchange-Transport-CrossTenantHeadersStamped: YTXPR01MB0190 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jan 2017 23:02:25 -0000 Slawa Olhovchenkov wrote: [stuff snipped] >> > >> >What data? In may case no data. You have a file system with no files in it. (It is file data I am referring= to.) Admittedly a read-only file system won't get corrupted, but you will still = have trouble reading files, since NFSv4 require that they be Open'd before reading. >> Certain NFSv4 operations (such as open and byte range locking) are stric= tly ordered using a >> seqid#. If you fail an RPC in progress (via a soft timeout or intr via a= signal) then this seqid gets >> out of sync between client and server and your mount is badly broken. > >Mount can be droped? Automatic forced unmount? >Or application can be manual killed for manual unmount? >This is will be perfect for me. This is will be best that current behavior= . Well, since recently written data could be lost, I can't see this ever bein= g automatic. The manual "umount -f " should work, but only if a "umount " has not already been done. (The latter gets stuck in the kernel, usually after = locking the mounted-on vnode and that blocks the subsequent "umount -f ". Someday, I plan on adding a new option to "umount" that goes directly to NF= S (via the nfssvc(2) syscall) to force a dismount, but I haven't gotten around to doing it. Until then, it's "umount -f" or reboot. And please don't use "soft,intr" op= tions, they won't usually help and will break the mount for opening files sooner or later. > >> I do not believe this caused your hang though, since processes were slee= ping on rpccon, which >> means they were trying to do a new TCP connection to the server unsucces= sfully. >> - Which normally indicates a problem with your underlying network fabric= . > >Network can fail always, at any time. >This should not cause a blockage of the system. Would you expect a local filesystem to keep working when the JBOD interface= to a drive is broken. For NFS, a broken network means "can't talk to the file system" just like a= broken JBOD to a file system's drive would mean this. For NFS to work well, you want the most reliable network fabric possible. One the network is fixed, it should again be possible for the mount to work= . (The processes in "rpccon" are trying to create a new TCP connection and wh= en they succeed the mount point should again start working.) rick From owner-freebsd-net@freebsd.org Fri Jan 13 23:39:27 2017 Return-Path: Delivered-To: freebsd-net@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 5D6FCCAE417 for ; Fri, 13 Jan 2017 23:39:27 +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 1B16E1059 for ; Fri, 13 Jan 2017 23:39:27 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1cSBR8-0006ye-EJ; Sat, 14 Jan 2017 02:39:10 +0300 Date: Sat, 14 Jan 2017 02:39:10 +0300 From: Slawa Olhovchenkov To: Rick Macklem Cc: Eugene Grosbein , Michael Sinatra , "freebsd-net@freebsd.org" Subject: Re: NFSv4 stuck Message-ID: <20170113233910.GQ30374@zxy.spb.ru> References: <20170111220818.GD30374@zxy.spb.ru> <20170111225922.GE30374@zxy.spb.ru> <20170111235020.GF30374@zxy.spb.ru> <58771EA6.1020104@grosbein.net> <20170112131504.GG30374@zxy.spb.ru> <20170112232016.GM30374@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jan 2017 23:39:27 -0000 On Fri, Jan 13, 2017 at 11:02:22PM +0000, Rick Macklem wrote: > Slawa Olhovchenkov wrote: > [stuff snipped] > >> > > >> >What data? In may case no data. > You have a file system with no files in it. (It is file data I am referring to.) > Admittedly a read-only file system won't get corrupted, but you will still have trouble > reading files, since NFSv4 require that they be Open'd before > reading. No problem if application can be interruptible and fs can be unmount. (in ideal, disk io also must be interruptible. but posix and k&r...) > >> Certain NFSv4 operations (such as open and byte range locking) are strictly ordered using a > >> seqid#. If you fail an RPC in progress (via a soft timeout or intr via a signal) then this seqid gets > >> out of sync between client and server and your mount is badly broken. > > > >Mount can be droped? Automatic forced unmount? > >Or application can be manual killed for manual unmount? > >This is will be perfect for me. This is will be best that current behavior. > Well, since recently written data could be lost, I can't see this ever being automatic. Data lost in any cases. > The manual "umount -f " should work, but only if a "umount " has > not already been done. (The latter gets stuck in the kernel, usually after locking the mounted-on I think "umount " may be called by autoumountd: in other cases "umount -f " also don't work. > vnode and that blocks the subsequent "umount -f ". > > Someday, I plan on adding a new option to "umount" that goes directly to NFS (via the nfssvc(2) > syscall) to force a dismount, but I haven't gotten around to doing it. > > Until then, it's "umount -f" or reboot. reboot also don't work. only power reset. this is sadly > And please don't use "soft,intr" options, they won't usually > help and will break the mount for opening files sooner or later. Break files is better locked system. For NSFv3 this is help and allow to kill apllication and do recover. > >> I do not believe this caused your hang though, since processes were sleeping on rpccon, which > >> means they were trying to do a new TCP connection to the server unsuccessfully. > >> - Which normally indicates a problem with your underlying network fabric. > > > >Network can fail always, at any time. > >This should not cause a blockage of the system. > Would you expect a local filesystem to keep working when the JBOD interface to a drive is broken. > For NFS, a broken network means "can't talk to the file system" just like a broken JBOD to a file > system's drive would mean this. broken JBOD now don't cause kernel panic. In RT11 broken JBOD don't cause any problem and RT11 allow application to cancel disk IO. > For NFS to work well, you want the most reliable network fabric > possible. Any relaible network can be failed. > One the network is fixed, it should again be possible for the mount to work. > (The processes in "rpccon" are trying to create a new TCP connection and when they succeed > the mount point should again start working.) Hm. This is may be missundertanding. Ay time of try unmount/interrapt/etc network will be stable and no issuses. Issuses may be in past, and after this NFS go to stuck. (or, may be no issuses. I am not sure) And no way to recover. From owner-freebsd-net@freebsd.org Fri Jan 13 23:47:49 2017 Return-Path: Delivered-To: freebsd-net@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 50DEBCAE90B for ; Fri, 13 Jan 2017 23:47:49 +0000 (UTC) (envelope-from rcarter@pinyon.org) Received: from h2.pinyon.org (h2.pinyon.org [65.101.20.170]) (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 1DFB31A6D for ; Fri, 13 Jan 2017 23:47:48 +0000 (UTC) (envelope-from rcarter@pinyon.org) Received: by h2.pinyon.org (Postfix, from userid 58) id 862DE128FE; Fri, 13 Jan 2017 16:47:42 -0700 (MST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=pinyon.org; s=DKIM; t=1484351262; bh=+tXSYfqCWp8DN+GAlOvAzgvUXSRdfiXVj7fT17axNoU=; h=Subject:To:References:From:Date:In-Reply-To; b=dfGb6wR2hLmq5Ur8z5knmudN/bbD6xSxtHAhqPc3xsVZA3qxxRv25zx/v7ujFZ0b/ mZkc9KJ1W+1tRg8QzIfd+zi1K9vZeMNyjo2Pfp5zeastkoYwC+7a1tRw4pBzT/lUgh U1v/POVxrqEAhorIKQm9LnJFmbgA1nHnVBrrgr74= X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on h2.pinyon.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED shortcircuit=no autolearn=ham autolearn_force=no version=3.4.1 Received: from [10.0.10.15] (h1.pinyon.org [65.101.20.169]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by h2.pinyon.org (Postfix) with ESMTPSA id AFB77128EF for ; Fri, 13 Jan 2017 16:47:41 -0700 (MST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=pinyon.org; s=DKIM; t=1484351261; bh=+tXSYfqCWp8DN+GAlOvAzgvUXSRdfiXVj7fT17axNoU=; h=Subject:To:References:From:Date:In-Reply-To; b=lb4Amf46c1rrDRE6X/0foKzNpNcnSf/g6PXCV/tF4mpkHqD0QvOZHJa2BLE/0Lk7c lGo4PBx2ktEKgojVmQshj5QTJahTC3zJx+hc6pj5J076L+5UMtb8mlokZGhSI9OUhG eeAYVeQ971d+zld0qV8IfUb6+waoD+wg0UuRyoO4= Subject: Re: NFSv4 stuck To: freebsd-net@freebsd.org References: <20170111220818.GD30374@zxy.spb.ru> <20170111225922.GE30374@zxy.spb.ru> <20170111235020.GF30374@zxy.spb.ru> <58771EA6.1020104@grosbein.net> <20170112131504.GG30374@zxy.spb.ru> From: "Russell L. Carter" Message-ID: <44a7df9c-b1a3-1191-05af-d73235bdf15a@pinyon.org> Date: Fri, 13 Jan 2017 16:47:41 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=koi8-r; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jan 2017 23:47:49 -0000 On 01/12/17 16:08, Rick Macklem wrote: > Slawa Olhovchenkov wrote: > >> On Thu, Jan 12, 2017 at 01:13:58PM +0700, Eugene Grosbein wrote: >> >>> 12.01.2017 6:50, Slawa Olhovchenkov ÐÉÛÅÔ: >>>> On Wed, Jan 11, 2017 at 03:20:22PM -0800, Michael Sinatra wrote: >>>> >>>>> On 01/11/17 14:59, Slawa Olhovchenkov wrote: >>>>>> On Wed, Jan 11, 2017 at 10:39:42PM +0000, Rick Macklem wrote: >>>>>> >>>>>>> "umount -f" is your only chance. However, if there is already a non-forced >>>>>>> dismount stuck, it won't work because the non-forced dismount will have >>>>>>> the mounted-on vnode locked. >>>>>> >>>>>> I am use 'intr,soft' flags -- why ignored? >>>>> >>>>> intr and soft are considered dangerous with nfsv4. See the "BUGS" >>>>> section of the mount_nfs(8) man page. >>>> >>>> Currently I am see dangerous w/o intr: system need reboot, application >>>> don't killable. >>> >>> NFSv4 confiders "intr,soft" dangerous for data generated by poorly written applications, not for a OS. >> >> What data? In may case no data. > Certain NFSv4 operations (such as open and byte range locking) are strictly ordered using a > seqid#. If you fail an RPC in progress (via a soft timeout or intr via a signal) then this seqid gets > out of sync between client and server and your mount is badly broken. > > I do not believe this caused your hang though, since processes were sleeping on rpccon, which > means they were trying to do a new TCP connection to the server unsuccessfully. > - Which normally indicates a problem with your underlying network fabric. > stuff snipped... FWIW I see this hang too, requiring a hard reset of the power to get the server to reboot. I learned the hard way about umount -f. Modestly annoying when you reboot the package server and then forget to umount -f && mount package server, and *then* do 'pkg install some-package' My linux clients don't have this problem. This is on 11/stable Russell > rick > > _______________________________________________ > freebsd-net@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > From owner-freebsd-net@freebsd.org Sat Jan 14 10:44:35 2017 Return-Path: Delivered-To: freebsd-net@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 BE678CA7BAD for ; Sat, 14 Jan 2017 10:44:35 +0000 (UTC) (envelope-from v.maffione@gmail.com) Received: from mail-ot0-x232.google.com (mail-ot0-x232.google.com [IPv6:2607:f8b0:4003:c0f::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8245A1ED2 for ; Sat, 14 Jan 2017 10:44:35 +0000 (UTC) (envelope-from v.maffione@gmail.com) Received: by mail-ot0-x232.google.com with SMTP id 104so17255542otd.3 for ; Sat, 14 Jan 2017 02:44:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=iiGF5v84NYO7bfihe5lKD3KgxcpAe/cVDxz7dY26HIg=; b=j2atgVmpZmEIb7bFsEHO8D3ecPGSQh44r1GIRR3dmrMfVpt/CoApua2fgvTjuJLSQf Uay9+Xa3wZyDL1WooUvuYizBW5iT8HC3JGh++4Q9S7m/9znxct8C0r447CwcKHIaspfr iG3Y+9u51W5VbBP2ycopLxh1UzGtdPMy5EWwK8Xz6GAOM1xANhcTC/dmn3ANRVBomRes OEii4TCxtyfgypic15QUJteNn0B1bEH/rkvP3OT3AiYTVkr3amZsW5HghvE6cxrj4CLe zJmFydaFaBNgRSU4o86aOlchBwM8SNsUak6jY2Ud/5y4k2uv+2gh27scNaI+PDDAwu4U nbag== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=iiGF5v84NYO7bfihe5lKD3KgxcpAe/cVDxz7dY26HIg=; b=hTPcs+uu0q2cLIL+GmL/yKOh6+0AGut3G2KxoAEfbWyrVxTdYyra/AXi2cirfdoXCZ wZfjs0SJwKlPbBKqFukWtQgAs2TZ4DNe15J0ADD6bVvadBbNyNdwsbmhf5PUSb9vZcia gGg0HZdmM+MQjv96QjEw7YTL9tguK0ZoAIA9CaXnwWgv/QD9Ro5Ievulv3hdPoHiFhqa hrDnEpd2txRIq1/Fb9qiSkt6rI8ksgJIM6EF9X9B8Z5QoF6gWDirwKT6Pa82d9YywIJ5 v1ctm2CCNpAUEPHWAr6mL1WuGojmSA+2PuUJKxtxcMph3HJosNuLjl0myHL5ov7rEMaK CY6w== X-Gm-Message-State: AIkVDXLVg+GhTGdJQdwxM8jNJ1cW/Ld70u5cBdbIce6wZUGlI7PkrojsUQ+jNU2bVYTf/9MG3byCpk5QD6v6Yw== X-Received: by 10.157.60.238 with SMTP id t43mr12472662otf.178.1484390674834; Sat, 14 Jan 2017 02:44:34 -0800 (PST) MIME-Version: 1.0 Received: by 10.157.6.166 with HTTP; Sat, 14 Jan 2017 02:44:34 -0800 (PST) In-Reply-To: <49F36EE5-D3BD-420A-9F16-2219C7C83AC8@gmail.com> References: <49F36EE5-D3BD-420A-9F16-2219C7C83AC8@gmail.com> From: Vincenzo Maffione Date: Sat, 14 Jan 2017 11:44:34 +0100 Message-ID: Subject: Re: powerpc.LINT* broken in netmap(4) To: FreeBSD Net Cc: Luigi Rizzo , "Ngie Cooper (yaneurabeya)" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Jan 2017 10:44:35 -0000 2017-01-13 23:27 GMT+01:00 Ngie Cooper (yaneurabeya) : > > > On Jan 13, 2017, at 02:22, Ngie Cooper (yaneurabeya) < > yaneurabeya@gmail.com> wrote: > > > > Hi, > > I spotted these compilation errors on universe12a.freebsd.org for > both powerpc.LINT and powerpc.LINT64: > > > > cc1: warnings being treated as errors > > /scratch/tmp/ngie/svn/sys/dev/netmap/netmap_generic.c: In function > 'generic_set_tx_event': > > /scratch/tmp/ngie/svn/sys/dev/netmap/netmap_generic.c:765: warning: the > address of 'generic_mbuf_destructor' will always evaluate as 'true' > [-Waddress] > > --- netmap_generic.o --- > > *** [netmap_generic.o] Error code 1 > > > > I haven=E2=80=99t yet dug into why this only surfaces on powerpc,= yet=E2=80=A6 > > (CC -powerpc; BCC +powerpc) > Hi, > sparc64 has the same issue as powerpc*, so I suspect that gcc is > flagging this as an issue. > Thanks, > -Ngie > > PS. Sidenote: why was the SET_MBUF_DESTRUCTOR macro added, but not used i= n > nm_os_get_mbuf ? > Because the destructor is set only on certain mbufs, selected to issue notifications to netmap applications. The proper fix is probably to turn the macro to a function, I cannot think of other solutions. Cheers, Vincenzo --=20 Vincenzo Maffione From owner-freebsd-net@freebsd.org Sat Jan 14 16:44:11 2017 Return-Path: Delivered-To: freebsd-net@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 21B0ACAF05D for ; Sat, 14 Jan 2017 16:44:11 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 114BB1A49 for ; Sat, 14 Jan 2017 16:44:11 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v0EGiA4R090201 for ; Sat, 14 Jan 2017 16:44:10 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 117733] [patch] [request] allow to tee(1) to sockets, descriptors Date: Sat, 14 Jan 2017 16:44:11 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 6.2-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: julian@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Jan 2017 16:44:11 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D117733 Julian Elischer changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |julian@FreeBSD.org --- Comment #2 from Julian Elischer --- I personally like this.. we should do it. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Sat Jan 14 16:46:18 2017 Return-Path: Delivered-To: freebsd-net@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 3BD1DCAF224 for ; Sat, 14 Jan 2017 16:46:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 2B98E1CC7 for ; Sat, 14 Jan 2017 16:46:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v0EGkHBc094700 for ; Sat, 14 Jan 2017 16:46:18 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 117733] [patch] [request] allow to tee(1) to sockets, descriptors Date: Sat, 14 Jan 2017 16:46:18 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 6.2-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: julian@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Jan 2017 16:46:18 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D117733 --- Comment #3 from Julian Elischer --- (In reply to Julian Elischer from comment #2) adding that in this world more and more cross-machine work is encountered. This would work well with netcat. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Sat Jan 14 18:57:37 2017 Return-Path: Delivered-To: freebsd-net@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 72423CAF120 for ; Sat, 14 Jan 2017 18:57:37 +0000 (UTC) (envelope-from kevin.bowling@kev009.com) Received: from mail-ot0-x22c.google.com (mail-ot0-x22c.google.com [IPv6:2607:f8b0:4003:c0f::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3C9D61926 for ; Sat, 14 Jan 2017 18:57:37 +0000 (UTC) (envelope-from kevin.bowling@kev009.com) Received: by mail-ot0-x22c.google.com with SMTP id 65so21851710otq.2 for ; Sat, 14 Jan 2017 10:57:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kev009.com; s=google; h=mime-version:from:date:message-id:subject:to; bh=cwNmzRB77B9Ltv3faQgYyadD6ALvLBESf12XFheXg2E=; b=L8yJUdl2vrwiA2i5TWCjBfRXBASVzbdI+CAxL1cFFfOw+2w+StJmr6p/Ppm04EJ8rD VQ8QZKxNE6hz0xewwHIPWjBPcB5xT1ymxq4B442QDWAPXW6b9FrCkl2vESYniazCr7Kp +nsuW6wzcLHEpMvz1r/k5kUIuxmdC6S8wycCU= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=cwNmzRB77B9Ltv3faQgYyadD6ALvLBESf12XFheXg2E=; b=leawSCR9q2lfxWV5NvpLWMpnBPqvRUAQmYuFocenSSBlrd9SsZt8YxhTk6Aoo5q986 +g/EZ8WUJoiRNbhubr6LcXFUqNhwIOmOh/Ny4vHrA0ENNDntBX4VQkJ6CzFkLqyfVmAG Y2csPE1dDMZsxwWXaDFxYRRYKt4Dr2v0YlXydkrq0gIJ0pL8PKT5kJiV1xtYwVe1P92a GD/St5mvsO0W5Nu5MIpnzUCUBxdBJ1uLaye8zbQ0dwdHGX6FjWmg5RXYAhA/2SVwwzqH VjoUSKKlc4E9q4rAECABZWfkGtI9o8RXDbNbDYint8Q3CyOSBzPKZUoAXVRnp4Hnidm6 tRGg== X-Gm-Message-State: AIkVDXJ2k8n+jHlOL7aEkLrbFzHNZllFdjVONPdAzO2xJqONjRhjuS3IxZwug+YUst+0miweAr7vNeRMY5fKuA== X-Received: by 10.157.19.117 with SMTP id q50mr13410896otq.54.1484420256435; Sat, 14 Jan 2017 10:57:36 -0800 (PST) MIME-Version: 1.0 Received: by 10.157.23.208 with HTTP; Sat, 14 Jan 2017 10:57:36 -0800 (PST) From: Kevin Bowling Date: Sat, 14 Jan 2017 11:57:36 -0700 Message-ID: Subject: ixgbe PF and ixv driver To: freebsd-net@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Jan 2017 18:57:37 -0000 Hi, I've been trying to test SR-IOV on -CURRENT and 11.0-RELEASE. Physical NIC is an X552. The ixgbe PF has to be limited to 1-4 queues in order to create VFs or you will get ENOSPC from iovctl. Either letting ixv try to attach on the host, or creating a passthrough and allowing pfsense 2.4.0 beta to try to attach yields this failure to attach: m 0xc0104000-0xc0107fff,0xc0108000-0xc010bfff at device 7.0 on pci0 ixv0: Using MSIX interrupts with 2 vectors ixv0: ixgbe_reset_hw() failed with error -10 device_attach: ixv0 attach returned 5 Another issue, the PF is unable to pass traffic after creating a VF. 'iovctl -D -d ix0; service netif restart; service routing restart' will restore connectivity. Regards, Kevin From owner-freebsd-net@freebsd.org Sat Jan 14 23:43:02 2017 Return-Path: Delivered-To: freebsd-net@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 9C97FCAFC55 for ; Sat, 14 Jan 2017 23:43:02 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: from reviews.nyi.freebsd.org (reviews.nyi.freebsd.org [IPv6:2610:1c1:1:607c::16:b]) by mx1.freebsd.org (Postfix) with ESMTP id 7779814E7 for ; Sat, 14 Jan 2017 23:43:02 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: by reviews.nyi.freebsd.org (Postfix, from userid 1346) id 3799936FED; Sat, 14 Jan 2017 23:43:02 +0000 (UTC) Date: Sat, 14 Jan 2017 23:43:02 +0000 To: freebsd-net@freebsd.org From: "sobomax (Maksym Sobolyev)" Reply-to: D8582+325+5aab40e87f8cbe09@reviews.freebsd.org Subject: [Differential] D8582: Bump so_options storage from "short" to "int" to match optname argument type in get/setsockopt system calls Message-ID: X-Priority: 3 X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: , Thread-Topic: D8582: Bump so_options storage from "short" to "int" to match optname argument type in get/setsockopt system calls X-Herald-Rules: <28>, <64>, <76> X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: Precedence: bulk In-Reply-To: References: Thread-Index: NWJmZjc3NmMyZjA1YTk2NWEzZDc1NjcwMTc5IFh6t4Y= MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Jan 2017 23:43:02 -0000 c29ib21heCBhYmFuZG9uZWQgdGhpcyByZXZpc2lvbi4Kc29ib21heCBhZGRlZCBhIGNvbW1lbnQu CgoKICBOb3QgbmVjZXNzYXJ5IGl0IHR1cm5zIG91dC4KClJFUE9TSVRPUlkKICByUyBGcmVlQlNE IHNyYyByZXBvc2l0b3J5CgpSRVZJU0lPTiBERVRBSUwKICBodHRwczovL3Jldmlld3MuZnJlZWJz ZC5vcmcvRDg1ODIKCkVNQUlMIFBSRUZFUkVOQ0VTCiAgaHR0cHM6Ly9yZXZpZXdzLmZyZWVic2Qu b3JnL3NldHRpbmdzL3BhbmVsL2VtYWlscHJlZmVyZW5jZXMvCgpUbzogc29ib21heCwgZnJlZWJz ZC1uZXQtbGlzdCwgI3RyYW5zcG9ydApDYzogaW1wCg==