From owner-freebsd-hackers@freebsd.org Sun Mar 13 03:39:50 2016 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 491D5A92D64; Sun, 13 Mar 2016 03:39:50 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from mail.metricspace.net (207-172-209-83.c3-0.arl-ubr1.sbo-arl.ma.static.cable.rcn.com [207.172.209.83]) by mx1.freebsd.org (Postfix) with ESMTP id 297C6B9D; Sun, 13 Mar 2016 03:39:49 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from [IPv6:2001:470:1f11:617:8fe:6a13:797b:e9c9] (unknown [IPv6:2001:470:1f11:617:8fe:6a13:797b:e9c9]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: eric) by mail.metricspace.net (Postfix) with ESMTPSA id 5614C144F; Sun, 13 Mar 2016 03:39:43 +0000 (UTC) Subject: Blank screen on resume From: Eric McCorkle Content-Type: text/plain; charset=us-ascii X-Mailer: iPad Mail (13D15) Message-Id: Date: Sat, 12 Mar 2016 22:39:42 -0500 To: freebsd-acpi@freebsd.org, "freebsd-hackers@freebsd.org" Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (1.0) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Mar 2016 03:39:50 -0000 Hello everyone, It seems I'm plagued by blank screens on resume again on a different laptop.= .. *sigh* I've done quite a bit of diagnostic work on this, and there seem to be some c= lues, but I'm a bit stumped at this point. The following github repo has pa= tches that add extra logging, which has proven useful in my attempts to diag= nose the issue: https://github.com/emc2/freebsd (sorry for distributing patc= hes/logs in this way, but the logs are quite big). Also in this repo, there= 's a pciconf, devinfo, and dmesg file. The dmesg file shows the trace from b= ooting a patched kernel in verbose mode then suspending it. There's two main curiosities in the dmesg trace. The first is that the powe= r state of all the vgapci device seems to be 0 as opposed to 3 during resume= , which was causing acpi_set_powerstate_method to skip resetting its power d= uring resume. I tried a simple patch (you can see it in the patch and its e= ffects in the trace), but that didn't seem to work. A second curiosity is t= hat acpi_pwr_switch_consumer only seems to have an effect during resume. The only other real lead I have is that the display doesn't seem to be activ= e in acpi_video. I'm not sure if this is an artifact of the efifb driver. Lastly, I recall looking into vga bios calls from earlier such efforts. I i= magine there's something similar for efifb, but I've been unable to track do= wn where this is happening. Advice or information on that front would be mu= ch appreciated. Best, Eric= From owner-freebsd-hackers@freebsd.org Sun Mar 13 04:45:01 2016 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 A490EACD386; Sun, 13 Mar 2016 04:45:01 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) 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 724437E0; Sun, 13 Mar 2016 04:45:01 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-ig0-x235.google.com with SMTP id nk17so16818393igb.1; Sat, 12 Mar 2016 20:45:01 -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; bh=9YdzS50fM9i8vJ8bKalkMQFiGbF+jXai8pKHLJxWEnw=; b=RWcP1A9ghYqynLXN5jjQxiMfNb0WLsGc1eq4izMo/Rv1Gblc28NHw/GW5V00Y8lWwb Z/emXl12MnrVaBdFQTe6Gw6akI9KMc8eJZSg0aitXQeKwkT5dqJ0K2Un+JflnMoXeq6h l9WDSzSyenn6X7uSuuYb6QcC8TKqeGYapUGPIiN/uyou6KOpI6H/+gbARltuyqk6JfHJ 5IpQJhAcnlQxgt8/9HiIE1crTrXP1EubwhJqrN8+D369CAKfcsDtKx88oszQ0ivmMBs+ ce+3ZExG6RX2EfimWldgeU1DOMiZexSrtqauCZdAkWl6sYhj5L0pIWLsmekomhcaFxrV ZPnA== 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; bh=9YdzS50fM9i8vJ8bKalkMQFiGbF+jXai8pKHLJxWEnw=; b=cM2PeymixAlTBoOhQDoenOMpHvinUjH0srCnbvtTF6xRcM19OtgM3H3eKtibk22dj9 PIgZhu9jzgShj6rQsAlXJ2C2h4g+uz0x8Wdd8azc7/xIt7w1AQ5Abtn0Dwwh2Z5iOwnA ry+yxwTDhiQ0VHyVrzfcvBKtauFWPIN9G0/khouv7SUH60yZrKGFT8sF/rFsxkA3w+mr jt/WfNi6/mqkFBwN2FHYY78xae8Q/URD06c03XO54beT5jvphDz/3k2KOc5hWnD1yHO5 tulRVmIQ1Nb5kHETcDQhTUe9Z78lnh9FCGkPD2O0RAxiXRn9X4huOcS3qIUnAIVAk6pq uCjQ== X-Gm-Message-State: AD7BkJLL5dh/9BtXekNG3W588j+ZJQZNGno/rc8ipSj3fRjBzE1GbtQ1Vr/GUaJlTBQ7i3AvskxcbGck8+rMXw== MIME-Version: 1.0 X-Received: by 10.50.157.39 with SMTP id wj7mr10901309igb.61.1457844300747; Sat, 12 Mar 2016 20:45:00 -0800 (PST) Received: by 10.36.14.19 with HTTP; Sat, 12 Mar 2016 20:45:00 -0800 (PST) In-Reply-To: References: Date: Sat, 12 Mar 2016 20:45:00 -0800 Message-ID: Subject: Re: Blank screen on resume From: Adrian Chadd To: Eric McCorkle Cc: "freebsd-acpi@freebsd.org" , "freebsd-hackers@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Mailman-Approved-At: Sun, 13 Mar 2016 05:29:15 +0000 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Mar 2016 04:45:01 -0000 Hi, Which laptop? Which chipset? etc. -adrian From owner-freebsd-hackers@freebsd.org Sun Mar 13 19:45:53 2016 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 ABDE4ACF3E4; Sun, 13 Mar 2016 19:45:53 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-6.mit.edu (dmz-mailsec-scanner-6.mit.edu [18.7.68.35]) (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 4A2C7CE3; Sun, 13 Mar 2016 19:45:52 +0000 (UTC) (envelope-from kaduk@mit.edu) X-AuditID: 12074423-4bfff700000061cf-8a-56e5c369211b Received: from mailhub-auth-4.mit.edu ( [18.7.62.39]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by (Symantec Messaging Gateway) with SMTP id 9A.44.25039.963C5E65; Sun, 13 Mar 2016 15:45:45 -0400 (EDT) Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by mailhub-auth-4.mit.edu (8.13.8/8.9.2) with ESMTP id u2DJjip4026984; Sun, 13 Mar 2016 15:45:44 -0400 Received: from multics.mit.edu (system-low-sipb.mit.edu [18.187.2.37]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id u2DJjf1s024531 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 13 Mar 2016 15:45:44 -0400 Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id u2DJjfU6020884; Sun, 13 Mar 2016 15:45:41 -0400 (EDT) Date: Sun, 13 Mar 2016 15:45:40 -0400 (EDT) From: Benjamin Kaduk X-X-Sender: kaduk@multics.mit.edu To: freebsd-hackers@FreeBSD.org cc: freebsd-current@FreeBSD.org Subject: Call for 2016Q1 quarterly status reports Message-ID: User-Agent: Alpine 1.10 (GSO 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrLIsWRmVeSWpSXmKPExsUixG6nrpt5+GmYwYqLwhZz3nxgsti++R+j A5PHjE/zWQIYo7hsUlJzMstSi/TtErgyzv85wFZwkqviUa97A+Mzji5GDg4JAROJJU+duhi5 OIQE2pgkHjR0sXYxcgI5GxklFr6th0gcYpJ48rCBFcJpYJT4NfEHO0g3i4C2xLOZBSANbAJq EutXXGMGsSUEFCU2n5oEZosIyEvsa3rPDmIzA9lbVk9mA7GFBQwlDnesA7N5BRwlPl5vYAGx RQV0JFbvn8ICEReUODnzCQtEr5bE8unbWCYw8s9CkpqFJLWAkWkVo2xKbpVubmJmTnFqsm5x cmJeXmqRrplebmaJXmpK6SZGcKi5KO9gfNnnfYhRgINRiYf3x5qnYUKsiWXFlbmHGCU5mJRE ed/LPAkT4kvKT6nMSCzOiC8qzUktPsQowcGsJMKrdAionDclsbIqtSgfJiXNwaIkzsvIwMAg JJCeWJKanZpakFoEk5Xh4FCS4J13EKhRsCg1PbUiLTOnBCHNxMEJMpwHaLge2PDigsTc4sx0 iPwpRkUpcV42kIQASCKjNA+uF5wKdjOpvmIUB3pFmNcZpIoHmEbgul8BDWYCGjyh6xHI4JJE hJRUA+PUD2/Dv9za9Wa/VOupObs47l1y28US5zvv5csSsz/a6YarL96R9TqQsyf/s4vkVAOu +xPSed+s+LJ3IeukLQLuB/Qk57oyXX+sFhN/5/+q1kdJnhL1AqV7d/zJsC0++aXjY5WAFs9V Dculp3/IGp7Ne6Z6lntX2l099Tu7r8c77rx35fLP189SlViKMxINtZiLihMBj4NdkeACAAA= X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Mar 2016 19:45:53 -0000 Dear FreeBSD Community, The deadline for the next FreeBSD Quarterly Status update is April 7, 2016, for work done in January through March. Status report submissions do not have to be very long. They may be about anything happening in the FreeBSD project and community, and provide a great way to inform FreeBSD users and developers about what you're working on. Submission of reports is not restricted to committers. Anyone doing anything interesting and FreeBSD-related can -- and should -- write one! The preferred and easiest submission method is to use the XML generator [1] with the results emailed to the status report team at monthly at FreeBSD.org . There is also an XML template [2] which can be filled out manually and attached if preferred. For the expected content and style, please study our guidelines on how to write a good status report [3]. You can also review previous issues [4][5] for ideas on the style and format. We are looking forward to all of your 2015Q4 reports! Thanks, Ben (on behalf of monthly@) [1] http://www.freebsd.org/cgi/monthly.cgi [2] http://www.freebsd.org/news/status/report-sample.xml [3] http://www.freebsd.org/news/status/howto.html [4] http://www.freebsd.org/news/status/report-2015-07-2015-09.html [5] http://www.freebsd.org/news/status/report-2015-10-2015-12.html From owner-freebsd-hackers@freebsd.org Mon Mar 14 14:39:34 2016 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 1C4A5AD0663 for ; Mon, 14 Mar 2016 14:39:34 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 08BBE21C for ; Mon, 14 Mar 2016 14:39:34 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: by mailman.ysv.freebsd.org (Postfix) id 08715AD0662; Mon, 14 Mar 2016 14:39:34 +0000 (UTC) Delivered-To: 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 08051AD0661 for ; Mon, 14 Mar 2016 14:39:34 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from smtp.digiware.nl (unknown [IPv6:2001:4cb8:90:ffff::3]) (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 C95FA21B for ; Mon, 14 Mar 2016 14:39:33 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from rack1.digiware.nl (unknown [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id 4BDE6153413 for ; Mon, 14 Mar 2016 15:39:29 +0100 (CET) X-Virus-Scanned: amavisd-new at digiware.nl Received: from smtp.digiware.nl ([127.0.0.1]) by rack1.digiware.nl (rack1.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wij2QY3zjcHZ; Mon, 14 Mar 2016 15:39:11 +0100 (CET) Received: from [IPv6:2001:4cb8:3:1:a05d:3dc6:57ab:71e4] (unknown [IPv6:2001:4cb8:3:1:a05d:3dc6:57ab:71e4]) by smtp.digiware.nl (Postfix) with ESMTP id F3A0D15340A for ; Mon, 14 Mar 2016 15:08:43 +0100 (CET) To: hackers@freebsd.org From: Willem Jan Withagen Subject: Mising ENODATA Organization: Digiware Management b.v. Message-ID: <56E6C5EA.2080005@digiware.nl> Date: Mon, 14 Mar 2016 15:08:42 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Mar 2016 14:39:34 -0000 Hi, According the standard is ENODATA an extention of errno.h defines... http://pubs.opengroup.org/onlinepubs/9699919799/ The Open Group Base Specifications Issue 7 IEEE Std 1003.1, 2013 Edition [ENODATA] [OB XSR] [Option Start] No message available. No message is available on the STREAM head read queue. [Option End] [XSR] [Option Start] XSI STREAMS [Option End] The functionality described is optional. The functionality described is also an extension to the ISO C standard. Where applicable, functions are marked with the XSR margin legend in the SYNOPSIS section. Where additional semantics apply to a function, the material is identified by use of the XSR margin legend. [OB] [Option Start] Obsolescent [Option End] The functionality described may be removed in a future version of this volume of POSIX.1-2008. Strictly Conforming POSIX Applications and Strictly Conforming XSI Applications shall not use obsolescent features. Where applicable, the material is identified by use of the OB margin legend. ---- The OB part makes a bit strange to ask for definition, but would it be possible to add ENODATA to our headers? The alternative question is: why would we not? Reason I ask, is that while porting Ceph, I keep on running into the fact that ENODATA is not defined. Currently we try to set it equal to ENOATTR, but that sort of feels silly. The next part comes with the additional tools ea. like cython, they don't really know about a missing definition. So this just propagates further and further. In the archives I was not able to find arguments on why not to add it. Hence my question. Thanx, --WjW From owner-freebsd-hackers@freebsd.org Mon Mar 14 18:07:20 2016 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 673F7AD009F for ; Mon, 14 Mar 2016 18:07:20 +0000 (UTC) (envelope-from superbisquit@gmail.com) Received: from mail-vk0-x233.google.com (mail-vk0-x233.google.com [IPv6:2607:f8b0:400c:c05::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 233FA105A for ; Mon, 14 Mar 2016 18:07:20 +0000 (UTC) (envelope-from superbisquit@gmail.com) Received: by mail-vk0-x233.google.com with SMTP id c3so219127459vkb.3 for ; Mon, 14 Mar 2016 11:07:20 -0700 (PDT) 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; bh=pUjYyuKEyRggBSyGL5V9KFQ29HvI6HWUe/6YuU8qqlM=; b=RpqRgWHfmmIkSw49ii8xkm2QMcVXkMFWIwcU3Idn1L5n5Yfo8dMr2nhywtZGWp2DzQ yYEsReFjX+Ypki4G8/14eOC9nG+BWzBUm19j87oV9NRnr8aKPXdNAxGfRqP8g7CjS8Pi WMWHL4tvKA44WgQCcuj/h1jnBLYreFlrL8fxpEyEouDTtALP48D5mHVpoqiRdu18Ovwv 42Vgfr55X+4T6XzijjOG3Es7+21cMfMF5NiaMkCvYZmsrx1n5auePNAT5xju11ptyi6h BILqe6Y5wBr7eYd8suNev5ngXtjspsa639HPaXCBa8274aJDwpKcIQk9juosMF9ZYtCw sS6g== 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; bh=pUjYyuKEyRggBSyGL5V9KFQ29HvI6HWUe/6YuU8qqlM=; b=P2yyuErh9LUZfldYKUsLTubchr48mfxtpJuT8SKPN02RKP1C4IwdvlebKxZpPJ/ZCd cL2BbLXxvpP/cwy8611nXC17W9Sv7dYvUePjhsQhsq+tjDuqbHDOhPQ0YFDLt4Sy1uyi 9BWJzY7WuAQrZMienjTkTxZk6FOe79MEtNEeJBUiGwSMdjIiF4M5lE6kl4cnmOaBKM6X pzQMQU8i20Vm45AOxw/MqRuUwU1c/SbSZ21/01AyIeXaQbAfQT6vhUbIvE6ZAQ2lIJfi Irs1GsQhZ3+DQkWZNWo+OMJz5vlPBn1ArCLXI1Fc9UmMEBPJoA2sfXFShyUv+mwrFeq7 copw== X-Gm-Message-State: AD7BkJJdexUMxD8m86Zaos1yahmfvZTQOi7udSniDtw8xLvqDFLEO6MKMBQCDpYmi7VzZKu8C/Y8Cz/z6cH3bQ== MIME-Version: 1.0 X-Received: by 10.31.3.193 with SMTP id f62mr23210569vki.27.1457978839135; Mon, 14 Mar 2016 11:07:19 -0700 (PDT) Received: by 10.103.37.196 with HTTP; Mon, 14 Mar 2016 11:07:19 -0700 (PDT) In-Reply-To: References: Date: Mon, 14 Mar 2016 14:07:19 -0400 Message-ID: Subject: Re: Help From: Joe Nosay To: Kamlesh Meena Cc: FreeBSD Hackers Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Mar 2016 18:07:20 -0000 Okay. In what city do you live? https://www.freebsd.org/usergroups.html#north-america look for your group there. Also, subscribe to the other mailing lists such as the FreeBSD questions, advocacy, and whatever desktop you will like - Gnome, KDE, etc. There are tutorials at the forums for installing. The forums are https://forums.freebsd.org http://lists.freebsd.org/mailman/listinfo/ <-- Go back to here and choose other lists AS for the rest of you. You expect someone to know something without informing them. Don't make any excuses because some had to inform each and every one of you at sometime. Come to think about it, if Thompson and Ritchie did not develop UNIX, none of you would really have anything to do. This man approaches you with respect and your reply is to be rude with your silence. On Mon, Mar 7, 2016 at 6:35 AM, Kamlesh Meena wrote: > Respected, > I am new to this platform.Please guide me ,how to find mentor > and what else to be done to get the project.I am very enthusiastic person > in the field of computer science.In the past 1 year year I have learnt a > lot which include c,c++,html,css,javascript ,bit of python and android > development and have knowlegde about network system and also know many > things relates to hacking stuffs which include > scanning,footprinting,reverse engineering,mysql injection,spoofing and > tools such as nmap(my favorite),john the ripper and > metasploit(meterpreter). > I dont want to loose the project as I am very energetic about it.So please > someone guide me how to find a mentor and from where. > > Thanking you, > Yours faithfully > Kamlesh Kumar Meena > 7755047785 > _______________________________________________ > 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 Mon Mar 14 18:13:18 2016 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 A2D3EAD06FF; Mon, 14 Mar 2016 18:13:18 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from mail.metricspace.net (mail.metricspace.net [IPv6:2001:470:1f11:617::107]) by mx1.freebsd.org (Postfix) with ESMTP id 8092A1858; Mon, 14 Mar 2016 18:13:18 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from [10.74.2.20] (mobile-107-107-57-225.mycingular.net [107.107.57.225]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: eric) by mail.metricspace.net (Postfix) with ESMTPSA id 456BE1649; Mon, 14 Mar 2016 18:13:17 +0000 (UTC) User-Agent: K-9 Mail for Android In-Reply-To: References: MIME-Version: 1.0 Subject: Re: Blank screen on resume From: Eric McCorkle Date: Mon, 14 Mar 2016 14:13:14 -0400 To: Adrian Chadd CC: "freebsd-acpi@freebsd.org" , "freebsd-hackers@freebsd.org" Message-ID: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Mar 2016 18:13:18 -0000 Laptop is the librem 13 (not helpful, I know). Graphics chipset is broadwell. Cpu is i5-5200. Haven't been able to get the motherboard model. However, I have model numbers from the bios. Bios is American Megatrends. BIOS Version is 108. EC version is 2.1u. M/B version is D. On March 12, 2016 11:45:00 PM EST, Adrian Chadd wrote: >Hi, > >Which laptop? Which chipset? etc. > > > >-adrian -- Sent from my Android device with K-9 Mail. Please excuse my brevity. From owner-freebsd-hackers@freebsd.org Mon Mar 14 18:53:37 2016 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 B6537AD1586; Mon, 14 Mar 2016 18:53:37 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from mail.metricspace.net (mail.metricspace.net [IPv6:2001:470:1f11:617::107]) by mx1.freebsd.org (Postfix) with ESMTP id 89F921DE; Mon, 14 Mar 2016 18:53:37 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from [10.74.2.20] (mobile-107-107-57-225.mycingular.net [107.107.57.225]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: eric) by mail.metricspace.net (Postfix) with ESMTPSA id 96B7A166B; Mon, 14 Mar 2016 18:53:35 +0000 (UTC) User-Agent: K-9 Mail for Android In-Reply-To: References: MIME-Version: 1.0 Subject: Re: Blank screen on resume From: Eric McCorkle Date: Mon, 14 Mar 2016 14:53:33 -0400 To: freebsd-acpi@freebsd.org, "freebsd-hackers@freebsd.org" Message-ID: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Mar 2016 18:53:37 -0000 Note: I've moved the patch and logs to a new branch: https://github.com/emc2/freebsd/tree/resume_blank_screen On March 12, 2016 10:39:42 PM EST, Eric McCorkle wrote: >Hello everyone, > >It seems I'm plagued by blank screens on resume again on a different >laptop... *sigh* > >I've done quite a bit of diagnostic work on this, and there seem to be >some clues, but I'm a bit stumped at this point. The following github >repo has patches that add extra logging, which has proven useful in my >attempts to diagnose the issue: https://github.com/emc2/freebsd (sorry >for distributing patches/logs in this way, but the logs are quite big). >Also in this repo, there's a pciconf, devinfo, and dmesg file. The >dmesg file shows the trace from booting a patched kernel in verbose >mode then suspending it. > >There's two main curiosities in the dmesg trace. The first is that the >power state of all the vgapci device seems to be 0 as opposed to 3 >during resume, which was causing acpi_set_powerstate_method to skip >resetting its power during resume. I tried a simple patch (you can see >it in the patch and its effects in the trace), but that didn't seem to >work. A second curiosity is that acpi_pwr_switch_consumer only seems >to have an effect during resume. > >The only other real lead I have is that the display doesn't seem to be >active in acpi_video. I'm not sure if this is an artifact of the efifb >driver. > >Lastly, I recall looking into vga bios calls from earlier such efforts. >I imagine there's something similar for efifb, but I've been unable to >track down where this is happening. Advice or information on that >front would be much appreciated. > >Best, >Eric >_______________________________________________ >freebsd-acpi@freebsd.org mailing list >https://lists.freebsd.org/mailman/listinfo/freebsd-acpi >To unsubscribe, send any mail to "freebsd-acpi-unsubscribe@freebsd.org" -- Sent from my Android device with K-9 Mail. Please excuse my brevity. From owner-freebsd-hackers@freebsd.org Mon Mar 14 19:43:09 2016 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 0A20FACF6DB; Mon, 14 Mar 2016 19:43:09 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-io0-x22e.google.com (mail-io0-x22e.google.com [IPv6:2607:f8b0:4001:c06::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D7C322DA; Mon, 14 Mar 2016 19:43:08 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-io0-x22e.google.com with SMTP id z76so235739892iof.3; Mon, 14 Mar 2016 12:43:08 -0700 (PDT) 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; bh=bBsOpUE0PzIEr3rOTzAanIEZZwO7uXybpZvtW5YP+lo=; b=KtcApfr6wyqdUF3hjz96LRpQeCnEej8yKw64WEuji66oEQRrhfc66UtcXxTBXEGnG8 ABo+IxqFaKa+Gox2GW9RgKoX5ykAr41VgQmPafT2lTGTFKLpbIJO90y9J5n9fkh3pPYa yHqhosvCEF8zwwZsK7V493B481/xnWqCB/1Oz1rTuLAMZrr9DW7r6J3LRFeIwKXlhTdY Lc49b6u1QizHJaMIiFRdusq1uHnB16yPbZb2th4PZuBrgENsdlmArpgTGwSuv1YxwGJC q64Y1NKA26Z5j5aKff9RjHTKKobMrt4ZPQtitKWqNNggftZ2wiaKhZZl3bKr4escSSRC khlA== 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; bh=bBsOpUE0PzIEr3rOTzAanIEZZwO7uXybpZvtW5YP+lo=; b=FEnwyWQ9KxhsmOvIt/Sth4u8KnSPYeJfCHgePEGkaJNVQnM57/EEBVxD+de27gDf9Y Dbnx1Rsam8z4xT7vNU0DU2s+aWpSUBdLbnxCP49KiwpkJDwcKpyI1YYGvZikjGzY/XBH 0rL7EI/QerHo3VWWXnDROhFVKyKlZ25SDVAirpam3UXUKDFr9U4MCw7yArNCOOb9yxYj ej5I8kTEd+CKR+2V7HrFiCzCkn9AvqOjHsr40Podn0rc2SDGuS+7zrPCZ/AbJGJcZtB+ YmZ5ESi7rNfGFavR1hSqrv4Z5e7Mq3pzqpP/TIcBPrsI0ipGr2rz3EGnUsFROqXxnHNv I7bg== X-Gm-Message-State: AD7BkJL0uilp+rcawRxNenZ4CjZg0wFj+avNlhPbsFR2Fm2PZVvGf5gbmMK8UQ17KDKH4641fL6dRIngAkW/JA== MIME-Version: 1.0 X-Received: by 10.107.19.73 with SMTP id b70mr24958528ioj.75.1457984588268; Mon, 14 Mar 2016 12:43:08 -0700 (PDT) Received: by 10.36.14.19 with HTTP; Mon, 14 Mar 2016 12:43:08 -0700 (PDT) In-Reply-To: References: Date: Mon, 14 Mar 2016 12:43:08 -0700 Message-ID: Subject: Re: Blank screen on resume From: Adrian Chadd To: Eric McCorkle Cc: "freebsd-acpi@freebsd.org" , "freebsd-hackers@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Mailman-Approved-At: Mon, 14 Mar 2016 19:50:21 +0000 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Mar 2016 19:43:09 -0000 Hiya, Yeah - the drm2 code needs to be involved in resuming, and right now there's no broadwell support in i915kms. Once that gets updated then yeah, the resume backlight will work. :-P -a From owner-freebsd-hackers@freebsd.org Mon Mar 14 20:23:04 2016 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 88E24AD0579; Mon, 14 Mar 2016 20:23:04 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from mail.metricspace.net (207-172-209-83.c3-0.arl-ubr1.sbo-arl.ma.static.cable.rcn.com [207.172.209.83]) by mx1.freebsd.org (Postfix) with ESMTP id 53EC7E2E; Mon, 14 Mar 2016 20:23:03 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from [10.74.2.20] (mobile-107-107-57-225.mycingular.net [107.107.57.225]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: eric) by mail.metricspace.net (Postfix) with ESMTPSA id 64ED016BE; Mon, 14 Mar 2016 20:22:56 +0000 (UTC) User-Agent: K-9 Mail for Android In-Reply-To: References: MIME-Version: 1.0 Subject: Re: Blank screen on resume From: Eric McCorkle Date: Mon, 14 Mar 2016 16:22:54 -0400 To: Adrian Chadd CC: "freebsd-acpi@freebsd.org" , "freebsd-hackers@freebsd.org" Message-ID: <25FD6DD3-4BDB-4C2D-9CF2-6DBD857620B0@metricspace.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Mar 2016 20:23:04 -0000 So no options at all until then? :( On March 14, 2016 3:43:08 PM EDT, Adrian Chadd wrote: >Hiya, > >Yeah - the drm2 code needs to be involved in resuming, and right now >there's no broadwell support in i915kms. > >Once that gets updated then yeah, the resume backlight will work. :-P > > > >-a -- Sent from my Android device with K-9 Mail. Please excuse my brevity. From owner-freebsd-hackers@freebsd.org Mon Mar 14 20:58:47 2016 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 97D9BAD12BC; Mon, 14 Mar 2016 20:58:47 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from mail.metricspace.net (207-172-209-83.c3-0.arl-ubr1.sbo-arl.ma.static.cable.rcn.com [207.172.209.83]) by mx1.freebsd.org (Postfix) with ESMTP id 512CB6E5; Mon, 14 Mar 2016 20:58:47 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from [10.74.2.20] (mobile-107-107-57-225.mycingular.net [107.107.57.225]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: eric) by mail.metricspace.net (Postfix) with ESMTPSA id 493BA16DA; Mon, 14 Mar 2016 20:58:46 +0000 (UTC) User-Agent: K-9 Mail for Android In-Reply-To: References: <25FD6DD3-4BDB-4C2D-9CF2-6DBD857620B0@metricspace.net> MIME-Version: 1.0 Subject: Re: Blank screen on resume From: Eric McCorkle Date: Mon, 14 Mar 2016 16:58:44 -0400 To: Adrian Chadd CC: "freebsd-acpi@freebsd.org" , "freebsd-hackers@freebsd.org" Message-ID: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Mar 2016 20:58:47 -0000 I think I will give that a shot, actually... It seems pretty unfortunate that we'd have to wait for full 3D graphics support on a card in order to get resume working. I can't guarantee success, of course. On March 14, 2016 4:49:51 PM EDT, Adrian Chadd wrote: >On 14 March 2016 at 13:22, Eric McCorkle wrote: >> So no options at all until then? :( > >If you want to figure out what minimal set you need from the >dri/i915kms code to restore backlight happiness, please do. :-P > >But yeah. We'll need to wait for the next dri sync > > >-adrian > >> >> On March 14, 2016 3:43:08 PM EDT, Adrian Chadd > >> wrote: >>> >>> Hiya, >>> >>> Yeah - the drm2 code needs to be involved in resuming, and right now >>> there's no broadwell support in i915kms. >>> >>> Once that gets updated then yeah, the resume backlight will work. >:-P >>> >>> >>> >>> -a >> >> >> -- >> Sent from my Android device with K-9 Mail. Please excuse my brevity. -- Sent from my Android device with K-9 Mail. Please excuse my brevity. From owner-freebsd-hackers@freebsd.org Mon Mar 14 20:49:52 2016 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 2E357AD0FC6; Mon, 14 Mar 2016 20:49:52 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-io0-x22f.google.com (mail-io0-x22f.google.com [IPv6:2607:f8b0:4001:c06::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EDA1D6F; Mon, 14 Mar 2016 20:49:51 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-io0-x22f.google.com with SMTP id z76so237866816iof.3; Mon, 14 Mar 2016 13:49:51 -0700 (PDT) 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; bh=nlSQH0BfAcExjGorcfr3Nde1Zb2z4hDzCQc1O9l3nCQ=; b=L6XsEjwrCP8w75KM9Bfo59oG+EISs3gyt+U5ZSEAFrcLwss0HVIMX/ey1RHdlNhTbI QaFsfgdFidrZOEtj1BGGh0QMm8M1H+kA7ILHFwWpLZ+MloK2ZzGEPmmtziJdSDS6VuI4 gigsIV9Ka/WhMsdE8glDzFNWhRzLck5r3ZVyiq9A85CfXy0vSY6sPuFB7f7A1fvKO5su 00RhruoFbejv02e6hmLe3YpTUuGZ4k6ScskgDE+hidxSdvQOsqpH0+vzimUzreNBDa8Q 6gk57txuOQ5gvbZgVIAw1ElymU3XWeJtDRfBcNNoKN6+L8HbE5d1qTdRZXS43faYTeiY i63Q== 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; bh=nlSQH0BfAcExjGorcfr3Nde1Zb2z4hDzCQc1O9l3nCQ=; b=h6HCMmXjjn/AdrJXqLXV0sHBps2a1vvcJ6dwK1+Sx7xQWfcP063DIV82FKIoe/phrH qAKdpI4y40HJ3zRBelbZICibRqislUDWCnTZwE4dqYG8Ios1x1vyWIV7+whXk65x6jA7 wnD8NaYGLVLLolx5R4mfPrMkxldGDwfa/cUQejjgFdR3xmjj2N9pw/e5nGVgH4hrTtKs zb5BsxWJBwKSGYMcjAPWd95S/RoPvBnk0t6TPyAJkWADRYtBwoclNBU4LbYXf8CzPVzR zyPAkQ07u9U09/N5ENKo1mfdkugG00i7n7+00FRJczpL58+JzOrYVl6U/uJuezEfpW0t S2rw== X-Gm-Message-State: AD7BkJKKn5Zra2ot5Lzq+SAl06NqBJP4eFUFO1fcrzxKP0wo4NR7OKX89P+nvQxl7MNysddoEvGIeazym5xW5Q== MIME-Version: 1.0 X-Received: by 10.107.11.162 with SMTP id 34mr25090407iol.165.1457988591297; Mon, 14 Mar 2016 13:49:51 -0700 (PDT) Received: by 10.36.14.19 with HTTP; Mon, 14 Mar 2016 13:49:51 -0700 (PDT) In-Reply-To: <25FD6DD3-4BDB-4C2D-9CF2-6DBD857620B0@metricspace.net> References: <25FD6DD3-4BDB-4C2D-9CF2-6DBD857620B0@metricspace.net> Date: Mon, 14 Mar 2016 13:49:51 -0700 Message-ID: Subject: Re: Blank screen on resume From: Adrian Chadd To: Eric McCorkle Cc: "freebsd-acpi@freebsd.org" , "freebsd-hackers@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Mailman-Approved-At: Mon, 14 Mar 2016 21:13:52 +0000 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Mar 2016 20:49:52 -0000 On 14 March 2016 at 13:22, Eric McCorkle wrote: > So no options at all until then? :( If you want to figure out what minimal set you need from the dri/i915kms code to restore backlight happiness, please do. :-P But yeah. We'll need to wait for the next dri sync -adrian > > On March 14, 2016 3:43:08 PM EDT, Adrian Chadd > wrote: >> >> Hiya, >> >> Yeah - the drm2 code needs to be involved in resuming, and right now >> there's no broadwell support in i915kms. >> >> Once that gets updated then yeah, the resume backlight will work. :-P >> >> >> >> -a > > > -- > Sent from my Android device with K-9 Mail. Please excuse my brevity. From owner-freebsd-hackers@freebsd.org Tue Mar 15 00:57:01 2016 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 2BEAFAD033E for ; Tue, 15 Mar 2016 00:57:01 +0000 (UTC) (envelope-from bchepkwny@att.net) Received: from nm15-vm1.access.bullet.mail.gq1.yahoo.com (nm15-vm1.access.bullet.mail.gq1.yahoo.com [216.39.63.13]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 06D321195 for ; Tue, 15 Mar 2016 00:57:00 +0000 (UTC) (envelope-from bchepkwny@att.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=att.net; s=s1024; t=1458003312; bh=nB0NjMtyxdx4tPINsCjk0bvukZ2xNwEMfmrpQnb2XKA=; h=To:From:Subject:Date:From:Subject; b=bvDRmF2gPPTgJglhAuDui+Kf7/W8WeUEC2P/gLA+HUag0eZDNTWhjkrB9YV1njRDpFG3mXp9IxSXE7wCYFwxqgGROSwMZcc03CA35nw7hG2SQgAmvDmYHRbUZ1hwGLF+RopNu5OM6k9fefnIqOEXbTzr9ZgX5p59CO+aXsQ2lpE= Received: from [216.39.60.169] by nm15.access.bullet.mail.gq1.yahoo.com with NNFMP; 15 Mar 2016 00:55:12 -0000 Received: from [98.138.226.244] by tm5.access.bullet.mail.gq1.yahoo.com with NNFMP; 15 Mar 2016 00:55:12 -0000 Received: from [127.0.0.1] by smtp115.sbc.mail.ne1.yahoo.com with NNFMP; 15 Mar 2016 00:55:12 -0000 X-Yahoo-Newman-Id: 264057.15286.bm@smtp115.sbc.mail.ne1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: l8bEJysVM1mNZ_S7KzlE819KDHRgkIDrxGK_KEXqf9Lbxhz XRAda7BASeeMbIpauKFj2c5wtYwPMxK.Zb0K4scfvfPfY5._uslwG1yndQf7 JOnRcFHy9JoI2inRnoy8i09NW4jdG8fVocP.JS0oJmny2WamGkSKzLBMkQui oZUo._TiAlTRq5I1dN_6S_awsalwB5mD68W_qizgwaOkx2uaABIwAeoRPfBH umuK71.PmF7ot4Nzj3vWvO_VS7SkWBhlYjDF49TFDOlbfzw6JxRbimDi3yoT n9WzzoUgn7OKkISngHVqByE_R4bdznu6UqrkvRzoodtZnQzLxP6rUAGQ_zcm DhEovFcYHs.uF8oFK5sA1Iv5GscnkbKcHVafXkDA.QxHiWQX6kJ9KUJO8jnH A_Dfk.c_BGYGOsOkrWnD7WChKj.z9t.lWRaIYv8GqNlkPXh4qncd2b.3xoAn _s8zhtYzVtOTFpz11hmsh4VFvqb92U.zsZNgdhet0WiGH7ZhuVkhHwomBErH d3lpjH6vtWdoL4rF1yoF8F8ONLJGCfV54JGYs X-Yahoo-SMTP: 48hWWCKswBApcya_m1HJrpoYFH7_9N7oaicF21jG To: freebsd-hackers@freebsd.org From: benson chepkwony Subject: REF: Introduction To GSoC 2016 Message-ID: <56E75D7B.5050108@att.net> Date: Mon, 14 Mar 2016 18:55:23 -0600 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Mar 2016 00:57:01 -0000 HI, Hay, First I would like to make an introduction. My name is Benson Chepkwony and I`am currently working on getting to a graduate school. I would also like to express my interest in participating in this year`s GSoC 2016. And in particular to contribute to FreeBSD. I learnt about FreeBSD from Google Summer of Code 2016, however I have been contributing to Open Source for over a year now. About me, I have more than 6 years programming experience with Java, C++, C and Javascript. Other Languages that I have programmed with include; CSS, HTML, XHTML, XML, XSLT, Schema, SQL, AngularJS, JQuery, Amazon S3, Amazon AWS and OpenGL. I am interested in Porting and Integrating application or applications in general. I have visited the Project Ideas list and I am yet to decide which Porting Idea to work on. Please, you can guide me on this. From, Benson Chepkwony From owner-freebsd-hackers@freebsd.org Tue Mar 15 04:51:43 2016 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 3823AAD12BD for ; Tue, 15 Mar 2016 04:51:43 +0000 (UTC) (envelope-from bchepkwny@att.net) Received: from nm4-vm8.access.bullet.mail.gq1.yahoo.com (nm4-vm8.access.bullet.mail.gq1.yahoo.com [216.39.63.212]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 10BF392F for ; Tue, 15 Mar 2016 04:51:42 +0000 (UTC) (envelope-from bchepkwny@att.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=att.net; s=s1024; t=1458017173; bh=+pn/+RPQmXeIkudxblr1t3omheKucI+AxOacri+5nr8=; h=Subject:To:References:From:Cc:Date:In-Reply-To:From:Subject; b=TCLSFegWZ9nJFSDSo9ivLLRA4pNXZgx36ytNdFJW+oT7q/mPF7zGhpnILinU7nGnYAJkHkYnK4f8usTd4b4VvV7EDh3nR4rFm8+EKOzMn48SfCsbrvekv+Iquy9M7PkuSfknzeXHzMglb7NSCE/VCLPf/DhF/dK9got+Svo8msM= Received: from [216.39.60.168] by nm4.access.bullet.mail.gq1.yahoo.com with NNFMP; 15 Mar 2016 04:46:13 -0000 Received: from [98.138.226.244] by tm4.access.bullet.mail.gq1.yahoo.com with NNFMP; 15 Mar 2016 04:46:13 -0000 Received: from [127.0.0.1] by smtp115.sbc.mail.ne1.yahoo.com with NNFMP; 15 Mar 2016 04:46:13 -0000 X-Yahoo-Newman-Id: 858223.93009.bm@smtp115.sbc.mail.ne1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: JltoyEIVM1m65nzr.hC4gfGzZxnm4C3CuD8dOd535DC4jz_ viS16kKCwXlNrwZEQfsXvBWyv6.1fA4fijxrywbYXuBl.S.hmCTo8gs.mY_E FrbQIKkTDkAsGMtiFPxPd3M07J4NTrijwXA293IRb02onf77fhBroIwZNoK5 GwOfmOMlVG4GD85Inb4s4wZu7safLvV0SPJ9Rwto0zozggMMpCzHRVjG3EBA D77B6_VKAhx8616BQCfXo.KLL5l8SNBY9hACKWadtWsVNzFQyhTJJvbJ43vz jUAOOms4WzOFzTC1Dv9g8_YLlYG76X9ZyCTmWA34iwxkLCnSOfJTGpKJld6I u17Qpe.dp_n0CBgQPhp4f.64.19yf2QxUqUz4bC6T8eZK.4D0qY5MUFFNmPF HRpVuVnB6frWXisekaJW00dzm56pRkfokdR9oUGHrAJ4tu3NYVEsoSMdpdk_ DomGXJOD90Iwz5oeycchbHWYWWBaB68PL9qK1aLxBlat34Kb4yE3Rl_AKQI0 PseTRV_WVOuPR307x7kQVCwupUBx9cMYagx1j X-Yahoo-SMTP: 48hWWCKswBApcya_m1HJrpoYFH7_9N7oaicF21jG Subject: REF: GSoC 2016 Introduction To: Pedro Giffuni References: <56E77E0F.20202@FreeBSD.org> From: benson chepkwony Cc: freebsd-hackers@freebsd.org Message-ID: <56E7939F.8000004@att.net> Date: Mon, 14 Mar 2016 22:46:23 -0600 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: <56E77E0F.20202@FreeBSD.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Mar 2016 04:51:43 -0000 HI, First I would like to download a copy of FreeBSD software for Developers, where do I get this software? and then I was going to ask, where can I get information about Porting, Regressions Test and ATF. I am interested with the "Port old-style regression tests to ATF" Idea. Thanks. From, Benson Chepkwony On 3/14/2016 9:14 PM, Pedro Giffuni wrote: > Hi benson; > > There is no actual "GSoC Mailing List": you can use the regular lists, > and in particular hackers@ to share your ideas, and look for a mentor, > before submitting your proposal. > > As a side note: we prefer detailed proposals that don't limit > themselves to repeat exactly what can be read in the Project ideas > list ;). > > Pedro. > From owner-freebsd-hackers@freebsd.org Tue Mar 15 16:25:01 2016 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 D9759AD0B5A for ; Tue, 15 Mar 2016 16:25:01 +0000 (UTC) (envelope-from pfg@FreeBSD.org) Received: from nm49-vm4.bullet.mail.bf1.yahoo.com (nm49-vm4.bullet.mail.bf1.yahoo.com [216.109.115.191]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 93EEF18FB for ; Tue, 15 Mar 2016 16:25:01 +0000 (UTC) (envelope-from pfg@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1458058772; bh=6ej8vA0YDDmd7f8kt53SBhXWCfBy+jsK3RHOhcSxTIg=; h=To:From:Subject:Cc:Date:From:Subject; b=A3nwcQ4N6NwZ5jlH1jE5KXbLHk5KIcIcJhFouVjU08neZEIdk2dP/b8uf8OQD6d3EDqZMBWLn+8ObWY6dF4xTUUH54iR8ajmVAV7gBNfCANX4ZHcnS2e+2a7HZ3zkQ33at275iX8aVh35JpnkrDyLpoHEUv8uPBEcWEiT++GpK5LLlEsNIhsKVbdqbQMOzN/GaF4Cqp9TI3DppbLT7TMi0stZoHIYHrDMDuvyBRAGxpn7NJQ5vchljn4R52T2wV/bPCfyVJw3+VvJ0jAw5EiVNtNLpSoDfmQw2SDz6JUCAPHcnHblPB/8WrK0EF5bew9RI/qh7D2GjCwPbewJN6otw== Received: from [66.196.81.174] by nm49.bullet.mail.bf1.yahoo.com with NNFMP; 15 Mar 2016 16:19:32 -0000 Received: from [98.139.213.15] by tm20.bullet.mail.bf1.yahoo.com with NNFMP; 15 Mar 2016 16:19:32 -0000 Received: from [127.0.0.1] by smtp115.mail.bf1.yahoo.com with NNFMP; 15 Mar 2016 16:19:32 -0000 X-Yahoo-Newman-Id: 310104.81402.bm@smtp115.mail.bf1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: VuI5BTEVM1nBdIZ7RZhJwe7V4lV5PysNN6hep2upj_TLUWG xGuYRagafP6WgMQdfLkVjUEhOxUObufDWoPCOAQ_RItNZVHaotkCBwF8uYk3 5YDvh32ZOv0Zvp_dlSEZbXz5IZMFD45JUqRsvgjdxwujWGCHft8SLhK_HANx xAZIJ3Qmr9CwGEs81wDZqL1PiR3BXrgwcEmaNvAdIBJr.3GsQWxaKU3E4AmP ZQmwAoExjvHelE6PgMXmBrWiaHCFjpaBMmH4Z7DjfDR8EeuDoj7xN8uAY19X Iz.DTHzl5XEb4DLclD.gGt1krqEsflpWqfL8V4G6T15WiXt9gsgCZOQv37mK 3mr9895sA9hBp_9fxxQRCIbP5o1yX20GAPbJt9TajKP2Ber2o3eDx0VvmLrG KCmaGuhoqWDXL84TNwXmO_SgZbAH7EC90K7oIQosZ0PXvZA3Vxxpr3b6esyd z7AqmvMRHcAPp3_FJ9t1nh4tctCsl7erDa_CHQIk.aW.GINxcnCQpJHU2MlH 31iV2UObv_aswOPtiejdBkNeP5vtcNZW7eg-- X-Yahoo-SMTP: xcjD0guswBAZaPPIbxpWwLcp9Unf To: benson chepkwony , FreeBSD Hackers From: Pedro Giffuni Subject: Re: REF: GSoC 2016 Introduction Cc: Julio Merino Message-ID: <56E83655.4070600@FreeBSD.org> Date: Tue, 15 Mar 2016 11:20:37 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.7.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Mar 2016 16:25:01 -0000 Hi Benson; Sorry for the delay in replying .. we all have busy lifes ;). It is a good idea to try FreeBSD initially so that you make yourself an idea on how things work and what to do. You could start by downloading a VM image. There is some information about that and on getting started in the FreeBSD Handbook: https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ I added some links to the "Port old-style regression tests to ATF" idea in the wiki. I am not sure if the mentor is available but the only way to find out is to write to him directly. I am CC'ing him for you We try our best to put the project ideas in Wiki but you could also take a look at previous project to see examples of projects that were accepted and what is expected from a GSoC project. Best of lucks, Pedro. From owner-freebsd-hackers@freebsd.org Tue Mar 15 18:27:35 2016 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 A1BFDAD2396 for ; Tue, 15 Mar 2016 18:27:35 +0000 (UTC) (envelope-from julio@meroh.net) Received: from mail-qg0-x234.google.com (mail-qg0-x234.google.com [IPv6:2607:f8b0:400d:c04::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 606D31A95 for ; Tue, 15 Mar 2016 18:27:35 +0000 (UTC) (envelope-from julio@meroh.net) Received: by mail-qg0-x234.google.com with SMTP id w104so22165408qge.1 for ; Tue, 15 Mar 2016 11:27:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=meroh-net.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=NIwln/iGZsvzR3Ga4H9QIqYfOK0tqUTh/Z1qV9Nl964=; b=FBOn/6hB174465PGf+1wPTRlj1PguCDv4tN53tFmH3EFCH/H38JUWRUCmvXYvp5IDA St0mxYjq+nbJ7a6XOUvVSR33T2RNA+gGdx3d8XweG5ry0HkuaeY04QTkN+hr07pe0J3o 2f9kHumh/X4cXX4RzaPnhu3bAEzcb6jeVekjDYPKRyCs5Jc5E8cRNLuYxw35O8FRZoM6 06/KCoGlqDAAreDxO1wVbrwT6ghaXTX1qVW1Gkdw0dTA7ClHt2Xq6ONHYccPlkfY5yHf X5AVKOnxkhwSXDMYbP/IseUUGgipSPD9NHHMXzHEk3vip7jA+ZhfCzGUkYjP220T9M6Z mrow== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=NIwln/iGZsvzR3Ga4H9QIqYfOK0tqUTh/Z1qV9Nl964=; b=ZyjLvUjfFdwcj8BRUdfM4VCWROC93xjVGS18GLna0BzB4qfH0pZQK1FUe47mxk0wGx 2OcrVNcWYSGDuLjJgUd00P1XeXLut+LuY8k5cfnGQTo4Is4S6M8WFP+Vk82TIVenG/No GEieyjkSHuQD4jbyzEdMd0bCGkPOCj6REY9t4K1ws5Mtiw8hPrUsKDTY+mvyVkw17OTN yjQ4gSO7qNNHg5o71F1go0e4gndYgyBG44tDWVTaEeU8W8qM7b8rBXw6dT2k/MP4/71+ Dveu9NKVuN+WpsJ2viyPrLZt+bOihlMuMUvKGeM1TdNEvLoB4W0/YM5R4zcdQDsNVUZ/ vFDw== X-Gm-Message-State: AD7BkJINICFbTvCWYLME6AY5zOHKnlFu83U+2MbRotSMUJYtapy50ZlIIGyn0I9Rwlv/GH2v+1rTSBImVifz2Q== X-Received: by 10.141.2.11 with SMTP id e11mr42705116qhd.69.1458066454520; Tue, 15 Mar 2016 11:27:34 -0700 (PDT) MIME-Version: 1.0 Sender: julio@meroh.net Received: by 10.55.214.3 with HTTP; Tue, 15 Mar 2016 11:27:15 -0700 (PDT) X-Originating-IP: [2620:0:1003:1008:b8ec:e01f:71fc:83cf] In-Reply-To: <56E83655.4070600@FreeBSD.org> References: <56E83655.4070600@FreeBSD.org> From: Julio Merino Date: Tue, 15 Mar 2016 14:27:15 -0400 X-Google-Sender-Auth: mXsaSsHqFDX_ozexBR5TwnSsz3g Message-ID: Subject: Re: REF: GSoC 2016 Introduction To: Pedro Giffuni Cc: benson chepkwony , FreeBSD Hackers , ngie@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Mar 2016 18:27:35 -0000 On Tue, Mar 15, 2016 at 12:20 PM, Pedro Giffuni wrote: > Hi Benson; > > Sorry for the delay in replying .. we all have busy lifes ;). > > It is a good idea to try FreeBSD initially so that you make yourself an idea > on how things work and what to do. You could start by downloading > a VM image. There is some information about that and on getting > started in the FreeBSD Handbook: > > https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ > > I added some links to the "Port old-style regression tests to ATF" idea in > the wiki. I am not sure if the mentor is available but the only way > to find out is to write to him directly. I am CC'ing him for you I can help with mentoring this proposal, but we need a detailed one :) The more details you can provide upfront, the better. Also note that ngie has been doing a lot of work in this area and I'm not sure what the current status of this is. CCd here. From owner-freebsd-hackers@freebsd.org Wed Mar 16 04:50:54 2016 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 963D3AD209F for ; Wed, 16 Mar 2016 04:50:54 +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 CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 7211215C4; Wed, 16 Mar 2016 04:50:54 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from Julian-MBP3.local (ppp121-45-229-231.lns20.per1.internode.on.net [121.45.229.231]) (authenticated bits=0) by vps1.elischer.org (8.15.2/8.15.2) with ESMTPSA id u2G4olFC014004 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Tue, 15 Mar 2016 21:50:50 -0700 (PDT) (envelope-from julian@freebsd.org) Subject: Re: REF: GSoC 2016 Introduction To: benson chepkwony , Pedro Giffuni References: <56E77E0F.20202@FreeBSD.org> <56E7939F.8000004@att.net> Cc: freebsd-hackers@freebsd.org From: Julian Elischer Message-ID: <56E8E622.3030509@freebsd.org> Date: Wed, 16 Mar 2016 12:50:42 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: <56E7939F.8000004@att.net> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Mar 2016 04:50:54 -0000 On 15/03/2016 12:46 PM, benson chepkwony wrote: > HI, > First I would like to download a copy of FreeBSD software for > Developers, where do I get this software? > and then I was going to ask, where can I get information about > Porting, Regressions Test and ATF. > I am interested with the "Port old-style regression tests to ATF" Idea. your wording suggests you don't really understand how things are set up. FreeBSD is "self hosting" which means when you set up a FreeBSD machine (or VM), the sources are in that machine and you use the tools in the system to build it. You should look at the FreeBSD handbook chapters on downloading and updating source, https://www.freebsd.org/doc/handbook/synching.html and on rebuilding the system. https://www.freebsd.org/doc/handbook/makeworld.html in fact just go make yourself familiar of what topics are in the entire book :-) https://www.freebsd.org/doc/handbook/ good luck and ask questions.. but only AFTER reading the book and the man pages at https://www.freebsd.org/cgi/man.cgi (man stands for "manual"). > > Thanks. > > From, > Benson Chepkwony > > On 3/14/2016 9:14 PM, Pedro Giffuni wrote: >> Hi benson; >> >> There is no actual "GSoC Mailing List": you can use the regular lists, >> and in particular hackers@ to share your ideas, and look for a mentor, >> before submitting your proposal. >> >> As a side note: we prefer detailed proposals that don't limit >> themselves to repeat exactly what can be read in the Project ideas >> list ;). >> >> Pedro. >> > > _______________________________________________ > 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 Mar 16 18:08:14 2016 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 83705AD25CC for ; Wed, 16 Mar 2016 18:08:14 +0000 (UTC) (envelope-from robin.guzniczak@gmail.com) Received: from mail-qg0-x231.google.com (mail-qg0-x231.google.com [IPv6:2607:f8b0:400d:c04::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 3F772C4 for ; Wed, 16 Mar 2016 18:08:14 +0000 (UTC) (envelope-from robin.guzniczak@gmail.com) Received: by mail-qg0-x231.google.com with SMTP id w104so50223963qge.1 for ; Wed, 16 Mar 2016 11:08:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:subject:message-id:date:user-agent:mime-version :content-transfer-encoding; bh=G/llaCQKzLodZBV1ImYOymlMLIk/BKvMQBdO9CWDU50=; b=gJzyCtL30DtAWls30m483wFMKQJPeSUjbe+A1ytdRcAdZTIC8qYQ8xtdekQVtrJzGi N8wTy3wuWsCnxFNLfhwbrzp1ZMgBcAN3ZRHNVgAciZRvNpG+yVzeDbKUK5pQtPER0mUZ lITZEVNpaFy3vXUGyzBGMOMjG3eXMhfUqloQmJqcLQfJENaihyUaDG0S5jBFiAtBGT5D fwyiT1jR2oXZHe/H1sF5rcofscfaXky5pT2KpNWJ2uQkpRIcQum3WZI+hxDJTJOci2MA Ljp4sTnRC/+ie1fs8+O924/qJ/4vTf8Smv3q6Dx0IaQlN4rM8xjvpBX45kc7OdxiOvy+ OChg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:subject:message-id:date:user-agent :mime-version:content-transfer-encoding; bh=G/llaCQKzLodZBV1ImYOymlMLIk/BKvMQBdO9CWDU50=; b=l1sC2YqEy9XwjedkU8XTBlQMGIrEGkDh6CS4J2/zQCdCoTyoz20tWJyfBWZESrMCMx kT9mLATBgC0doOipdhGGXuLfrQBW5CDxXp3kNjP0jlLvlX/20AEhw2mxvSM+Zu0XTwZg P0/3540QT9NxC20xvQ7AyxsHEHW0zWpSWylq0mdtrcwGCHTyY020Lnmmaoh0IAnk85Ds LuTImniP4pZX8Tb+GmnZgF+qJgQWFG6cCHkvbEcNyZY6fXRZEgaIbddgmujeA4ClrZs7 7ZGy/HS9SiUk3baTU0F1nKXXHYSmni3iNKLlY4DVpIZ7GhvI5B7nYNoiRc0cNL/IXtOd 9I5A== X-Gm-Message-State: AD7BkJJ+7L3xNkQ3f9tEIgBFvBh8+JCll8+ej+IteqOLtk3ewJdKpqyaodA2QyL6Pcax0Q== X-Received: by 10.140.229.199 with SMTP id z190mr7606729qhb.48.1458151689204; Wed, 16 Mar 2016 11:08:09 -0700 (PDT) Received: from [142.157.197.15] (dhcp197015.rez.mcgill.ca. [142.157.197.15]) by smtp.googlemail.com with ESMTPSA id i46sm1098812qgd.19.2016.03.16.11.08.08 for (version=TLSv1/SSLv3 cipher=OTHER); Wed, 16 Mar 2016 11:08:08 -0700 (PDT) From: Robin Guzniczak To: freebsd-hackers@freebsd.org Subject: GSoc 2016 Introduction Message-ID: <56E9A108.7030304@gmail.com> Date: Wed, 16 Mar 2016 14:08:08 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Mar 2016 18:08:14 -0000 Hi, My name is Robin Guzniczak and I'm a student at McGill University in Montreal, Canada. I'm currently finishing up my first year in Maths and Computer Science. I would like to participate in this year's GSoC by contributing to FreeBSD. I've been using Debian for a long time and I recently switched to FreeBSD. I've always wanted to become an active member of a large open source project, and I feel like GSoC is the right place to start. I have about 5 years of experience using Python, Lua, C and C++, mostly for creating games and applications. I am interested in the KDE front-end to the freebsd-update utility; I am currently in the process of writing my proposal. In the idea description on the wiki, it says that a GTK frontend was developed as part of GSoC 2007 and that design ideas could be shared, but the link given is broken. I didn't manage to find any link to the project elsewhere. Could anyone tell me where I can find it? I am also looking for a possible mentor, since the project has no available mentor. I've already used Qt a lot before and I am fairly autonomous in my work. Thanks. Robin From owner-freebsd-hackers@freebsd.org Wed Mar 16 20:29:55 2016 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 CA5B3AD3391 for ; Wed, 16 Mar 2016 20:29:55 +0000 (UTC) (envelope-from stas@freebsd.org) Received: from mx0.deglitch.com (mx0.deglitch.com [IPv6:2a00:13c0:63:7194:1::3]) by mx1.freebsd.org (Postfix) with ESMTP id 567C186D; Wed, 16 Mar 2016 20:29:55 +0000 (UTC) (envelope-from stas@freebsd.org) Received: from [IPv6:2620:10d:c082:1803:e9ee:be74:4bb7:1ef6] (unknown [IPv6:2620:10d:c090:200::8:4655]) by mx0.deglitch.com (Postfix) with ESMTPSA id 35C308FC0B; Wed, 16 Mar 2016 13:29:50 -0700 (PDT) From: Stanislav Sedov Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: Peformance issues with r278325 Date: Wed, 16 Mar 2016 13:29:47 -0700 Message-Id: To: freebsd-hackers@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\)) X-Mailer: Apple Mail (2.3112) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Mar 2016 20:29:55 -0000 Hi! We're seeing weird performance issues on some of our systems on both FreeBSD stable/10 and HEAD with r278325. In particular, the part of the change that switched the lapic_ipi_wait to microsecond-based delay seem to cause slowdowns. Some background. Out systems mostly run a single large application that is both I/O heavy and memory allocation heavy. It is doing network = traffic processing, but that does not seem to be the culprit. What we noticed = is that when running on FreeBSD 10.2+ or HEAD the memory allocations (and, = particularly, munmaps) become exponentially slower the bigger the application becomes = in terms of the memory space allocated. This does not seem to happen on FreeBSD = 10.1 or stable/10 with the lapic_ipi_wait() change reverted. The top output when this slowdown happens shows the following: = __________________________________________________________________________= _________ / | 1585 user -21 r31 20225M 17260M vm map 5 483:20 78.47% = [beam.smp{beam.smp}] | 1585 user -21 r31 20225M 17260M *proce 11 483:26 77.29% = [beam.smp{beam.smp}] | 1585 user -21 r31 20225M 17260M vm map 15 484:05 76.86% = [beam.smp{beam.smp}] | 1585 user -21 r31 20225M 17260M CPU21 21 262:49 76.86% = [beam.smp{beam.smp}] | 1585 user -21 r31 20225M 17260M CPU26 26 473:31 76.76% = [beam.smp{beam.smp}] | 1585 user -21 r31 20225M 17260M RUN 5 462:01 76.56% = [beam.smp{beam.smp}] | 1585 user -21 r31 20225M 17260M vm map 2 282:16 76.37% = [beam.smp{beam.smp}] | 1585 user -21 r31 20225M 17260M CPU4 4 475:24 76.27% = [beam.smp{beam.smp}] | 1585 user -21 r31 20225M 17260M CPU38 38 366:16 76.17% = [beam.smp{beam.smp}] | 1585 user -21 r31 20225M 17260M vm map 16 434:35 76.07% = [beam.smp{beam.smp}] = `-------------------------------------------------------------------------= ----------- I had a pmcstat output as well somewhere, but can't find it at the = moment. But it was indicating that a lot of time has been spend in VM mutexes as far as I = remember. I'm not entirely sure why this change would cause any effects like this. = One theory I have is that TLB shootdowns become slower due to lapic_ipi_wait taking = longer than before to complete (as it was using pause instructions instead of = explicit delays). Any ideas? Anything else I can look at to track the reason down? Out = platform is Supermicro X9DRi-LN4+ with dual Xeon(R) CPU E5-2690 v2 CPUs. I'm not = sure if it's platform specific or not though. I've seen that happen on servers with = E5-2690 v3 as well. Thanks! = __________________________________________________________________________= ___________ / | int | lapic_ipi_wait(int delay) | { | - int x; | + int x, incr; | =20 | /* | - * Wait delay microseconds for IPI to be sent. If delay is | + * Wait delay loops for IPI to be sent. This is highly bogus | + * since this is sensitive to CPU clock speed. If delay is | * -1, we wait forever. | */ | if (delay =3D=3D -1) { | - while ((lapic->icr_lo & APIC_DELSTAT_MASK) !=3D = APIC_DELSTAT_IDLE) | - ia32_pause(); | - return (1); | - } | - | - for (x =3D 0; x < delay; x +=3D 5) { | + incr =3D 0; | + delay =3D 1; | + } else | + incr =3D 1; | + for (x =3D 0; x < delay; x +=3D incr) { | if ((lapic->icr_lo & APIC_DELSTAT_MASK) =3D=3D = APIC_DELSTAT_IDLE) | return (1); | - DELAY(5); | + ia32_pause(); | } | return (0); | } | @@ -1433,9 +1433,9 @@ lapic_ipi_raw(register_t icrlo, u_int dest) | intr_restore(saveintr); | } | =20 | -#define BEFORE_SPIN 50000 | +#define BEFORE_SPIN 1000000 | #ifdef DETECT_DEADLOCK | -#define AFTER_SPIN 50 | +#define AFTER_SPIN 1000 | #endif = `-------------------------------------------------------------------------= ---------- -- Stanislav Sedov ST4096-RIPE From owner-freebsd-hackers@freebsd.org Thu Mar 17 05:37:09 2016 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 907ECAD3BE9 for ; Thu, 17 Mar 2016 05:37:09 +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 2A845DAF; Thu, 17 Mar 2016 05:37:09 +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 u2H5b4sr085371 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Thu, 17 Mar 2016 07:37:04 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua u2H5b4sr085371 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id u2H5b4t5085370; Thu, 17 Mar 2016 07:37:04 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Thu, 17 Mar 2016 07:37:04 +0200 From: Konstantin Belousov To: Stanislav Sedov Cc: freebsd-hackers@freebsd.org, jhb@freebsd.org Subject: Re: Peformance issues with r278325 Message-ID: <20160317053704.GP1741@kib.kiev.ua> References: 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.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Mar 2016 05:37:09 -0000 On Wed, Mar 16, 2016 at 01:29:47PM -0700, Stanislav Sedov wrote: > Hi! > > We're seeing weird performance issues on some of our systems on both > FreeBSD stable/10 and HEAD with r278325. In particular, the part of the > change that switched the lapic_ipi_wait to microsecond-based delay seem > to cause slowdowns. > > Some background. Out systems mostly run a single large application that > is both I/O heavy and memory allocation heavy. It is doing network traffic > processing, but that does not seem to be the culprit. What we noticed is that > when running on FreeBSD 10.2+ or HEAD the memory allocations (and, particularly, > munmaps) become exponentially slower the bigger the application becomes in terms > of the memory space allocated. This does not seem to happen on FreeBSD 10.1 > or stable/10 with the lapic_ipi_wait() change reverted. > > The top output when this slowdown happens shows the following: > ___________________________________________________________________________________ > / > | 1585 user -21 r31 20225M 17260M vm map 5 483:20 78.47% [beam.smp{beam.smp}] > | 1585 user -21 r31 20225M 17260M *proce 11 483:26 77.29% [beam.smp{beam.smp}] > | 1585 user -21 r31 20225M 17260M vm map 15 484:05 76.86% [beam.smp{beam.smp}] > | 1585 user -21 r31 20225M 17260M CPU21 21 262:49 76.86% [beam.smp{beam.smp}] > | 1585 user -21 r31 20225M 17260M CPU26 26 473:31 76.76% [beam.smp{beam.smp}] > | 1585 user -21 r31 20225M 17260M RUN 5 462:01 76.56% [beam.smp{beam.smp}] > | 1585 user -21 r31 20225M 17260M vm map 2 282:16 76.37% [beam.smp{beam.smp}] > | 1585 user -21 r31 20225M 17260M CPU4 4 475:24 76.27% [beam.smp{beam.smp}] > | 1585 user -21 r31 20225M 17260M CPU38 38 366:16 76.17% [beam.smp{beam.smp}] > | 1585 user -21 r31 20225M 17260M vm map 16 434:35 76.07% [beam.smp{beam.smp}] > `------------------------------------------------------------------------------------ > > I had a pmcstat output as well somewhere, but can't find it at the moment. But it was > indicating that a lot of time has been spend in VM mutexes as far as I remember. > > I'm not entirely sure why this change would cause any effects like this. One theory > I have is that TLB shootdowns become slower due to lapic_ipi_wait taking longer than > before to complete (as it was using pause instructions instead of explicit delays). > > Any ideas? Anything else I can look at to track the reason down? Out platform is > Supermicro X9DRi-LN4+ with dual Xeon(R) CPU E5-2690 v2 CPUs. I'm not sure if it's > platform specific or not though. I've seen that happen on servers with E5-2690 v3 > as well. > > Thanks! > > _____________________________________________________________________________________ > / > | int > | lapic_ipi_wait(int delay) > | { > | - int x; > | + int x, incr; > | > | /* > | - * Wait delay microseconds for IPI to be sent. If delay is > | + * Wait delay loops for IPI to be sent. This is highly bogus > | + * since this is sensitive to CPU clock speed. If delay is > | * -1, we wait forever. > | */ > | if (delay == -1) { > | - while ((lapic->icr_lo & APIC_DELSTAT_MASK) != APIC_DELSTAT_IDLE) > | - ia32_pause(); > | - return (1); > | - } > | - > | - for (x = 0; x < delay; x += 5) { > | + incr = 0; > | + delay = 1; > | + } else > | + incr = 1; > | + for (x = 0; x < delay; x += incr) { > | if ((lapic->icr_lo & APIC_DELSTAT_MASK) == APIC_DELSTAT_IDLE) > | return (1); > | - DELAY(5); > | + ia32_pause(); > | } > | return (0); > | } > | @@ -1433,9 +1433,9 @@ lapic_ipi_raw(register_t icrlo, u_int dest) > | intr_restore(saveintr); > | } > | > | -#define BEFORE_SPIN 50000 > | +#define BEFORE_SPIN 1000000 > | #ifdef DETECT_DEADLOCK > | -#define AFTER_SPIN 50 > | +#define AFTER_SPIN 1000 > | #endif > `----------------------------------------------------------------------------------- > IPIs are used not only for TLB shutdowns, but also to notify other CPUs about new runnable threads. Basically the call path is [setrunnable()->sched_wakeup()->]sched_add()->tdq_notify()->ipi(). The sched_wakeup()/sched_add() are the scheduler primitive called from misc. unlock pathes, to notify other cores about threads on run queues. Delivery of IPI causes rescheduling. Look at the turnstile code (for non-sleepable) or sleepqueue (for sleepable) locks. So if the latency of unlock becomes higher, it adds both latency to unlock and re-shuffle the patterns of runnable threads appearing on the run queues. And the latency of unlock is very important, as illustrated by significant gains from the adaptive locks. I think that the revert you posted above is a good candidate for commit, but I defer to John. What else you could do, is to try the HEAD kernel on your machines. Your CPUs should support x2APIC mode, which is utilized in HEAD. In x2APIC mode, there is no need to wait for the ack from the IPI command at all. Look at the verbose dmesg LAPIC detection lines to see if x2APIC is enabled. From owner-freebsd-hackers@freebsd.org Thu Mar 17 17:23:09 2016 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 0FC15AD4A45 for ; Thu, 17 Mar 2016 17:23:09 +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 C4574D41; Thu, 17 Mar 2016 17:23:08 +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 7C571B977; Thu, 17 Mar 2016 13:23:07 -0400 (EDT) From: John Baldwin To: Konstantin Belousov Cc: Stanislav Sedov , freebsd-hackers@freebsd.org Subject: Re: Peformance issues with r278325 Date: Thu, 17 Mar 2016 10:23:01 -0700 Message-ID: <8403291.NqUNo0Qq5W@ralph.baldwin.cx> User-Agent: KMail/4.14.3 (FreeBSD/10.2-STABLE; KDE/4.14.3; amd64; ; ) In-Reply-To: <20160317053704.GP1741@kib.kiev.ua> References: <20160317053704.GP1741@kib.kiev.ua> 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); Thu, 17 Mar 2016 13:23:07 -0400 (EDT) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Mar 2016 17:23:09 -0000 On Thursday, March 17, 2016 07:37:04 AM Konstantin Belousov wrote: > On Wed, Mar 16, 2016 at 01:29:47PM -0700, Stanislav Sedov wrote: > > Hi! > > > > We're seeing weird performance issues on some of our systems on both > > FreeBSD stable/10 and HEAD with r278325. In particular, the part of the > > change that switched the lapic_ipi_wait to microsecond-based delay seem > > to cause slowdowns. > > > > Some background. Out systems mostly run a single large application that > > is both I/O heavy and memory allocation heavy. It is doing network traffic > > processing, but that does not seem to be the culprit. What we noticed is that > > when running on FreeBSD 10.2+ or HEAD the memory allocations (and, particularly, > > munmaps) become exponentially slower the bigger the application becomes in terms > > of the memory space allocated. This does not seem to happen on FreeBSD 10.1 > > or stable/10 with the lapic_ipi_wait() change reverted. > > > > The top output when this slowdown happens shows the following: > > ___________________________________________________________________________________ > > / > > | 1585 user -21 r31 20225M 17260M vm map 5 483:20 78.47% [beam.smp{beam.smp}] > > | 1585 user -21 r31 20225M 17260M *proce 11 483:26 77.29% [beam.smp{beam.smp}] > > | 1585 user -21 r31 20225M 17260M vm map 15 484:05 76.86% [beam.smp{beam.smp}] > > | 1585 user -21 r31 20225M 17260M CPU21 21 262:49 76.86% [beam.smp{beam.smp}] > > | 1585 user -21 r31 20225M 17260M CPU26 26 473:31 76.76% [beam.smp{beam.smp}] > > | 1585 user -21 r31 20225M 17260M RUN 5 462:01 76.56% [beam.smp{beam.smp}] > > | 1585 user -21 r31 20225M 17260M vm map 2 282:16 76.37% [beam.smp{beam.smp}] > > | 1585 user -21 r31 20225M 17260M CPU4 4 475:24 76.27% [beam.smp{beam.smp}] > > | 1585 user -21 r31 20225M 17260M CPU38 38 366:16 76.17% [beam.smp{beam.smp}] > > | 1585 user -21 r31 20225M 17260M vm map 16 434:35 76.07% [beam.smp{beam.smp}] > > `------------------------------------------------------------------------------------ > > > > I had a pmcstat output as well somewhere, but can't find it at the moment. But it was > > indicating that a lot of time has been spend in VM mutexes as far as I remember. > > > > I'm not entirely sure why this change would cause any effects like this. One theory > > I have is that TLB shootdowns become slower due to lapic_ipi_wait taking longer than > > before to complete (as it was using pause instructions instead of explicit delays). > > > > Any ideas? Anything else I can look at to track the reason down? Out platform is > > Supermicro X9DRi-LN4+ with dual Xeon(R) CPU E5-2690 v2 CPUs. I'm not sure if it's > > platform specific or not though. I've seen that happen on servers with E5-2690 v3 > > as well. > > > > Thanks! > > > > _____________________________________________________________________________________ > > / > > | int > > | lapic_ipi_wait(int delay) > > | { > > | - int x; > > | + int x, incr; > > | > > | /* > > | - * Wait delay microseconds for IPI to be sent. If delay is > > | + * Wait delay loops for IPI to be sent. This is highly bogus > > | + * since this is sensitive to CPU clock speed. If delay is > > | * -1, we wait forever. > > | */ > > | if (delay == -1) { > > | - while ((lapic->icr_lo & APIC_DELSTAT_MASK) != APIC_DELSTAT_IDLE) > > | - ia32_pause(); > > | - return (1); > > | - } > > | - > > | - for (x = 0; x < delay; x += 5) { > > | + incr = 0; > > | + delay = 1; > > | + } else > > | + incr = 1; > > | + for (x = 0; x < delay; x += incr) { > > | if ((lapic->icr_lo & APIC_DELSTAT_MASK) == APIC_DELSTAT_IDLE) > > | return (1); > > | - DELAY(5); > > | + ia32_pause(); > > | } > > | return (0); > > | } > > | @@ -1433,9 +1433,9 @@ lapic_ipi_raw(register_t icrlo, u_int dest) > > | intr_restore(saveintr); > > | } > > | > > | -#define BEFORE_SPIN 50000 > > | +#define BEFORE_SPIN 1000000 > > | #ifdef DETECT_DEADLOCK > > | -#define AFTER_SPIN 50 > > | +#define AFTER_SPIN 1000 > > | #endif > > `----------------------------------------------------------------------------------- > > > > IPIs are used not only for TLB shutdowns, but also to notify other CPUs > about new runnable threads. Basically the call path is > [setrunnable()->sched_wakeup()->]sched_add()->tdq_notify()->ipi(). > The sched_wakeup()/sched_add() are the scheduler primitive called from > misc. unlock pathes, to notify other cores about threads on run queues. > Delivery of IPI causes rescheduling. Look at the turnstile code (for > non-sleepable) or sleepqueue (for sleepable) locks. > > So if the latency of unlock becomes higher, it adds both latency to unlock > and re-shuffle the patterns of runnable threads appearing on the run queues. > And the latency of unlock is very important, as illustrated by significant > gains from the adaptive locks. > > I think that the revert you posted above is a good candidate for commit, > but I defer to John. > > What else you could do, is to try the HEAD kernel on your machines. > Your CPUs should support x2APIC mode, which is utilized in HEAD. In > x2APIC mode, there is no need to wait for the ack from the IPI command > at all. Look at the verbose dmesg LAPIC detection lines to see if > x2APIC is enabled. I had not expected this commit to have this impact, but Konstantin is correct. I wonder if simply reducing the DELAY() from 5 down to 1 or so would be sufficient? (Note that you need to adjust the prior loop to use += 1 instead of += 5 in that case.) Note that DETECT_DEADLOCK is not enabled by default, so the AFTER_SPIN case (which waits for an IPI just sent to be delivered) shouldn't be enabled (and in fact I'd like to just remove that code entirely). This means that only BEFORE_SPIN should be spinning, and it should only be spinning if a CPU sends IPIs back to back such that the previous IPI is still pending (not yet delivered) when the CPU wants to send another IPI. We can probably assume a TSC if we have SMP, so if changing the delay from 5 to 1 doesn't work we can try just using the TSC directly to control the spin length and go back to using a simple pause. I have an old set of changes that might also be interesting that permit TLB shootdown IPI handlers to run while spinlocks are held (by using cr8/TPR to control interrupts when a spinlock is held instead of disabling all interrupts). I haven't found a workload where that helped yet. However, yours might be an interesting workload to try those changes out on. -- John Baldwin From owner-freebsd-hackers@freebsd.org Thu Mar 17 17:45:40 2016 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 20CB8AD30BF for ; Thu, 17 Mar 2016 17:45:40 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-io0-x22d.google.com (mail-io0-x22d.google.com [IPv6:2607:f8b0:4001:c06::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 E11CE981; Thu, 17 Mar 2016 17:45:39 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-io0-x22d.google.com with SMTP id g184so51094295ioa.3; Thu, 17 Mar 2016 10:45:39 -0700 (PDT) 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; bh=UCuHFb65NPOBHih+9SxyFiiBOSlc4sL2tNkDZwQS3oE=; b=EeGGEun4uYUFUU5+I7kapBCZ6GH1QqIrzY2Z94dRBRJkqL8YZAgOzqR+rx9/in7XNx g3c6zJ8hxUmZ0MgGw7len6YamoSKn8oAhOSRBEx2HlRF9WDAsZHCOMaWHx71E41Q/adY ADExLkh+o8Rad0OhKprpYQ70q10O/m80COsQLb6Nfd5ZeyWjCM4GhC4KTorQQiz2/Umm pNxc0WPRrmLMafh/F0ICpKsBal6nBga6/HIMqZ2J/D13GZV+wR/I2HwEhFCfhXFYLgj/ D58bayjFPbD3mzB1mTkiT8JCIF8+sPjXqmT53rFA1foBiqVkJpEkF/Q6gkdmvDHZIDqs j7Hg== 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; bh=UCuHFb65NPOBHih+9SxyFiiBOSlc4sL2tNkDZwQS3oE=; b=dr9c8ucoTJjG/6gUW5ZicFWl7BZEWBdrFRnCabVgD13TLZyocKUD24NMfS1z8o00o0 KKtF+wSm8P2FWkDYuloYuQXCE80ljruN0+tboY2ZiUfMJqnkp0SJb2whBi8H4Vh4xToi DCwY5Y7uEljiHvbPqR0A1d8J9ActU+eE/sqF+VEOZ068Ww6r5xMKSzcwamg+yCyfwzpF b0wEbmivMuYfKkKmm+GfIJjBEwEVyZYIixs9kYeWwsA1QiKOTASYYLDOmDcTCvm8Ze3t Z6w3UW3lBua3VO7JhtGTkgbCKX+Dn7FZQ+l3qHGp8m3gIXUIletMZ8jTFAbTCpas39K1 IPsA== X-Gm-Message-State: AD7BkJIcnMq2Z/iuIp+3fDoF8GEpJrH0e5LbCPmRq9uz5MEUY/76/UYgMTUEiBuJSvmRe81nplNMNb7HtxtelA== MIME-Version: 1.0 X-Received: by 10.107.11.162 with SMTP id 34mr10728098iol.165.1458236739369; Thu, 17 Mar 2016 10:45:39 -0700 (PDT) Received: by 10.36.14.19 with HTTP; Thu, 17 Mar 2016 10:45:39 -0700 (PDT) In-Reply-To: <8403291.NqUNo0Qq5W@ralph.baldwin.cx> References: <20160317053704.GP1741@kib.kiev.ua> <8403291.NqUNo0Qq5W@ralph.baldwin.cx> Date: Thu, 17 Mar 2016 10:45:39 -0700 Message-ID: Subject: Re: Peformance issues with r278325 From: Adrian Chadd To: John Baldwin Cc: Konstantin Belousov , Stanislav Sedov , "freebsd-hackers@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Mailman-Approved-At: Thu, 17 Mar 2016 18:31:10 +0000 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Mar 2016 17:45:40 -0000 On 17 March 2016 at 10:23, John Baldwin wrote: > > I had not expected this commit to have this impact, but Konstantin is correct. > I wonder if simply reducing the DELAY() from 5 down to 1 or so would be > sufficient? (Note that you need to adjust the prior loop to use += 1 instead > of += 5 in that case.) > > Note that DETECT_DEADLOCK is not enabled by default, so the AFTER_SPIN case > (which waits for an IPI just sent to be delivered) shouldn't be enabled (and > in fact I'd like to just remove that code entirely). This means that only > BEFORE_SPIN should be spinning, and it should only be spinning if a CPU sends > IPIs back to back such that the previous IPI is still pending (not yet > delivered) when the CPU wants to send another IPI. > > We can probably assume a TSC if we have SMP, so if changing the delay from 5 > to 1 doesn't work we can try just using the TSC directly to control the > spin length and go back to using a simple pause. > > I have an old set of changes that might also be interesting that permit > TLB shootdown IPI handlers to run while spinlocks are held (by using cr8/TPR > to control interrupts when a spinlock is held instead of disabling all > interrupts). I haven't found a workload where that helped yet. However, > yours might be an interesting workload to try those changes out on. Do you think it's worth just reverting it for now just so it lands in 10.3-RELEASE? -adrian From owner-freebsd-hackers@freebsd.org Fri Mar 18 07:23:10 2016 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 56CF7AD4F89 for ; Fri, 18 Mar 2016 07:23:10 +0000 (UTC) (envelope-from by@reorigin.com) Received: from reorigin.com (reorigin.com [199.48.133.238]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freebsd10-1-64", Issuer "freebsd10-1-64" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 182E61AE6 for ; Fri, 18 Mar 2016 07:23:09 +0000 (UTC) (envelope-from by@reorigin.com) Received: from reorigin.com (localhost [127.0.0.1]) by reorigin.com (8.14.9/8.14.9) with ESMTP id u2I79TK8005578 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Fri, 18 Mar 2016 03:09:29 -0400 (EDT) (envelope-from by@reorigin.com) Received: (from by@localhost) by reorigin.com (8.14.9/8.14.9/Submit) id u2I79T2i005577 for freebsd-hackers@freebsd.org; Fri, 18 Mar 2016 03:09:29 -0400 (EDT) (envelope-from by) Date: Fri, 18 Mar 2016 03:09:29 -0400 (EDT) From: Yao Bao Message-Id: <201603180709.u2I79T2i005577@reorigin.com> To: freebsd-hackers@freebsd.org Subject: Strange php shell_exec() issue. X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Mar 2016 07:23:10 -0000 Hi, I am trying to get disk usage information via php. So I use shell_exec("du -s file/") to get it. I execute the command via shell and php CLI, both return the same right result. But the problem is, when I try to echo the result on browser, the number field of the output doubled! I searched the issue via Google, there is someone got the same issue, but seems no resolutions yet. This seems not a php bug, can this be related with nginx? I use php 7.0.4, nginx 1.8.1, FreeBSD 10.1-RELEASE-p31. Is there anyone got any idea about it? Thanks. by From owner-freebsd-hackers@freebsd.org Fri Mar 18 07:33:23 2016 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 B935FAD4710 for ; Fri, 18 Mar 2016 07:33:23 +0000 (UTC) (envelope-from fullermd@over-yonder.net) Received: from mail.infocus-llc.com (mail.infocus-llc.com [199.15.120.13]) (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 9AB331E17 for ; Fri, 18 Mar 2016 07:33:23 +0000 (UTC) (envelope-from fullermd@over-yonder.net) Received: from draco.over-yonder.net (c-75-65-60-66.hsd1.ms.comcast.net [75.65.60.66]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.tarragon.infocus-llc.com (Postfix) with ESMTPSA id 3qRH584dQXz4f; Fri, 18 Mar 2016 02:33:16 -0500 (CDT) Received: by draco.over-yonder.net (Postfix, from userid 100) id 3qRH575mBlz2L1; Fri, 18 Mar 2016 02:33:15 -0500 (CDT) Date: Fri, 18 Mar 2016 02:33:15 -0500 From: "Matthew D. Fuller" To: Yao Bao Cc: freebsd-hackers@freebsd.org Subject: Re: Strange php shell_exec() issue. Message-ID: <20160318073315.GC4672@over-yonder.net> References: <201603180709.u2I79T2i005577@reorigin.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201603180709.u2I79T2i005577@reorigin.com> X-Editor: vi X-OS: FreeBSD X-Virus-Scanned: clamav-milter 0.99 at mail.tarragon.infocus-llc.com X-Virus-Status: Clean User-Agent: Mutt/1.5.24-fullermd.4 (2015-08-30) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Mar 2016 07:33:23 -0000 On Fri, Mar 18, 2016 at 03:09:29AM -0400 I heard the voice of Yao Bao, and lo! it spake thus: > > I execute the command via shell and php CLI, both return the same > right result. But the problem is, when I try to echo the result on > browser, the number field of the output doubled! Perhaps you've got $BLOCKSIZE=1024 in your env, so when you run it from your shell (or a descendent thereof), it's showing the output in multiples of 1k, but from the web there's no such env, so you're showing in multiples of 512. Try with du -k (or -h, if it's for human consumption anyway). -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. From owner-freebsd-hackers@freebsd.org Fri Mar 18 07:48:04 2016 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 B8BC9AD4D56 for ; Fri, 18 Mar 2016 07:48:04 +0000 (UTC) (envelope-from by@reorigin.com) Received: from reorigin.com (reorigin.com [199.48.133.238]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freebsd10-1-64", Issuer "freebsd10-1-64" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 8143F2DA for ; Fri, 18 Mar 2016 07:48:04 +0000 (UTC) (envelope-from by@reorigin.com) Received: from reorigin.com (localhost [127.0.0.1]) by reorigin.com (8.14.9/8.14.9) with ESMTP id u2I7m05Y005825 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Fri, 18 Mar 2016 03:48:00 -0400 (EDT) (envelope-from by@reorigin.com) Received: (from by@localhost) by reorigin.com (8.14.9/8.14.9/Submit) id u2I7m0uo005824 for freebsd-hackers@freebsd.org; Fri, 18 Mar 2016 03:48:00 -0400 (EDT) (envelope-from by) Date: Fri, 18 Mar 2016 03:48:00 -0400 (EDT) From: Yao Bao Message-Id: <201603180748.u2I7m0uo005824@reorigin.com> To: freebsd-hackers@freebsd.org Subject: Yes, it is! X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Mar 2016 07:48:04 -0000 Thanks Matthew, It works with -k option! The $BLOCKSIZE env is the root cause. by From owner-freebsd-hackers@freebsd.org Fri Mar 18 18:05:15 2016 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 B2A24AD4D59 for ; Fri, 18 Mar 2016 18:05:15 +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 939181053; Fri, 18 Mar 2016 18:05:15 +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 A3C63B94B; Fri, 18 Mar 2016 14:05:14 -0400 (EDT) From: John Baldwin To: Adrian Chadd Cc: Konstantin Belousov , Stanislav Sedov , "freebsd-hackers@freebsd.org" Subject: Re: Peformance issues with r278325 Date: Fri, 18 Mar 2016 10:37:55 -0700 Message-ID: <3277812.DVsZx4uMun@ralph.baldwin.cx> User-Agent: KMail/4.14.3 (FreeBSD/10.2-STABLE; KDE/4.14.3; amd64; ; ) In-Reply-To: References: <8403291.NqUNo0Qq5W@ralph.baldwin.cx> 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); Fri, 18 Mar 2016 14:05:14 -0400 (EDT) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Mar 2016 18:05:15 -0000 On Thursday, March 17, 2016 10:45:39 AM Adrian Chadd wrote: > On 17 March 2016 at 10:23, John Baldwin wrote: > > > > > I had not expected this commit to have this impact, but Konstantin is correct. > > I wonder if simply reducing the DELAY() from 5 down to 1 or so would be > > sufficient? (Note that you need to adjust the prior loop to use += 1 instead > > of += 5 in that case.) > > > > Note that DETECT_DEADLOCK is not enabled by default, so the AFTER_SPIN case > > (which waits for an IPI just sent to be delivered) shouldn't be enabled (and > > in fact I'd like to just remove that code entirely). This means that only > > BEFORE_SPIN should be spinning, and it should only be spinning if a CPU sends > > IPIs back to back such that the previous IPI is still pending (not yet > > delivered) when the CPU wants to send another IPI. > > > > We can probably assume a TSC if we have SMP, so if changing the delay from 5 > > to 1 doesn't work we can try just using the TSC directly to control the > > spin length and go back to using a simple pause. > > > > I have an old set of changes that might also be interesting that permit > > TLB shootdown IPI handlers to run while spinlocks are held (by using cr8/TPR > > to control interrupts when a spinlock is held instead of disabling all > > interrupts). I haven't found a workload where that helped yet. However, > > yours might be an interesting workload to try those changes out on. > > Do you think it's worth just reverting it for now just so it lands in > 10.3-RELEASE? Probably. If the '1' change fixes it that is a simple test, otherwise we can revert in 10.x. I think I'll likely just convert it to use a direct TSC delay loop always in HEAD (assuming that verifies ok in testing as well). -- John Baldwin From owner-freebsd-hackers@freebsd.org Fri Mar 18 18:16:28 2016 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 E9CD1AD5232 for ; Fri, 18 Mar 2016 18:16:28 +0000 (UTC) (envelope-from stas@FreeBSD.org) Received: from mx0.deglitch.com (mx0.deglitch.com [IPv6:2a00:13c0:63:7194:1::3]) by mx1.freebsd.org (Postfix) with ESMTP id A2AEC1D52; Fri, 18 Mar 2016 18:16:28 +0000 (UTC) (envelope-from stas@FreeBSD.org) Received: from [IPv6:2620:10d:c082:1803:9c65:ebd8:7cd2:7e46] (unknown [IPv6:2620:10d:c090:200::f:9a2b]) by mx0.deglitch.com (Postfix) with ESMTPSA id 1125D8FC0B; Fri, 18 Mar 2016 11:16:23 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\)) Subject: Re: Peformance issues with r278325 From: Stanislav Sedov In-Reply-To: <3277812.DVsZx4uMun@ralph.baldwin.cx> Date: Fri, 18 Mar 2016 11:16:21 -0700 Cc: Adrian Chadd , Konstantin Belousov , "freebsd-hackers@freebsd.org" Content-Transfer-Encoding: quoted-printable Message-Id: <8EE51E0E-41F4-4B5A-A755-B58E8E1D1776@FreeBSD.org> References: <8403291.NqUNo0Qq5W@ralph.baldwin.cx> <3277812.DVsZx4uMun@ralph.baldwin.cx> To: John Baldwin X-Mailer: Apple Mail (2.3112) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Mar 2016 18:16:29 -0000 > On Mar 18, 2016, at 10:37 AM, John Baldwin wrote: >=20 > On Thursday, March 17, 2016 10:45:39 AM Adrian Chadd wrote: >> On 17 March 2016 at 10:23, John Baldwin wrote: >>=20 >>>=20 >>> I had not expected this commit to have this impact, but Konstantin = is correct. >>> I wonder if simply reducing the DELAY() from 5 down to 1 or so would = be >>> sufficient? (Note that you need to adjust the prior loop to use +=3D = 1 instead >>> of +=3D 5 in that case.) >>>=20 >>> Note that DETECT_DEADLOCK is not enabled by default, so the = AFTER_SPIN case >>> (which waits for an IPI just sent to be delivered) shouldn't be = enabled (and >>> in fact I'd like to just remove that code entirely). This means = that only >>> BEFORE_SPIN should be spinning, and it should only be spinning if a = CPU sends >>> IPIs back to back such that the previous IPI is still pending (not = yet >>> delivered) when the CPU wants to send another IPI. >>>=20 >>> We can probably assume a TSC if we have SMP, so if changing the = delay from 5 >>> to 1 doesn't work we can try just using the TSC directly to control = the >>> spin length and go back to using a simple pause. >>>=20 >>> I have an old set of changes that might also be interesting that = permit >>> TLB shootdown IPI handlers to run while spinlocks are held (by using = cr8/TPR >>> to control interrupts when a spinlock is held instead of disabling = all >>> interrupts). I haven't found a workload where that helped yet. = However, >>> yours might be an interesting workload to try those changes out on. >>=20 >> Do you think it's worth just reverting it for now just so it lands in >> 10.3-RELEASE? >=20 > Probably. If the '1' change fixes it that is a simple test, otherwise = we > can revert in 10.x. I think I'll likely just convert it to use a = direct > TSC delay loop always in HEAD (assuming that verifies ok in testing as = well). >=20 FWIW we are currently testing the delay '1' change. Unfortunately, the = test is not easy to repeat (we didn't find a synthetic one yet that results in = the same outcome), so it does take more time that I would like. Will follow up = with the=20 results. We did try HEAD as well a while ago, and although it exhibited the same = pattern. However it did not utilize the x2apic unfortunately, as it does seem to = be disables in the BIOS (FreeBSD reports it being disables in the DMAR table). Thanks for looking into it! -- Stanislav Sedov ST4096-RIPE From owner-freebsd-hackers@freebsd.org Fri Mar 18 18:49:20 2016 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 890A9AD5D41 for ; Fri, 18 Mar 2016 18:49:20 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: from mail-io0-x229.google.com (mail-io0-x229.google.com [IPv6:2607:f8b0:4001:c06::229]) (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 33264FE2; Fri, 18 Mar 2016 18:49:20 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: by mail-io0-x229.google.com with SMTP id v123so37458109ioe.0; Fri, 18 Mar 2016 11:49:20 -0700 (PDT) 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; bh=AoF8jD67/vh0nsS7HUDCyZWYAb8r7DIse4lqrfEDTRc=; b=CEbMUdrO5CxPRtmNWLfgpvq9h4HKtFohDY4EDVLf+WoIwYKOLkgUvJ0NmBJzHYJlPX ohZMQRDqhUflQbY49ct50xXB5so/hWtlay2MzNo4HTX9jSBNH7c5NMlCBlraXj54Jtwh gN9u95ZX5iD4AX3Ve8gllpqLTvccldw8OacG7I1Oq9qXAQ4Rnv5KC4AZs0wlWnK51G3J ZYJRwz2pA9gRpLdW3ANu96HwVT839Ow1mV6NOZy4RwOULl5kL9xUfn02OTh1YTJgYt6P Nsvn83i9aR48hOkvNdNpclgqYutiW28k18zGFaaXoZsug0IDvdrjinE2pJYZzoxAO759 f4Dw== 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; bh=AoF8jD67/vh0nsS7HUDCyZWYAb8r7DIse4lqrfEDTRc=; b=PF7dzzH5N714ODVKQomhRFOsKYf1x+YaykJjJiO71Oh2hJFICpM7N7ej+YyIfvHJXj cKhzoOE3/6AjYBtQ0aK927cwQPVlenvW7rd9qJwSA/qe6FtGihSBFSPhABB07zKgrkI0 yKDfg+5kO1DNyFSYHwAVMsgwiOc5VOa6SXn0uk+d58UczuUtKWoQDdkPK1/pd5V+zr2r L/f899B9oLCKtp/+mZuLlo7PGNL9NYrbrAEIIaktxkHLh36fZ3nxW5t9RtvcI+qZtBJu wK8Exrd0Ot0WN3UQjQGaiIHE+DZmTqyoAe/1rPdsr4z38vKa2YDIg7WMDOPx5LWbiFel PPKA== X-Gm-Message-State: AD7BkJJGBI+LC7yS9IJdq9VfpJ4BPzQPQExzJS+6kO/IlfTSx7GkFvrHSDzJTWwbucMHLp4HNQZslaLpO3GXUg== MIME-Version: 1.0 X-Received: by 10.107.159.137 with SMTP id i131mr8269871ioe.29.1458326959633; Fri, 18 Mar 2016 11:49:19 -0700 (PDT) Received: by 10.107.6.32 with HTTP; Fri, 18 Mar 2016 11:49:19 -0700 (PDT) In-Reply-To: <3277812.DVsZx4uMun@ralph.baldwin.cx> References: <8403291.NqUNo0Qq5W@ralph.baldwin.cx> <3277812.DVsZx4uMun@ralph.baldwin.cx> Date: Fri, 18 Mar 2016 14:49:19 -0400 Message-ID: Subject: Re: Peformance issues with r278325 From: Ryan Stone To: John Baldwin Cc: Adrian Chadd , Konstantin Belousov , Stanislav Sedov , "freebsd-hackers@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Mar 2016 18:49:20 -0000 On Fri, Mar 18, 2016 at 1:37 PM, John Baldwin wrote: > I think I'll likely just convert it to use a direct > TSC delay loop always in HEAD (assuming that verifies ok in testing as > well). > Couldn't that work incorrectly on VM guests? The tsc is not guaranteed to be monotonic in that environment. From owner-freebsd-hackers@freebsd.org Fri Mar 18 18:58:31 2016 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 236D3AD40CF for ; Fri, 18 Mar 2016 18:58:31 +0000 (UTC) (envelope-from stas@FreeBSD.org) Received: from mx0.deglitch.com (mx0.deglitch.com [62.152.53.178]) by mx1.freebsd.org (Postfix) with ESMTP id D8165158A; Fri, 18 Mar 2016 18:58:30 +0000 (UTC) (envelope-from stas@FreeBSD.org) Received: from [IPv6:2620:10d:c082:1803:9c65:ebd8:7cd2:7e46] (unknown [IPv6:2620:10d:c090:200::f:9a2b]) by mx0.deglitch.com (Postfix) with ESMTPSA id DC8B58FC0B; Fri, 18 Mar 2016 11:58:21 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\)) Subject: Re: Peformance issues with r278325 From: Stanislav Sedov In-Reply-To: Date: Fri, 18 Mar 2016 11:58:19 -0700 Cc: John Baldwin , Adrian Chadd , Konstantin Belousov , "freebsd-hackers@freebsd.org" Content-Transfer-Encoding: quoted-printable Message-Id: <59BA610B-3754-43D6-839D-84FEE8F13CF7@FreeBSD.org> References: <8403291.NqUNo0Qq5W@ralph.baldwin.cx> <3277812.DVsZx4uMun@ralph.baldwin.cx> To: Ryan Stone X-Mailer: Apple Mail (2.3112) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Mar 2016 18:58:31 -0000 > On Mar 18, 2016, at 11:49 AM, Ryan Stone wrote: >=20 > On Fri, Mar 18, 2016 at 1:37 PM, John Baldwin wrote: > I think I'll likely just convert it to use a direct > TSC delay loop always in HEAD (assuming that verifies ok in testing as = well). >=20 > Couldn't that work incorrectly on VM guests? The tsc is not = guaranteed to be monotonic in that environment. >=20 Another concern is SMP systems where the clock is not synchronized. SMP = TSC requires a complicated setup procedure on the system boot which is not followed = properly by all vendors, and I have seen some recent systems with SMP TSC skew. I'm afraid that using TSC in this code will make FreeBSD unusable on = such (arguably buggy) systems.=20 -- Stanislav Sedov ST4096-RIPE From owner-freebsd-hackers@freebsd.org Fri Mar 18 19:01:42 2016 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 2B893AD42D6 for ; Fri, 18 Mar 2016 19:01:42 +0000 (UTC) (envelope-from stas@FreeBSD.org) Received: from mx0.deglitch.com (mx0.deglitch.com [IPv6:2a00:13c0:63:7194:1::3]) by mx1.freebsd.org (Postfix) with ESMTP id DB9A819A8; Fri, 18 Mar 2016 19:01:41 +0000 (UTC) (envelope-from stas@FreeBSD.org) Received: from [IPv6:2620:10d:c082:1803:9c65:ebd8:7cd2:7e46] (unknown [IPv6:2620:10d:c090:200::f:9a2b]) by mx0.deglitch.com (Postfix) with ESMTPSA id 704348FC0B; Fri, 18 Mar 2016 12:01:39 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\)) Subject: Re: Peformance issues with r278325 From: Stanislav Sedov In-Reply-To: <8EE51E0E-41F4-4B5A-A755-B58E8E1D1776@FreeBSD.org> Date: Fri, 18 Mar 2016 12:01:37 -0700 Cc: Adrian Chadd , Konstantin Belousov , "freebsd-hackers@freebsd.org" Content-Transfer-Encoding: quoted-printable Message-Id: References: <8403291.NqUNo0Qq5W@ralph.baldwin.cx> <3277812.DVsZx4uMun@ralph.baldwin.cx> <8EE51E0E-41F4-4B5A-A755-B58E8E1D1776@FreeBSD.org> To: John Baldwin X-Mailer: Apple Mail (2.3112) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Mar 2016 19:01:42 -0000 > On Mar 18, 2016, at 11:16 AM, Stanislav Sedov = wrote: >=20 > FWIW we are currently testing the delay '1' change. Unfortunately, = the test is > not easy to repeat (we didn't find a synthetic one yet that results in = the same > outcome), so it does take more time that I would like. Will follow up = with the=20 > results. >=20 > We did try HEAD as well a while ago, and although it exhibited the = same pattern. > However it did not utilize the x2apic unfortunately, as it does seem = to be disables > in the BIOS (FreeBSD reports it being disables in the DMAR table). >=20 > Thanks for looking into it! >=20 Replying to my own message. The `delay 1` test was a success, we were not able to reproduce the same = issues as we had with a 5us delay in that loop. So perhaps we should commit = the delay change into stable/10 instead of reverting the code altogether (I assume = the original change was done to solve a real issue?). -- Stanislav Sedov ST4096-RIPE From owner-freebsd-hackers@freebsd.org Fri Mar 18 19:56:21 2016 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 12342AD581B for ; Fri, 18 Mar 2016 19:56:21 +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 E73D71BC5; Fri, 18 Mar 2016 19:56:20 +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 051B9B977; Fri, 18 Mar 2016 15:56:20 -0400 (EDT) From: John Baldwin To: Stanislav Sedov Cc: Adrian Chadd , Konstantin Belousov , "freebsd-hackers@freebsd.org" Subject: Re: Peformance issues with r278325 Date: Fri, 18 Mar 2016 12:39:17 -0700 Message-ID: <2326466.jJrZ2mpkPP@ralph.baldwin.cx> User-Agent: KMail/4.14.3 (FreeBSD/10.2-STABLE; KDE/4.14.3; amd64; ; ) In-Reply-To: References: <8EE51E0E-41F4-4B5A-A755-B58E8E1D1776@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); Fri, 18 Mar 2016 15:56:20 -0400 (EDT) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Mar 2016 19:56:21 -0000 On Friday, March 18, 2016 12:01:37 PM Stanislav Sedov wrote: > > > On Mar 18, 2016, at 11:16 AM, Stanislav Sedov wrote: > > > > FWIW we are currently testing the delay '1' change. Unfortunately, the test is > > not easy to repeat (we didn't find a synthetic one yet that results in the same > > outcome), so it does take more time that I would like. Will follow up with the > > results. > > > > We did try HEAD as well a while ago, and although it exhibited the same pattern. > > However it did not utilize the x2apic unfortunately, as it does seem to be disables > > in the BIOS (FreeBSD reports it being disables in the DMAR table). > > > > Thanks for looking into it! > > > > Replying to my own message. > > The `delay 1` test was a success, we were not able to reproduce the same issues > as we had with a 5us delay in that loop. So perhaps we should commit the delay > change into stable/10 instead of reverting the code altogether (I assume the original > change was done to solve a real issue?). Ok, I will commit this to HEAD today. Thanks! -- John Baldwin From owner-freebsd-hackers@freebsd.org Fri Mar 18 19:56:19 2016 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 B9B3CAD5818 for ; Fri, 18 Mar 2016 19:56:19 +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 98B8E1BC1; Fri, 18 Mar 2016 19:56:19 +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 B11C8B94B; Fri, 18 Mar 2016 15:56:18 -0400 (EDT) From: John Baldwin To: Ryan Stone Cc: Adrian Chadd , Konstantin Belousov , Stanislav Sedov , "freebsd-hackers@freebsd.org" Subject: Re: Peformance issues with r278325 Date: Fri, 18 Mar 2016 12:52:31 -0700 Message-ID: <3596968.BYL0ZzVcSC@ralph.baldwin.cx> User-Agent: KMail/4.14.3 (FreeBSD/10.2-STABLE; KDE/4.14.3; amd64; ; ) In-Reply-To: References: <3277812.DVsZx4uMun@ralph.baldwin.cx> 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); Fri, 18 Mar 2016 15:56:18 -0400 (EDT) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Mar 2016 19:56:19 -0000 On Friday, March 18, 2016 02:49:19 PM Ryan Stone wrote: > On Fri, Mar 18, 2016 at 1:37 PM, John Baldwin wrote: > > > I think I'll likely just convert it to use a direct > > TSC delay loop always in HEAD (assuming that verifies ok in testing as > > well). > > > > Couldn't that work incorrectly on VM guests? The tsc is not guaranteed to > be monotonic in that environment. DELAY() is already using TSC there (unless the guest has disabled TSC entirely which is unlikely). Using a direct TSC deadline means that we can break out of the loop as soon as the previous IPI unpends while still having a somewhat reasonable deadline timeout while checking the status of the previous IPI at a finer granularity than 1 usec. Of course, as kib@ noted, x2APIC doesn't suffer from this at all as IPI sends are "atomic" on x2APIc,s x2APIC is a better all-around solution when available. -- John Baldwin From owner-freebsd-hackers@freebsd.org Fri Mar 18 19:56:22 2016 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 57F8CAD5823 for ; Fri, 18 Mar 2016 19:56:22 +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 38B8F1BC7; Fri, 18 Mar 2016 19:56:22 +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 4FD48B93A; Fri, 18 Mar 2016 15:56:21 -0400 (EDT) From: John Baldwin To: Stanislav Sedov Cc: Ryan Stone , Adrian Chadd , Konstantin Belousov , "freebsd-hackers@freebsd.org" Subject: Re: Peformance issues with r278325 Date: Fri, 18 Mar 2016 12:38:42 -0700 Message-ID: <3213721.SRyKE0LtiG@ralph.baldwin.cx> User-Agent: KMail/4.14.3 (FreeBSD/10.2-STABLE; KDE/4.14.3; amd64; ; ) In-Reply-To: <59BA610B-3754-43D6-839D-84FEE8F13CF7@FreeBSD.org> References: <59BA610B-3754-43D6-839D-84FEE8F13CF7@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); Fri, 18 Mar 2016 15:56:21 -0400 (EDT) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Mar 2016 19:56:22 -0000 On Friday, March 18, 2016 11:58:19 AM Stanislav Sedov wrote: > > > On Mar 18, 2016, at 11:49 AM, Ryan Stone wrote: > > > > On Fri, Mar 18, 2016 at 1:37 PM, John Baldwin wrote: > > I think I'll likely just convert it to use a direct > > TSC delay loop always in HEAD (assuming that verifies ok in testing as well). > > > > Couldn't that work incorrectly on VM guests? The tsc is not guaranteed to be monotonic in that environment. > > > > Another concern is SMP systems where the clock is not synchronized. SMP TSC requires > a complicated setup procedure on the system boot which is not followed properly by all > vendors, and I have seen some recent systems with SMP TSC skew. > > I'm afraid that using TSC in this code will make FreeBSD unusable on such (arguably buggy) > systems. Eh, SMP does not matter here. DELAY() already uses TSC on FreeBSD. The current thread is pinned to a single CPU in lapic_ipi_wait(). The idea would be to do this: deadline = rdtsc() + freq * delay / 1000000; while (rdtsc() < deadline) { if (APIC_DELSTAT_IDLE) return (1); ia32_pause(); } -- John Baldwin From owner-freebsd-hackers@freebsd.org Fri Mar 18 20:11:16 2016 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 9D248AD5D7F for ; Fri, 18 Mar 2016 20:11:16 +0000 (UTC) (envelope-from kmacybsd@gmail.com) Received: from mail-io0-x230.google.com (mail-io0-x230.google.com [IPv6:2607:f8b0:4001:c06::230]) (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 47E771948; Fri, 18 Mar 2016 20:11:16 +0000 (UTC) (envelope-from kmacybsd@gmail.com) Received: by mail-io0-x230.google.com with SMTP id g184so93019543ioa.3; Fri, 18 Mar 2016 13:11:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc; bh=J0YlUPekAhiRacOUrIaBuw1Vi+1XUEMTjfflni3hPuI=; b=p9Zr2MlE8p5A6a4mN0cTwsn9FwXu6hrzNH/5BPsf7KR2iBWbgxn/78LvaVLDiQ6J4H WaD8F19w9WV/ZNh90Ufcot7bHj3+S+iUFczucEpdlRX9mwc9je1vtbMMlwuSivdo9FF8 TI2BgrZaX7qdEIrIeSFIhphOCbz4+NLsA7h60/39IYg4JP6URCXrm6flBECPcAKgrqgd 04xakIKZDSX+5vHx3j6JhTwi0mxEf/fSeed6YI8n09tnUMrIyooeLPWeNuzrQCMhN8lX ecEYb/jTN5g3+mfR6j6xPZ1R6StkYyjQvI6Yt4Cse4bmBApDa6lyQrNsNlyJdBin+8iN u6lA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc; bh=J0YlUPekAhiRacOUrIaBuw1Vi+1XUEMTjfflni3hPuI=; b=R0/d2PS1v5J7FaymUZIVfLJcsZcCRmQKmnUiuT7mb9I2XIHfUrXQ+PvR6YCab9+nFD +UU/YbqyW8zMkz9SUKJdjKECK/Hc5belDTuc3ab/bdxqYc37D62Ol3FwBTV6FZMcljh+ tZaUYF8fFruE2l/y/n08HnKVGWMXTsOE46eS2oDp3k/WnA5z1fEkFAgndmf5RLyhoSWb nVWavYO2wr7NwiqzfPWFd897+smQzO+HM0svG9k8qddVWl7AxFR5N0+TAvy8RJHjjrtn gRcPky9yl3HzgSsNOIy+Vumg1zn6boRqtIbFASuK9/tbvij9kMYAbo+vIIDiqq7ncSRI YnyA== X-Gm-Message-State: AD7BkJIoWdGNpz64jLWCnCXEyJfMrC5wYdxtK8a0rtpcfIC8QsaJ6idZzHiyJzI5ghyw/Y1BeCeRxf3mZbKE+g== MIME-Version: 1.0 X-Received: by 10.107.7.194 with SMTP id g63mr17410721ioi.81.1458331875596; Fri, 18 Mar 2016 13:11:15 -0700 (PDT) Sender: kmacybsd@gmail.com Received: by 10.107.132.81 with HTTP; Fri, 18 Mar 2016 13:11:15 -0700 (PDT) In-Reply-To: <3213721.SRyKE0LtiG@ralph.baldwin.cx> References: <59BA610B-3754-43D6-839D-84FEE8F13CF7@FreeBSD.org> <3213721.SRyKE0LtiG@ralph.baldwin.cx> Date: Fri, 18 Mar 2016 13:11:15 -0700 X-Google-Sender-Auth: Dm1yPy5d7ObJnEKUspPAfn-zjzk Message-ID: Subject: Re: Peformance issues with r278325 From: "K. Macy" To: John Baldwin Cc: Stanislav Sedov , Adrian Chadd , Konstantin Belousov , Ryan Stone , "freebsd-hackers@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Mar 2016 20:11:16 -0000 On Friday, March 18, 2016, John Baldwin wrote: > On Friday, March 18, 2016 11:58:19 AM Stanislav Sedov wrote: > > > > > On Mar 18, 2016, at 11:49 AM, Ryan Stone > wrote: > > > > > > On Fri, Mar 18, 2016 at 1:37 PM, John Baldwin > wrote: > > > I think I'll likely just convert it to use a direct > > > TSC delay loop always in HEAD (assuming that verifies ok in testing as > well). > > > > > > Couldn't that work incorrectly on VM guests? The tsc is not > guaranteed to be monotonic in that environment. > > > > > > > Another concern is SMP systems where the clock is not synchronized. SMP > TSC requires > > a complicated setup procedure on the system boot which is not followed > properly by all > > vendors, and I have seen some recent systems with SMP TSC skew. > > > > I'm afraid that using TSC in this code will make FreeBSD unusable on > such (arguably buggy) > > systems. > > Eh, SMP does not matter here. DELAY() already uses TSC on FreeBSD. The > current thread is pinned to a single CPU in lapic_ipi_wait(). The idea > would be to do this: > > deadline = rdtsc() + freq * delay / 1000000; > > while (rdtsc() < deadline) { > if (APIC_DELSTAT_IDLE) > return (1); > ia32_pause(); > } > > > In a VM the thread is pinned to the _vcpu_. You have no control over what physical core the underlying thread is running on. If the vcpu is migrated to a different package there is a possibility of the next TSC reading be a lower value. The rdtsc instruction reads the value of the physical core. Although I doubt this is a problem in practice, it is a possibility if vcpus are not pinned for the lifetime of the VM. -M > John Baldwin > _______________________________________________ > 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 Fri Mar 18 21:07:50 2016 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 34083AD5EF3 for ; Fri, 18 Mar 2016 21:07:50 +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 13660132A; Fri, 18 Mar 2016 21:07:50 +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 CA63AB94B; Fri, 18 Mar 2016 17:07:48 -0400 (EDT) From: John Baldwin To: "K. Macy" Cc: Stanislav Sedov , Adrian Chadd , Konstantin Belousov , Ryan Stone , "freebsd-hackers@freebsd.org" Subject: Re: Peformance issues with r278325 Date: Fri, 18 Mar 2016 14:05:39 -0700 Message-ID: <1938968.vRTG1GJntD@ralph.baldwin.cx> User-Agent: KMail/4.14.3 (FreeBSD/10.2-STABLE; KDE/4.14.3; amd64; ; ) In-Reply-To: References: <3213721.SRyKE0LtiG@ralph.baldwin.cx> 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); Fri, 18 Mar 2016 17:07:48 -0400 (EDT) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Mar 2016 21:07:50 -0000 On Friday, March 18, 2016 01:11:15 PM K. Macy wrote: > On Friday, March 18, 2016, John Baldwin wrote: > > > On Friday, March 18, 2016 11:58:19 AM Stanislav Sedov wrote: > > > > > > > On Mar 18, 2016, at 11:49 AM, Ryan Stone > > wrote: > > > > > > > > On Fri, Mar 18, 2016 at 1:37 PM, John Baldwin > > wrote: > > > > I think I'll likely just convert it to use a direct > > > > TSC delay loop always in HEAD (assuming that verifies ok in testing as > > well). > > > > > > > > Couldn't that work incorrectly on VM guests? The tsc is not > > guaranteed to be monotonic in that environment. > > > > > > > > > > Another concern is SMP systems where the clock is not synchronized. SMP > > TSC requires > > > a complicated setup procedure on the system boot which is not followed > > properly by all > > > vendors, and I have seen some recent systems with SMP TSC skew. > > > > > > I'm afraid that using TSC in this code will make FreeBSD unusable on > > such (arguably buggy) > > > systems. > > > > Eh, SMP does not matter here. DELAY() already uses TSC on FreeBSD. The > > current thread is pinned to a single CPU in lapic_ipi_wait(). The idea > > would be to do this: > > > > deadline = rdtsc() + freq * delay / 1000000; > > > > while (rdtsc() < deadline) { > > if (APIC_DELSTAT_IDLE) > > return (1); > > ia32_pause(); > > } > > > > > > > In a VM the thread is pinned to the _vcpu_. You have no control over what > physical core the underlying thread is running on. If the vcpu is migrated > to a different package there is a possibility of the next TSC reading be a > lower value. The rdtsc instruction reads the value of the physical core. > Although I doubt this is a problem in practice, it is a possibility if > vcpus are not pinned for the lifetime of the VM. Again, DELAY() already makes this assumption on FreeBSD/x86. If this is broken, it's broken in far, far many more places than this. In addition, a hypervisor is capable of handling this if it uses the TSC adjustment field in the VMCS. OTOH, TSC's on modern systems generally are in sync. Invariant TSCs are generated from a timer in the uncore on all the i[357] CPUs AFAIK, so they are identical across cores and threads within a package. They are also in sync across packages on all of the i[357] systems I have worked with (and generations prior to those) in the last 7-8 years (barring one machine I'm aware of that was a quad-socket i7 box where the BIOS overwrote the TSC of the first core in each package on each reboot to try to reset it to zero on each boot). -- John Baldwin From owner-freebsd-hackers@freebsd.org Sat Mar 19 08:08:42 2016 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 2FA74AD6F46 for ; Sat, 19 Mar 2016 08:08:42 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: from mail-wm0-x241.google.com (mail-wm0-x241.google.com [IPv6:2a00:1450:400c: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 B9D3AF0D; Sat, 19 Mar 2016 08:08:41 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: by mail-wm0-x241.google.com with SMTP id l68so10562462wml.3; Sat, 19 Mar 2016 01:08:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:in-reply-to:references:reply-to :mime-version:content-transfer-encoding; bh=pzEu347SieYbhlSwmPfTonQWbm/IB8lxI7TyLWmFgXg=; b=L/+MXmG3ykKbWwM8Fx6IWPZlEpYtKHZCzGCHTANVpl1w1FCWL7V/gqR2CjpTSQF3yO clasPu85m1s2UBsjsnaDzctMGdTETL2EepOqFzTNY5W364a4HNQXaWZUogpHtufO/Vgq 0du++dVXbLyx5VJTSMjg7rcZfFtwbepa8UspvUUg6MD5tFpC4dDFoS+3TnC3Md4EzS7K 2Zi0A+Js/HxMDOStgQrB0f0SXkX/aQga1KiFesW1t12XpV5pzRMBJUuq0wIJ3h7p2k1Q b+l6Ipt/05CiYL8NLj4vjy4z9Hi9MLUPiXsUAhjesF7eEHbz8uK7EVITPNYOq8CZS8K+ /I5w== 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:reply-to:mime-version:content-transfer-encoding; bh=pzEu347SieYbhlSwmPfTonQWbm/IB8lxI7TyLWmFgXg=; b=RA3MSc88uILgkRcluGkWt8yb9UZtyKuMg41SQIJurjtDl41lG34CfyrkaqTpDAOgCj cVU5o79Md3Vq1CPHCmutjF56NYWW0ty3lRNYKVoUk/4s+h+mm0048TV+mQWaftQdypMe IKa8X55qJkuS6leIdn+w+5dPvdV0gmoSbskdJ3zLV/9Uhrt9TDsK3PWMMM6YYCGnXzFg EinS9P3xMFltWlbw5BWJx6cKkU1XCl6U1V3ZdUW0vKQE7l6UtX9qZmkxiGAV7Uz4CNhG 1VYIfhOAAoovYc78hFTpNfRCtEd/wBnVqvFqHKsCKKSjfGL2naxupP/N+mFFbcl/uig5 vz7Q== X-Gm-Message-State: AD7BkJIpRumkWpRJkIdt7MJTzCyNxWiY8txgYSUPFn3T1zEt9SV/jDcnebW6l5GLDQQjCw== X-Received: by 10.28.104.131 with SMTP id d125mr2892664wmc.99.1458374920334; Sat, 19 Mar 2016 01:08:40 -0700 (PDT) Received: from ernst.home (p4FCA7056.dip0.t-ipconnect.de. [79.202.112.86]) by smtp.gmail.com with ESMTPSA id 82sm2574421wmd.4.2016.03.19.01.08.38 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 19 Mar 2016 01:08:39 -0700 (PDT) Date: Sat, 19 Mar 2016 09:08:37 +0100 From: Gary Jennejohn To: John Baldwin Cc: "K. Macy" , Stanislav Sedov , Adrian Chadd , Konstantin Belousov , Ryan Stone , "freebsd-hackers@freebsd.org" Subject: Re: Peformance issues with r278325 Message-ID: <20160319090837.7799561c@ernst.home> In-Reply-To: <1938968.vRTG1GJntD@ralph.baldwin.cx> References: <3213721.SRyKE0LtiG@ralph.baldwin.cx> <1938968.vRTG1GJntD@ralph.baldwin.cx> Reply-To: gljennjohn@gmail.com X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.29; amd64-portbld-freebsd11.0) 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.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Mar 2016 08:08:42 -0000 On Fri, 18 Mar 2016 14:05:39 -0700 John Baldwin wrote: > On Friday, March 18, 2016 01:11:15 PM K. Macy wrote: > > On Friday, March 18, 2016, John Baldwin wrote: > > > > > On Friday, March 18, 2016 11:58:19 AM Stanislav Sedov wrote: > > > > > > > > > On Mar 18, 2016, at 11:49 AM, Ryan Stone > > > wrote: > > > > > > > > > > On Fri, Mar 18, 2016 at 1:37 PM, John Baldwin > > > wrote: > > > > > I think I'll likely just convert it to use a direct > > > > > TSC delay loop always in HEAD (assuming that verifies ok in testing as > > > well). > > > > > > > > > > Couldn't that work incorrectly on VM guests? The tsc is not > > > guaranteed to be monotonic in that environment. > > > > > > > > > > > > > Another concern is SMP systems where the clock is not synchronized. SMP > > > TSC requires > > > > a complicated setup procedure on the system boot which is not followed > > > properly by all > > > > vendors, and I have seen some recent systems with SMP TSC skew. > > > > > > > > I'm afraid that using TSC in this code will make FreeBSD unusable on > > > such (arguably buggy) > > > > systems. > > > > > > Eh, SMP does not matter here. DELAY() already uses TSC on FreeBSD. The > > > current thread is pinned to a single CPU in lapic_ipi_wait(). The idea > > > would be to do this: > > > > > > deadline = rdtsc() + freq * delay / 1000000; > > > > > > while (rdtsc() < deadline) { > > > if (APIC_DELSTAT_IDLE) > > > return (1); > > > ia32_pause(); > > > } > > > > > > > > > > > In a VM the thread is pinned to the _vcpu_. You have no control over what > > physical core the underlying thread is running on. If the vcpu is migrated > > to a different package there is a possibility of the next TSC reading be a > > lower value. The rdtsc instruction reads the value of the physical core. > > Although I doubt this is a problem in practice, it is a possibility if > > vcpus are not pinned for the lifetime of the VM. > > Again, DELAY() already makes this assumption on FreeBSD/x86. If this is > broken, it's broken in far, far many more places than this. In addition, a > hypervisor is capable of handling this if it uses the TSC adjustment field > in the VMCS. OTOH, TSC's on modern systems generally are in sync. Invariant > TSCs are generated from a timer in the uncore on all the i[357] CPUs AFAIK, so > they are identical across cores and threads within a package. They are also > in sync across packages on all of the i[357] systems I have worked with (and > generations prior to those) in the last 7-8 years (barring one machine I'm > aware of that was a quad-socket i7 box where the BIOS overwrote the TSC of > the first core in each package on each reboot to try to reset it to zero on > each boot). > Just out of curiosity, can one assume that this is also true for AMD CPUs? I'm using a Phenom II X6 1090T in my box. -- Gary Jennejohn From owner-freebsd-hackers@freebsd.org Sat Mar 19 15:47:40 2016 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 2FA43AD6409 for ; Sat, 19 Mar 2016 15:47:40 +0000 (UTC) (envelope-from tyler@tysdomain.com) Received: from tds-solutions.net (tds-solutions.net [174.136.96.202]) (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 1E95F24A for ; Sat, 19 Mar 2016 15:47:39 +0000 (UTC) (envelope-from tyler@tysdomain.com) Received: from tds-solutions.net (localhost [127.0.0.1]) by tds-solutions.net (Postfix) with ESMTP id 6C04C208782E for ; Sat, 19 Mar 2016 11:47:39 -0400 (EDT) X-Virus-Scanned: amavisd-new at tds-solutions.net Received: from tds-solutions.net ([127.0.0.1]) by tds-solutions.net (tds-solutions.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id tXfd9QG6zatL for ; Sat, 19 Mar 2016 11:47:39 -0400 (EDT) Received: from [10.0.0.3] (c-50-164-134-175.hsd1.ma.comcast.net [50.164.134.175]) (Authenticated sender: sorressean) by tds-solutions.net (Postfix) with ESMTPSA id D11CD20877BA for ; Sat, 19 Mar 2016 11:47:38 -0400 (EDT) Reply-To: tyler@tysdomain.com To: freebsd-hackers@freebsd.org From: "Littlefield, Tyler" Subject: looking for areas to contribute Message-ID: <56ED75D8.1050800@tysdomain.com> Date: Sat, 19 Mar 2016 11:52:56 -0400 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Mar 2016 15:47:40 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 All, I've asked this before, but I'm in a better position now to make this work. I'm fluent with C and other languages and want to start contributing to BSD. I'm happy to work where ever I can be of use, I love more lower level stuff but anything that has me working on code would be great. My questions: 1) How do people usually have their environments set up? I'm thinking of running fbsd11 in BHyve where I can do testing, but if there's a better way to test that won't require so many resources that would be nice as well. I didn't want to break my host with testing since it's going to run various other services. 2) How do you prevent rebuilding world and kernel for simple patches? 3) ideas on what to work on would be great. I haven't gotten into really advanced BSD work for a while now, so I haven't found anything that is incredibly broken. Also although this may be off topic, I'm hoping I might find someone who uses IOCage here since this seems to be out of the realm of what most people do. Has anyone used IOCage on FreeBSD 11? If so, how did you manage to fetch the release? I pointed it to the snapshot FTP path and it fetched and extracted (freebsd-update failed to get public keys), but it doesn't show it as a release. My second thought is if I'm working on world then I can just rebuild world under the jail. Is this a good solution? Thanks, - -- Take care, Ty Twitter: @sorressean Web: https://tysdomain.com Pubkey: https://tysdomain.com/files/pubkey.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJW7XXYAAoJEAdP60+BYxejT/YIAIFzhdY6Z0dEWwbqIbXx3sZu 5Md/o4rR3Nui5x1DyM7p+g666cmJd+2TX1cl1nkbhYUt9sNiQbrHHfup+pIKGsaU F38lkBfGZ+t7vFEgSmiTd9B71IYrLHOkOmgUZE0WMpc3zJs7Y+Stku7kL2R3ej+w qaR+bSMpc9RQ6rgtBbKS4ubim5gyjdaOdQpp4FUt40eJGGDN+k+ecc3jgRE6S2z+ 7F4uwck+NLUhSybH+kjB6HHqX0oRcEu+XqNveFp7kGKY2aFSPdhgPdD+MAoKFunW ZzCwCgvY3aaGnKy/VfFP9oQ+P3gdVY4DccnQvufE3AyvNN7d+fl+b4HsZMGXXmI= =Ybcf -----END PGP SIGNATURE----- From owner-freebsd-hackers@freebsd.org Sat Mar 19 19:33:49 2016 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 6B76AAD645E for ; Sat, 19 Mar 2016 19:33:49 +0000 (UTC) (envelope-from mark@heily.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 41BDD18B2 for ; Sat, 19 Mar 2016 19:33:49 +0000 (UTC) (envelope-from mark@heily.com) Received: by mail-ig0-x22c.google.com with SMTP id cl4so7069194igb.0 for ; Sat, 19 Mar 2016 12:33:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heily-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=XCJEbFwIk+qHn1m04ExBfEYvLdwxlHiF2qNeARFuR7k=; b=whFr1yd2FTJJIDKktA4H50UyjSTlzH5DSYe2RBJlYl7LtVTgKyHpF5dIFgo9QI1Cfv pKKzIIrkoR7+FOCSW4tyXOfqYS4A9bd/0XK6Scosr5pAhuqdt6C4X9j5Lden9f2M4Tfr a+NwpdMbpYLnVaRj/3LbsnDOck8eTy6q+MZIVRYtPu5aGrmh8Zs46b2XiBC31LenxV1M nwxo18DXK7v6UqDIF///JOOsZ97VTyX8E5RHkbSGxs6To9OAcGiC8ipV9+rG15hpC+tL dxkceglm+0X+0psgm5P7ucCd4kPl2A7oIAtAWzeUdWJ3vA3R7HL/eWw3rlKBtMBK5Q0G cfZw== 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; bh=XCJEbFwIk+qHn1m04ExBfEYvLdwxlHiF2qNeARFuR7k=; b=b9ZSNld/6k/VViw4dHhxhFamDt1b+B7SIKyTofxsJuWzT+RqH2XdverJdqgcTcRBPz FGTdNi25fhly7qnYRuOL1eItuZRHrVhP7qPBTavIZMUDLv8QzFE6K4G6pTFcNNV4uksa XDtWRlQ64jNS7lXwZ1Xzwqv05E8A0E+zSSK3PzpLSCnTnh6hK3ZloHt73MoWXopulcTE LfPNCJCFDnjqnll7uPMfWfIzVAKcOYiN0wXbtaIe4H5TrXU5aWVWFFQFn5JU1Mn9Sil5 HUW0uGX4Zd68Iw4uJt1m5RkS7CNHeq8Sp93kclOs8GeE5XttwftKxOrDuh/dRAgJRT0T 9RAQ== X-Gm-Message-State: AD7BkJJTHWJxviyeSaLag2s4klFf0JrvsM5wcdJXvZzJ+pHVCJcivH4lbSKzFDve78gTt0paG1l6WyYMLKweIw== MIME-Version: 1.0 X-Received: by 10.50.79.198 with SMTP id l6mr4901717igx.30.1458416028514; Sat, 19 Mar 2016 12:33:48 -0700 (PDT) Received: by 10.79.30.133 with HTTP; Sat, 19 Mar 2016 12:33:48 -0700 (PDT) X-Originating-IP: [71.70.175.250] In-Reply-To: <56ED75D8.1050800@tysdomain.com> References: <56ED75D8.1050800@tysdomain.com> Date: Sat, 19 Mar 2016 15:33:48 -0400 Message-ID: Subject: Re: looking for areas to contribute From: Mark Heily To: tyler@tysdomain.com Cc: FreeBSD Hackers Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Mar 2016 19:33:49 -0000 Hi Tyler, On Sat, Mar 19, 2016 at 11:52 AM, Littlefield, Tyler wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > All, > I've asked this before, but I'm in a better position now to make this > work. > > I'm fluent with C and other languages and want to start contributing > to BSD. I'm happy to work where ever I can be of use, I love more > lower level stuff but anything that has me working on code would be > great. My questions: > > 1) How do people usually have their environments set up? I'm thinking > of running fbsd11 in BHyve where I can do testing, but if there's a > better way to test that won't require so many resources that would be > nice as well. I didn't want to break my host with testing since it's > going to run various other services. I tried using BHyve but was unable to get guest networking to work. Currently, I'm using VirtualBox and found this guide helpful in setting it up: https://www.freebsd.org/doc/handbook/virtualization-host-virtualbox.html What the guide doesn't mention is that port forwarding is very useful to allow you to SSH to your virtual machines, instead of working on the console. I typically assign a dedicated port on 127.0.0.1 mapped to each VM, and then have a simple 'vmssh' script to connect to each VM like so: vmssh freebsd11 The script looks like: vm=$1 shift case $1 in freebsd11) ssh -p 2222 localhost $* ;; freebsd9) ssh -p 2223 localhost $* ;; *) echo "Error: unknown guest" exit 1 esac > 3) ideas on what to work on would be great. I haven't gotten into > really advanced BSD work for a while now, so I haven't found anything > that is incredibly broken. > I'm looking for volunteers to help with relaunchd, which is a new service manager for FreeBSD and other Unix-like platforms. Here's the GitHub site: https://github.com/mheily/relaunchd There are a number of issues in the GitHub issue tracker that you could hack on. There's also a general need to take existing software that runs under rc(8) and write the configuration files to allow them to run under launchd(8). Are there any particular subject areas that interest you? Regards, - Mark