From owner-freebsd-hackers@freebsd.org  Tue Oct 23 21:34:13 2018
Return-Path: <owner-freebsd-hackers@freebsd.org>
Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id A8F3BFFD82F
 for <freebsd-hackers@mailman.ysv.freebsd.org>;
 Tue, 23 Oct 2018 21:34:13 +0000 (UTC) (envelope-from lev@FreeBSD.org)
Received: from onlyone.not-for.work (onlyone.not-for.work [148.251.9.81])
 by mx1.freebsd.org (Postfix) with ESMTP id 40E02714A8;
 Tue, 23 Oct 2018 21:34:13 +0000 (UTC) (envelope-from lev@FreeBSD.org)
Received: from lion.home.serebryakov.spb.ru (unknown [94.19.235.70])
 (Authenticated sender: lev@serebryakov.spb.ru)
 by onlyone.not-for.work (Postfix) with ESMTPSA id EFCEDBAF;
 Wed, 24 Oct 2018 00:34:11 +0300 (MSK)
Date: Wed, 24 Oct 2018 00:34:12 +0300
From: Lev Serebryakov <lev@FreeBSD.org>
Reply-To: lev@FreeBSD.org
Organization: FreeBSD
Message-ID: <168122586.20181024003412@serebryakov.spb.ru>
To: Ryan Stone <rysto32@gmail.com>
CC: freebsd-hackers@freebsd.org, cse.cem@gmail.com, 
 Alan Somers <asomers@freebsd.org>
Subject: Re: What is wrong with dtrace's stack()?
In-Reply-To: <CAFMmRNz35Ay82NcMnUkSAvpyU5p2m9ykiji1xXcbEanH9A2H+w@mail.gmail.com>
References: <170994671.20181021201021@serebryakov.spb.ru> 
 <CAG6CVpVCe-8OVU+KEyAh8swFSAjRshNcNLN0tjAS3W8bZxyrTA@mail.gmail.com>
 <475670271.20181022003734@serebryakov.spb.ru>
 <CAOtMX2goztCYJXM72WNR711DEBEKAGk1zFHF=NpE4UiVAF2bAQ@mail.gmail.com>
 <234d745d-37a9-9610-15b9-0f5cd5af21bf@FreeBSD.org>
 <b30f2080-1037-1752-60fb-6d22e28ce90d@FreeBSD.org>
 <CAFMmRNz35Ay82NcMnUkSAvpyU5p2m9ykiji1xXcbEanH9A2H+w@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
 <freebsd-hackers.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers/>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Oct 2018 21:34:13 -0000

Hello Ryan,

Monday, October 22, 2018, 11:50:29 PM, you wrote:

> Adding -fno-optimize-sibling-calls to the compiler flags will eliminate the TCO.
 Stacks are better but still strange. For example I have such stack (which I
 like better than previous):

 kernel`lock_delay+0x72
 kernel`sosend_generic+0x112c
 kernel`sosend+0x79
 kernel`soo_write+0x6b
 kernel`fo_write+0x4a
 kernel`dofilewrite+0xcd
 kernel`kern_writev+0x79
 kernel`sys_write+0x8f
 kernel`syscallenter+0x774
 kernel`amd64_syscall+0x1b
 kernel`0xffffffff80cebf6d

According to addr2line `sosend_generic+0x112c' is

https://svnweb.freebsd.org/base/head/sys/kern/uipc_socket.c?revision=339419&view=markup#l1579

 Which is call to protocol-specific send function. Where is this function
(it should be tcp for sure)?!

-- 
Best regards,
 Lev                            mailto:lev@FreeBSD.org