From owner-freebsd-hackers@freebsd.org Sun Nov 8 00:36:49 2015 Return-Path: Delivered-To: freebsd-hackers@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 8FEC8A220D6; Sun, 8 Nov 2015 00:36:49 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 767621FF2; Sun, 8 Nov 2015 00:36:49 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mail.xzibition.com (localhost [IPv6:::1]) by freefall.freebsd.org (Postfix) with ESMTP id 714871F0E; Sun, 8 Nov 2015 00:36:49 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mail.xzibition.com (localhost [172.31.3.2]) by mail.xzibition.com (Postfix) with ESMTP id 312001247C; Sun, 8 Nov 2015 00:36:49 +0000 (UTC) X-Virus-Scanned: amavisd-new at mail.xzibition.com Received: from mail.xzibition.com ([172.31.3.2]) by mail.xzibition.com (mail.xzibition.com [172.31.3.2]) (amavisd-new, port 10026) with LMTP id MFo3S1K959VF; Sun, 8 Nov 2015 00:36:46 +0000 (UTC) Subject: Re: strange kernel crash DKIM-Filter: OpenDKIM Filter v2.9.2 mail.xzibition.com 48DF912477 To: Andriy Gapon , FreeBSD Current , FreeBSD Hackers References: <563C8CED.3020101@FreeBSD.org> <563E5589.3040100@FreeBSD.org> <563E846E.4010205@FreeBSD.org> From: Bryan Drewery Openpgp: id=F9173CB2C3AAEA7A5C8A1F0935D771BB6E4697CF; url=http://www.shatow.net/bryan/bryan2.asc Organization: FreeBSD Message-ID: <563E9925.1000806@FreeBSD.org> Date: Sat, 7 Nov 2015 16:36:53 -0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <563E846E.4010205@FreeBSD.org> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="d63vSo0lbibKqOkCvIS5IDfM3N48C2kOm" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Nov 2015 00:36:49 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --d63vSo0lbibKqOkCvIS5IDfM3N48C2kOm Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 11/7/2015 3:08 PM, Andriy Gapon wrote: > On 07/11/2015 21:48, Bryan Drewery wrote: >> On 11/6/15 3:20 AM, Andriy Gapon wrote: >>> Unread portion of the kernel message buffer: >>> >>> Fatal trap 1: privileged instruction fault while in kernel mode >> ... >> >> What SVN revision? >=20 > r289875 from October 24. >=20 I ask because I fixed an uninitialized ptr write in the kernel in r290155 on October 29th. I would only expect it to happen in low memory situations. --=20 Regards, Bryan Drewery --d63vSo0lbibKqOkCvIS5IDfM3N48C2kOm 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 iQEcBAEBAgAGBQJWPpklAAoJEDXXcbtuRpfP9O0H/1Tx3F/T8XtpWDpU9HO0Acwr oJcCdT1x2sbzL5VKxUejuBv5GNiQQ+htGuSYuFfWykDA1ZcdZkc07SYiQCLYYmCK chjiOyVXGXwwPkgidFw4sxN/Wgp01YQC0ar1igOUR5QKquYP5B7fEynD0oaLais4 edqji9hfeVQHa9wA+HwrQBJSDwxz9iWjvYOoLkDYuoLVt8Ho6Fd9TY5xLd64/+1X OUmzUdsTwXknN2mnwB9HBH9G2y1cQa13UR4npLJbU7JwyVRx44ezAZ2sJz/Rbrsm QH0MBRsFcr87rUAsSOEVxef6dp8zeEzNzyZknor6OJqj3TydeYeoib8uZAdP5z0= =eQm+ -----END PGP SIGNATURE----- --d63vSo0lbibKqOkCvIS5IDfM3N48C2kOm-- From owner-freebsd-hackers@freebsd.org Sun Nov 8 02:07:46 2015 Return-Path: Delivered-To: freebsd-hackers@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 921A3A22A39; Sun, 8 Nov 2015 02:07:46 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from gw.catspoiler.org (unknown [IPv6:2602:304:b010:ef20::f2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gw.catspoiler.org", Issuer "gw.catspoiler.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 7559D15F4; Sun, 8 Nov 2015 02:07:46 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.15.2/8.15.2) with ESMTP id tA827aeV030767; Sat, 7 Nov 2015 18:07:40 -0800 (PST) (envelope-from truckman@FreeBSD.org) Message-Id: <201511080207.tA827aeV030767@gw.catspoiler.org> Date: Sat, 7 Nov 2015 18:07:36 -0800 (PST) From: Don Lewis Subject: Re: strange kernel crash To: bdrewery@FreeBSD.org cc: avg@FreeBSD.org, freebsd-current@FreeBSD.org, freebsd-hackers@FreeBSD.org In-Reply-To: <563E9925.1000806@FreeBSD.org> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Nov 2015 02:07:46 -0000 On 7 Nov, Bryan Drewery wrote: > On 11/7/2015 3:08 PM, Andriy Gapon wrote: >> On 07/11/2015 21:48, Bryan Drewery wrote: >>> On 11/6/15 3:20 AM, Andriy Gapon wrote: >>>> Unread portion of the kernel message buffer: >>>> >>>> Fatal trap 1: privileged instruction fault while in kernel mode >>> ... >>> >>> What SVN revision? >> >> r289875 from October 24. >> > > I ask because I fixed an uninitialized ptr write in the kernel in > r290155 on October 29th. I would only expect it to happen in low memory > situations. I haven't seen it since I upgraded from r290039 Tue Oct 27 to r290224 Sat Oct 31. I can believe that low memory would trigger it since I often it uses zfs and I sometimes drive it heavily into swap (using tmpfs) when running poudriere with parallel builds. The timing makes sense because the bug was introduce by r289279, and before r290039 I had been running r289123 without having any problems. From owner-freebsd-hackers@freebsd.org Sun Nov 8 02:22:11 2015 Return-Path: Delivered-To: freebsd-hackers@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 76992A22F42; Sun, 8 Nov 2015 02:22:11 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from gw.catspoiler.org (unknown [IPv6:2602:304:b010:ef20::f2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gw.catspoiler.org", Issuer "gw.catspoiler.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 565F41CE0; Sun, 8 Nov 2015 02:22:11 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.15.2/8.15.2) with ESMTP id tA82M1Ao030808; Sat, 7 Nov 2015 18:22:05 -0800 (PST) (envelope-from truckman@FreeBSD.org) Message-Id: <201511080222.tA82M1Ao030808@gw.catspoiler.org> Date: Sat, 7 Nov 2015 18:22:01 -0800 (PST) From: Don Lewis Subject: Re: strange kernel crash To: bdrewery@FreeBSD.org cc: avg@FreeBSD.org, freebsd-current@FreeBSD.org, freebsd-hackers@FreeBSD.org In-Reply-To: <201511080207.tA827aeV030767@gw.catspoiler.org> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Nov 2015 02:22:11 -0000 On 7 Nov, To: bdrewery@FreeBSD.org wrote: > On 7 Nov, Bryan Drewery wrote: >> On 11/7/2015 3:08 PM, Andriy Gapon wrote: >>> On 07/11/2015 21:48, Bryan Drewery wrote: >>>> On 11/6/15 3:20 AM, Andriy Gapon wrote: >>>>> Unread portion of the kernel message buffer: >>>>> >>>>> Fatal trap 1: privileged instruction fault while in kernel mode >>>> ... >>>> >>>> What SVN revision? >>> >>> r289875 from October 24. >>> >> >> I ask because I fixed an uninitialized ptr write in the kernel in >> r290155 on October 29th. I would only expect it to happen in low memory >> situations. > > I haven't seen it since I upgraded from r290039 Tue Oct 27 to r290224 > Sat Oct 31. I can believe that low memory would trigger it since I > often it uses zfs and I sometimes drive it heavily into swap (using > tmpfs) when running poudriere with parallel builds. Wow, that sentence makes no sense at all ... change it to: I can believe that low memory would trigger it since that machine uses zfs and I often drive it heavily into swap (using tmpfs) when running poudriere with parallel builds. > The timing makes > sense because the bug was introduce by r289279, and before r290039 I had > been running r289123 without having any problems. > > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-hackers@freebsd.org Sun Nov 8 03:20:24 2015 Return-Path: Delivered-To: freebsd-hackers@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 11D01A278C7 for ; Sun, 8 Nov 2015 03:20:24 +0000 (UTC) (envelope-from d0lph1n98@yahoo.com) Received: from nm4-vm6.bullet.mail.ne1.yahoo.com (nm4-vm6.bullet.mail.ne1.yahoo.com [98.138.91.97]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C743E13E2 for ; Sun, 8 Nov 2015 03:20:23 +0000 (UTC) (envelope-from d0lph1n98@yahoo.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1446952708; bh=zRLb0MqSng8f98duw46Exzm0/CmoQTcqzfBhCjurM80=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject; b=hPpuZJivOpUY52BR2BEltQrkI++p+Of2HuRz7+b19fBgknlKCRoQobDcNW0E/F6UQyPlObNwFWq2+jqTScxQPqhKa5w4keWfWSOLoqGdy6ZplhdT3XNf3gf5z/uAwy1InJmd9/Q3R8UDj6AjX7+R3aQUfZo2COYTyPjlJquynasKcbV94qRu2h4jqpz0NChhpR33HN3XnCvt+3XTN7ZsUVZgWS6kowUlxY1Hha3dGXzPoQgTUPvzCVGeEtywZXpTAIadh+Aj9gifC3KIpWpxGPl4PipY1nLhSbTI279Me0VpecYo2DApwDz6D6hI0GG0jv+r39KUw+hclTkFJCYmWQ== Received: from [98.138.100.113] by nm4.bullet.mail.ne1.yahoo.com with NNFMP; 08 Nov 2015 03:18:28 -0000 Received: from [98.138.89.196] by tm104.bullet.mail.ne1.yahoo.com with NNFMP; 08 Nov 2015 03:18:28 -0000 Received: from [127.0.0.1] by omp1054.mail.ne1.yahoo.com with NNFMP; 08 Nov 2015 03:18:28 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 84249.49483.bm@omp1054.mail.ne1.yahoo.com X-YMail-OSG: OF5QJAMVM1nL2DKmwnk5l_DHZdM3dsDqRYgiHH38pPqdBY8G.2V8NcsS_d4Zcm5 RsUAWEXiuTEmbvzOUVfLLJzVwmEHMtlMvritBCnLeAfJMF0A_0QXfdJ7iv2rwMjXSP2JHpL2WO2M RI9yx2BOnrDJ7dOymKwDKbDAqpfldsVO3G26.cx.5SBYm4mmepETHaw4PC7MUzXwU8.c6t7hJn.I RIbKdiqDotwkvxRGIhznRuhXVKavgqA8dfMhKgKCMilezKqcV5IZPdQDOsx5LVYQr80z.OGAYryh FGxAwJ1IwWlmql.9AG0Ia0ZX.eq9CSUokTJy0F3RY4wUkcEPVY772njA.Ylic8eV2KdG.PCLnp1B MPj2FyzStyT9x4tab_.0yJ5iQwXF2YnG7r7bwIRYUs9bUr3sRVihsA3MqjI6UHpPUsCfcfNYTi9d Jt395zxLlhh8rePr9NTPIRv9.3nY5fA4XRgPXV1k3bwinQ.1LT6WTu0mJDB6_QibT4ClRf6DP4qE fkLnTazuxl6_4EdEWfGrPQewShGkwRA-- Received: by 98.138.105.243; Sun, 08 Nov 2015 03:18:27 +0000 Date: Sun, 8 Nov 2015 03:18:26 +0000 (UTC) From: Big Whale Reply-To: Big Whale To: Adrian Chadd , Constantinos Georgiades Cc: "freebsd-hackers@freebsd.org" Message-ID: <2024364727.1157969.1446952707296.JavaMail.yahoo@mail.yahoo.com> In-Reply-To: References: Subject: Re: Code contribution MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Nov 2015 03:20:24 -0000 You also can start by subscribing to the correct mailing list, and always c= atch up with latest problem. See if you can contribute to any of them. Some= might ask about their problem there.=C2=A0=20 On Sunday, November 8, 2015 12:35 AM, Adrian Chadd wrote: =20 Sure! Just ask on here and see who helps out! There are plenty of us that are happy to help where we can! -a On 7 November 2015 at 06:53, Constantinos Georgiades wrote: > Hello All, > > I am willing to contribute code in my free time for fun and experience. > > I am interested for some of the juniors kernel projects and > particularly for the "Free old file descriptor tables". > > Contributing to userland projects is ok too. > "Improve cron(8) and atrun(8)" seems nice project. > > > I will probably need some help. > Should i get a mentor? > > Regards, > Constantinos > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org= " _______________________________________________ freebsd-hackers@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" From owner-freebsd-hackers@freebsd.org Sun Nov 8 10:23:12 2015 Return-Path: Delivered-To: freebsd-hackers@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 4C988A22C21 for ; Sun, 8 Nov 2015 10:23:12 +0000 (UTC) (envelope-from deco33000@yandex.com) Received: from forward18p.cmail.yandex.net (forward18p.cmail.yandex.net [IPv6:2a02:6b8:0:1465::ab]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Certum Level IV CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 09887195F for ; Sun, 8 Nov 2015 10:23:11 +0000 (UTC) (envelope-from deco33000@yandex.com) Received: from web22g.yandex.ru (web22g.yandex.ru [IPv6:2a02:6b8:0:1402::32]) by forward18p.cmail.yandex.net (Yandex) with ESMTP id C8E4C210C9 for ; Sun, 8 Nov 2015 13:22:59 +0300 (MSK) Received: from 127.0.0.1 (localhost [127.0.0.1]) by web22g.yandex.ru (Yandex) with ESMTP id 675ED8A11D8; Sun, 8 Nov 2015 13:22:59 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.com; s=mail; t=1446978179; bh=mU0nAayEsxTV5vkCVHzR67kf/HEUgBYxLnV+c9W5bkU=; h=From:To:Subject:Date; b=MHLOAkb2JD6BwsPr0uoGWz3TSkkELyExgTZdc7Q06Ml0pf1jJ/OJhR33sM3Uv0rqB Z/xhYTWakiJ1qdUH25wujUJ2OZPSbnivB1EAd+MlrgEznpdlz2I0fbbQ/K/1KRYUP8 iiNxLpfCcwricICkh8OpF25Ygjt7Yk72dYmL8Nxw= Received: by web22g.yandex.ru with HTTP; Sun, 08 Nov 2015 13:22:57 +0300 From: AlexHully To: freebsd-hackers@freebsd.org Subject: dma MIME-Version: 1.0 Message-Id: <298361446978177@web22g.yandex.ru> X-Mailer: Yamail [ http://yandex.ru ] 5.0 Date: Sun, 08 Nov 2015 11:22:57 +0100 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=koi8-r X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Nov 2015 10:23:12 -0000 Hi, I would like a clarification for dma. The context: most dma capable devices have 32 bits address range. Is it correct that, if there was no 3G/1G mapping in the kernel, or that kernel low memory could map 4Gb memory, one could choose any free addresses in that low memory to set up a dma buffer? That would avoid all the mapping hassle, and performance cost associated. Thanks --š Alex From owner-freebsd-hackers@freebsd.org Sun Nov 8 11:56:48 2015 Return-Path: Delivered-To: freebsd-hackers@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 7113DA2956D for ; Sun, 8 Nov 2015 11:56:48 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (heidi.turbocat.net [88.198.202.214]) (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 3A2681202 for ; Sun, 8 Nov 2015 11:56:47 +0000 (UTC) (envelope-from hps@selasky.org) Received: from laptop015.home.selasky.org (unknown [62.141.129.119]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id E072E1FE023; Sun, 8 Nov 2015 12:56:38 +0100 (CET) Subject: Re: dma To: AlexHully , freebsd-hackers@freebsd.org References: <298361446978177@web22g.yandex.ru> From: Hans Petter Selasky Message-ID: <563F38DD.5070409@selasky.org> Date: Sun, 8 Nov 2015 12:58:21 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: <298361446978177@web22g.yandex.ru> Content-Type: text/plain; charset=koi8-r; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Nov 2015 11:56:48 -0000 On 11/08/15 11:22, AlexHully wrote: > Hi, > > I would like a clarification for dma. > > The context: most dma capable devices have 32 bits address range. > Is it correct that, if there was no 3G/1G mapping in the kernel, or that kernel low memory could map 4Gb memory, one could choose any free addresses in that low memory to set up a dma buffer? > > That would avoid all the mapping hassle, and performance cost associated. > I've seen USB controllers only supporting 2G address range. --HPS From owner-freebsd-hackers@freebsd.org Sun Nov 8 12:00:15 2015 Return-Path: Delivered-To: freebsd-hackers@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 61E13A29987 for ; Sun, 8 Nov 2015 12:00:15 +0000 (UTC) (envelope-from deco33000@yandex.com) Received: from forward12j.cmail.yandex.net (forward12j.cmail.yandex.net [IPv6:2a02:6b8:0:1630::b2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Certum Level IV CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1D56B158B for ; Sun, 8 Nov 2015 12:00:15 +0000 (UTC) (envelope-from deco33000@yandex.com) Received: from web20j.yandex.ru (web20j.yandex.ru [5.45.198.61]) by forward12j.cmail.yandex.net (Yandex) with ESMTP id 8B0C120D21; Sun, 8 Nov 2015 15:00:03 +0300 (MSK) Received: from 127.0.0.1 (localhost [127.0.0.1]) by web20j.yandex.ru (Yandex) with ESMTP id E049221C0B95; Sun, 8 Nov 2015 15:00:02 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.com; s=mail; t=1446984003; bh=Fg0ytSzGxOx9CPEkXEbD/kTndirVGdJpyrG/V2xmvNQ=; h=From:To:In-Reply-To:References:Subject:Date; b=JMSKchfPD64ajU7/gu1rzz/xVkCjlsiZ8+ePoJEbS/4LPie65LRx8/en5z7ajSGnI mbnA95F0mQMpjKcDl2ol/YeTYahNOGp1FhxfcU+Wp3zDcbEOKm6pyX2r7be+k2u/Qw vcIT+aGtxzm6+bd5nJ88aaKsqq4ziNGrHUVacqak= Received: by web20j.yandex.ru with HTTP; Sun, 08 Nov 2015 15:00:02 +0300 From: AlexHully To: Hans Petter Selasky , "freebsd-hackers@freebsd.org" In-Reply-To: <563F38DD.5070409@selasky.org> References: <298361446978177@web22g.yandex.ru> <563F38DD.5070409@selasky.org> Subject: Re: dma MIME-Version: 1.0 Message-Id: <373471446984002@web20j.yandex.ru> X-Mailer: Yamail [ http://yandex.ru ] 5.0 Date: Sun, 08 Nov 2015 13:00:02 +0100 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=koi8-r X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Nov 2015 12:00:15 -0000 Ok, those were recent? --š Alex 08.11.2015, 12:56, "Hans Petter Selasky" : > On 11/08/15 11:22, AlexHully wrote: >> šHi, >> >> šI would like a clarification for dma. >> >> šThe context: most dma capable devices have 32 bits address range. >> šIs it correct that, if there was no 3G/1G mapping in the kernel, or that kernel low memory could map 4Gb memory, one could choose any free addresses in that low memory to set up a dma buffer? >> >> šThat would avoid all the mapping hassle, and performance cost associated. > > I've seen USB controllers only supporting 2G address range. > > --HPS From owner-freebsd-hackers@freebsd.org Sun Nov 8 12:01:17 2015 Return-Path: Delivered-To: freebsd-hackers@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 EE3CBA29BEE for ; Sun, 8 Nov 2015 12:01:17 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (mail.turbocat.net [IPv6:2a01:4f8:d16:4514::2]) (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 B5FC61A36 for ; Sun, 8 Nov 2015 12:01:17 +0000 (UTC) (envelope-from hps@selasky.org) Received: from laptop015.home.selasky.org (unknown [62.141.129.119]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id C9DF11FE023; Sun, 8 Nov 2015 13:01:15 +0100 (CET) Subject: Re: dma To: AlexHully , "freebsd-hackers@freebsd.org" References: <298361446978177@web22g.yandex.ru> <563F38DD.5070409@selasky.org> <373471446984002@web20j.yandex.ru> From: Hans Petter Selasky Message-ID: <563F39F2.9060503@selasky.org> Date: Sun, 8 Nov 2015 13:02:58 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: <373471446984002@web20j.yandex.ru> Content-Type: text/plain; charset=koi8-r; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Nov 2015 12:01:18 -0000 On 11/08/15 13:00, AlexHully wrote: > Ok, those were recent? > Old ones. --HPS From owner-freebsd-hackers@freebsd.org Sun Nov 8 12:03:27 2015 Return-Path: Delivered-To: freebsd-hackers@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 BBAC9A29D85 for ; Sun, 8 Nov 2015 12:03:27 +0000 (UTC) (envelope-from deco33000@yandex.com) Received: from forward12j.cmail.yandex.net (forward12j.cmail.yandex.net [5.255.227.176]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Certum Level IV CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 74DA41D4D for ; Sun, 8 Nov 2015 12:03:26 +0000 (UTC) (envelope-from deco33000@yandex.com) Received: from web20j.yandex.ru (web20j.yandex.ru [5.45.198.61]) by forward12j.cmail.yandex.net (Yandex) with ESMTP id 3314120C67; Sun, 8 Nov 2015 15:03:24 +0300 (MSK) Received: from 127.0.0.1 (localhost [127.0.0.1]) by web20j.yandex.ru (Yandex) with ESMTP id 8D9AC21C00ED; Sun, 8 Nov 2015 15:03:23 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.com; s=mail; t=1446984203; bh=ymd49+XerOlcb63C/eEA1GRT5m+6MhZBWwArFS/py10=; h=From:To:In-Reply-To:References:Subject:Date; b=H/vaVonptBqABgVdsInAk3PRspjosPUwzQcjhCKXJA/uOee3yVHf6++Sw6fXwN4eK JR/wYmMjEEQN2eTEpcR3N/CBvtB+ZNjhnG3h0W1t2RfCrn4wcJLSYOFkg6jnNYTBgB wKGufPdK2eGKtkAFPyaDKsgRoR9B/xq+Cl2e3+GA= Received: by web20j.yandex.ru with HTTP; Sun, 08 Nov 2015 15:03:23 +0300 From: AlexHully To: Hans Petter Selasky , "freebsd-hackers@freebsd.org" In-Reply-To: <563F39F2.9060503@selasky.org> References: <298361446978177@web22g.yandex.ru> <563F38DD.5070409@selasky.org> <373471446984002@web20j.yandex.ru> <563F39F2.9060503@selasky.org> Subject: Re: dma MIME-Version: 1.0 Message-Id: <378751446984203@web20j.yandex.ru> X-Mailer: Yamail [ http://yandex.ru ] 5.0 Date: Sun, 08 Nov 2015 13:03:23 +0100 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=koi8-r X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Nov 2015 12:03:27 -0000 OK, so it should not apply to hardware 2010+. Then, is my assumption correct? (-> if the kernel space is made 4Gb, we can use any free memory in that space to set dma up) --š Alex 08.11.2015, 13:01, "Hans Petter Selasky" : > On 11/08/15 13:00, AlexHully wrote: >> šOk, those were recent? > > Old ones. > > --HPS From owner-freebsd-hackers@freebsd.org Sun Nov 8 12:43:21 2015 Return-Path: Delivered-To: freebsd-hackers@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 8593CA27AF5 for ; Sun, 8 Nov 2015 12:43:21 +0000 (UTC) (envelope-from csgeorgiades@gmail.com) Received: from mail-oi0-x232.google.com (mail-oi0-x232.google.com [IPv6:2607:f8b0:4003:c06::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 4C2EA1EB0 for ; Sun, 8 Nov 2015 12:43:21 +0000 (UTC) (envelope-from csgeorgiades@gmail.com) Received: by oies6 with SMTP id s6so45037615oie.1 for ; Sun, 08 Nov 2015 04:43:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=HkioQjRYHlF512+TtRaqab3EotUB+KxqumfbIR14jrE=; b=w4mbuJ8uagFy4VPfnynJ+WImafqZLkc0JsW+6jTY7TSOjdCIsnvyaR6iaS4BzcZO7S Q7XlYGnhNAhhgjT/xJsFi+u7Pvb9ENRRhfOMzS6MtnsBKjUwB0VaU+chOi+r+AcsrMrD n54zPQdehdW1FeSn8scuJuYr1KLLmS+LVVVzOaXIOYM8N+BlDIkabkvk6J2HhIK05Nlh zZYGgGDRSLismf+s6aAivgXdH5n2GW9LX9ct8qp642LoySFc++iMB0o0BDLYWcTEsqiu xVf9qrXTcpsv5i8KKVzBxCeqwAPO6SRv+JEuZWRQS6AGtuXfPN3Y62NxOvZJXbBn5+3H UOsg== MIME-Version: 1.0 X-Received: by 10.202.95.5 with SMTP id t5mr6391920oib.114.1446986600498; Sun, 08 Nov 2015 04:43:20 -0800 (PST) Received: by 10.76.34.199 with HTTP; Sun, 8 Nov 2015 04:43:20 -0800 (PST) In-Reply-To: References: <2024364727.1157969.1446952707296.JavaMail.yahoo@mail.yahoo.com> Date: Sun, 8 Nov 2015 14:43:20 +0200 Message-ID: Subject: Fwd: Code contribution From: Constantinos Georgiades To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Nov 2015 12:43:21 -0000 Ok thats great! Who should i inform for my willingness to work on a particular job? Contact the (technical contact) developer directly or inform the list? On Sun, Nov 8, 2015 at 2:39 PM, Constantinos Georgiades < csgeorgiades@gmail.com> wrote: > Ok thats great! > > Who should i inform for my willingness to work on a particular job? > Contact the (technical contact) developer directly or inform the list? > > Constantinos > > On Sun, Nov 8, 2015 at 5:18 AM, Big Whale wrote: > >> You also can start by subscribing to the correct mailing list, and always >> catch up with latest problem. See if you can contribute to any of them. >> Some might ask about their problem there. >> >> >> >> On Sunday, November 8, 2015 12:35 AM, Adrian Chadd < >> adrian.chadd@gmail.com> wrote: >> >> >> Sure! Just ask on here and see who helps out! There are plenty of us >> that are happy to help where we can! >> >> >> -a >> >> >> On 7 November 2015 at 06:53, Constantinos Georgiades >> wrote: >> > Hello All, >> > >> > I am willing to contribute code in my free time for fun and experience. >> > >> > I am interested for some of the juniors kernel projects and >> > particularly for the "Free old file descriptor tables". >> > >> > Contributing to userland projects is ok too. >> > "Improve cron(8) and atrun(8)" seems nice project. >> > >> > >> > I will probably need some help. >> > Should i get a mentor? >> > >> > Regards, >> > Constantinos >> > _______________________________________________ >> > freebsd-hackers@freebsd.org mailing list >> > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> > To unsubscribe, send any mail to " >> freebsd-hackers-unsubscribe@freebsd.org" >> >> _______________________________________________ >> freebsd-hackers@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org >> " >> >> >> > From owner-freebsd-hackers@freebsd.org Sun Nov 8 21:21:51 2015 Return-Path: Delivered-To: freebsd-hackers@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 481D3A290AA for ; Sun, 8 Nov 2015 21:21:51 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: from mail-ob0-x231.google.com (mail-ob0-x231.google.com [IPv6:2607:f8b0:4003:c01::231]) (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 0C87B1AA8 for ; Sun, 8 Nov 2015 21:21:51 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: by obbww6 with SMTP id ww6so100948432obb.0 for ; Sun, 08 Nov 2015 13:21:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=/JPzbNbe8oh0ZXta5bjQ1em0jb6h11TrzW/Iwfm2a88=; b=vEJwNOP354ReGALT/sDUJX19CqmTv+7l0XAMiMfTLs0W2wi2tviqlNJiXpaZ/EM5u7 KxDmNVZYPRIq0D0dVvEk0SQ4Qqxo63ji8pB+f4LeJAg6T7/WxgSDtYYhrRaUDjgbCa2N qJ3LnZqmGw/iMoto/OpKxPAyzi4bxH7/kbs3sSGW2+K5oqv1jl4DRO/ULIbNLDX2221S F8xWlfVyrnXI+FhmwVXq2meyDwOJNAXWinJJ1bOzoN3eQPSD1enhqKZxYSoiCRNwaI6J 9BM1LFw66V6i3S5+nBhPKJ61Uv/H/TKZWFSjeTKnkO1QApD+eOXkKCQ6lkOz9dEV0uCk fBeQ== X-Received: by 10.60.138.130 with SMTP id qq2mr14182731oeb.23.1447017710374; Sun, 08 Nov 2015 13:21:50 -0800 (PST) Received: from ?IPv6:2601:601:800:126d:84dd:ce91:2fcc:f08e? ([2601:601:800:126d:84dd:ce91:2fcc:f08e]) by smtp.gmail.com with ESMTPSA id 130sm3931042oid.21.2015.11.08.13.21.49 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 08 Nov 2015 13:21:49 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) Subject: Re: Code contribution From: Garrett Cooper X-Mailer: iPhone Mail (13B143) In-Reply-To: Date: Sun, 8 Nov 2015 13:21:48 -0800 Cc: freebsd-hackers@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <2F5C8D81-9357-421F-B1A7-C9B936577DB1@gmail.com> References: <2024364727.1157969.1446952707296.JavaMail.yahoo@mail.yahoo.com> To: Constantinos Georgiades X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Nov 2015 21:21:51 -0000 > On Nov 8, 2015, at 04:43, Constantinos Georgiades = wrote: >=20 > Ok thats great! >=20 > Who should i inform for my willingness to work on a particular job? > Contact the (technical contact) developer directly or inform the list? Contact the dev first; see if they have any areas that they recommend lookin= g at first, etc. If they don't reply that quickly, feel free to send an emai= l to the specific list. Feel free to reach me offline if you need help getting pointed in the right d= irection (ngie@). Thank you! -NGie= From owner-freebsd-hackers@freebsd.org Mon Nov 9 16:16:28 2015 Return-Path: Delivered-To: freebsd-hackers@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 A8886A29E12 for ; Mon, 9 Nov 2015 16:16:28 +0000 (UTC) (envelope-from csgeorgiades@gmail.com) Received: from mail-oi0-x22b.google.com (mail-oi0-x22b.google.com [IPv6:2607:f8b0:4003: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 6E5981034 for ; Mon, 9 Nov 2015 16:16:28 +0000 (UTC) (envelope-from csgeorgiades@gmail.com) Received: by oies6 with SMTP id s6so59319291oie.1 for ; Mon, 09 Nov 2015 08:16:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=YEkU+KDzmbfsw457g0/mRDgMUqyyBKhlm53cdfUaA0U=; b=YpEh3kL8na6NyXhvDwM22lzfvvNY4IIkwRYj1rTluyRJnftfxXLvNx0QCvPT+cwGYc JuInbjB5heJHZkVo2whIdRlDuuhxx2I9b5Bo39EuYGtOLHoKj7rtFFONIly0DJ5GJWOE qCQ2Vihc9Hc5JbxG95BRAa5nBg90IVLiDSmv2SpF2Ca5H9S/EGwGp/wX6ugaad+kkOep 6PavmFSy9FWUt3CieA1AxLpTfbRZdyB8HPGM4T+xzgQBJCSj7uonLvenr9GiQWKvW8vL VjHYlcjbaCd0amNikdooGse/L24TqJMny+gdVo+QVRWeg7GT8ArJcjLLN48e66wXqAVe tLcA== MIME-Version: 1.0 X-Received: by 10.202.87.68 with SMTP id l65mr1988715oib.118.1447085787833; Mon, 09 Nov 2015 08:16:27 -0800 (PST) Received: by 10.76.34.199 with HTTP; Mon, 9 Nov 2015 08:16:27 -0800 (PST) In-Reply-To: <2F5C8D81-9357-421F-B1A7-C9B936577DB1@gmail.com> References: <2024364727.1157969.1446952707296.JavaMail.yahoo@mail.yahoo.com> <2F5C8D81-9357-421F-B1A7-C9B936577DB1@gmail.com> Date: Mon, 9 Nov 2015 18:16:27 +0200 Message-ID: Subject: Re: Code contribution From: Constantinos Georgiades To: Garrett Cooper Cc: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Nov 2015 16:16:28 -0000 On Sun, Nov 8, 2015 at 11:21 PM, Garrett Cooper wrote: > > > On Nov 8, 2015, at 04:43, Constantinos Georgiades < > csgeorgiades@gmail.com> wrote: > > > > Ok thats great! > > > > Who should i inform for my willingness to work on a particular job? > > Contact the (technical contact) developer directly or inform the list? > > Contact the dev first; see if they have any areas that they recommend > looking at first, etc. If they don't reply that quickly, feel free to send > an email to the specific list. > Great, this is what i wanted to know. > > Feel free to reach me offline if you need help getting pointed in the > right direction (ngie@). > > Thank you! > -NGie Thank you all for your help. Constantinos From owner-freebsd-hackers@freebsd.org Mon Nov 9 16:59:05 2015 Return-Path: Delivered-To: freebsd-hackers@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 BF207A2A879 for ; Mon, 9 Nov 2015 16:59:05 +0000 (UTC) (envelope-from christophersacchi@gmail.com) Received: from mail-ig0-x22c.google.com (mail-ig0-x22c.google.com [IPv6:2607:f8b0:4001:c05::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 961C71C8E for ; Mon, 9 Nov 2015 16:59:05 +0000 (UTC) (envelope-from christophersacchi@gmail.com) Received: by igbhv6 with SMTP id hv6so79450572igb.0 for ; Mon, 09 Nov 2015 08:59:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=szVzj2byD6Q0CdbQmjndp7BBz0ZQVukp2oo38ax49kI=; b=aIdFuIY0qQPabwBztTV7VWhij60Kyo3c+3Icj9CK3sMysGDJ/Bz731XEwd84gU3iRd rLRXRNspxhLOWv/af/j7BNb63L8eVwOD3WRiuFTawWxfGbA1ZBBH4MUugrer20Qkz5yh 8D8gdhviCFfHXXgyQsahCc6HWTeOHqIjHx3JYPFkkRWzCCWibrqyJwL5iBq1MY5Ri5bX 4S1DkBaq2+0yBuFlbt1IPyquOvsPb7sJB52jQVye1DH+GNZQSFutK5yu6ubtxkdHQtQS YWXcZZzlPQukZ2HV6bvx9oj/66NPThEiWC2hRlcBcbqN5RiCXQwZ6tXat3kFRMvni3Fe H1uA== MIME-Version: 1.0 X-Received: by 10.50.150.37 with SMTP id uf5mr17230953igb.10.1447088344821; Mon, 09 Nov 2015 08:59:04 -0800 (PST) Received: by 10.79.96.67 with HTTP; Mon, 9 Nov 2015 08:59:04 -0800 (PST) Received: by 10.79.96.67 with HTTP; Mon, 9 Nov 2015 08:59:04 -0800 (PST) Date: Mon, 9 Nov 2015 11:59:04 -0500 Message-ID: Subject: 14 year old programmer would like to contribute code to FreeBSD From: Christopher Sacchi To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Nov 2015 16:59:05 -0000 Hey, My name is Chris, (in case you cannot already tell) and at a CodeDay event I realized I'm better at working in a team than by myself or when I lead it ATM, and because I love FreeBSD and Linux as well as programming (in the subject of the email) I would love to help whenever I can. Thanks, Chris PS for CodeDay go to http://codeday.org From owner-freebsd-hackers@freebsd.org Mon Nov 9 17:45:35 2015 Return-Path: Delivered-To: freebsd-hackers@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 34BA0A2A78A for ; Mon, 9 Nov 2015 17:45:35 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1b.ore.mailhop.org (outbound1b.ore.mailhop.org [54.200.247.200]) (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 16BB51A2E for ; Mon, 9 Nov 2015 17:45:34 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from ilsoft.org (unknown [73.34.117.227]) by outbound1.ore.mailhop.org (Halon Mail Gateway) with ESMTPSA; Mon, 9 Nov 2015 17:45:40 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.14.9/8.14.9) with ESMTP id tA9HjWke001317; Mon, 9 Nov 2015 10:45:32 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: <1447091132.91534.480.camel@freebsd.org> Subject: Re: dma From: Ian Lepore To: AlexHully , freebsd-hackers@freebsd.org Date: Mon, 09 Nov 2015 10:45:32 -0700 In-Reply-To: <298361446978177@web22g.yandex.ru> References: <298361446978177@web22g.yandex.ru> Content-Type: text/plain; charset="us-ascii" X-Mailer: Evolution 3.16.5 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Nov 2015 17:45:35 -0000 On Sun, 2015-11-08 at 11:22 +0100, AlexHully wrote: > Hi, > > I would like a clarification for dma. > > The context: most dma capable devices have 32 bits address range. > Is it correct that, if there was no 3G/1G mapping in the kernel, or > that kernel low memory could map 4Gb memory, one could choose any > free addresses in that low memory to set up a dma buffer? > > That would avoid all the mapping hassle, and performance cost > associated. > > Thanks There is more to DMA that just how many bits are in the address space. On platforms with software-assisted cache coherency such as ARM and MIPS, DMA usually must also be aligned to cacheline boundaries, and will be bounced if it is not. Plus, of course, it's also required that you perform the correct busdma sync operations before and after the DMA to keep the caches coherent. -- Ian From owner-freebsd-hackers@freebsd.org Mon Nov 9 19:48:36 2015 Return-Path: Delivered-To: freebsd-hackers@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 13169A2AF1E for ; Mon, 9 Nov 2015 19:48:36 +0000 (UTC) (envelope-from pfg@FreeBSD.org) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1.freebsd.org (Postfix) with SMTP id E02B912A3 for ; Mon, 9 Nov 2015 19:48:35 +0000 (UTC) (envelope-from pfg@FreeBSD.org) Received: (qmail 76529 invoked by uid 99); 9 Nov 2015 19:48:35 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Nov 2015 19:48:35 +0000 Received: from [192.168.0.103] (unknown [181.55.232.163]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id EE0ED1A012E; Mon, 9 Nov 2015 19:48:34 +0000 (UTC) From: Pedro Giffuni Subject: Re: 14 year old programmer would like to contribute code to FreeBSD Date: Mon, 9 Nov 2015 14:48:32 -0500 Message-Id: <7A6FD2A2-68A1-4B10-B528-886AE9CBA238@FreeBSD.org> Cc: "" To: Christopher Sacchi Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) X-Mailer: Apple Mail (2.2104) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Nov 2015 19:48:36 -0000 Hi Chris; Great to see you wanting to get involved in FreeBSD. FWIW, we had a 16 = yr. old developer once, so perhaps you will break the record ;). I would recommend starting with the ports tree (that=E2=80=99s how I got = started): https://www.freebsd.org/doc/en/books/porters-handbook/ = You could probably start updating some port of interest. Updating = something like editors/calligra would be really nice ;). Pedro.= From owner-freebsd-hackers@freebsd.org Mon Nov 9 20:28:33 2015 Return-Path: Delivered-To: freebsd-hackers@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 60B3BA2AC4A for ; Mon, 9 Nov 2015 20:28:33 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1b.ore.mailhop.org (outbound1b.ore.mailhop.org [54.200.247.200]) (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 3F8D31BD5 for ; Mon, 9 Nov 2015 20:28:32 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from ilsoft.org (unknown [73.34.117.227]) by outbound1.ore.mailhop.org (Halon Mail Gateway) with ESMTPSA; Mon, 9 Nov 2015 20:28:37 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.14.9/8.14.9) with ESMTP id tA9KSTeb001569; Mon, 9 Nov 2015 13:28:29 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: <1447100910.91534.526.camel@freebsd.org> Subject: Re: dma From: Ian Lepore To: Adrian Chadd Cc: AlexHully , "freebsd-hackers@freebsd.org" Date: Mon, 09 Nov 2015 13:28:30 -0700 In-Reply-To: References: <298361446978177@web22g.yandex.ru> <1447091132.91534.480.camel@freebsd.org> Content-Type: text/plain; charset="us-ascii" X-Mailer: Evolution 3.16.5 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Nov 2015 20:28:33 -0000 On Mon, 2015-11-09 at 12:27 -0800, Adrian Chadd wrote: > Hi, > > You still have 32 bit capable DMA machines on > 32 bit platform > devices. > > eg, the 36 bit PAE stuff on x86, or the PAE style stuff that showed > up > on powerpc, or 32 bit DMA devices on 64 bit intel/arm/mips platforms, > etc. > > Bounce buffers aren't going anywhere. > > > > -adrian I sure wish I knew what you were talking about. Why do you trim away all context? -- Ian From owner-freebsd-hackers@freebsd.org Mon Nov 9 20:27:25 2015 Return-Path: Delivered-To: freebsd-hackers@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 C6D18A2AC16 for ; Mon, 9 Nov 2015 20:27:25 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-ig0-x22d.google.com (mail-ig0-x22d.google.com [IPv6:2607:f8b0:4001: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 93CF61BAC; Mon, 9 Nov 2015 20:27:25 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by igcph11 with SMTP id ph11so35734039igc.1; Mon, 09 Nov 2015 12:27:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=rRtVbjWIBOE6n//+oo3zd49HkWaHDF94VOBYLDytkcw=; b=tJUeUngdD1KK+BvoVSUOuoMsMy9IZN3ZKDrKBMynTIr6fLEBhkcxZpLCMhgkWIZSRh /nqFWfVeTGZXCKAH/H71ncaESBAxbf1AGvjxq7GO+Ssme85N5Wy8i4guUCPYUthdkvfZ P9mRaJPzSmbN8JJgm6+h2wdYDVptPoqrilEerGRQ9GA0TnB3V1rQ3uAolmr9YifmbbhR IECXyPEdAOsVdb9Jm3Ep33H5MVxXr4X0nlKQdXSk9N6c7jMuDODwn98JKcYiZaYD3HEp Z/Lrqa+UqhoqSgcaT/DuDIQ/4MboJL5mPxskhZ4jkkwjEndUbA+PM4euw9cXz+EEUF77 z+yA== MIME-Version: 1.0 X-Received: by 10.50.155.41 with SMTP id vt9mr21027321igb.22.1447100844967; Mon, 09 Nov 2015 12:27:24 -0800 (PST) Received: by 10.36.217.196 with HTTP; Mon, 9 Nov 2015 12:27:24 -0800 (PST) In-Reply-To: <1447091132.91534.480.camel@freebsd.org> References: <298361446978177@web22g.yandex.ru> <1447091132.91534.480.camel@freebsd.org> Date: Mon, 9 Nov 2015 12:27:24 -0800 Message-ID: Subject: Re: dma From: Adrian Chadd To: Ian Lepore Cc: AlexHully , "freebsd-hackers@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Mailman-Approved-At: Mon, 09 Nov 2015 20:48:02 +0000 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Nov 2015 20:27:25 -0000 Hi, You still have 32 bit capable DMA machines on > 32 bit platform devices. eg, the 36 bit PAE stuff on x86, or the PAE style stuff that showed up on powerpc, or 32 bit DMA devices on 64 bit intel/arm/mips platforms, etc. Bounce buffers aren't going anywhere. -adrian From owner-freebsd-hackers@freebsd.org Mon Nov 9 21:15:38 2015 Return-Path: Delivered-To: freebsd-hackers@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 6E5BFA29ECF; Mon, 9 Nov 2015 21:15:38 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4C1A31DE6; Mon, 9 Nov 2015 21:15:38 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from ralph.baldwin.cx (c-73-231-226-104.hsd1.ca.comcast.net [73.231.226.104]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id E200EB923; Mon, 9 Nov 2015 16:15:35 -0500 (EST) From: John Baldwin To: freebsd-current@freebsd.org Cc: Hans Petter Selasky , Andriy Gapon , FreeBSD Current , FreeBSD Hackers Subject: Re: strange kernel crash Date: Mon, 09 Nov 2015 12:16:38 -0800 Message-ID: <2278845.gkxYBUMIWE@ralph.baldwin.cx> User-Agent: KMail/4.14.3 (FreeBSD/10.2-STABLE; KDE/4.14.3; amd64; ; ) In-Reply-To: <563CEB53.50909@selasky.org> References: <563C8CED.3020101@FreeBSD.org> <563CEB53.50909@selasky.org> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Mon, 09 Nov 2015 16:15:36 -0500 (EST) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Nov 2015 21:15:38 -0000 On Friday, November 06, 2015 07:02:59 PM Hans Petter Selasky wrote: > On 11/06/15 12:20, Andriy Gapon wrote: > > Now the strange part: > > > > 0xffffffff80619a18 <+744>: jne 0xffffffff80619a61 <__mtx_lock_flags+817> > > 0xffffffff80619a1a <+746>: mov %rbx,(%rsp) > > => 0xffffffff80619a1e <+750>: movq $0x0,0x18(%rsp) > > 0xffffffff80619a27 <+759>: movq $0x0,0x10(%rsp) > > 0xffffffff80619a30 <+768>: movq $0x0,0x8(%rsp) > > Were these instructions dumped from RAM or from the kernel ELF file? Probably not from RAM. You can use 'info files' in gdb to see what is handling the address range in question (core vs executable). x/i in ddb would have been the "real" truth. -- John Baldwin From owner-freebsd-hackers@freebsd.org Mon Nov 9 23:26:54 2015 Return-Path: Delivered-To: freebsd-hackers@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 EB115A2A7C7 for ; Mon, 9 Nov 2015 23:26:54 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from gold.funkthat.com (gate2.funkthat.com [208.87.223.18]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "gold.funkthat.com", Issuer "gold.funkthat.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id CACF01D1D for ; Mon, 9 Nov 2015 23:26:54 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from gold.funkthat.com (localhost [127.0.0.1]) by gold.funkthat.com (8.14.5/8.14.5) with ESMTP id tA9NQl5A076171 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 9 Nov 2015 15:26:47 -0800 (PST) (envelope-from jmg@gold.funkthat.com) Received: (from jmg@localhost) by gold.funkthat.com (8.14.5/8.14.5/Submit) id tA9NQl5P076170; Mon, 9 Nov 2015 15:26:47 -0800 (PST) (envelope-from jmg) Date: Mon, 9 Nov 2015 15:26:47 -0800 From: John-Mark Gurney To: Christopher Sacchi Cc: freebsd-hackers@freebsd.org Subject: Re: 14 year old programmer would like to contribute code to FreeBSD Message-ID: <20151109232647.GL65715@funkthat.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 9.1-PRERELEASE amd64 X-PGP-Fingerprint: 54BA 873B 6515 3F10 9E88 9322 9CB1 8F74 6D3F A396 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html X-TipJar: bitcoin:13Qmb6AeTgQecazTWph4XasEsP7nGRbAPE X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? User-Agent: Mutt/1.5.21 (2010-09-15) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (gold.funkthat.com [127.0.0.1]); Mon, 09 Nov 2015 15:26:48 -0800 (PST) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Nov 2015 23:26:55 -0000 Christopher Sacchi wrote this message on Mon, Nov 09, 2015 at 11:59 -0500: > My name is Chris, (in case you cannot already tell) and at a CodeDay event > I realized I'm better at working in a team than by myself or when I lead it > ATM, and because I love FreeBSD and Linux as well as programming (in the > subject of the email) I would love to help whenever I can. Ports is a good way to get started, but you can also look at the bug database (https://bugs.freebsd.org/bugzilla/) for bugs that look interesting to track down. There is also a list of tasks that people have put together too: https://wiki.freebsd.org/JuniorJobs Best way is just start using it, and when you see a rough edge, contact a responsible developer and work on it. Good luck! -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-hackers@freebsd.org Mon Nov 9 23:34:39 2015 Return-Path: Delivered-To: freebsd-hackers@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 5F5D2A2A9CC for ; Mon, 9 Nov 2015 23:34:39 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from gold.funkthat.com (gate2.funkthat.com [208.87.223.18]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "gold.funkthat.com", Issuer "gold.funkthat.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4521C11A9 for ; Mon, 9 Nov 2015 23:34:39 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from gold.funkthat.com (localhost [127.0.0.1]) by gold.funkthat.com (8.14.5/8.14.5) with ESMTP id tA9NYcR3076256 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 9 Nov 2015 15:34:38 -0800 (PST) (envelope-from jmg@gold.funkthat.com) Received: (from jmg@localhost) by gold.funkthat.com (8.14.5/8.14.5/Submit) id tA9NYctW076255; Mon, 9 Nov 2015 15:34:38 -0800 (PST) (envelope-from jmg) Date: Mon, 9 Nov 2015 15:34:38 -0800 From: John-Mark Gurney To: AlexHully Cc: freebsd-hackers@freebsd.org Subject: Re: dma Message-ID: <20151109233438.GM65715@funkthat.com> References: <298361446978177@web22g.yandex.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <298361446978177@web22g.yandex.ru> X-Operating-System: FreeBSD 9.1-PRERELEASE amd64 X-PGP-Fingerprint: 54BA 873B 6515 3F10 9E88 9322 9CB1 8F74 6D3F A396 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html X-TipJar: bitcoin:13Qmb6AeTgQecazTWph4XasEsP7nGRbAPE X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? User-Agent: Mutt/1.5.21 (2010-09-15) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (gold.funkthat.com [127.0.0.1]); Mon, 09 Nov 2015 15:34:38 -0800 (PST) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Nov 2015 23:34:39 -0000 AlexHully wrote this message on Sun, Nov 08, 2015 at 11:22 +0100: > I would like a clarification for dma. > > The context: most dma capable devices have 32 bits address range. Depends upon the bus, and now w/ PCIe, 64bit is commonly supported... > Is it correct that, if there was no 3G/1G mapping in the kernel, or that kernel low memory could map 4Gb memory, one could choose any free addresses in that low memory to set up a dma buffer? I assume you're talking about i386... If you are, the kernel/userland mapping split has nothing to do w/ DMA... the 3G/1G split is a virtual address space construct and DMA purely deals w/ the physical memory layout. Or are you talking about the 3G/1G physical memory, PCI device hole? On non-PAE i386 systems (with only 32bit physical addressing), there is no performance impact when dealing w/ a 32bit only capabile DMA device as all of physical memory is addressable. -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-hackers@freebsd.org Tue Nov 10 06:05:59 2015 Return-Path: Delivered-To: freebsd-hackers@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 A56A3A2A06A for ; Tue, 10 Nov 2015 06:05:59 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (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 783C01C6B for ; Tue, 10 Nov 2015 06:05:59 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from Julian-MBP3.local (ppp121-45-229-78.lns20.per1.internode.on.net [121.45.229.78]) (authenticated bits=0) by vps1.elischer.org (8.15.2/8.15.2) with ESMTPSA id tAA65s6b085837 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 9 Nov 2015 22:05:57 -0800 (PST) (envelope-from julian@freebsd.org) Subject: Re: 14 year old programmer would like to contribute code to FreeBSD To: Christopher Sacchi , freebsd-hackers@freebsd.org References: From: Julian Elischer Message-ID: <5641893C.4060708@freebsd.org> Date: Tue, 10 Nov 2015 14:05:48 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Nov 2015 06:05:59 -0000 On 11/10/15 12:59 AM, Christopher Sacchi wrote: > Hey, > > My name is Chris, (in case you cannot already tell) and at a CodeDay event > I realized I'm better at working in a team than by myself or when I lead it > ATM, and because I love FreeBSD and Linux as well as programming (in the > subject of the email) I would love to help whenever I can. Hi chris, Being an open source project, FreeBSD is basically yours to do with what you will. Find something that interests you and try understand it. Almost anything. That's pretty much how we all started. You don't need an invitation. (and you won't get one :-) ) Probably as you are just starting out you'll not immediately reinvent the answer to world famine or even a better wifi driver, but if you're enjoying yourself that doesn't matter. If you ARE enjoying yourself, then EVENTUALLY you'll see something that's just broken, or you can see how it can be improved. look in the web source interface for some of the last people to touch that code. ( https://svnweb.freebsd.org/ ) and just email the last 3 people with your idea. if they are still active (some people decide to go get real lives some times) you'll probably get a reply and you can run the idea past them. As a beginner you'll probably find there are sides of the problem you just hadn't realised, like "backwards compatibility" or "POLA" .. look it up :-) https://www.freebsd.org/doc/handbook/freebsd-glossary.html Don't get discouraged. Speak up on the mailing lists and you'll get to know people and people will get to know you. It won't happen over night, but nothing worth while does. Julian > > Thanks, > Chris > > PS for CodeDay go to http://codeday.org > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > From owner-freebsd-hackers@freebsd.org Tue Nov 10 06:20:11 2015 Return-Path: Delivered-To: freebsd-hackers@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 79972A2A68D for ; Tue, 10 Nov 2015 06:20:11 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from mx1.scaleengine.net (mx1.scaleengine.net [209.51.186.6]) by mx1.freebsd.org (Postfix) with ESMTP id 52491111B for ; Tue, 10 Nov 2015 06:20:11 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from [10.1.1.2] (unknown [10.1.1.2]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 77399D0C3; Tue, 10 Nov 2015 06:20:09 +0000 (UTC) Subject: Re: 14 year old programmer would like to contribute code to FreeBSD To: Christopher Sacchi , freebsd-hackers@freebsd.org References: From: Allan Jude Message-ID: <56418C9F.8080406@freebsd.org> Date: Tue, 10 Nov 2015 01:20:15 -0500 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="D0NSXHcJpGrn1J5S2hFvX1quANlaa2NrL" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Nov 2015 06:20:11 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --D0NSXHcJpGrn1J5S2hFvX1quANlaa2NrL Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 2015-11-09 11:59, Christopher Sacchi wrote: > Hey, >=20 > My name is Chris, (in case you cannot already tell) and at a CodeDay ev= ent > I realized I'm better at working in a team than by myself or when I lea= d it > ATM, and because I love FreeBSD and Linux as well as programming (in th= e > subject of the email) I would love to help whenever I can. >=20 > Thanks, > Chris >=20 > PS for CodeDay go to http://codeday.org > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.o= rg" >=20 If you are looking for additional beginner friendly ways to get started: libxo: https://wiki.freebsd.org/LibXo (make programs able to emit json/xml/etc instead of just text) and libucl: https://wiki.freebsd.org/201506DevSummit/UCL (universal config language, making nicer config files) You can contact me, or others working on these areas if you would like more information or help getting started. --=20 Allan Jude --D0NSXHcJpGrn1J5S2hFvX1quANlaa2NrL 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) iQIcBAEBAgAGBQJWQYyiAAoJEBmVNT4SmAt+hcEQAKq+bRV7rdUME+O3yH8yvjdt RTmQtlBsGVB7pWBlV5ahx3jKFdDSOr6cyzzmM+5WHFlXFiqVIzSsQror/kFAhKPc MlMnG4S+fuE1lU5Y2DVSSjWcmF3YsDeuabZy274d8ottWhAVuQRK7zBAcmn6X+Kn XwKWrE6ypHhTK8UiwVDNg2mCd7ADH9vTFGEIcVIjniqwLByKnODcl3xivebN6Lep l9cZvEYNCbpvrtM+pkFRQq1CqPNNoJytzXOENWnGrDAl7P1pIF5ioZd0bcg0PEvT JPZs6zfQNVW0GRATQAGHKJzhRfpaiQc/EGHY8R9Dd3zbFRyA8Vkr8U0o1EOkD8la 7vvIH2FUYNHiDE6+V9iIdBPm+1CyQryrW3gzjRnvymlSUd+GtYP9wVSqLdm/pdMp lQGuQOD4a76SHRVBH7I4YmFPW5ncUWAb1TMxl7jC2pRBCI/uQiZjWQzZqGey9wWa bPlyjvrc06Qo5GNaPa1nJ0oDuDL1vzpDWv6zkbiv2D/mewIMra5PqCSGtm6GIVGK 4F9BrJGOzchZf2j96+c3p09zlv8ZnM9ZjhSEB90FJGpbJtA27f480gM5EgaH6OXE 99RzAFl1vFvHyUsR2iUTNfTgybNgbJLgKRCQXItpMmeslsVtAwyjaRE8XoWbA/k7 XLK4rUdf6LgHd+IxdS44 =GDYw -----END PGP SIGNATURE----- --D0NSXHcJpGrn1J5S2hFvX1quANlaa2NrL-- From owner-freebsd-hackers@freebsd.org Tue Nov 10 06:57:41 2015 Return-Path: Delivered-To: freebsd-hackers@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 D679FA2B136 for ; Tue, 10 Nov 2015 06:57:41 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from vps.rulingia.com (vps.rulingia.com [103.243.244.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps.rulingia.com", Issuer "CAcert Class 3 Root" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 68F6210A3 for ; Tue, 10 Nov 2015 06:57:40 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from server.rulingia.com (c220-239-242-83.belrs5.nsw.optusnet.com.au [220.239.242.83]) by vps.rulingia.com (8.15.2/8.15.2) with ESMTPS id tAA6vMCi074169 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 10 Nov 2015 17:57:28 +1100 (AEDT) (envelope-from peter@rulingia.com) X-Bogosity: Ham, spamicity=0.000000 Received: from server.rulingia.com (localhost.rulingia.com [127.0.0.1]) by server.rulingia.com (8.15.2/8.15.2) with ESMTPS id tAA6vGYq072277 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 10 Nov 2015 17:57:16 +1100 (AEDT) (envelope-from peter@server.rulingia.com) Received: (from peter@localhost) by server.rulingia.com (8.15.2/8.15.2/Submit) id tAA6vEMr072276; Tue, 10 Nov 2015 17:57:14 +1100 (AEDT) (envelope-from peter) Date: Tue, 10 Nov 2015 17:57:14 +1100 From: Peter Jeremy To: Christopher Sacchi Cc: freebsd-hackers@freebsd.org Subject: Re: 14 year old programmer would like to contribute code to FreeBSD Message-ID: <20151110065714.GA72199@server.rulingia.com> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="T4sUOijqQbZv57TR" Content-Disposition: inline In-Reply-To: X-PGP-Key: http://www.rulingia.com/keys/peter.pgp User-Agent: Mutt/1.5.24 (2015-08-30) X-Greylist: Sender succeeded STARTTLS authentication, not delayed by milter-greylist-4.4.3 (vps.rulingia.com [103.243.244.15]); Tue, 10 Nov 2015 17:57:29 +1100 (AEDT) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Nov 2015 06:57:42 -0000 --T4sUOijqQbZv57TR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Chris, On 2015-Nov-09 11:59:04 -0500, Christopher Sacchi wrote: >My name is Chris, (in case you cannot already tell) and at a CodeDay event >I realized I'm better at working in a team than by myself or when I lead it >ATM, and because I love FreeBSD and Linux as well as programming (in the >subject of the email) I would love to help whenever I can. You don't mention what you've already done with/on FreeBSD so it's difficult to know what level to pitch things to you at. As well as looking through existing bug reports, you could also try running FreeBSD-current and seeing what issues you run into. This is especially true if you have access to unusual hardware (like non-x86 stuff). You could also see if there are any user groups near you. --=20 Peter Jeremy --T4sUOijqQbZv57TR Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJWQZVKXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRFRUIyOTg2QzMwNjcxRTc0RTY1QzIyN0Ux NkE1OTdBMEU0QTIwQjM0AAoJEBall6Dkogs0UyUP/1ZdcjMtlvO/+02o6jdOqvhP oVdz1aM/otnz0Tch242nY2PJzjWx47fxuTRT8EBPiUzw1jl/if+agBezXO6KV9VK ceMCnMwOAKv/Puv7kqjTVLkwoiQFatvYmfTm1tf6CN/keSDgKbJHSn6VQ60pceXV ZvV7cdiNlYCE3TFDfpdrQYVPRz/KYyna3Q3XynnID/0d6ShJGBunkYyrJvQaodaI Tm5K2Xe/NEK9a8/KWIO+OPqnJ111JhagWyUmAzo11bLQ33X9lfQmU2cAsUcL1O54 99115f6t4LMzJIzXeyimcOBVotiMN5ga46rgGcIMBGT7VoVjPVXc88+IzHMKNq+m Ju1u7azgIPYbbVGVDomcLErY+CGROeC2xBZ6wnRpy1USuHsItkEev42to4zf7fFs c2PAxikeJVTwx33S20RTPiLzV33x7KNg6/TDylax2SOPbPtJHXy8sgT2iaz3Giz0 /6EeMLk3sce7CIno64WOnpQgGQvIzV/oiYMGiZ1dV3V5VPr+Rpq9tB+XWlW0gbpn Emy6ltqbDABPPhw/lZTf96OL4yApIbMDvWcBQazdMoGZpMYPkOd745qUltd3+CJh 63D4ogECjnjuGAu6I7+1CrwwZKx5Magg0z1NMtMC/mYXazjQ6qvLWUaZsvEXsFJJ ZJPkTcUT/HN+3K8tLlDU =Rw1S -----END PGP SIGNATURE----- --T4sUOijqQbZv57TR-- From owner-freebsd-hackers@freebsd.org Tue Nov 10 07:54:18 2015 Return-Path: Delivered-To: freebsd-hackers@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 1940EA2A654 for ; Tue, 10 Nov 2015 07:54:18 +0000 (UTC) (envelope-from radovanovic@gmail.com) Received: from mail-wm0-x22b.google.com (mail-wm0-x22b.google.com [IPv6:2a00:1450:400c:c09::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 A4C6D127F for ; Tue, 10 Nov 2015 07:54:17 +0000 (UTC) (envelope-from radovanovic@gmail.com) Received: by wmww144 with SMTP id w144so63876922wmw.0 for ; Mon, 09 Nov 2015 23:54:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=P6xbWbeuBtRUB/H/8C5y3taZMlnvnUoxsVECiy0Eg5s=; b=Y2RQ/93X/dM1w710yJyyIOSP7L0Se7Ifhsw5UkeZRjZIAG44YQO4M2Lj75KOVF/CYy ul386I9MVQqQnS9/MIoI1SP8fuX0SmeCdGHTTzNPceaqc+Rz1+Ocai0FwrInuQE27rV2 J644TMGkcyqdFfRHTSwTCw94DLSow2naLxTic8LVJcXvrqyM271LFx7y53NAF5uS50dK lr9KENXPx/CsQR6cYk/2wxd08O0HkiC55gGbJJvh2+W9yxhCwXXP4CFmJtocmACAb+G5 LMQPryPT3GCsybITKmiwvHZumJ1t6zw5sulyl1uVxnL/B1fpoHnciShzoYgDYE5jL2LR 1OGw== X-Received: by 10.194.7.97 with SMTP id i1mr2552907wja.87.1447142055256; Mon, 09 Nov 2015 23:54:15 -0800 (PST) Received: from zmaj.softwarehood.com (93-87-243-129.dynamic.isp.telekom.rs. [93.87.243.129]) by smtp.googlemail.com with ESMTPSA id c1sm2033174wjf.19.2015.11.09.23.54.14 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 09 Nov 2015 23:54:14 -0800 (PST) Message-ID: <5641A2A5.7070909@gmail.com> Date: Tue, 10 Nov 2015 08:54:13 +0100 From: Ivan Radovanovic User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130812 Thunderbird/17.0.8 MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.org Subject: Detecting new file name after receiving kevent's NOTE_RENAME Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Nov 2015 07:54:18 -0000 What is the best practice for discovering new file name after receiving kevent(2) NOTE_RENAME on its descriptor? At the moment I am storing fileno from dirent(5) structure together with descriptor and name, and when I receive NOTE_RENAME I re-read directory and use it (fileno) to discover new name, but this obviously requires re-reading entire directory on each NOTE_RENAME. I am wondering is there some more clever way to get this new name (kernel is obviously aware of it, otherwise it couldn't notify descriptor about rename)? Kind regards, Ivan From owner-freebsd-hackers@freebsd.org Tue Nov 10 08:14:26 2015 Return-Path: Delivered-To: freebsd-hackers@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 E4EC2A2B21C for ; Tue, 10 Nov 2015 08:14:26 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5FD091F20 for ; Tue, 10 Nov 2015 08:14:26 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id tAA8ELQY024055 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 10 Nov 2015 10:14:21 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua tAA8ELQY024055 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id tAA8ELtA024049; Tue, 10 Nov 2015 10:14:21 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Tue, 10 Nov 2015 10:14:21 +0200 From: Konstantin Belousov To: Ivan Radovanovic Cc: freebsd-hackers@FreeBSD.org Subject: Re: Detecting new file name after receiving kevent's NOTE_RENAME Message-ID: <20151110081421.GL2257@kib.kiev.ua> References: <5641A2A5.7070909@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5641A2A5.7070909@gmail.com> User-Agent: Mutt/1.5.24 (2015-08-30) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Nov 2015 08:14:27 -0000 On Tue, Nov 10, 2015 at 08:54:13AM +0100, Ivan Radovanovic wrote: > What is the best practice for discovering new file name after receiving > kevent(2) NOTE_RENAME on its descriptor? > > At the moment I am storing fileno from dirent(5) structure together with > descriptor and name, and when I receive NOTE_RENAME I re-read directory > and use it (fileno) to discover new name, but this obviously requires > re-reading entire directory on each NOTE_RENAME. NOTE_RENAME means that the file backing the given file descriptor was renamed, not that some directory entry in the contained directory renamed. In particular, the new dirent for the file, for which you get the notification, may belong to some other directory. As such, scanning the directory which contained the file before rename is useless. > > I am wondering is there some more clever way to get this new name > (kernel is obviously aware of it, otherwise it couldn't notify > descriptor about rename)? The most correct way is to use sysctl kern.proc.filedesc and look for the path of the given file descriptor. This is inefficient since kern.proc.filedesc returns information about all opened files for the process. If somebody cares about this, she should implement e.g. sysctl kern.proc.onefd which takes both pid and filedescriptor, to return single fileinfo structure for given file descriptor. From owner-freebsd-hackers@freebsd.org Tue Nov 10 08:49:44 2015 Return-Path: Delivered-To: freebsd-hackers@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 1F61DA2BDCF; Tue, 10 Nov 2015 08:49:44 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id D0B521251; Tue, 10 Nov 2015 08:49:42 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id KAA06657; Tue, 10 Nov 2015 10:49:34 +0200 (EET) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1Zw4cP-000EdF-3g; Tue, 10 Nov 2015 10:49:34 +0200 Subject: Re: strange kernel crash To: John Baldwin , freebsd-current@FreeBSD.org References: <563C8CED.3020101@FreeBSD.org> <563CEB53.50909@selasky.org> <2278845.gkxYBUMIWE@ralph.baldwin.cx> Cc: Hans Petter Selasky , FreeBSD Hackers From: Andriy Gapon X-Enigmail-Draft-Status: N1110 Message-ID: <5641AF48.1000507@FreeBSD.org> Date: Tue, 10 Nov 2015 10:48:08 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <2278845.gkxYBUMIWE@ralph.baldwin.cx> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Nov 2015 08:49:44 -0000 On 09/11/2015 22:16, John Baldwin wrote: > On Friday, November 06, 2015 07:02:59 PM Hans Petter Selasky wrote: >> On 11/06/15 12:20, Andriy Gapon wrote: >>> Now the strange part: >>> >>> 0xffffffff80619a18 <+744>: jne 0xffffffff80619a61 <__mtx_lock_flags+817> >>> 0xffffffff80619a1a <+746>: mov %rbx,(%rsp) >>> => 0xffffffff80619a1e <+750>: movq $0x0,0x18(%rsp) >>> 0xffffffff80619a27 <+759>: movq $0x0,0x10(%rsp) >>> 0xffffffff80619a30 <+768>: movq $0x0,0x8(%rsp) >> >> Were these instructions dumped from RAM or from the kernel ELF file? > > Probably not from RAM. You can use 'info files' in gdb to see what is > handling the address range in question (core vs executable). x/i in ddb > would have been the "real" truth. Yes, according to the output of files it looks like gdb would read that data from the text section of the kernel file. How about libkvm? Would kvm_read read data from the core file? I've written the following small program (cut down dmesg.c, actually): https://people.freebsd.org/~avg/vmcore_read.c (kgdb) disassemble /r => 0xffffffff80619a1e <+750>: 48 c7 44 24 18 00 00 00 00 movq $0x0,0x18(%rsp) $ vmcore_read -N /boot/kernel.29/kernel -M /var/crash/vmcore.29 0xffffffff80619a1e 9 48 c7 44 24 18 00 00 00 00 Seems like the code is intact. P.S. 1. To correct something I said earlier, the fault is #UD, not #GP. 2. The only "suspicious" activity at the time of the crash was the execution of a bhyve VM. -- Andriy Gapon From owner-freebsd-hackers@freebsd.org Tue Nov 10 09:20:19 2015 Return-Path: Delivered-To: freebsd-hackers@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 BC1A1A2AB8A for ; Tue, 10 Nov 2015 09:20:19 +0000 (UTC) (envelope-from radovanovic@gmail.com) Received: from mail-wm0-x22d.google.com (mail-wm0-x22d.google.com [IPv6:2a00:1450:400c:c09::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 5186E102B for ; Tue, 10 Nov 2015 09:20:19 +0000 (UTC) (envelope-from radovanovic@gmail.com) Received: by wmec201 with SMTP id c201so105061600wme.1 for ; Tue, 10 Nov 2015 01:20:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=45oXpxFJ32MsbQblZqiX0LkVqK8BjzuivVd/Hiy6FsY=; b=s8SgYU5Xg5+mgt2er3gGsilP/VcaGCdSPW4cZuQ01vyFkwlEV/1PCdv5j2sJsMbvm8 wpqyYxWbXdYMxuVQ1UekZhjKvcJO/h/5Y8HmfqYxVAupVrFeR0w3PncEVklvj0ibSxr+ wMKw9tK3DzYJLI1DpmbCswZygHAZeBzqzQ4hAvPC5oydUWkiJUXQxPc4xkSK/etPNgi8 jqL8HDB+7ELKzaIR97TsfIdlWTF521Ia5kZTWBRIXFfUE0pEsAj5ntXnwF3aHX42vJE4 UZB75Ui1oSu5bX64AenflVSorZkf/7GQHOUElgVXrzjK8cKR7a7gp8cZ3jnq06TVC9U2 /OTQ== X-Received: by 10.194.90.98 with SMTP id bv2mr2664685wjb.78.1447147217551; Tue, 10 Nov 2015 01:20:17 -0800 (PST) Received: from zmaj.softwarehood.com (93-87-243-129.dynamic.isp.telekom.rs. [93.87.243.129]) by smtp.googlemail.com with ESMTPSA id iw8sm2434509wjb.5.2015.11.10.01.20.16 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 10 Nov 2015 01:20:16 -0800 (PST) Message-ID: <5641B6D0.4070207@gmail.com> Date: Tue, 10 Nov 2015 10:20:16 +0100 From: Ivan Radovanovic User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130812 Thunderbird/17.0.8 MIME-Version: 1.0 To: Konstantin Belousov CC: freebsd-hackers@FreeBSD.org Subject: Re: Detecting new file name after receiving kevent's NOTE_RENAME References: <5641A2A5.7070909@gmail.com> <20151110081421.GL2257@kib.kiev.ua> In-Reply-To: <20151110081421.GL2257@kib.kiev.ua> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Nov 2015 09:20:19 -0000 On 11/10/15 09:14, Konstantin Belousov napisa: > On Tue, Nov 10, 2015 at 08:54:13AM +0100, Ivan Radovanovic wrote: >> What is the best practice for discovering new file name after receiving >> kevent(2) NOTE_RENAME on its descriptor? >> >> At the moment I am storing fileno from dirent(5) structure together with >> descriptor and name, and when I receive NOTE_RENAME I re-read directory >> and use it (fileno) to discover new name, but this obviously requires >> re-reading entire directory on each NOTE_RENAME. > NOTE_RENAME means that the file backing the given file descriptor was > renamed, not that some directory entry in the contained directory > renamed. In particular, the new dirent for the file, for which you get > the notification, may belong to some other directory. As such, scanning > the directory which contained the file before rename is useless. > >> >> I am wondering is there some more clever way to get this new name >> (kernel is obviously aware of it, otherwise it couldn't notify >> descriptor about rename)? > The most correct way is to use sysctl kern.proc.filedesc and look > for the path of the given file descriptor. This is inefficient since > kern.proc.filedesc returns information about all opened files for the > process. > > If somebody cares about this, she should implement e.g. sysctl > kern.proc.onefd which takes both pid and filedescriptor, to return > single fileinfo structure for given file descriptor. > Thanks, kern.proc.filedesc is super-efficient compared to what I had in mind. I assume right way to use it would be through kinfo_getfile(3). From owner-freebsd-hackers@freebsd.org Tue Nov 10 12:13:18 2015 Return-Path: Delivered-To: freebsd-hackers@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 9EDC4A2A669 for ; Tue, 10 Nov 2015 12:13:18 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 31D0A14A2 for ; Tue, 10 Nov 2015 12:13:18 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id tAACD9mo092572 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 10 Nov 2015 14:13:09 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua tAACD9mo092572 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id tAACD9fj092571; Tue, 10 Nov 2015 14:13:09 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Tue, 10 Nov 2015 14:13:09 +0200 From: Konstantin Belousov To: Ivan Radovanovic Cc: freebsd-hackers@FreeBSD.org Subject: Re: Detecting new file name after receiving kevent's NOTE_RENAME Message-ID: <20151110121309.GO2257@kib.kiev.ua> References: <5641A2A5.7070909@gmail.com> <20151110081421.GL2257@kib.kiev.ua> <5641B6D0.4070207@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5641B6D0.4070207@gmail.com> User-Agent: Mutt/1.5.24 (2015-08-30) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Nov 2015 12:13:18 -0000 On Tue, Nov 10, 2015 at 10:20:16AM +0100, Ivan Radovanovic wrote: > Thanks, kern.proc.filedesc is super-efficient compared to what I had in > mind. I assume right way to use it would be through kinfo_getfile(3). Both direct sysctl use and kinfo_getfile() are supported, in the sense that the API and ABI of the interfaces are not supposed to change in non-backward compatible way, and the interfaces itself are not supposed to disappear. From owner-freebsd-hackers@freebsd.org Tue Nov 10 19:49:51 2015 Return-Path: Delivered-To: freebsd-hackers@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 4BC09A2CC15 for ; Tue, 10 Nov 2015 19:49:51 +0000 (UTC) (envelope-from radovanovic@gmail.com) Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::233]) (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 D578314CA for ; Tue, 10 Nov 2015 19:49:50 +0000 (UTC) (envelope-from radovanovic@gmail.com) Received: by wmec201 with SMTP id c201so150824064wme.0 for ; Tue, 10 Nov 2015 11:49:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=30HtG4j6bNXNXru5ZAwtyLDnC9hwR2ac2b7jGs8gm7o=; b=V6Aq7XxrN2OHZvOBHqUM3gP6aAskH4xC2b6uZSsYf8H97eoHE6NQIl0vr79UaO9+v3 XCQc56PJl6m8DJV1os6FfqKrQSEtj2uMgWVN8sYwaIoDyI2uRudz8V4299T2FXarLEXE wzhzvKZiNRB6txIt54HMM5WikvARJKoC6ulY75xC//gTf9ta8VAcJvKgIvLginPvMr9N 9QO9rr7vOOztdmRwVv+44xKqGLxCNbyFsjfIXjxZcs2zlllZvpSzIlBc/tyiXieCE4NX xXFhf66xw7p2goKJ1nVy36AlppqfqIp41ewlbHGuZXknSqN20QBRg3O1s7EbUSpGt+kA ld0g== X-Received: by 10.194.110.38 with SMTP id hx6mr6924850wjb.41.1447184989433; Tue, 10 Nov 2015 11:49:49 -0800 (PST) Received: from zmaj.softwarehood.com (93-87-243-129.dynamic.isp.telekom.rs. [93.87.243.129]) by smtp.googlemail.com with ESMTPSA id q1sm5176489wjy.31.2015.11.10.11.49.48 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 10 Nov 2015 11:49:48 -0800 (PST) Message-ID: <56424A5B.3070208@gmail.com> Date: Tue, 10 Nov 2015 20:49:47 +0100 From: Ivan Radovanovic User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130812 Thunderbird/17.0.8 MIME-Version: 1.0 To: Konstantin Belousov CC: freebsd-hackers@FreeBSD.org Subject: Re: Detecting new file name after receiving kevent's NOTE_RENAME References: <5641A2A5.7070909@gmail.com> <20151110081421.GL2257@kib.kiev.ua> <5641B6D0.4070207@gmail.com> <20151110121309.GO2257@kib.kiev.ua> In-Reply-To: <20151110121309.GO2257@kib.kiev.ua> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Nov 2015 19:49:51 -0000 On 11/10/15 13:13, Konstantin Belousov napisa: > On Tue, Nov 10, 2015 at 10:20:16AM +0100, Ivan Radovanovic wrote: >> Thanks, kern.proc.filedesc is super-efficient compared to what I had in >> mind. I assume right way to use it would be through kinfo_getfile(3). > > Both direct sysctl use and kinfo_getfile() are supported, in the sense > that the API and ABI of the interfaces are not supposed to change in > non-backward compatible way, and the interfaces itself are not supposed > to disappear. > Thanks. After *lot* of copying structures from C to C# I got to the file structure, but it doesn't seem obvious to me how to get to the file name from there? From owner-freebsd-hackers@freebsd.org Tue Nov 10 20:01:30 2015 Return-Path: Delivered-To: freebsd-hackers@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 425FBA2CE57 for ; Tue, 10 Nov 2015 20:01:30 +0000 (UTC) (envelope-from radovanovic@gmail.com) Received: from mail-wm0-x235.google.com (mail-wm0-x235.google.com [IPv6:2a00:1450:400c:c09::235]) (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 CBE621A7D for ; Tue, 10 Nov 2015 20:01:29 +0000 (UTC) (envelope-from radovanovic@gmail.com) Received: by wmec201 with SMTP id c201so151279867wme.0 for ; Tue, 10 Nov 2015 12:01:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=J+5a0R2d60/HlzFkHec/qwgRq3spynglwrRa5lQ9f1s=; b=M3Ux9KA8SsJ0d2LvRG/UHytGHa00FreOJRzJwKY5Os0QGo3utNpTKr3LVzaggnrtPV 6kFrNmr3cpQ1+xy2456PbTZzqcxUpi//GyWdPphShqLy6LgU4c0GldvtJ2FtSkpDsR5o u9OXzoGfvxbTI1nGBY0y5ddTVy6I6OGwj8h50mDjbVbHgBB99WPeXBd2MfmSuU3gK++7 ogqrRrS+Cciv0HAoaHVRQcl3Rng7h/HbNMAyB2tZyVctvqfmU3OlRo7lZy5aqkDG915C H00OAx8vgIMAJcinZ7Q8VUeQV4nAqHNeSBwN5Fbz4a2X4Tc9lwcqHhe+qGWTq+O5yhRh 0UdQ== X-Received: by 10.194.200.233 with SMTP id jv9mr5910541wjc.133.1447185688310; Tue, 10 Nov 2015 12:01:28 -0800 (PST) Received: from zmaj.softwarehood.com (93-87-243-129.dynamic.isp.telekom.rs. [93.87.243.129]) by smtp.googlemail.com with ESMTPSA id cw3sm1038833wjb.26.2015.11.10.12.01.27 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 10 Nov 2015 12:01:27 -0800 (PST) Message-ID: <56424D17.3060303@gmail.com> Date: Tue, 10 Nov 2015 21:01:27 +0100 From: Ivan Radovanovic User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130812 Thunderbird/17.0.8 MIME-Version: 1.0 To: Konstantin Belousov CC: freebsd-hackers@FreeBSD.org Subject: Re: Detecting new file name after receiving kevent's NOTE_RENAME References: <5641A2A5.7070909@gmail.com> <20151110081421.GL2257@kib.kiev.ua> <5641B6D0.4070207@gmail.com> <20151110121309.GO2257@kib.kiev.ua> <56424A5B.3070208@gmail.com> In-Reply-To: <56424A5B.3070208@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Nov 2015 20:01:30 -0000 On 11/10/15 20:49, Ivan Radovanovic napisa: > On 11/10/15 13:13, Konstantin Belousov napisa: >> On Tue, Nov 10, 2015 at 10:20:16AM +0100, Ivan Radovanovic wrote: >>> Thanks, kern.proc.filedesc is super-efficient compared to what I had in >>> mind. I assume right way to use it would be through kinfo_getfile(3). >> >> Both direct sysctl use and kinfo_getfile() are supported, in the sense >> that the API and ABI of the interfaces are not supposed to change in >> non-backward compatible way, and the interfaces itself are not supposed >> to disappear. >> > > Thanks. After *lot* of copying structures from C to C# I got to the file > structure, but it doesn't seem obvious to me how to get to the file name > from there? Ignore previous email, I wasted time copying kinfo_proc instead of kinfo_file... From owner-freebsd-hackers@freebsd.org Tue Nov 10 21:23:35 2015 Return-Path: Delivered-To: freebsd-hackers@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 E36D8A2C272 for ; Tue, 10 Nov 2015 21:23:35 +0000 (UTC) (envelope-from radovanovic@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 790FC138B for ; Tue, 10 Nov 2015 21:23:35 +0000 (UTC) (envelope-from radovanovic@gmail.com) Received: by wmdw130 with SMTP id w130so89061714wmd.0 for ; Tue, 10 Nov 2015 13:23:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=jWUKE/lll9o8jvKahn5UDq7n4S4UsTpAsibB32D58Is=; b=ZDfep9VcDPwvxjXcS7i4OGUXek/cS4hje4YsAt4z5hy1yp0SDzIvUYFQNhwBHOakqL x4XAGPD6LD+zSt1EIy+Dvc5DPfgDntjq2WoTM9BbI8BKoSem5PX54vvk0ELO1tO6GJhq hftZ2zOGMBEChdPCtoJ1/AypXJNXUf/ZSjxp07rxgO/xRxcBQ3Z6PF9vah4Wk/3lyKXN CMqRWSODnk7TV1FXB8k7QKi4I9/9VvP2XdkLKooqZE2O0OiUWCeoSN7j9y/PNVRptDtL OVPKAx0uGBeIiHtQ91TXzV6ToWsOqwFaJMj5MOVp2zLjtb9TRORuKUjmOUIAMoLMneXr lzkw== X-Received: by 10.194.133.233 with SMTP id pf9mr5377428wjb.71.1447190613871; Tue, 10 Nov 2015 13:23:33 -0800 (PST) Received: from zmaj.softwarehood.com (93-87-243-129.dynamic.isp.telekom.rs. [93.87.243.129]) by smtp.googlemail.com with ESMTPSA id j8sm5571303wjf.1.2015.11.10.13.23.32 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 10 Nov 2015 13:23:33 -0800 (PST) Message-ID: <56426054.2070007@gmail.com> Date: Tue, 10 Nov 2015 22:23:32 +0100 From: Ivan Radovanovic User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130812 Thunderbird/17.0.8 MIME-Version: 1.0 To: Konstantin Belousov CC: freebsd-hackers@FreeBSD.org Subject: Re: Detecting new file name after receiving kevent's NOTE_RENAME References: <5641A2A5.7070909@gmail.com> <20151110081421.GL2257@kib.kiev.ua> In-Reply-To: <20151110081421.GL2257@kib.kiev.ua> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Nov 2015 21:23:36 -0000 On 11/10/15 09:14, Konstantin Belousov napisa: >> >I am wondering is there some more clever way to get this new name >> >(kernel is obviously aware of it, otherwise it couldn't notify >> >descriptor about rename)? > > The most correct way is to use sysctl kern.proc.filedesc and look > for the path of the given file descriptor. This is inefficient since > kern.proc.filedesc returns information about all opened files for the > process. Unfortunately it seems that this method (at least using kinfo_getfile(3)) doesn't work - as soon as file is renamed kf_path returned contains only zeros. Shame, it sounded like perfect solution for the problem... From owner-freebsd-hackers@freebsd.org Wed Nov 11 01:50:59 2015 Return-Path: Delivered-To: freebsd-hackers@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 0FDC9A2AA88; Wed, 11 Nov 2015 01:50:59 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DD18913D1; Wed, 11 Nov 2015 01:50:58 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from ralph.baldwin.cx (c-73-231-226-104.hsd1.ca.comcast.net [73.231.226.104]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 53660B922; Tue, 10 Nov 2015 20:50:57 -0500 (EST) From: John Baldwin To: Andriy Gapon Cc: freebsd-current@freebsd.org, Hans Petter Selasky , FreeBSD Hackers Subject: Re: strange kernel crash Date: Tue, 10 Nov 2015 10:42:17 -0800 Message-ID: <18887451.3zmRk4crln@ralph.baldwin.cx> User-Agent: KMail/4.14.3 (FreeBSD/10.2-STABLE; KDE/4.14.3; amd64; ; ) In-Reply-To: <5641AF48.1000507@FreeBSD.org> References: <563C8CED.3020101@FreeBSD.org> <2278845.gkxYBUMIWE@ralph.baldwin.cx> <5641AF48.1000507@FreeBSD.org> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Tue, 10 Nov 2015 20:50:57 -0500 (EST) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Nov 2015 01:50:59 -0000 On Tuesday, November 10, 2015 10:48:08 AM Andriy Gapon wrote: > On 09/11/2015 22:16, John Baldwin wrote: > > On Friday, November 06, 2015 07:02:59 PM Hans Petter Selasky wrote: > >> On 11/06/15 12:20, Andriy Gapon wrote: > >>> Now the strange part: > >>> > >>> 0xffffffff80619a18 <+744>: jne 0xffffffff80619a61 <__mtx_lock_flags+817> > >>> 0xffffffff80619a1a <+746>: mov %rbx,(%rsp) > >>> => 0xffffffff80619a1e <+750>: movq $0x0,0x18(%rsp) > >>> 0xffffffff80619a27 <+759>: movq $0x0,0x10(%rsp) > >>> 0xffffffff80619a30 <+768>: movq $0x0,0x8(%rsp) > >> > >> Were these instructions dumped from RAM or from the kernel ELF file? > > > > Probably not from RAM. You can use 'info files' in gdb to see what is > > handling the address range in question (core vs executable). x/i in ddb > > would have been the "real" truth. > > Yes, according to the output of files it looks like gdb would read that data > from the text section of the kernel file. > > How about libkvm? Would kvm_read read data from the core file? kvm_read should only access the vmcore, yes. > I've written the following small program (cut down dmesg.c, actually): > https://people.freebsd.org/~avg/vmcore_read.c > > (kgdb) disassemble /r > => 0xffffffff80619a1e <+750>: 48 c7 44 24 18 00 00 00 00 movq > $0x0,0x18(%rsp) > > $ vmcore_read -N /boot/kernel.29/kernel -M /var/crash/vmcore.29 0xffffffff80619a1e 9 > 48 c7 44 24 18 00 00 00 00 > > Seems like the code is intact. > > P.S. > 1. To correct something I said earlier, the fault is #UD, not #GP. > 2. The only "suspicious" activity at the time of the crash was the execution of > a bhyve VM. Was the crash in the guest or the host? UD# seems even more bizarre. -- John Baldwin From owner-freebsd-hackers@freebsd.org Wed Nov 11 08:03:02 2015 Return-Path: Delivered-To: freebsd-hackers@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 7675BA2B6D6; Wed, 11 Nov 2015 08:03:02 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 4B7841BD1; Wed, 11 Nov 2015 08:03:00 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id KAA26200; Wed, 11 Nov 2015 10:02:58 +0200 (EET) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1ZwQMs-000G6Q-9u; Wed, 11 Nov 2015 10:02:58 +0200 Subject: Re: strange kernel crash To: John Baldwin References: <563C8CED.3020101@FreeBSD.org> <2278845.gkxYBUMIWE@ralph.baldwin.cx> <5641AF48.1000507@FreeBSD.org> <18887451.3zmRk4crln@ralph.baldwin.cx> Cc: freebsd-current@FreeBSD.org, Hans Petter Selasky , FreeBSD Hackers From: Andriy Gapon Message-ID: <5642F5E0.4050402@FreeBSD.org> Date: Wed, 11 Nov 2015 10:01:36 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <18887451.3zmRk4crln@ralph.baldwin.cx> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Nov 2015 08:03:02 -0000 On 10/11/2015 20:42, John Baldwin wrote: > On Tuesday, November 10, 2015 10:48:08 AM Andriy Gapon wrote: >> On 09/11/2015 22:16, John Baldwin wrote: >>> On Friday, November 06, 2015 07:02:59 PM Hans Petter Selasky wrote: >>>> On 11/06/15 12:20, Andriy Gapon wrote: >>>>> Now the strange part: >>>>> >>>>> 0xffffffff80619a18 <+744>: jne 0xffffffff80619a61 <__mtx_lock_flags+817> >>>>> 0xffffffff80619a1a <+746>: mov %rbx,(%rsp) >>>>> => 0xffffffff80619a1e <+750>: movq $0x0,0x18(%rsp) >>>>> 0xffffffff80619a27 <+759>: movq $0x0,0x10(%rsp) >>>>> 0xffffffff80619a30 <+768>: movq $0x0,0x8(%rsp) >>>> >>>> Were these instructions dumped from RAM or from the kernel ELF file? >>> >>> Probably not from RAM. You can use 'info files' in gdb to see what is >>> handling the address range in question (core vs executable). x/i in ddb >>> would have been the "real" truth. >> >> Yes, according to the output of files it looks like gdb would read that data >> from the text section of the kernel file. >> >> How about libkvm? Would kvm_read read data from the core file? > > kvm_read should only access the vmcore, yes. > >> I've written the following small program (cut down dmesg.c, actually): >> https://people.freebsd.org/~avg/vmcore_read.c >> >> (kgdb) disassemble /r >> => 0xffffffff80619a1e <+750>: 48 c7 44 24 18 00 00 00 00 movq >> $0x0,0x18(%rsp) >> >> $ vmcore_read -N /boot/kernel.29/kernel -M /var/crash/vmcore.29 0xffffffff80619a1e 9 >> 48 c7 44 24 18 00 00 00 00 >> >> Seems like the code is intact. >> >> P.S. >> 1. To correct something I said earlier, the fault is #UD, not #GP. >> 2. The only "suspicious" activity at the time of the crash was the execution of >> a bhyve VM. > > Was the crash in the guest or the host? UD# seems even more bizarre. It was the host. This is bizarre indeed. I can think only of two possibilities: - new CPU erratum - corrupted data somehow getting into the instruction cache, but the correct data being read during the crash dump (i.e. flaky memory) -- Andriy Gapon From owner-freebsd-hackers@freebsd.org Wed Nov 11 10:57:04 2015 Return-Path: Delivered-To: freebsd-hackers@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 00FAFA2B80E for ; Wed, 11 Nov 2015 10:57:04 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6F4361A35 for ; Wed, 11 Nov 2015 10:57:03 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id tABAuwWr078065 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 11 Nov 2015 12:56:58 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua tABAuwWr078065 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id tABAuuaf078063; Wed, 11 Nov 2015 12:56:56 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 11 Nov 2015 12:56:56 +0200 From: Konstantin Belousov To: Ivan Radovanovic Cc: freebsd-hackers@FreeBSD.org Subject: Re: Detecting new file name after receiving kevent's NOTE_RENAME Message-ID: <20151111105656.GX2257@kib.kiev.ua> References: <5641A2A5.7070909@gmail.com> <20151110081421.GL2257@kib.kiev.ua> <56426054.2070007@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <56426054.2070007@gmail.com> User-Agent: Mutt/1.5.24 (2015-08-30) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Nov 2015 10:57:04 -0000 On Tue, Nov 10, 2015 at 10:23:32PM +0100, Ivan Radovanovic wrote: > On 11/10/15 09:14, Konstantin Belousov napisa: > >> >I am wondering is there some more clever way to get this new name > >> >(kernel is obviously aware of it, otherwise it couldn't notify > >> >descriptor about rename)? > > > > The most correct way is to use sysctl kern.proc.filedesc and look > > for the path of the given file descriptor. This is inefficient since > > kern.proc.filedesc returns information about all opened files for the > > process. > > Unfortunately it seems that this method (at least using > kinfo_getfile(3)) doesn't work - as soon as file is renamed kf_path > returned contains only zeros. Shame, it sounded like perfect solution > for the problem... It is up to filesystem to cache or not cache the file name entry. If filesystem does not insert the name entry into namecache on rename, there is nothing which could help vn_fullpath(9) to return a path. OTOH, I do not see a reason why filesystems could not be changed to start caching the renamed file name consistently. From owner-freebsd-hackers@freebsd.org Wed Nov 11 13:01:54 2015 Return-Path: Delivered-To: freebsd-hackers@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 73CE4A2C0B9; Wed, 11 Nov 2015 13:01:54 +0000 (UTC) (envelope-from aduane@juniper.net) Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1on0132.outbound.protection.outlook.com [157.56.110.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "MSIT Machine Auth CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C358B12E9; Wed, 11 Nov 2015 13:01:53 +0000 (UTC) (envelope-from aduane@juniper.net) Received: from BLUPR05MB723.namprd05.prod.outlook.com (10.141.207.153) by BLUPR05MB721.namprd05.prod.outlook.com (10.141.207.144) with Microsoft SMTP Server (TLS) id 15.1.318.15; Wed, 11 Nov 2015 12:46:05 +0000 Received: from BLUPR05MB723.namprd05.prod.outlook.com ([10.141.207.153]) by BLUPR05MB723.namprd05.prod.outlook.com ([10.141.207.153]) with mapi id 15.01.0318.003; Wed, 11 Nov 2015 12:46:05 +0000 From: Andrew Duane To: Andriy Gapon , John Baldwin CC: Hans Petter Selasky , FreeBSD Hackers , "freebsd-current@FreeBSD.org" Subject: RE: strange kernel crash Thread-Topic: strange kernel crash Thread-Index: AQHRHCNwVoZ/0UuTME+ghwXWxzr5bp6WdhgAgABOyyA= Date: Wed, 11 Nov 2015 12:46:05 +0000 Message-ID: References: <563C8CED.3020101@FreeBSD.org> <2278845.gkxYBUMIWE@ralph.baldwin.cx> <5641AF48.1000507@FreeBSD.org> <18887451.3zmRk4crln@ralph.baldwin.cx> <5642F5E0.4050402@FreeBSD.org> In-Reply-To: <5642F5E0.4050402@FreeBSD.org> 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=aduane@juniper.net; x-originating-ip: [66.129.241.11] x-microsoft-exchange-diagnostics: 1; BLUPR05MB721; 5:YOMjMDcHkhFLEZ2TVQkdckkjC/1B4AGSC3I4b01Ndu9ZY3FkmA9r+kz4YyzTUM/+jZWBDSSfwA5NQmCrjR+YL5YjKuvmPCXAfK/uShdLM3b9gVpqszv9vqL+h4gx0kVLFO8g3ye+vjfEEKiqGj7HLw==; 24:13y6mwhIKvSk/F/7rVo7tebSrz6UF5RqkyAG7mlPwSqLq78hX1cWywHUEJd27IU2gJPcAKjHzm8nVHq+dyfZTvaLLzV4KbEKTpF019d9vWs=; 20:IYWdDqr9mbi1J9JA++FozGhW24F54w9cL64HOuI4gI9RmhoARQtz1cTR7k+DsZSQ+yGrcqPtJwh4WiLzRHtcVw== x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(42134001)(42139001); SRVR:BLUPR05MB721; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:; x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(520078)(5005006)(8121501046)(10201501046)(3002001); SRVR:BLUPR05MB721; BCL:0; PCL:0; RULEID:; SRVR:BLUPR05MB721; x-forefront-prvs: 0757EEBDCA x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(189002)(479174004)(24454002)(13464003)(199003)(377454003)(76576001)(5008740100001)(5001960100002)(76176999)(50986999)(101416001)(10400500002)(5002640100001)(11100500001)(189998001)(54356999)(5003600100002)(5004730100002)(74316001)(5007970100001)(122556002)(33656002)(99286002)(40100003)(106116001)(19580395003)(19580405001)(66066001)(106356001)(93886004)(15975445007)(2950100001)(102836002)(2900100001)(97736004)(81156007)(5001770100001)(87936001)(77096005)(92566002)(86362001)(105586002); DIR:OUT; SFP:1102; SCL:1; SRVR:BLUPR05MB721; H:BLUPR05MB723.namprd05.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts) spamdiagnosticoutput: 1:23 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: juniper.net X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Nov 2015 12:46:05.0445 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4 X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR05MB721 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Nov 2015 13:01:54 -0000 > -----Original Message----- > From: owner-freebsd-hackers@freebsd.org [mailto:owner-freebsd-hackers@fre= ebsd.org] On Behalf Of Andriy Gapon > Sent: Wednesday, November 11, 2015 3:02 AM > To: John Baldwin > Cc: Hans Petter Selasky ; FreeBSD Hackers ; freebsd-current@FreeBSD.org > Subject: Re: strange kernel crash >=20 > On 10/11/2015 20:42, John Baldwin wrote: > > On Tuesday, November 10, 2015 10:48:08 AM Andriy Gapon wrote: > >> On 09/11/2015 22:16, John Baldwin wrote: > >>> On Friday, November 06, 2015 07:02:59 PM Hans Petter Selasky wrote: > >>>> On 11/06/15 12:20, Andriy Gapon wrote: > >>>>> Now the strange part: > >>>>> > >>>>> 0xffffffff80619a18 <+744>: jne 0xffffffff80619a61 <__mtx_l= ock_flags+817> > >>>>> 0xffffffff80619a1a <+746>: mov %rbx,(%rsp) > >>>>> =3D> 0xffffffff80619a1e <+750>: movq $0x0,0x18(%rsp) > >>>>> 0xffffffff80619a27 <+759>: movq $0x0,0x10(%rsp) > >>>>> 0xffffffff80619a30 <+768>: movq $0x0,0x8(%rsp) > >>>> > >>>> Were these instructions dumped from RAM or from the kernel ELF file? > >>> > >>> Probably not from RAM. You can use 'info files' in gdb to see what > >>> is handling the address range in question (core vs executable). x/i > >>> in ddb would have been the "real" truth. > >> > >> Yes, according to the output of files it looks like gdb would read > >> that data from the text section of the kernel file. > >> > >> How about libkvm? Would kvm_read read data from the core file? > > > > kvm_read should only access the vmcore, yes. > > > >> I've written the following small program (cut down dmesg.c, actually): > >> https://people.freebsd.org/~avg/vmcore_read.c > >> > >> (kgdb) disassemble /r > >> =3D> 0xffffffff80619a1e <+750>: 48 c7 44 24 18 00 00 00 00 movq > >> $0x0,0x18(%rsp) > >> > >> $ vmcore_read -N /boot/kernel.29/kernel -M /var/crash/vmcore.29 > >> 0xffffffff80619a1e 9 > >> 48 c7 44 24 18 00 00 00 00 > >> > >> Seems like the code is intact. > >> > >> P.S. > >> 1. To correct something I said earlier, the fault is #UD, not #GP. > >> 2. The only "suspicious" activity at the time of the crash was the exe= cution of a bhyve VM. > > > > Was the crash in the guest or the host? UD# seems even more bizarre. >=20 > It was the host. This is bizarre indeed. I can think only of two possib= ilities: > - new CPU erratum > - corrupted data somehow getting into the instruction cache, but the co= rrect data being read during the crash dump (i.e. flaky memory) Or perhaps a missing memory sync operation somewhere.... >=20 > -- > Andriy Gapon > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org= " From owner-freebsd-hackers@freebsd.org Wed Nov 11 17:24:59 2015 Return-Path: Delivered-To: freebsd-hackers@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 3E294A2CCCD for ; Wed, 11 Nov 2015 17:24:59 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: from mail-yk0-f181.google.com (mail-yk0-f181.google.com [209.85.160.181]) (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 F3FC61DEC for ; Wed, 11 Nov 2015 17:24:58 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: by ykba77 with SMTP id a77so59749370ykb.2 for ; Wed, 11 Nov 2015 09:24:52 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=Zj4S63X1r4KRN0d9mXL5ECuObb2yL7GgHfRYIVBy1H0=; b=ma0xWSwWFktgral4NEYlnrxHBP0kf8QeUFhj+QFS9uEI6OtESvx9jQhCGjgdaqz8KA g9/b2dqrtrDIM4yIFxKJAK07RMzi5MLxtJNM9UsB1GIOPd1kXN9JDuk6YqKZo3JsHnE0 LZszbZrUSOK/QfFjiWgl7TegbonGDIbKEWtliQ7Tcu52AcR8ruX12NpqIJZghiW1NdzR kAGuQJIEe/OZZ/D9EyXT4BLauj75E36xqZUsu1yDhwroLzngqiyxwREWueOHM68CO52A AXH5UkvtT3aMqL+czeo8IkVPmEUQ7MGDId0hTAFkEUYcn+kw4JVvWpMq8E8el883W9oI 3CzQ== X-Received: by 10.129.53.148 with SMTP id c142mr10875096ywa.138.1447262692332; Wed, 11 Nov 2015 09:24:52 -0800 (PST) Received: from mail-yk0-f171.google.com (mail-yk0-f171.google.com. [209.85.160.171]) by smtp.gmail.com with ESMTPSA id a143sm11612014ywe.54.2015.11.11.09.24.51 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 11 Nov 2015 09:24:52 -0800 (PST) Received: by ykdv3 with SMTP id v3so60108535ykd.0 for ; Wed, 11 Nov 2015 09:24:51 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.129.102.5 with SMTP id a5mr12246849ywc.9.1447262691600; Wed, 11 Nov 2015 09:24:51 -0800 (PST) Reply-To: cem@FreeBSD.org Received: by 10.37.17.2 with HTTP; Wed, 11 Nov 2015 09:24:51 -0800 (PST) In-Reply-To: <20151111105656.GX2257@kib.kiev.ua> References: <5641A2A5.7070909@gmail.com> <20151110081421.GL2257@kib.kiev.ua> <56426054.2070007@gmail.com> <20151111105656.GX2257@kib.kiev.ua> Date: Wed, 11 Nov 2015 09:24:51 -0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Detecting new file name after receiving kevent's NOTE_RENAME From: Conrad Meyer To: Konstantin Belousov Cc: Ivan Radovanovic , FreeBSD Hackers Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Nov 2015 17:24:59 -0000 On Wed, Nov 11, 2015 at 2:56 AM, Konstantin Belousov wrote: > It is up to filesystem to cache or not cache the file name entry. > If filesystem does not insert the name entry into namecache on rename, > there is nothing which could help vn_fullpath(9) to return a path. Besides vn_vptocnp? I thought vn_fullpath(9) should always succeed since 10.0 if the vnode still exists. Best, Conrad From owner-freebsd-hackers@freebsd.org Wed Nov 11 19:36:21 2015 Return-Path: Delivered-To: freebsd-hackers@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 AE842A2B734 for ; Wed, 11 Nov 2015 19:36:21 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 23B241D38; Wed, 11 Nov 2015 19:36:20 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id tABJaCT3002797 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 11 Nov 2015 21:36:12 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua tABJaCT3002797 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id tABJaCJK002796; Wed, 11 Nov 2015 21:36:12 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 11 Nov 2015 21:36:12 +0200 From: Konstantin Belousov To: Conrad Meyer Cc: Ivan Radovanovic , FreeBSD Hackers Subject: Re: Detecting new file name after receiving kevent's NOTE_RENAME Message-ID: <20151111193612.GG2257@kib.kiev.ua> References: <5641A2A5.7070909@gmail.com> <20151110081421.GL2257@kib.kiev.ua> <56426054.2070007@gmail.com> <20151111105656.GX2257@kib.kiev.ua> 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-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Nov 2015 19:36:21 -0000 On Wed, Nov 11, 2015 at 09:24:51AM -0800, Conrad Meyer wrote: > On Wed, Nov 11, 2015 at 2:56 AM, Konstantin Belousov > wrote: > > It is up to filesystem to cache or not cache the file name entry. > > If filesystem does not insert the name entry into namecache on rename, > > there is nothing which could help vn_fullpath(9) to return a path. > > Besides vn_vptocnp? I thought vn_fullpath(9) should always succeed > since 10.0 if the vnode still exists. VOP_VPTOCNP() still must get the data somewhere. It is usually easy to provide the name for a synthetic file system, where the data is fully controlled by the filesystem. Also, it is always possible to provide the name for a directory on any unix-like filesystem, due to dotdot. Both cases are what handled by fs-specific implementations of VOP_VPTOCNP() and by the default code. For the rest, you e.g. must be able to answer with the name for regular inode on UFS, given the inode number. If you can provide such code, I will be quite amazed. From owner-freebsd-hackers@freebsd.org Wed Nov 11 20:08:07 2015 Return-Path: Delivered-To: freebsd-hackers@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 86FFAA2BE0C for ; Wed, 11 Nov 2015 20:08:07 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: from mail-yk0-f181.google.com (mail-yk0-f181.google.com [209.85.160.181]) (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 47E7F1CD6 for ; Wed, 11 Nov 2015 20:08:06 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: by ykba77 with SMTP id a77so67749338ykb.2 for ; Wed, 11 Nov 2015 12:08:06 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=rB1ClKAYQjVNZF4txwfioMzyViJLL7OGufVGs2UxpKA=; b=KmDvj9pGu+QeIPF4P5PEKMDADlQfA9rg/tw7LJ523J9asvO7hkmDwxhYvZHGDIWwQp frrPy3FAxGYmfbUV8bw4ap6lMZzfG/3LCWof+4eDo8yQDELIBvrUB3o+MmB9EIqH3jOr 71IF+PIHg+1QBsXLa1OBonXh30si94J8hvbYuYuuvp1j6NoO88DKPQB+2xb6bPZc5MeD i+0JQ1Z//xfMOmdyvHZFZPlKU0nzEshtN9UDT97H/cJjXf3JbKRvJiwyyRLcHvMQ37vF zmGopDvY0tYUg9J4KTdrnO0TRgUQDuR5dH79Eyqz30E+nfp24BOoBMvu2zy8mFO7i0+s b+9A== X-Received: by 10.13.213.134 with SMTP id x128mr1897299ywd.139.1447272083485; Wed, 11 Nov 2015 12:01:23 -0800 (PST) Received: from mail-yk0-f175.google.com (mail-yk0-f175.google.com. [209.85.160.175]) by smtp.gmail.com with ESMTPSA id e64sm12432458ywb.25.2015.11.11.12.01.22 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 11 Nov 2015 12:01:23 -0800 (PST) Received: by ykfs79 with SMTP id s79so67799792ykf.1 for ; Wed, 11 Nov 2015 12:01:22 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.129.13.213 with SMTP id 204mr12642748ywn.281.1447272082795; Wed, 11 Nov 2015 12:01:22 -0800 (PST) Reply-To: cem@FreeBSD.org Received: by 10.37.17.2 with HTTP; Wed, 11 Nov 2015 12:01:22 -0800 (PST) In-Reply-To: <20151111193612.GG2257@kib.kiev.ua> References: <5641A2A5.7070909@gmail.com> <20151110081421.GL2257@kib.kiev.ua> <56426054.2070007@gmail.com> <20151111105656.GX2257@kib.kiev.ua> <20151111193612.GG2257@kib.kiev.ua> Date: Wed, 11 Nov 2015 12:01:22 -0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Detecting new file name after receiving kevent's NOTE_RENAME From: Conrad Meyer To: Konstantin Belousov Cc: Ivan Radovanovic , FreeBSD Hackers Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Nov 2015 20:08:07 -0000 On Wed, Nov 11, 2015 at 11:36 AM, Konstantin Belousov wrote: > VOP_VPTOCNP() still must get the data somewhere. It is usually easy to > provide the name for a synthetic file system, where the data is fully > controlled by the filesystem. Also, it is always possible to provide the > name for a directory on any unix-like filesystem, due to dotdot. Both > cases are what handled by fs-specific implementations of VOP_VPTOCNP() > and by the default code. > > For the rest, you e.g. must be able to answer with the name for regular > inode on UFS, given the inode number. If you can provide such code, I > will be quite amazed. I'm not sure what you're talking about. To have a NOTE_RENAME monitor as originally discussed, the userspace program must have an fd open to the vnode. With a vnode, the boring generic vn_fullpath and vop_stdvptocnp can find a whole path using .. and directory traversal. It may not be fast, but it is possible. Conrad From owner-freebsd-hackers@freebsd.org Thu Nov 12 08:30:16 2015 Return-Path: Delivered-To: freebsd-hackers@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 BA9F4A2C380 for ; Thu, 12 Nov 2015 08:30:16 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 31F121CB4; Thu, 12 Nov 2015 08:30:16 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id tAC8U7ZF094917 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Thu, 12 Nov 2015 10:30:07 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua tAC8U7ZF094917 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id tAC8U6ik094914; Thu, 12 Nov 2015 10:30:06 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Thu, 12 Nov 2015 10:30:06 +0200 From: Konstantin Belousov To: Conrad Meyer Cc: Ivan Radovanovic , FreeBSD Hackers Subject: Re: Detecting new file name after receiving kevent's NOTE_RENAME Message-ID: <20151112083006.GH2257@kib.kiev.ua> References: <5641A2A5.7070909@gmail.com> <20151110081421.GL2257@kib.kiev.ua> <56426054.2070007@gmail.com> <20151111105656.GX2257@kib.kiev.ua> <20151111193612.GG2257@kib.kiev.ua> 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-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Nov 2015 08:30:16 -0000 On Wed, Nov 11, 2015 at 12:01:22PM -0800, Conrad Meyer wrote: > On Wed, Nov 11, 2015 at 11:36 AM, Konstantin Belousov > wrote: > > VOP_VPTOCNP() still must get the data somewhere. It is usually easy to > > provide the name for a synthetic file system, where the data is fully > > controlled by the filesystem. Also, it is always possible to provide the > > name for a directory on any unix-like filesystem, due to dotdot. Both > > cases are what handled by fs-specific implementations of VOP_VPTOCNP() > > and by the default code. > > > > For the rest, you e.g. must be able to answer with the name for regular > > inode on UFS, given the inode number. If you can provide such code, I > > will be quite amazed. > > I'm not sure what you're talking about. To have a NOTE_RENAME monitor > as originally discussed, the userspace program must have an fd open to > the vnode. With a vnode, the boring generic vn_fullpath and > vop_stdvptocnp can find a whole path using .. and directory traversal. > It may not be fast, but it is possible. I have no idea what you are talking about either. How dotdot algorithm can be used to find the parent directory for a regular inode ? From owner-freebsd-hackers@freebsd.org Fri Nov 13 19:20:56 2015 Return-Path: Delivered-To: freebsd-hackers@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 2B324A2EEFA for ; Fri, 13 Nov 2015 19:20:56 +0000 (UTC) (envelope-from lobo@bsd.com.br) Received: from mail-qk0-x22d.google.com (mail-qk0-x22d.google.com [IPv6:2607:f8b0:400d:c09::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 DB86E1335 for ; Fri, 13 Nov 2015 19:20:55 +0000 (UTC) (envelope-from lobo@bsd.com.br) Received: by qkao63 with SMTP id o63so57303623qka.2 for ; Fri, 13 Nov 2015 11:20:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsd.com.br; s=capeta; h=date:from:to:subject:message-id:organization:mime-version :content-type; bh=UEObxGmizQ4rzDWp+QgIL4Pdo4zsuPwvke3PJ+AW3Qw=; b=SgX4lJchlpODy0prZCdD1xgNWh4Mg9DniJJ0oi57GG474LXk62cwG6r9rgrtC2rkwO S5h5Gy+xkHPoU9g9tCZKI9HnGTpLuePligdxo+cC4ET7MDiaxgn58gOAkWQjqnj6U07w il4DW1jnsTHVn+CQLGWHJR8DFZvRuNINXDG58= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:subject:message-id:organization :mime-version:content-type; bh=UEObxGmizQ4rzDWp+QgIL4Pdo4zsuPwvke3PJ+AW3Qw=; b=P89BB8rU8nsWoQrNzGxMOI7XJcRdcNnqAC7RIjwpbQAwIcCyUcmO2RDRrRllP4nQm1 6EpMTXslfn/cnNYKIQofvWSqhWwK3K3LUSSHTenUbOHfD37gqNj+/IzeIpDj6VSNBt/a T9vDezZtXIxPMufZJMUc+zbgT4HJFA2Ug+h5rAEj4Kz0e8t8Mc43/ODetPu3h8hEwtaf AsMnckOhaCwodi8nvaTrSR9MgPy+xsNZJZvGTRZvVmZzEpCFqJ0tDuaUd5KCV5KJecur +awiz79B0DA8dBraZRezZbk52Qw3AVAJbc6DFNAcL6OEZV25Liv97FjEpZ30qBW1sL6X c5BA== X-Gm-Message-State: ALoCoQm6FtyZSfyJiE/aiIrhJQBccEHXYn8SyjRaoAf834I6j3B53obVlaorZkmDMpTVTwcVEgpg X-Received: by 10.140.94.116 with SMTP id f107mr24021122qge.0.1447442454443; Fri, 13 Nov 2015 11:20:54 -0800 (PST) Received: from Papi (177.207.112.36.dynamic.adsl.gvt.net.br. [177.207.112.36]) by smtp.gmail.com with ESMTPSA id b63sm5674834qka.31.2015.11.13.11.20.53 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 13 Nov 2015 11:20:54 -0800 (PST) Date: Fri, 13 Nov 2015 16:25:48 -0300 From: Mario Lobo To: FreeBSD Hackers Subject: Fw: FreeBSD smbfs horribly slow Message-ID: <20151113162548.61529137@Papi> Organization: BSD X-Mailer: Claws Mail 3.12.0 (GTK+ 2.24.25; amd64-portbld-freebsd10.2) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="MP_/w2g4B/gupupHUSYxijlrvA3" X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Nov 2015 19:20:56 -0000 --MP_/w2g4B/gupupHUSYxijlrvA3 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi; It seems no one in @questions had any info/pointers/interest on this so I'm trying @hackers for some light. Thanks, Begin forwarded message: Date: Wed, 11 Nov 2015 17:53:11 -0300 From: Mario Lobo To: freebsd-questions Subject: FreeBSD smbfs horribly slow Googling on this subject, I found: http://lists.freebsd.org/pipermail/freebsd-questions/2005-September/098717.html https://lists.freebsd.org/pipermail/freebsd-net/2013-January/034239.html https://lists.freebsd.org/pipermail/freebsd-questions/2014-October/261804.html I am on 10.2-STABLE and using FreeBSD as a client to any amb share continues to be very slow. The share is mounted through mount_smbfs. I tried smbnetfs (fuse) and it is just a tiny bit better but doesn't compare to other clients (linux or win) when writing/reading files It gets even worse if an application is doing operations with variable size records inside a data file on the share. Does anyone have any advice to improve this? Thanks, -- Mario Lobo http://www.mallavoodoo.com.br FreeBSD since 2.2.8 [not Pro-Audio.... YET!!] "UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things." --MP_/w2g4B/gupupHUSYxijlrvA3 Content-Disposition: attachment; filename="Original html part" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" --MP_/w2g4B/gupupHUSYxijlrvA3-- From owner-freebsd-hackers@freebsd.org Fri Nov 13 19:32:14 2015 Return-Path: Delivered-To: freebsd-hackers@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 B6443A2E391 for ; Fri, 13 Nov 2015 19:32:14 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from mx1.scaleengine.net (mx1.scaleengine.net [209.51.186.6]) by mx1.freebsd.org (Postfix) with ESMTP id 94D7A1F09 for ; Fri, 13 Nov 2015 19:32:14 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from [10.1.1.2] (unknown [10.1.1.2]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id DD63DD939 for ; Fri, 13 Nov 2015 19:32:07 +0000 (UTC) Subject: Re: Fw: FreeBSD smbfs horribly slow To: freebsd-hackers@freebsd.org References: <20151113162548.61529137@Papi> From: Allan Jude X-Enigmail-Draft-Status: N1110 Message-ID: <56463ACE.5020605@freebsd.org> Date: Fri, 13 Nov 2015 14:32:30 -0500 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <20151113162548.61529137@Papi> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Anx1m72NXlpdbQBgc9Kp1LtKp7gSt40BR" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Nov 2015 19:32:14 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --Anx1m72NXlpdbQBgc9Kp1LtKp7gSt40BR Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 2015-11-13 14:25, Mario Lobo wrote: > Hi; >=20 > It seems no one in @questions had any info/pointers/interest on this > so I'm trying @hackers for some light. >=20 > Thanks, >=20 >=20 > Begin forwarded message: >=20 > Date: Wed, 11 Nov 2015 17:53:11 -0300 > From: Mario Lobo > To: freebsd-questions > Subject: FreeBSD smbfs horribly slow >=20 > Googling on this subject, I found: >=20 > http://lists.freebsd.org/pipermail/freebsd-questions/2005-September/098= 717.html > https://lists.freebsd.org/pipermail/freebsd-net/2013-January/034239.htm= l > https://lists.freebsd.org/pipermail/freebsd-questions/2014-October/2618= 04.html >=20 > I am on 10.2-STABLE and using FreeBSD as a client to any amb share > continues to be very slow. >=20 > The share is mounted through mount_smbfs. I tried smbnetfs (fuse) and > it is just a tiny bit better but doesn't compare to other clients > (linux or win) when writing/reading files >=20 > It gets even worse if an application is doing operations with variable > size records inside a data file on the share. >=20 > Does anyone have any advice to improve this? >=20 > Thanks, >=20 >=20 >=20 > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.o= rg" >=20 What kind of operations are you doing? I just mounted a share from my windows desktop on my FreeBSD -CURRENT machine, and was able to write new files at 64 megabytes/s (roughly 1/2 the available gigabit/sec) Reading it back only got 50 megabytes/s, not sure why. --=20 Allan Jude --Anx1m72NXlpdbQBgc9Kp1LtKp7gSt40BR 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) iQIcBAEBAgAGBQJWRjrRAAoJEBmVNT4SmAt+63oP/jKcyo5lJzAjRnudMYiznK13 e6dITUJPfVqV+441HzoX70gLd9eiVTjz4EOif1cUegGyNlZkzHU779z8EQyD9ilW 9TPhJCDW//TmYPtdLZ0Dn62na9pO6qMikjaqH/acXHLs+0MMQgGNFBsqw2Db692x BHfNuuZF/b/iPv1C3WOXVvf9dLui/+lo64Kt9DWXYQHXEjTdmNHFRsI+JBICWmNh YuC2eOVbQs6qNtacAfrR1fiX7s5516icYyeo2x0zAnXr9/af1wFEDuReE2n+Bz2R 4paLOWfED6Tyi6LawFDxX7XYxJ6RVPaYR+7fMqGjlX1KGqys4kbzYeHsJhJ6rrb2 sjd/5QHoSEVpsQXlKovEye2GVT7ws9G0a84gq2mRxZXWpQuPl37P0ObZxFQ1l8e9 vqKk56HlwXw99UOQKE7Sg9PxQjdg8UgzOLR3TdiOgXMglgBhil8W/gp4vJ5iNQXr cw/seStkrwAgZjU9mVeNCLWDX5RcolcNQPI3zekG6omjQLHDx6P7na+KJrSlVtbB i9l8JJoPHZ0m5IjgtIIaZnYA8z5qxw0mxCgu8mzMAVNR76TQ/TziHVI1wBNHeJgp 4GGm6rj3TbBWxtt3jm3IuE0FioSbWHb/hLhnHYtzDVZZgDNGXe4fVqBny6OntrU/ 7IPMIHZgMpNKygn2yt41 =quRU -----END PGP SIGNATURE----- --Anx1m72NXlpdbQBgc9Kp1LtKp7gSt40BR-- From owner-freebsd-hackers@freebsd.org Fri Nov 13 23:13:33 2015 Return-Path: Delivered-To: freebsd-hackers@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 1F1E5A2E8E7 for ; Fri, 13 Nov 2015 23:13:33 +0000 (UTC) (envelope-from lobo@bsd.com.br) Received: from mail-io0-x244.google.com (mail-io0-x244.google.com [IPv6:2607:f8b0:4001:c06::244]) (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 E34371F4E for ; Fri, 13 Nov 2015 23:13:32 +0000 (UTC) (envelope-from lobo@bsd.com.br) Received: by ioef137 with SMTP id f137so10523393ioe.0 for ; Fri, 13 Nov 2015 15:13:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsd.com.br; s=capeta; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=5t0murpuh3GpdIzy8R+2hYn5cWI9MSv9a7aZ5uw/KXQ=; b=RbFg0SQOXaXjkqJ9Pu8SUso7ipiCwU0BY/TgMp9TkXKiw4p+jC2P7A5pnAnjk8kca2 ZQsOPWi/zjHdcnwN50cWgT2rNKkQtwEOWb/1jTLYvAMWyfoGTjqapMhIJdnqWUXKKfy8 lxQyTvCC2+0wlpCQ7ZiwteeksgdKbvR7u8vWw= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=5t0murpuh3GpdIzy8R+2hYn5cWI9MSv9a7aZ5uw/KXQ=; b=cDN6UvH2K8qSpdrGSAVQfvLove4X4Uoq/iDHJAIAEjxF3IoC3BpzZ0JBJnZNTNbJjg /UM0Eh9cZ4U7krOgpg/ByZxz/aZPo2cwa2IacqJnt3hKpB9FVCMfrG4f2YNiXTkiek4+ fxJRy/1ThnZ25LzhR0MbUquLMvIRcMd8f5qvB0fHxnFgZdbW6vA7jZt9VIliiZLfbnFz 6A4iY/jRY4VPP1v0oybwEN4WOnUWLJuZijEuwbjAIGPhdTyKQtmte0wVX2u12eTuoQci b7C+e9JL8W84YFrzcuRGkEQhTopPNf2YIu9SHa4R5cy17wy4jKNbvULdqnsAJ7jonNB1 BsHg== X-Gm-Message-State: ALoCoQnEN7YTEnU2iBKiSmrTJVEi0qqXxbSbBHP8Hs+u/7aWog1UnwcD3w0NkehS8Wp0R/bmPrwM MIME-Version: 1.0 X-Received: by 10.107.164.227 with SMTP id d96mr22184534ioj.73.1447456412101; Fri, 13 Nov 2015 15:13:32 -0800 (PST) Received: by 10.79.3.131 with HTTP; Fri, 13 Nov 2015 15:13:32 -0800 (PST) In-Reply-To: <56463ACE.5020605@freebsd.org> References: <20151113162548.61529137@Papi> <56463ACE.5020605@freebsd.org> Date: Fri, 13 Nov 2015 20:13:32 -0300 Message-ID: Subject: Re: Fw: FreeBSD smbfs horribly slow From: Mario Lobo To: Allan Jude Cc: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Nov 2015 23:13:33 -0000 2015-11-13 16:32 GMT-03:00 Allan Jude : > On 2015-11-13 14:25, Mario Lobo wrote: > > Hi; > > > > It seems no one in @questions had any info/pointers/interest on this > > so I'm trying @hackers for some light. > > > > Thanks, > > > > > > Begin forwarded message: > > > > Date: Wed, 11 Nov 2015 17:53:11 -0300 > > From: Mario Lobo > > To: freebsd-questions > > Subject: FreeBSD smbfs horribly slow > > > > Googling on this subject, I found: > > > > > http://lists.freebsd.org/pipermail/freebsd-questions/2005-September/098717.html > > https://lists.freebsd.org/pipermail/freebsd-net/2013-January/034239.html > > > https://lists.freebsd.org/pipermail/freebsd-questions/2014-October/261804.html > > > > I am on 10.2-STABLE and using FreeBSD as a client to any amb share > > continues to be very slow. > > > > The share is mounted through mount_smbfs. I tried smbnetfs (fuse) and > > it is just a tiny bit better but doesn't compare to other clients > > (linux or win) when writing/reading files > > > > It gets even worse if an application is doing operations with variable > > size records inside a data file on the share. > > > > Does anyone have any advice to improve this? > > > > Thanks, > > > > > > > > _______________________________________________ > > freebsd-hackers@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > > To unsubscribe, send any mail to " > freebsd-hackers-unsubscribe@freebsd.org" > > > > What kind of operations are you doing? > > I just mounted a share from my windows desktop on my FreeBSD -CURRENT > machine, and was able to write new files at 64 megabytes/s (roughly 1/2 > the available gigabit/sec) > > Reading it back only got 50 megabytes/s, not sure why. > > -- > Allan Jude > > Which one is the server? Windows or FBSD? I have no problems with either one being the server. The problem is when FBSD is the client. I wrote a daemon that executes operations on old DBF/NTX (clipper) files (Yeah, I know ... but that's what they have for 20+ years ..). Anyway, a site interacts with this daemon via tcp, with commands to add/delete/update records/indexes, as well as finding keys on the indexxes. I prepared a test that has several of these routines together on a 10.2-STABLE machine. Enough to say that when executing the tests with the files stored locally, the whole test takes 3-4 seconds to complete. When doing the same test with the files on a share on the same wire (1G connection, no matter which OS runs the share), the test takes around 3:50 minutes to complete! I am preparing a Centos VM and compiling the deamon on it to check the results. -- Mario Lobo http://www.mallavoodoo.com.br FreeBSD since version 2.2.8 [not Pro-Audio.... YET!!] (99,7% winfoes FREE) From owner-freebsd-hackers@freebsd.org Sat Nov 14 00:04:12 2015 Return-Path: Delivered-To: freebsd-hackers@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 B578AA2E7AB for ; Sat, 14 Nov 2015 00:04:12 +0000 (UTC) (envelope-from nonesuch@longcount.org) Received: from mail-io0-x232.google.com (mail-io0-x232.google.com [IPv6:2607:f8b0:4001:c06::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 7EE401159 for ; Sat, 14 Nov 2015 00:04:12 +0000 (UTC) (envelope-from nonesuch@longcount.org) Received: by iofh3 with SMTP id h3so113416287iof.3 for ; Fri, 13 Nov 2015 16:04:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=longcount_org.20150623.gappssmtp.com; s=20150623; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=+O24p77KbCCW93HEllg2uWCk2VgIlj+qjaiVZsSOCLQ=; b=NDAGYnZKWgiYJpIp4SVZfu27cU+ZL6OWMxEVaDNKRGwyVUV+kc+Unbx4WQU/cLBG7a oXwJ21Zg7t6veLiCw9upHcMeB5E13xtvDfUj8N26IzjQpAWLaeVp6IzGNlj+PABGlx4b zyvXYHTqAlLjM2LzPyi3qnQuoYDlQyawbAz+aco0XIXGfwmKlU+1Qau9+lPNvOy/uZP2 YzfZwp6BWs2CSbYt3knfQUoni8YZdtcXoWGPtl/37ALj/ro1XqnDKGr/VUit/6Udf+Hz XI4pKF6YwzYWBpqwe5gvn9aRN/tuEMnJEVfUBJr9hSnuI4HKPf9q9EM+6MKyG2j9AytJ tkag== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=+O24p77KbCCW93HEllg2uWCk2VgIlj+qjaiVZsSOCLQ=; b=bLNmw3y5qOzW6r5IpOmQ40RL39xCzWJoawbFcDkU+glnPR9lVlI96IsJDFGbQ5ib++ U5RZcHOdFA3kFz4JQGzhNFREVEi6Zhjbe6J10c8i3BQ2gYSGJnoJt8GE9oVG5TZcMrLU Ljes+4VAG/3KLAR5lJmM4qCcl7JWNsGUIQcBhTsVL+7xWbngyeb6Y4oHCJ1heMO5rhpK QvBAYq0dZLszT5IGI0h6aVBIipwGzW7QE+V6s/vzMkSk0w7dtx2BL+xnUoPj6FE8Jgzs JrHVyCCdIpjxsmrkcq7K7HW+mfAHGAhFEnJ6SaFe7vdnYKxQ7GGHwJ2BVDIQ+HXhj9pJ prbA== X-Gm-Message-State: ALoCoQmFcIpqHH28DwyuUoQsRqc0BDgPnMX/jwgbTAfI6OlWLFOMgO0tif1rTRLD10CEDMM+0tMq X-Received: by 10.107.16.21 with SMTP id y21mr25788665ioi.194.1447459451427; Fri, 13 Nov 2015 16:04:11 -0800 (PST) Received: from [100.104.94.67] (80.sub-70-199-113.myvzw.com. [70.199.113.80]) by smtp.gmail.com with ESMTPSA id d7sm2241231igl.1.2015.11.13.16.04.07 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 13 Nov 2015 16:04:10 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) Subject: Re: FreeBSD smbfs horribly slow From: Mark Saad X-Mailer: iPhone Mail (13B143) In-Reply-To: Date: Fri, 13 Nov 2015 19:04:05 -0500 Cc: Allan Jude , freebsd-hackers@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <20151113162548.61529137@Papi> <56463ACE.5020605@freebsd.org> To: Mario Lobo X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Nov 2015 00:04:12 -0000 Mario Can you share more about your setup . What filesystem is the samba share exported from . What mount options on the= filesystem level do you use ? What version of samba , was it from ports or a package ? On the samba level can you tell us about your config ? Have you tried any of= the tuning from=20 https://calomel.org/samba_optimize.html Did you change any sysctls ? What did you set ? Lastly what's the hardware like ; CPU, nic type , ram , etc=20 --- Mark Saad | nonesuch@longcount.org > On Nov 13, 2015, at 6:13 PM, Mario Lobo wrote: >=20 > 2015-11-13 16:32 GMT-03:00 Allan Jude : >=20 >>> On 2015-11-13 14:25, Mario Lobo wrote: >>> Hi; >>>=20 >>> It seems no one in @questions had any info/pointers/interest on this >>> so I'm trying @hackers for some light. >>>=20 >>> Thanks, >>>=20 >>>=20 >>> Begin forwarded message: >>>=20 >>> Date: Wed, 11 Nov 2015 17:53:11 -0300 >>> From: Mario Lobo >>> To: freebsd-questions >>> Subject: FreeBSD smbfs horribly slow >>>=20 >>> Googling on this subject, I found: >> http://lists.freebsd.org/pipermail/freebsd-questions/2005-September/09871= 7.html >>> https://lists.freebsd.org/pipermail/freebsd-net/2013-January/034239.html= >> https://lists.freebsd.org/pipermail/freebsd-questions/2014-October/261804= .html >>>=20 >>> I am on 10.2-STABLE and using FreeBSD as a client to any amb share >>> continues to be very slow. >>>=20 >>> The share is mounted through mount_smbfs. I tried smbnetfs (fuse) and >>> it is just a tiny bit better but doesn't compare to other clients >>> (linux or win) when writing/reading files >>>=20 >>> It gets even worse if an application is doing operations with variable >>> size records inside a data file on the share. >>>=20 >>> Does anyone have any advice to improve this? >>>=20 >>> Thanks, >>>=20 >>>=20 >>>=20 >>> _______________________________________________ >>> freebsd-hackers@freebsd.org mailing list >>> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers >>> To unsubscribe, send any mail to " >> freebsd-hackers-unsubscribe@freebsd.org" >>=20 >> What kind of operations are you doing? >>=20 >> I just mounted a share from my windows desktop on my FreeBSD -CURRENT >> machine, and was able to write new files at 64 megabytes/s (roughly 1/2 >> the available gigabit/sec) >>=20 >> Reading it back only got 50 megabytes/s, not sure why. >>=20 >> -- >> Allan Jude > Which one is the server? Windows or FBSD? >=20 > I have no problems with either one being the server. The problem is > when FBSD is the client. >=20 > I wrote a daemon that executes operations on old DBF/NTX (clipper) > files (Yeah, I know ... but that's what they have for 20+ years ..). >=20 > Anyway, a site interacts with this daemon via tcp, with commands to > add/delete/update records/indexes, as well as finding keys on the > indexxes. >=20 > I prepared a test that has several of these routines together on a > 10.2-STABLE machine. >=20 > Enough to say that when executing the tests with the files stored > locally, the whole test takes 3-4 seconds to complete. >=20 > When doing the same test with the files on a share on the same wire (1G > connection, no matter which OS runs the share), the test takes around > 3:50 minutes to complete! >=20 > I am preparing a Centos VM and compiling the deamon on it to check the > results. >=20 > --=20 > Mario Lobo > http://www.mallavoodoo.com.br > FreeBSD since version 2.2.8 [not Pro-Audio.... YET!!] (99,7% winfoes FREE)= > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"= From owner-freebsd-hackers@freebsd.org Sat Nov 14 00:18:27 2015 Return-Path: Delivered-To: freebsd-hackers@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 67380A2EBEA for ; Sat, 14 Nov 2015 00:18:27 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from mx1.scaleengine.net (mx1.scaleengine.net [209.51.186.6]) by mx1.freebsd.org (Postfix) with ESMTP id 2A7A11A57 for ; Sat, 14 Nov 2015 00:18:26 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from [10.1.1.2] (unknown [10.1.1.2]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id D9E0CDEB4 for ; Sat, 14 Nov 2015 00:18:25 +0000 (UTC) Subject: Re: Fw: FreeBSD smbfs horribly slow To: freebsd-hackers@freebsd.org References: <20151113162548.61529137@Papi> <56463ACE.5020605@freebsd.org> From: Allan Jude Message-ID: <56467DE9.4060204@freebsd.org> Date: Fri, 13 Nov 2015 19:18:49 -0500 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="HTBJGG7PcUgcfbUMJbkQRliHUiv0WTjNI" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Nov 2015 00:18:27 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --HTBJGG7PcUgcfbUMJbkQRliHUiv0WTjNI Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 2015-11-13 18:13, Mario Lobo wrote: > 2015-11-13 16:32 GMT-03:00 Allan Jude : >=20 >> On 2015-11-13 14:25, Mario Lobo wrote: >>> Hi; >>> >>> It seems no one in @questions had any info/pointers/interest on this >>> so I'm trying @hackers for some light. >>> >>> Thanks, >>> >>> >>> Begin forwarded message: >>> >>> Date: Wed, 11 Nov 2015 17:53:11 -0300 >>> From: Mario Lobo >>> To: freebsd-questions >>> Subject: FreeBSD smbfs horribly slow >>> >>> Googling on this subject, I found: >>> >>> >> http://lists.freebsd.org/pipermail/freebsd-questions/2005-September/09= 8717.html >>> https://lists.freebsd.org/pipermail/freebsd-net/2013-January/034239.h= tml >>> >> https://lists.freebsd.org/pipermail/freebsd-questions/2014-October/261= 804.html >>> >>> I am on 10.2-STABLE and using FreeBSD as a client to any amb share >>> continues to be very slow. >>> >>> The share is mounted through mount_smbfs. I tried smbnetfs (fuse) and= >>> it is just a tiny bit better but doesn't compare to other clients >>> (linux or win) when writing/reading files >>> >>> It gets even worse if an application is doing operations with variabl= e >>> size records inside a data file on the share. >>> >>> Does anyone have any advice to improve this? >>> >>> Thanks, >>> >>> >>> >>> _______________________________________________ >>> freebsd-hackers@freebsd.org mailing list >>> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers >>> To unsubscribe, send any mail to " >> freebsd-hackers-unsubscribe@freebsd.org" >>> >> >> What kind of operations are you doing? >> >> I just mounted a share from my windows desktop on my FreeBSD -CURRENT >> machine, and was able to write new files at 64 megabytes/s (roughly 1/= 2 >> the available gigabit/sec) >> >> Reading it back only got 50 megabytes/s, not sure why. >> >> -- >> Allan Jude >> >> > Which one is the server? Windows or FBSD? >=20 > I have no problems with either one being the server. The problem is > when FBSD is the client. >=20 > I wrote a daemon that executes operations on old DBF/NTX (clipper) > files (Yeah, I know ... but that's what they have for 20+ years ..). >=20 > Anyway, a site interacts with this daemon via tcp, with commands to > add/delete/update records/indexes, as well as finding keys on the > indexxes. >=20 > I prepared a test that has several of these routines together on a > 10.2-STABLE machine. >=20 > Enough to say that when executing the tests with the files stored > locally, the whole test takes 3-4 seconds to complete. >=20 > When doing the same test with the files on a share on the same wire (1G= > connection, no matter which OS runs the share), the test takes around > 3:50 minutes to complete! >=20 > I am preparing a Centos VM and compiling the deamon on it to check the > results. >=20 My tests were done with the 'server' being a Windows 7 desktop sharing a directory on an NTFS formatted SSD, and the 'client' being mount_smbfs on FreeBSD 11 r284588 (quite a few months old now) --=20 Allan Jude --HTBJGG7PcUgcfbUMJbkQRliHUiv0WTjNI 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) iQIcBAEBAgAGBQJWRn3sAAoJEBmVNT4SmAt+nxwQANbv5MPukoRFRgblZS/DcL+K RgYPY+/0IAvPtZHQAZOdvyzjm4rWw38a05ShzpGbCjMaYszkxtknLh5Twse1BAgJ juSpq9XXIH5bjAus0Y2/1lGahNmRW0V/QBtTfEnGFOZ9gIT87ymkUSMHMDEMyYdt GgVccUzgN+eATDmBU31wzsSU4668LIyj2ojX8L9IRrISdRP7i4gM8YFiBCMj3jS8 mwspx53wx3X6v6pcfoD1Ml/DQjuP1zrz9DuviUqX7SVNT7WEiEtMWViWuM84C7W6 aJwAh86wkSAG3Env1/GjDTy9rd/WNk8cjO4Dl/BJvYRss9GxllfHpOkQXe5F1szj /E5E6JbPnLgnuPto9hDbSOTQf4ZmAuZN8lnD+4AsZwPNRVfOcdoQfFM2TjQxDgwv NHwPBGEqBKJABrZtBrZnkNRxifz/lcx0Eq5tpZxoPbW18Dd+wyqwAeXrPFfVLUg+ U+0h2meyMbM+IR5U8u2Csf92+1QLkA4oGWYuSqDGgUoih9+1FUcAyvOf//mVxHIQ RIA54k68q/0JzVDCpFRjEmaalnYVmCIA768SJp45aEAF9HwlMfKXOzkOyr1PMPfy b4W056rdXnFo3i7PMXZy+fJFDnjexfk0Q8PI2dwtABZ62XNPvQ3gDzLyKhMpGpI3 BA3jMwCbCiWPSO2hDn4S =2jDN -----END PGP SIGNATURE----- --HTBJGG7PcUgcfbUMJbkQRliHUiv0WTjNI-- From owner-freebsd-hackers@freebsd.org Sat Nov 14 00:20:50 2015 Return-Path: Delivered-To: freebsd-hackers@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 606F4A2EC89 for ; Sat, 14 Nov 2015 00:20:50 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from mx1.scaleengine.net (mx1.scaleengine.net [209.51.186.6]) by mx1.freebsd.org (Postfix) with ESMTP id 23C9A1BCA for ; Sat, 14 Nov 2015 00:20:49 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from [10.1.1.2] (unknown [10.1.1.2]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id C3324DEC8 for ; Sat, 14 Nov 2015 00:20:48 +0000 (UTC) Subject: Re: Fw: FreeBSD smbfs horribly slow To: freebsd-hackers@freebsd.org References: <20151113162548.61529137@Papi> <56463ACE.5020605@freebsd.org> From: Allan Jude Message-ID: <56467E7B.3010704@freebsd.org> Date: Fri, 13 Nov 2015 19:21:15 -0500 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <56463ACE.5020605@freebsd.org> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="BFKFOFUJRsOnxP980uN0WUWvvepetopR5" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Nov 2015 00:20:50 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --BFKFOFUJRsOnxP980uN0WUWvvepetopR5 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 2015-11-13 14:32, Allan Jude wrote: > On 2015-11-13 14:25, Mario Lobo wrote: >> Hi; >> >> It seems no one in @questions had any info/pointers/interest on this >> so I'm trying @hackers for some light. >> >> Thanks, >> >> >> Begin forwarded message: >> >> Date: Wed, 11 Nov 2015 17:53:11 -0300 >> From: Mario Lobo >> To: freebsd-questions >> Subject: FreeBSD smbfs horribly slow >> >> Googling on this subject, I found: >> >> http://lists.freebsd.org/pipermail/freebsd-questions/2005-September/09= 8717.html >> https://lists.freebsd.org/pipermail/freebsd-net/2013-January/034239.ht= ml >> https://lists.freebsd.org/pipermail/freebsd-questions/2014-October/261= 804.html >> >> I am on 10.2-STABLE and using FreeBSD as a client to any amb share >> continues to be very slow. >> >> The share is mounted through mount_smbfs. I tried smbnetfs (fuse) and >> it is just a tiny bit better but doesn't compare to other clients >> (linux or win) when writing/reading files >> >> It gets even worse if an application is doing operations with variable= >> size records inside a data file on the share. >> >> Does anyone have any advice to improve this? >> >> Thanks, >> >> >> >> _______________________________________________ >> freebsd-hackers@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.= org" >> >=20 > What kind of operations are you doing? >=20 > I just mounted a share from my windows desktop on my FreeBSD -CURRENT > machine, and was able to write new files at 64 megabytes/s (roughly 1/2= > the available gigabit/sec) >=20 > Reading it back only got 50 megabytes/s, not sure why. >=20 My tests: #mount_smbfs -I 10.1.1.2 //allan@seawolf/junk /mnt Password: #cd /mnt #ls bsdnow_ep104_0.mov bsdnow_ep106_8.mov bsdnow_ep114_1.mov bsdnow_ep104_2.mov bsdnow_ep106_8b.mov #dd if=3D/dev/zero of=3Dzerofile bs=3D1m count=3D4k 4096+0 records in 4096+0 records out 4294967296 bytes transferred in 65.787577 secs (65285385 bytes/sec) dd if=3Dzerofile of=3D/dev/null bs=3D1m ^C2446+0 records in 2446+0 records out 2564816896 bytes transferred in 50.894606 secs (50394670 bytes/sec) #cd / #umount /mnt --=20 Allan Jude --BFKFOFUJRsOnxP980uN0WUWvvepetopR5 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) iQIcBAEBAgAGBQJWRn57AAoJEBmVNT4SmAt+9ckP/i3aLogP9PlRQSbTUpoc58Zi a8trJXLQ3sbKEZtyeW1kK2oY3HQFpUNgxInR1Pu+HFc07s0B8WDRxSC8JV3f+U55 lYFRlhcUtqApIkzTDp1k1vm7fj3Yaj2MCG/py7k6V1L2ARzZ0p6T7UhFQMhjKIBr tqJsdIpeb6vnn88dTFGzOB0PMlVza5KcTo0mPGt+xaI6cNGpKjqsVs9wuqoxkJ5M JbCdy7qSFMnIWz+SF0SdXuOFXyxAzexfYeEkn8gDKYRyvi0IVeErbSywQLmcC4zv mGaauY1NCTHyvfv4WN8XnLWF/AYy9Z0Bn1bXeOxnviA8QYqlEW2BujtCuFQVHmeG ORm8NiLGQNwyfXNBSt62nYan5OMG3jRzA5qajwpK/YsGAiPo6Xb06Ttjh//8Yyco Pvukx/+lq8S2sQN5yzqEDupm9VVeduO8zGQvCFHrpu0CF4q4Om2fDEtxY8+s9KJ3 cD9Df2AQSjaHzRKz7pY/PAMe9XdTDGH0ZJCF8BOo4QsZ0pWVMOrdfJfTyKx5be2m lncJEYEuR9v7PV85OvNfANt79bHKUy1GmHW/6ec7AWm34H4XXXFkRCh6AjPcCj6r /WvCJiw970xTfFHEjzLrKVbDHAxujljIrvYr6T3eSqB+xHV3vLzfSTjQgTD3H4J6 oJnK1l32OnOc2J1dRofM =pmH9 -----END PGP SIGNATURE----- --BFKFOFUJRsOnxP980uN0WUWvvepetopR5-- From owner-freebsd-hackers@freebsd.org Sat Nov 14 00:31:03 2015 Return-Path: Delivered-To: freebsd-hackers@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 BDED6A2EE6C for ; Sat, 14 Nov 2015 00:31:03 +0000 (UTC) (envelope-from jhellenthal@dataix.net) Received: from mail-ig0-x235.google.com (mail-ig0-x235.google.com [IPv6:2607:f8b0:4001:c05::235]) (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 804491FAD for ; Sat, 14 Nov 2015 00:31:03 +0000 (UTC) (envelope-from jhellenthal@dataix.net) Received: by igvi2 with SMTP id i2so46773148igv.0 for ; Fri, 13 Nov 2015 16:31:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dataix.net; s=rsa; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=IghE7lfakDNkzhI9W5qc4+uzzKDnKM1pED5eem+A6Ec=; b=aQ6FhR3U1YCGVu8Ek5F3dSknJQ5wPVio25wYo77FHb1RXljoZNIxnfaGLnaV0g6dX2 NoDlyZ/VHyELpFzritrDjsoEewFYZJ2GLOCK61EJwjHsSUVNeY5JDy1RQeLi9X4Ynd1n BqttJjV/D2tfuyg+RrtVT+Y7ljLF94xuKz4rQ= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=IghE7lfakDNkzhI9W5qc4+uzzKDnKM1pED5eem+A6Ec=; b=GuF/yJa2pE66LqPl9Qe2p+F8797rMdqjHeQvLJWl/mdVrOHXH9hKuqEUgwjGA9l5Zy 4RsWln8wA+vRsGCSmuZRQTNrUv/e54JrFrBx7ZZ/97LC0qDIgdLAKCtCmPv3y4gp+rMt 46PV7E2gEAR1chjvAH9FI/xDZ96x3MvPqUfeYRkSPbRz8vDT7cZHTmLX1GBVDU84paOz 1bLsixKpuI7FDSZVMSxiRg70wP1+NKDEq4E9OBSRp/CMDbUyHD0QGtijT13kW4K7CHkN PkCdDXV0BibMIKPhG1o6Oqgi1LzxQ9OPoc54iwkBZC74/tNNOA1YdNkPkxkQZQ+xSfYZ eYwQ== X-Gm-Message-State: ALoCoQnBtMlKAbAWgP4/SboAd6rwCMG4m9tI63QrMurJgeKc/QvKZ506pSSnvlJoqhOQ8FCk9VwF X-Received: by 10.50.3.34 with SMTP id 2mr6889057igz.54.1447461062743; Fri, 13 Nov 2015 16:31:02 -0800 (PST) Received: from [172.31.32.31] (cpe-65-26-238-24.wi.res.rr.com. [65.26.238.24]) by smtp.gmail.com with ESMTPSA id s38sm5971959ioi.18.2015.11.13.16.31.02 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 13 Nov 2015 16:31:02 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) Subject: Re: FreeBSD smbfs horribly slow From: Jason Hellenthal X-Mailer: iPhone Mail (13B143) In-Reply-To: <56467E7B.3010704@freebsd.org> Date: Fri, 13 Nov 2015 18:31:01 -0600 Cc: freebsd-hackers@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <20151113162548.61529137@Papi> <56463ACE.5020605@freebsd.org> <56467E7B.3010704@freebsd.org> To: Allan Jude X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Nov 2015 00:31:03 -0000 Is that with the QoS Limit Reservable Bandwidth set to zero ? Or QoS uncheck= ed (disabled) on the source interface of the Win7 machine. By default Win7 l= imits 10% bandwidth reserved without adjusting the local GPO of the system a= nd sometimes fights with itself to get you the information as quick as you'd= like. Changes here are immediate=20 http://windows7themes.net/en-us/disable-bandwidth-limit-in-windows-7-speed-u= p-your-internet/ --=20 Jason Hellenthal JJH48-ARIN On Nov 13, 2015, at 18:21, Allan Jude wrote: > On 2015-11-13 14:32, Allan Jude wrote: >> On 2015-11-13 14:25, Mario Lobo wrote: >> Hi; >>=20 >> It seems no one in @questions had any info/pointers/interest on this >> so I'm trying @hackers for some light. >>=20 >> Thanks, >>=20 >>=20 >> Begin forwarded message: >>=20 >> Date: Wed, 11 Nov 2015 17:53:11 -0300 >> From: Mario Lobo >> To: freebsd-questions >> Subject: FreeBSD smbfs horribly slow >>=20 >> Googling on this subject, I found: >>=20 >> http://lists.freebsd.org/pipermail/freebsd-questions/2005-September/09871= 7.html >> https://lists.freebsd.org/pipermail/freebsd-net/2013-January/034239.html >> https://lists.freebsd.org/pipermail/freebsd-questions/2014-October/261804= .html >>=20 >> I am on 10.2-STABLE and using FreeBSD as a client to any amb share >> continues to be very slow. >>=20 >> The share is mounted through mount_smbfs. I tried smbnetfs (fuse) and >> it is just a tiny bit better but doesn't compare to other clients >> (linux or win) when writing/reading files >>=20 >> It gets even worse if an application is doing operations with variable >> size records inside a data file on the share. >>=20 >> Does anyone have any advice to improve this? >>=20 >> Thanks, >>=20 >>=20 >>=20 >> _______________________________________________ >> freebsd-hackers@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org= " >=20 > What kind of operations are you doing? >=20 > I just mounted a share from my windows desktop on my FreeBSD -CURRENT > machine, and was able to write new files at 64 megabytes/s (roughly 1/2 > the available gigabit/sec) >=20 > Reading it back only got 50 megabytes/s, not sure why. My tests: #mount_smbfs -I 10.1.1.2 //allan@seawolf/junk /mnt Password: #cd /mnt #ls bsdnow_ep104_0.mov bsdnow_ep106_8.mov bsdnow_ep114_1.mov bsdnow_ep104_2.mov bsdnow_ep106_8b.mov #dd if=3D/dev/zero of=3Dzerofile bs=3D1m count=3D4k 4096+0 records in 4096+0 records out 4294967296 bytes transferred in 65.787577 secs (65285385 bytes/sec) dd if=3Dzerofile of=3D/dev/null bs=3D1m ^C2446+0 records in 2446+0 records out 2564816896 bytes transferred in 50.894606 secs (50394670 bytes/sec) #cd / #umount /mnt --=20 Allan Jude From owner-freebsd-hackers@freebsd.org Sat Nov 14 14:45:40 2015 Return-Path: Delivered-To: freebsd-hackers@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 1097CA2F188 for ; Sat, 14 Nov 2015 14:45:40 +0000 (UTC) (envelope-from lobo@bsd.com.br) Received: from mail-qk0-x241.google.com (mail-qk0-x241.google.com [IPv6:2607:f8b0:400d:c09::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 BF8B71996 for ; Sat, 14 Nov 2015 14:45:39 +0000 (UTC) (envelope-from lobo@bsd.com.br) Received: by qkbo184 with SMTP id o184so123908qkb.3 for ; Sat, 14 Nov 2015 06:45:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsd.com.br; s=capeta; h=date:from:to:cc:subject:message-id:in-reply-to:references :organization:mime-version:content-type:content-transfer-encoding; bh=ljKXxUFyj9s4w+XsbDk22PLEIGk+cC8/xjzjjtoPFFE=; b=KlvJVdnpg0YveYirn3eFVx8hrgFgsRE6VZUucql/E96bo3jq//wRtEOur8T1+yqPak Cv1smdDtwHnqQAIkQzRjIq+7/afW1kSWiydf2OMOl3CPHNRusiQv741jCCRw60L0RzQh NQNzqkFGjqvALCNMXxZmBkgTlL4m6z7pLoQrU= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:organization:mime-version:content-type :content-transfer-encoding; bh=ljKXxUFyj9s4w+XsbDk22PLEIGk+cC8/xjzjjtoPFFE=; b=R2TgnoOWq8kOzrLwUUkbH6rUqdwrbE/Zy/k9xtKSjflZ+Qb0WQ098mRNj9C7bxv1Fw iL2A47ZCV/30i1LKW0OD/ZI3a5WIF7ovvx7TIUachUfz6WH3hqgtFdTj6/s/uWzN6t5y fKtut5k0H2/gdXCamOTkOt9wzZH1VByl+oD+lId3xG2J+EMxHKNvJACt7EM8Jp82weUw R99yaz6IHbl2/0z0M5+TNccOZVZH9VPpizPg4qk5V8HARFhIGbbNvkMl2X6SV327oRnf vHlCpCiW6UfOoHd8pS+EqK6I6rAg3yVDEVGwAjdKtLjtsH5/CBq3XUPKH98iCCoOhDFo elwg== X-Gm-Message-State: ALoCoQnzs8gIa3yNGEYj4Hs+aUzRC+0svsn7Cy0okmt9zwanMGHwlVIkoviosOA+C466e4lCGnTH X-Received: by 10.55.49.197 with SMTP id x188mr28035608qkx.45.1447512338590; Sat, 14 Nov 2015 06:45:38 -0800 (PST) Received: from Papi ([179.181.62.208]) by smtp.gmail.com with ESMTPSA id u59sm1593283qge.0.2015.11.14.06.45.34 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 14 Nov 2015 06:45:38 -0800 (PST) Date: Sat, 14 Nov 2015 11:50:22 -0300 From: Mario Lobo To: Mark Saad Cc: Allan Jude , freebsd-hackers@freebsd.org Subject: Re: FreeBSD smbfs horribly slow Message-ID: <20151114115022.781c0bc1@Papi> In-Reply-To: References: <20151113162548.61529137@Papi> <56463ACE.5020605@freebsd.org> Organization: BSD X-Mailer: Claws Mail 3.12.0 (GTK+ 2.24.25; amd64-portbld-freebsd10.2) 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.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Nov 2015 14:45:40 -0000 On Fri, 13 Nov 2015 19:04:05 -0500 Mark Saad wrote: > Mario > Can you share more about your setup . > What filesystem is the samba share exported from ? The shares tested were both from a FBSD (10.2-STABLE) samba4 and Linux (Centos) samba 3.6. > What mount options > on the filesystem level do you use ? > smbfs rw,noatime,-N,-Iserverip 0 0 > What version of samba , was it from ports or a package ? > See above. > On the samba level can you tell us about your config ? Have you tried > any of the tuning from https://calomel.org/samba_optimize.html > Like I said, the problem is not with the server. > Did you change any sysctls ? What did you set ? > > Lastly what's the hardware like ; CPU, nic type , ram , etc > I tried the same FBSD client on different hardware. Made no difference. > --- > Mark Saad | nonesuch@longcount.org > > > On Nov 13, 2015, at 6:13 PM, Mario Lobo wrote: > > > > 2015-11-13 16:32 GMT-03:00 Allan Jude : > > > >>> On 2015-11-13 14:25, Mario Lobo wrote: > >>> Hi; > >>> > >>> It seems no one in @questions had any info/pointers/interest on > >>> this so I'm trying @hackers for some light. > >>> > >>> Thanks, > >>> > >>> > >>> Begin forwarded message: > >>> > >>> Date: Wed, 11 Nov 2015 17:53:11 -0300 > >>> From: Mario Lobo > >>> To: freebsd-questions > >>> Subject: FreeBSD smbfs horribly slow > >>> > >>> Googling on this subject, I found: > >> http://lists.freebsd.org/pipermail/freebsd-questions/2005-September/098717.html > >>> https://lists.freebsd.org/pipermail/freebsd-net/2013-January/034239.html > >> https://lists.freebsd.org/pipermail/freebsd-questions/2014-October/261804.html > >>> > >>> I am on 10.2-STABLE and using FreeBSD as a client to any amb share > >>> continues to be very slow. > >>> > >>> The share is mounted through mount_smbfs. I tried smbnetfs (fuse) > >>> and it is just a tiny bit better but doesn't compare to other > >>> clients (linux or win) when writing/reading files > >>> > >>> It gets even worse if an application is doing operations with > >>> variable size records inside a data file on the share. > >>> > >>> Does anyone have any advice to improve this? > >>> > >>> Thanks, > >>> > >>> > >>> > >>> _______________________________________________ > >>> freebsd-hackers@freebsd.org mailing list > >>> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > >>> To unsubscribe, send any mail to " > >> freebsd-hackers-unsubscribe@freebsd.org" > >> > >> What kind of operations are you doing? > >> > >> I just mounted a share from my windows desktop on my FreeBSD > >> -CURRENT machine, and was able to write new files at 64 > >> megabytes/s (roughly 1/2 the available gigabit/sec) > >> > >> Reading it back only got 50 megabytes/s, not sure why. > >> > >> -- > >> Allan Jude > > Which one is the server? Windows or FBSD? > > > > I have no problems with either one being the server. The problem is > > when FBSD is the client. > > > > I wrote a daemon that executes operations on old DBF/NTX (clipper) > > files (Yeah, I know ... but that's what they have for 20+ years ..). > > > > Anyway, a site interacts with this daemon via tcp, with commands to > > add/delete/update records/indexes, as well as finding keys on the > > indexxes. > > > > I prepared a test that has several of these routines together on a > > 10.2-STABLE machine. > > > > Enough to say that when executing the tests with the files stored > > locally, the whole test takes 3-4 seconds to complete. > > > > When doing the same test with the files on a share on the same wire > > (1G connection, no matter which OS runs the share), the test takes > > around 3:50 minutes to complete! > > > > I am preparing a Centos VM and compiling the deamon on it to check > > the results. > > > > -- > > Mario Lobo > > http://www.mallavoodoo.com.br > > FreeBSD since version 2.2.8 [not Pro-Audio.... YET!!] (99,7% > > winfoes FREE) _______________________________________________ > > freebsd-hackers@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > > To unsubscribe, send any mail to > > "freebsd-hackers-unsubscribe@freebsd.org" -- Mario Lobo http://www.mallavoodoo.com.br FreeBSD since 2.2.8 [not Pro-Audio.... YET!!] "UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things." From owner-freebsd-hackers@freebsd.org Sat Nov 14 22:11:03 2015 Return-Path: Delivered-To: freebsd-hackers@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 80FE9A2F69D for ; Sat, 14 Nov 2015 22:11:03 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-annu.net.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id 23F351F20; Sat, 14 Nov 2015 22:11:02 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) IronPort-PHdr: 9a23:HLBFORLxyAA+ITc6J9mcpTZWNBhigK39O0sv0rFitYgVKvvxwZ3uMQTl6Ol3ixeRBMOAu68C1rad6vqxEUU7or+/81k6OKRWUBEEjchE1ycBO+WiTXPBEfjxciYhF95DXlI2t1uyMExSBdqsLwaK+i760zceF13FOBZvIaytQ8iJ35nxirz5oseCKyxzxxODIppKZC2sqgvQssREyaBDEY0WjiXzn31TZu5NznlpL1/A1zz158O34YIxu38I46Fp34d6XK77Z6U1S6BDRHRjajhtpZ6jiB/YUAHa5mcASjdR1QVXHE7A5RX+V4n2tSf9sax23yzcN9elcbdhfD247qAjbBjij29TMzkz90ndkcA2h6Ve5hi78U9R2YnRNbuUP/k2W6rWftcXQCIVRMNYXC9FD4aUcowAEucFJeYepICr9AhGlge3GQT5XLCn8TRPnHKjmPRii+k= X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A2DPAQAesEdW/61jaINehA5vBr5HAQ2BZBcMhSNKAoFkFAEBAQEBAQEBgQmCLYIHAQEBBAEBASAEJyALEAIBCBEDAQIBAgINGQICJwEJGAEFCAIECAcEARwBA4gNDaZTkA4BAQEBAQEBAQEBAQEBAQEBAQEBGoEBhVOEfoQ7AQEFgnk6E4ExBYdGhkuIN4UdhSCERUmRTYRig3ACHwEBQoIRHYF0IDQBBoQDOoEHAQEB X-IronPort-AV: E=Sophos;i="5.20,294,1444708800"; d="scan'208";a="251859744" Received: from nipigon.cs.uoguelph.ca (HELO zcs1.mail.uoguelph.ca) ([131.104.99.173]) by esa-annu.net.uoguelph.ca with ESMTP; 14 Nov 2015 17:10:56 -0500 Received: from localhost (localhost [127.0.0.1]) by zcs1.mail.uoguelph.ca (Postfix) with ESMTP id 0AEF815F565; Sat, 14 Nov 2015 17:10:56 -0500 (EST) Received: from zcs1.mail.uoguelph.ca ([127.0.0.1]) by localhost (zcs1.mail.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id uYgEA5yM56TC; Sat, 14 Nov 2015 17:10:55 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by zcs1.mail.uoguelph.ca (Postfix) with ESMTP id E555415F56D; Sat, 14 Nov 2015 17:10:54 -0500 (EST) X-Virus-Scanned: amavisd-new at zcs1.mail.uoguelph.ca Received: from zcs1.mail.uoguelph.ca ([127.0.0.1]) by localhost (zcs1.mail.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id CG5VoHt5bSlu; Sat, 14 Nov 2015 17:10:54 -0500 (EST) Received: from zcs1.mail.uoguelph.ca (zcs1.mail.uoguelph.ca [172.17.95.18]) by zcs1.mail.uoguelph.ca (Postfix) with ESMTP id C595315F565; Sat, 14 Nov 2015 17:10:54 -0500 (EST) Date: Sat, 14 Nov 2015 17:10:54 -0500 (EST) From: Rick Macklem To: Mario Lobo Cc: Mark Saad , freebsd-hackers@freebsd.org, Allan Jude Message-ID: <1312151904.87133792.1447539054621.JavaMail.zimbra@uoguelph.ca> In-Reply-To: <20151114115022.781c0bc1@Papi> References: <20151113162548.61529137@Papi> <56463ACE.5020605@freebsd.org> <20151114115022.781c0bc1@Papi> Subject: Re: FreeBSD smbfs horribly slow MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.95.11] X-Mailer: Zimbra 8.0.9_GA_6191 (ZimbraWebClient - FF34 (Win)/8.0.9_GA_6191) Thread-Topic: FreeBSD smbfs horribly slow Thread-Index: 2xR+YRa6JksNN8Sh1bv7mWSgUyB6kQ== X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Nov 2015 22:11:03 -0000 Mario Lobo wrote: > On Fri, 13 Nov 2015 19:04:05 -0500 > Mark Saad wrote: > > > Mario > > Can you share more about your setup . > > What filesystem is the samba share exported from ? > > The shares tested were both from a FBSD (10.2-STABLE) samba4 and Linux > (Centos) samba 3.6. > > > What mount options > > on the filesystem level do you use ? > > > > smbfs rw,noatime,-N,-Iserverip 0 0 > > > What version of samba , was it from ports or a package ? > > > > See above. > > > On the samba level can you tell us about your config ? Have you tried > > any of the tuning from https://calomel.org/samba_optimize.html > > > > Like I said, the problem is not with the server. > > > Did you change any sysctls ? What did you set ? > > > > Lastly what's the hardware like ; CPU, nic type , ram , etc > > > > I tried the same FBSD client on different hardware. Made no difference. > Did that different hardware have a different type of net interface that uses a different net device driver? I have no idea if smbfs can do the same thing, but both NFS and iSCSI can generate TCP TSO output segments of near 64K in data length and that can cause problems for some net device drivers. --> If the net interface has TSO enabled, try disabling it. I never use smbfs, so I can't help more, rick > > > > --- > > Mark Saad | nonesuch@longcount.org > > > > > On Nov 13, 2015, at 6:13 PM, Mario Lobo wrote: > > > > > > 2015-11-13 16:32 GMT-03:00 Allan Jude : > > > > > >>> On 2015-11-13 14:25, Mario Lobo wrote: > > >>> Hi; > > >>> > > >>> It seems no one in @questions had any info/pointers/interest on > > >>> this so I'm trying @hackers for some light. > > >>> > > >>> Thanks, > > >>> > > >>> > > >>> Begin forwarded message: > > >>> > > >>> Date: Wed, 11 Nov 2015 17:53:11 -0300 > > >>> From: Mario Lobo > > >>> To: freebsd-questions > > >>> Subject: FreeBSD smbfs horribly slow > > >>> > > >>> Googling on this subject, I found: > > >> http://lists.freebsd.org/pipermail/freebsd-questions/2005-September/098717.html > > >>> https://lists.freebsd.org/pipermail/freebsd-net/2013-January/034239.html > > >> https://lists.freebsd.org/pipermail/freebsd-questions/2014-October/261804.html > > >>> > > >>> I am on 10.2-STABLE and using FreeBSD as a client to any amb share > > >>> continues to be very slow. > > >>> > > >>> The share is mounted through mount_smbfs. I tried smbnetfs (fuse) > > >>> and it is just a tiny bit better but doesn't compare to other > > >>> clients (linux or win) when writing/reading files > > >>> > > >>> It gets even worse if an application is doing operations with > > >>> variable size records inside a data file on the share. > > >>> > > >>> Does anyone have any advice to improve this? > > >>> > > >>> Thanks, > > >>> > > >>> > > >>> > > >>> _______________________________________________ > > >>> freebsd-hackers@freebsd.org mailing list > > >>> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > > >>> To unsubscribe, send any mail to " > > >> freebsd-hackers-unsubscribe@freebsd.org" > > >> > > >> What kind of operations are you doing? > > >> > > >> I just mounted a share from my windows desktop on my FreeBSD > > >> -CURRENT machine, and was able to write new files at 64 > > >> megabytes/s (roughly 1/2 the available gigabit/sec) > > >> > > >> Reading it back only got 50 megabytes/s, not sure why. > > >> > > >> -- > > >> Allan Jude > > > Which one is the server? Windows or FBSD? > > > > > > I have no problems with either one being the server. The problem is > > > when FBSD is the client. > > > > > > I wrote a daemon that executes operations on old DBF/NTX (clipper) > > > files (Yeah, I know ... but that's what they have for 20+ years ..). > > > > > > Anyway, a site interacts with this daemon via tcp, with commands to > > > add/delete/update records/indexes, as well as finding keys on the > > > indexxes. > > > > > > I prepared a test that has several of these routines together on a > > > 10.2-STABLE machine. > > > > > > Enough to say that when executing the tests with the files stored > > > locally, the whole test takes 3-4 seconds to complete. > > > > > > When doing the same test with the files on a share on the same wire > > > (1G connection, no matter which OS runs the share), the test takes > > > around 3:50 minutes to complete! > > > > > > I am preparing a Centos VM and compiling the deamon on it to check > > > the results. > > > > > > -- > > > Mario Lobo > > > http://www.mallavoodoo.com.br > > > FreeBSD since version 2.2.8 [not Pro-Audio.... YET!!] (99,7% > > > winfoes FREE) _______________________________________________ > > > freebsd-hackers@freebsd.org mailing list > > > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > > > To unsubscribe, send any mail to > > > "freebsd-hackers-unsubscribe@freebsd.org" > > > > -- > Mario Lobo > http://www.mallavoodoo.com.br > FreeBSD since 2.2.8 [not Pro-Audio.... YET!!] > > "UNIX was not designed to stop you from doing stupid things, > because that would also stop you from doing clever things." > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" >