From owner-freebsd-hackers@FreeBSD.ORG Sun Sep 4 00:57:06 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7C838106566B; Sun, 4 Sep 2011 00:57:06 +0000 (UTC) (envelope-from jlpetz@internode.on.net) Received: from ipmail05.adl6.internode.on.net (ipmail05.adl6.internode.on.net [150.101.137.143]) by mx1.freebsd.org (Postfix) with ESMTP id C1F598FC15; Sun, 4 Sep 2011 00:57:05 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av8EAJ7MYk55LH3F/2dsb2JhbABDqGp5gUYBAQUIAh4SHC8BAwIGAxEEAQEBJwcZIA0JCAIEARILBb8thmoEm22IYA Received: from ppp121-44-125-197.lns20.syd6.internode.on.net (HELO Minx) ([121.44.125.197]) by ipmail05.adl6.internode.on.net with ESMTP; 04 Sep 2011 10:27:03 +0930 From: "Jarrod Lee Petz" To: "'Doug Barton'" , "'Erik Trulsson'" , References: <007301cc6979$a690f9a0$f3b2ece0$@internode.on.net> <4E616D6E.4030903@FreeBSD.org> <001701cc69d3$aea9a0b0$0bfce210$@internode.on.net> <4E61BA37.2060204@FreeBSD.org> <20110903134634.GA55652@owl.midgard.homeip.net> <4E62B99C.6020707@FreeBSD.org> In-Reply-To: <4E62B99C.6020707@FreeBSD.org> Date: Sun, 4 Sep 2011 10:57:00 +1000 Message-ID: <001e01cc6a9d$8e62c870$ab285950$@internode.on.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQHuPCHqJDmDdIw669xIXvDN9LM1EADkjGxsAa6N1kUCHwUDBgGXq6DUAa0cmgGUuQd40A== Content-Language: en-au Cc: Subject: RE: TIME_WAIT Assassination in FreeBSD??? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: petz@nisshoko.net List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Sep 2011 00:57:06 -0000 Hi Guys, Doug, I can appreciate your stance. I realize my problem description does not state any impact to FreeBSD and so I am unlikely to get a response on that. However I would like to know the theory behind how TCP/IP and FTP should handle this. One question, which list would have been more appropriate (freebsd-net)? Also just so you know I did get some other responses privately. Thanks you for your feedback. Erik, I think your right about testing how BSD would react. I'll run up a BSD VM on Monday(Australia time). If it works maybe I can deduce from the tcpdump why and what is does different. If it doesn't well, I'll have another test case and a little more insight. Regards Jarrod -----Original Message----- From: Doug Barton [mailto:dougb@FreeBSD.org] Sent: Sunday, 4 September 2011 9:35 AM To: Erik Trulsson Cc: freebsd-hackers@FreeBSD.org; petz@nisshoko.net; Jarrod Lee Petz Subject: Re: TIME_WAIT Assassination in FreeBSD??? On 09/03/2011 06:46, Erik Trulsson wrote: > On Fri, Sep 02, 2011 at 10:25:11PM -0700, Doug Barton wrote: >> On 09/02/2011 17:51, Jarrod Lee Petz wrote: >>> Hi Doug, >>> >>> The problem itself is currently seen on AIX yes. >> >> So you're much more likely to get help on an AIX list. > > Unlikely, since what he primarily asked about was if the problem in > question also exists on FreeBSD. That is something that AIX people are > unlikely to know anything about. I'd argue with "primarily," but since one other person has told me privately that they think my response was wrong, I'll respond publicly with my rationale. 1. His question is unlikely to get answered 2. ... at least in part because he mailed the wrong list 3. ... therefore I'm trying to manage expectations. Now, oddly enough, I notice that my responses to the OP are a hot topic of conversation, but no one has bothered to actually answer his questions. Hmmmmm..... Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ From owner-freebsd-hackers@FreeBSD.ORG Sun Sep 4 23:04:47 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 996251065676 for ; Sun, 4 Sep 2011 23:04:47 +0000 (UTC) (envelope-from olafBuddenhagen@gmx.net) Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by mx1.freebsd.org (Postfix) with SMTP id DC1F58FC1B for ; Sun, 4 Sep 2011 23:04:46 +0000 (UTC) Received: (qmail invoked by alias); 04 Sep 2011 22:38:04 -0000 Received: from port-92-195-29-21.dynamic.qsc.de (EHLO sky.local) [92.195.29.21] by mail.gmx.net (mp059) with SMTP; 05 Sep 2011 00:38:04 +0200 X-Authenticated: #1379927 X-Provags-ID: V01U2FsdGVkX1+0jvJ6G2m0blxquRlR96EO6Sb9K+bVc5cfPWXOHZ itEIjxaA3dKvoO Received: from 192.168.1.6 (ident=unknown) by sky.local with smtp (masqmail 0.2.27) id 1Qzgix-5uX-00; Sat, 03 Sep 2011 05:16:51 +0200 Received: by alien.local (sSMTP sendmail emulation); Sat, 03 Sep 2011 05:17:02 +0200 Date: Sat, 3 Sep 2011 05:17:02 +0200 From: To: Robert Millan Message-ID: <20110903031659.GR10284@alien.local> Mail-Followup-To: Robert Millan , freebsd-hackers@freebsd.org, Ed Maste , debian-hurd@lists.debian.org References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Y-GMX-Trusted: 0 X-Mailman-Approved-At: Sun, 04 Sep 2011 23:26:53 +0000 Cc: freebsd-hackers@freebsd.org, Ed Maste , debian-hurd@lists.debian.org Subject: Re: [PATCH] avoid assuming MAXPATHLEN in config(8) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Sep 2011 23:04:47 -0000 Hi, On Thu, Jul 07, 2011 at 11:33:53AM +0200, Robert Millan wrote: > - (void)snprintf(fname, sizeof fname, "../../conf/options.%s", > + (void)asprintf(&fname, "../../conf/options.%s", > machinename); Ignoring the return value of asprintf() is not a good idea, as it can indicate a failed allocation. On a related note, the return value of strdup() also should be checked. -antrik- From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 5 07:39:57 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 60FB0106564A for ; Mon, 5 Sep 2011 07:39:57 +0000 (UTC) (envelope-from seanhamilton@gmail.com) Received: from mail-ww0-f42.google.com (mail-ww0-f42.google.com [74.125.82.42]) by mx1.freebsd.org (Postfix) with ESMTP id F20BF8FC12 for ; Mon, 5 Sep 2011 07:39:56 +0000 (UTC) Received: by wwe5 with SMTP id 5so3726009wwe.1 for ; Mon, 05 Sep 2011 00:39:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=LzMjojrH5Q9N6fUI665cnzR7bpvCJx/A/Pp453K3XS8=; b=BeyvlbeucuxOsBflHMtR6Sq3IGQqA51MnPWIib8fKfYSaCeRsQitPycQwNomlAitqG 4RcDjf3jLsO4v05Rcw0ikPpGmygndAfabPymWHdmyTqtPgteJu8MyOWVRCFt9M2VUTUV vaZElad9cZXkbRPwjBgwpLnOJfHyVDMp6qVek= MIME-Version: 1.0 Received: by 10.216.200.102 with SMTP id y80mr3376772wen.38.1315206616875; Mon, 05 Sep 2011 00:10:16 -0700 (PDT) Received: by 10.216.29.65 with HTTP; Mon, 5 Sep 2011 00:10:16 -0700 (PDT) Date: Mon, 5 Sep 2011 00:10:16 -0700 Message-ID: From: Sean Hamilton To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Mailman-Approved-At: Mon, 05 Sep 2011 12:37:52 +0000 Subject: Recommended amount of swap X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Sep 2011 07:39:57 -0000 What is the state of the art for the recommended amount of swap in FreeBSD? Both "normal" systems with 512 MB - 8 GB of RAM, and large database systems with around 128 - 256 GB. Thanks in advance, -- Sean Hamilton From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 5 13:40:46 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9D626106566B for ; Mon, 5 Sep 2011 13:40:46 +0000 (UTC) (envelope-from dgre090@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 2DA858FC16 for ; Mon, 5 Sep 2011 13:40:45 +0000 (UTC) Received: by fxe4 with SMTP id 4so4600406fxe.13 for ; Mon, 05 Sep 2011 06:40:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=OVCfY4gWmF0IuXai/tJko4R6MLAglT+ZexvJLfZ/Nvc=; b=NYU7G0iFaHpQ+nUhrO8Jk1JOfOW8vJvtw2fBTgeuayGD37357UBuZV8vZOSNVrUXDQ /qengK+QnmD9K0SbY01BiTOk6YMW8P66iDaOmKiWSTXATI5TitHQ7St8h46+Ba3inCq2 rp/iOmWD3oCfEfYC8JnZdOfPIjt9MXYzRt2tM= MIME-Version: 1.0 Received: by 10.223.6.214 with SMTP id a22mr2962069faa.99.1315230044988; Mon, 05 Sep 2011 06:40:44 -0700 (PDT) Received: by 10.152.9.35 with HTTP; Mon, 5 Sep 2011 06:40:44 -0700 (PDT) Date: Mon, 5 Sep 2011 15:40:44 +0200 Message-ID: From: Daniel Grech To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Detach USB Device Driver and Attach it to ugen driver at runtime X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Sep 2011 13:40:46 -0000 Hi, I'm using libusb to gain access to raw USB Data from userspace. My problem is that this library only works with devices which are treated as generic devices ("handled by the ugen driver"). I need a mechanism that will allow me to detach any device specific drivers that are attached to a device and attach the ugen driver instead. I want to do this without re-compiling the FreeBSD Kernel. Thanks in advance for your help. From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 5 13:44:22 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E538D106564A for ; Mon, 5 Sep 2011 13:44:22 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe06.c2i.net [212.247.154.162]) by mx1.freebsd.org (Postfix) with ESMTP id 6E76A8FC20 for ; Mon, 5 Sep 2011 13:44:22 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.1 cv=MmhuielNmoAwiWCiiefMnqMoo9XwPcHPH2oGFNV1oLM= c=1 sm=1 a=SvYTsOw2Z4kA:10 a=ze3EKyZnpQUA:10 a=WQU8e4WWZSUA:10 a=8nJEP1OIZ-IA:10 a=CL8lFSKtTFcA:10 a=i9M/sDlu2rpZ9XS819oYzg==:17 a=24EVkJ6CNt3X5WJoCMUA:9 a=wPNLvfGTeEIA:10 a=gn1vydRif76bWShp:21 a=BdaDqphQex-B8GSz:21 a=i9M/sDlu2rpZ9XS819oYzg==:117 Received: from [188.126.198.129] (account mc467741@c2i.net HELO laptop002.hselasky.homeunix.org) by mailfe06.swip.net (CommuniGate Pro SMTP 5.2.19) with ESMTPA id 174542095; Mon, 05 Sep 2011 15:44:19 +0200 From: Hans Petter Selasky To: freebsd-hackers@freebsd.org Date: Mon, 5 Sep 2011 15:41:41 +0200 User-Agent: KMail/1.13.5 (FreeBSD/8.2-STABLE; KDE/4.4.5; amd64; ; ) References: In-Reply-To: X-Face: *nPdTl_}RuAI6^PVpA02T?$%Xa^>@hE0uyUIoiha$pC:9TVgl.Oq, NwSZ4V"|LR.+tj}g5 %V,x^qOs~mnU3]Gn; cQLv&.N>TrxmSFf+p6(30a/{)KUU!s}w\IhQBj}[g}bj0I3^glmC( :AuzV9:.hESm-x4h240C`9=w MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201109051541.41092.hselasky@c2i.net> Cc: Daniel Grech Subject: Re: Detach USB Device Driver and Attach it to ugen driver at runtime X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Sep 2011 13:44:23 -0000 On Monday 05 September 2011 15:40:44 Daniel Grech wrote: > Hi, I'm using libusb to gain access to raw USB Data from userspace. My > problem is that this library only works with devices which are treated as > generic devices ("handled by the ugen driver"). I need a mechanism that > will allow me to detach any device specific drivers that are attached to a > device and attach the ugen driver instead. I want to do this without > re-compiling the FreeBSD Kernel. Thanks in advance for your help. Hi, The following functions should be implemented: int libusb20_dev_detach_kernel_driver(struct libusb20_device *pdev, uint8_t iface_index); int libusb_detach_kernel_driver(libusb_device_handle *devh, int interface) or int libusb_detach_kernel_driver_np(libusb_device_handle *devh, int interface) Detach a kernel driver from an interface. This is needed to claim an interface required by a kernel driver. Returns 0 on success, LIBUSB_ERROR_NOT_FOUND if no kernel driver was active, LIBUSB_ERROR_INVALID_PARAM if the interface does not exist, LIBUSB_ERROR_NO_DEVICE if the device has been disconnected and a LIBUSB_ERROR code on failure. This function is non-portable. man libusb20 man libusb --HPS From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 5 15:25:13 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 487641065670 for ; Mon, 5 Sep 2011 15:25:13 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 25C2F8FC12 for ; Mon, 5 Sep 2011 15:25:13 +0000 (UTC) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTPS id BF92D46B38; Mon, 5 Sep 2011 11:25:12 -0400 (EDT) Date: Mon, 5 Sep 2011 16:25:12 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: petz@nisshoko.net In-Reply-To: <007301cc6979$a690f9a0$f3b2ece0$@internode.on.net> Message-ID: References: <007301cc6979$a690f9a0$f3b2ece0$@internode.on.net> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-hackers@freebsd.org Subject: Re: TIME_WAIT Assassination in FreeBSD??? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Sep 2011 15:25:13 -0000 On Sat, 3 Sep 2011, Jarrod Lee Petz wrote: > 3. Does FreeBSD handle this situation? How? I can't seem to find much info > on TIME_WAIT assassination in FreeBSD is mentioned in RFC 6056 I'm not familiar with the RFC side here, but I can confirm that FreeBSD will recycle TIMEWAIT connections more quickly than specified when load is very high. This is done on the basis of allocated space; the sysctl: net.inet.tcp.maxtcptw Instructs the stack regarding how much state to retain -- this is implemented by adjusting the allocation limit on the tcptw zone. On my system, it seems to auto-tune to about 5000 connections, a value derived from the global limit on the number of sockets on the box I'm looking at -- your mileage may vary. The resource limit case can occur in tcp_twstart(), when uma_zalloc() returns NULL on failing to allocate new TIMEWAIT state for a connection. At that point, it forces an early scan of TIMEWAIT connections (which normally happens on 2msl intervals) with a 'reuse' argument of 1, authorising premature reuse. Without too close an analysis, it appears on face value to implement LRU: we reuse storage held by the connection that has been in TIMEWAIT the longest. Robert From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 5 15:26:38 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 64901106564A for ; Mon, 5 Sep 2011 15:26:38 +0000 (UTC) (envelope-from dhartmei@insomnia.benzedrine.cx) Received: from insomnia.benzedrine.cx (106-30.3-213.fix.bluewin.ch [213.3.30.106]) by mx1.freebsd.org (Postfix) with ESMTP id CE2478FC18 for ; Mon, 5 Sep 2011 15:26:37 +0000 (UTC) Received: from insomnia.benzedrine.cx (localhost.benzedrine.cx [127.0.0.1]) by insomnia.benzedrine.cx (8.14.1/8.13.4) with ESMTP id p85FBo9r029718 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO); Mon, 5 Sep 2011 17:11:50 +0200 (MEST) Received: (from dhartmei@localhost) by insomnia.benzedrine.cx (8.14.1/8.12.10/Submit) id p85FBlvw019231; Mon, 5 Sep 2011 17:11:47 +0200 (MEST) Date: Mon, 5 Sep 2011 17:11:46 +0200 From: Daniel Hartmeier To: petz@nisshoko.net Message-ID: <20110905151146.GA10185@insomnia.benzedrine.cx> References: <007301cc6979$a690f9a0$f3b2ece0$@internode.on.net> <4E616D6E.4030903@FreeBSD.org> <001701cc69d3$aea9a0b0$0bfce210$@internode.on.net> <4E61BA37.2060204@FreeBSD.org> <20110903134634.GA55652@owl.midgard.homeip.net> <4E62B99C.6020707@FreeBSD.org> <001e01cc6a9d$8e62c870$ab285950$@internode.on.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <001e01cc6a9d$8e62c870$ab285950$@internode.on.net> User-Agent: Mutt/1.5.12-2006-07-14 Cc: freebsd-hackers@freebsd.org Subject: Re: TIME_WAIT Assassination in FreeBSD??? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Sep 2011 15:26:38 -0000 In FreeBSD, the ftp client allocates the port for an active-mode data connection by calling bind(2) with so_port set to 0, which means it lets the kernel pick a port, see http://www.freebsd.org/cgi/cvsweb.cgi/src/contrib/lukemftp/src/Attic/ftp.c?rev=1.1.1.8;content-type=text%2Fplain;hideattic=0 The kernel code where the port is picked is in function in_pcb_lport(), see http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/netinet/in_pcb.c?rev=1.281;content-type=text%2Fplain Basically, there is a range of ports (49152-65535, adjustable with sysctl), and the algorithm picks a random port within that range: if (dorandom) *lastport = first + (arc4random() % (last - first)); It checks whether that port is available. If not, it increments it by one, and tries again, etc. in a loop, until it finds one. So, for your case, it is unlikely that two subsequent bind() calls from the ftp client would result in the same port being picked randomly, unless a large part of the port range is unavailable. You can get port re-use that is quick enough to confuse pf, for instance, by opening new connections (to the same destination address and port) at a high rate, e.g. when running the Apache web server benchmark tool. But if you're simply running the ftp client on an otherwise idle host, and two subsequent bind() calls get assigned the same 'random' port, I'd say the port randomization is not working properly :) HTH, Daniel From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 5 20:16:37 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A7328106566C for ; Mon, 5 Sep 2011 20:16:37 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: from email2.allantgroup.com (email2.emsphone.com [199.67.51.116]) by mx1.freebsd.org (Postfix) with ESMTP id 6C4698FC08 for ; Mon, 5 Sep 2011 20:16:37 +0000 (UTC) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by email2.allantgroup.com (8.14.4/8.14.4) with ESMTP id p85Jmwct016629 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 5 Sep 2011 14:48:58 -0500 (CDT) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (smmsp@localhost [127.0.0.1]) by dan.emsphone.com (8.14.5/8.14.5) with ESMTP id p85JmvkM026316 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 5 Sep 2011 14:48:57 -0500 (CDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.14.5/8.14.5/Submit) id p85JmvSR026315; Mon, 5 Sep 2011 14:48:57 -0500 (CDT) (envelope-from dan) Date: Mon, 5 Sep 2011 14:48:57 -0500 From: Dan Nelson To: Sean Hamilton Message-ID: <20110905194857.GC9801@dan.emsphone.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-OS: FreeBSD 8.2-STABLE User-Agent: Mutt/1.5.21 (2010-09-15) X-Virus-Scanned: clamav-milter 0.97.2 at email2.allantgroup.com X-Virus-Status: Clean X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.6 (email2.allantgroup.com [199.67.51.78]); Mon, 05 Sep 2011 14:48:58 -0500 (CDT) X-Scanned-By: MIMEDefang 2.68 on 199.67.51.78 Cc: freebsd-hackers@freebsd.org Subject: Re: Recommended amount of swap X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Sep 2011 20:16:37 -0000 In the last episode (Sep 05), Sean Hamilton said: > What is the state of the art for the recommended amount of swap in > FreeBSD? Both "normal" systems with 512 MB - 8 GB of RAM, and large > database systems with around 128 - 256 GB. I suggest 2x RAM for systems less than 4gb or so. Anything more than 4GB of swap is probably never going to be used, and if it is used, you're just going to thrash your swap device. If you have 128GB of RAM and need to swap to disk, you desperately need more RAM, not swap :) -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 5 20:53:58 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 085EB106566C for ; Mon, 5 Sep 2011 20:53:58 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id BAC158FC14 for ; Mon, 5 Sep 2011 20:53:57 +0000 (UTC) Received: by vxh11 with SMTP id 11so5260758vxh.13 for ; Mon, 05 Sep 2011 13:53:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=PuDjUDEW+hE9yA+W0+gLMvpfXU+eDmyj5Dyb8h74/xw=; b=M/2osPYpUDRw0SqW6bP4iBFl4WiJV2yz3GXEJ76L2bcTvdeNZAtnsZzaZ1LE/1dtJ1 YRqXFJJoErA9sqLEXKgGpUBZ2XkMrvaH9ig/U75YdprtGj8jZjO2QmW8UOWVI/yasS2l mZzTrSZd/MSuBn0Hr2p0AifGCJ1h5qZT5DyOM= Received: by 10.52.187.40 with SMTP id fp8mr3075537vdc.42.1315254194273; Mon, 05 Sep 2011 13:23:14 -0700 (PDT) MIME-Version: 1.0 Received: by 10.220.180.72 with HTTP; Mon, 5 Sep 2011 13:22:44 -0700 (PDT) In-Reply-To: <20110905194857.GC9801@dan.emsphone.com> References: <20110905194857.GC9801@dan.emsphone.com> From: Eitan Adler Date: Mon, 5 Sep 2011 16:22:44 -0400 Message-ID: To: Dan Nelson Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@freebsd.org, Sean Hamilton Subject: Re: Recommended amount of swap X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Sep 2011 20:53:58 -0000 On Mon, Sep 5, 2011 at 3:48 PM, Dan Nelson wrote: > In the last episode (Sep 05), Sean Hamilton said: >> What is the state of the art for the recommended amount of swap in >> FreeBSD? Both "normal" systems with 512 MB - 8 GB of RAM, and large >> database systems with around 128 - 256 GB. Keep in mind that you need at least ram =3D swap to get a coredump. > -- > =C2=A0 =C2=A0 =C2=A0 =C2=A0Dan Nelson > =C2=A0 =C2=A0 =C2=A0 =C2=A0dnelson@allantgroup.com > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org= " > --=20 Eitan Adler From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 5 22:58:18 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 47D151065676 for ; Mon, 5 Sep 2011 22:58:18 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id CCF878FC18 for ; Mon, 5 Sep 2011 22:58:17 +0000 (UTC) Received: by wwi36 with SMTP id 36so5606896wwi.31 for ; Mon, 05 Sep 2011 15:58:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=date:from:to:subject:message-id:in-reply-to:references:x-mailer :mime-version:content-type:content-transfer-encoding; bh=FNehRoKeTfHgAf0B7i62nYOU3DGxmZkeZkyumsiS8rY=; b=AHBBeWawS7ny0mhC04gIVdZyxy3IaMljY0Cky90NtoQs90qg0BEQAcd6lAYgyh1vFG k/zY1QTttX4r9H4QOuKGCA33oHhMpKUqN6mdepXDQBwBBLBc9piL8pSiEfgDhPB7Zc+S tRaQ9UG4qdigyW2n+SwR9fXNZzh1ayfm2Eb+8= Received: by 10.227.197.195 with SMTP id el3mr4558135wbb.58.1315263496484; Mon, 05 Sep 2011 15:58:16 -0700 (PDT) Received: from gumby.homeunix.com (87-194-105-247.bethere.co.uk [87.194.105.247]) by mx.google.com with ESMTPS id gh14sm9754524wbb.17.2011.09.05.15.58.13 (version=SSLv3 cipher=OTHER); Mon, 05 Sep 2011 15:58:14 -0700 (PDT) Date: Mon, 5 Sep 2011 23:58:12 +0100 From: RW To: freebsd-hackers@freebsd.org Message-ID: <20110905235812.47d8e685@gumby.homeunix.com> In-Reply-To: <20110905194857.GC9801@dan.emsphone.com> References: <20110905194857.GC9801@dan.emsphone.com> X-Mailer: Claws Mail 3.7.10 (GTK+ 2.24.6; amd64-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: Recommended amount of swap X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Sep 2011 22:58:18 -0000 On Mon, 5 Sep 2011 14:48:57 -0500 Dan Nelson wrote: > In the last episode (Sep 05), Sean Hamilton said: > > What is the state of the art for the recommended amount of swap in > > FreeBSD? Both "normal" systems with 512 MB - 8 GB of RAM, and large > > database systems with around 128 - 256 GB. > > I suggest 2x RAM for systems less than 4gb or so. Anything more than > 4GB of swap is probably never going to be used, and if it is used, > you're just going to thrash your swap device. but tmpfs (and swap-backed md devices) can use substantial amounts of swap without contributing to thrashing. In some cases it may be possible to justify larger amounts of swap. From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 5 23:15:36 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A34BE106564A for ; Mon, 5 Sep 2011 23:15:36 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: from email2.allantgroup.com (email2.emsphone.com [199.67.51.116]) by mx1.freebsd.org (Postfix) with ESMTP id 6451A8FC0C for ; Mon, 5 Sep 2011 23:15:35 +0000 (UTC) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by email2.allantgroup.com (8.14.4/8.14.4) with ESMTP id p85NFYVV034792 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 5 Sep 2011 18:15:34 -0500 (CDT) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (smmsp@localhost [127.0.0.1]) by dan.emsphone.com (8.14.5/8.14.5) with ESMTP id p85NFY0X093587 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 5 Sep 2011 18:15:34 -0500 (CDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.14.5/8.14.5/Submit) id p85MjbY2012207; Mon, 5 Sep 2011 17:45:37 -0500 (CDT) (envelope-from dan) Date: Mon, 5 Sep 2011 17:45:37 -0500 From: Dan Nelson To: Eitan Adler Message-ID: <20110905224537.GD9801@dan.emsphone.com> References: <20110905194857.GC9801@dan.emsphone.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-OS: FreeBSD 8.2-STABLE User-Agent: Mutt/1.5.21 (2010-09-15) X-Virus-Scanned: clamav-milter 0.97.2 at email2.allantgroup.com X-Virus-Status: Clean X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.6 (email2.allantgroup.com [199.67.51.78]); Mon, 05 Sep 2011 18:15:34 -0500 (CDT) X-Scanned-By: MIMEDefang 2.68 on 199.67.51.78 Cc: freebsd-hackers@freebsd.org, Sean Hamilton Subject: Re: Recommended amount of swap X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Sep 2011 23:15:36 -0000 In the last episode (Sep 05), Eitan Adler said: > On Mon, Sep 5, 2011 at 3:48 PM, Dan Nelson wrote: > > In the last episode (Sep 05), Sean Hamilton said: > >> What is the state of the art for the recommended amount of swap in > >> FreeBSD? Both "normal" systems with 512 MB - 8 GB of RAM, and large > >> database systems with around 128 - 256 GB. > > Keep in mind that you need at least ram = swap to get a coredump. Not if debug.minidump is set to 1, which it is by default. In that case, only mapped memory gets dumped, which should ignore disk cache pages and be a lot smaller than your RAM size. Enabling ZFS may make your dumps bigger unless the minidump code is smart enough to not dump the ARC. -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 6 01:54:05 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 954D71065675 for ; Tue, 6 Sep 2011 01:54:05 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id 0FB3C8FC14 for ; Tue, 6 Sep 2011 01:54:04 +0000 (UTC) Received: from ur.gsoft.com.au (Ur.gsoft.com.au [203.31.81.44]) (authenticated bits=0) by cain.gsoft.com.au (8.14.4/8.14.3) with ESMTP id p861rsfC059650 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 6 Sep 2011 11:24:00 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Mime-Version: 1.0 (Apple Message framework v1244.3) Content-Type: text/plain; charset=iso-8859-1 From: "Daniel O'Connor" In-Reply-To: Date: Tue, 6 Sep 2011 11:23:55 +0930 Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Daniel Grech X-Mailer: Apple Mail (2.1244.3) X-Spam-Score: -4.391 () ALL_TRUSTED,BAYES_00,RP_MATCHES_RCVD X-Scanned-By: MIMEDefang 2.67 on 203.31.81.10 Cc: freebsd-hackers@freebsd.org Subject: Re: Detach USB Device Driver and Attach it to ugen driver at runtime X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Sep 2011 01:54:05 -0000 On 05/09/2011, at 23:10, Daniel Grech wrote: > Hi, I'm using libusb to gain access to raw USB Data from userspace. My > problem is that this library only works with devices which are treated = as > generic devices ("handled by the ugen driver"). I need a mechanism = that will > allow me to detach any device specific drivers that are attached to a = device > and attach the ugen driver instead. I want to do this without = re-compiling > the FreeBSD Kernel. Thanks in advance for your help. You can access the device via ugen even if a kernel driver has attached = to it. I suspect you wouldn't be able to if the kernel driver that did attach = is in use, but I am not sure. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 6 02:24:14 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B4AFE106566B for ; Tue, 6 Sep 2011 02:24:14 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (pancho.soaustin.net [76.74.250.40]) by mx1.freebsd.org (Postfix) with ESMTP id 978718FC1D for ; Tue, 6 Sep 2011 02:24:14 +0000 (UTC) Received: by mail.soaustin.net (Postfix, from userid 502) id AB8EB561B2; Mon, 5 Sep 2011 21:06:51 -0500 (CDT) Date: Mon, 5 Sep 2011 21:06:51 -0500 From: Mark Linimon To: Dan Nelson Message-ID: <20110906020651.GE13195@lonesome.com> References: <20110905194857.GC9801@dan.emsphone.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110905194857.GC9801@dan.emsphone.com> User-Agent: Mutt/1.5.20 (2009-06-14) X-Mailman-Approved-At: Tue, 06 Sep 2011 02:32:56 +0000 Cc: freebsd-hackers@freebsd.org, Sean Hamilton Subject: Re: Recommended amount of swap X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Sep 2011 02:24:14 -0000 On Mon, Sep 05, 2011 at 02:48:57PM -0500, Dan Nelson wrote: > I suggest 2x RAM for systems less than 4gb or so. Anything more than 4GB of > swap is probably never going to be used I see you don't do mass package builds :-) Or, even build openoffice or some of the math packages. > and if it is used, you're just going to thrash your swap device. That's us! :-) mcl From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 6 07:15:24 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9FA6F106566B for ; Tue, 6 Sep 2011 07:15:24 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe03.c2i.net [212.247.154.66]) by mx1.freebsd.org (Postfix) with ESMTP id 23EB68FC12 for ; Tue, 6 Sep 2011 07:15:23 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.1 cv=yVKV3zusvCapyMfYJBNW2j35FMEuTKq6vh/tt/1L5+g= c=1 sm=1 a=SvYTsOw2Z4kA:10 a=ze3EKyZnpQUA:10 a=WQU8e4WWZSUA:10 a=8nJEP1OIZ-IA:10 a=CL8lFSKtTFcA:10 a=i9M/sDlu2rpZ9XS819oYzg==:17 a=xF7t-OYbmS5wLagobAoA:9 a=wPNLvfGTeEIA:10 a=i9M/sDlu2rpZ9XS819oYzg==:117 Received: from [188.126.198.129] (account mc467741@c2i.net HELO laptop002.hselasky.homeunix.org) by mailfe03.swip.net (CommuniGate Pro SMTP 5.2.19) with ESMTPA id 7981201; Tue, 06 Sep 2011 09:11:58 +0200 From: Hans Petter Selasky To: freebsd-hackers@freebsd.org Date: Tue, 6 Sep 2011 09:09:18 +0200 User-Agent: KMail/1.13.5 (FreeBSD/8.2-STABLE; KDE/4.4.5; amd64; ; ) References: In-Reply-To: X-Face: *nPdTl_}RuAI6^PVpA02T?$%Xa^>@hE0uyUIoiha$pC:9TVgl.Oq, NwSZ4V"|LR.+tj}g5 %V,x^qOs~mnU3]Gn; cQLv&.N>TrxmSFf+p6(30a/{)KUU!s}w\IhQBj}[g}bj0I3^glmC( :AuzV9:.hESm-x4h240C`9=w MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201109060909.18300.hselasky@c2i.net> Cc: Daniel Grech Subject: Re: Detach USB Device Driver and Attach it to ugen driver at runtime X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Sep 2011 07:15:24 -0000 On Tuesday 06 September 2011 03:53:55 Daniel O'Connor wrote: > On 05/09/2011, at 23:10, Daniel Grech wrote: > > Hi, I'm using libusb to gain access to raw USB Data from userspace. My > > problem is that this library only works with devices which are treated as > > generic devices ("handled by the ugen driver"). I need a mechanism that > > will allow me to detach any device specific drivers that are attached to > > a device and attach the ugen driver instead. I want to do this without > > re-compiling the FreeBSD Kernel. Thanks in advance for your help. > > You can access the device via ugen even if a kernel driver has attached to > it. > > I suspect you wouldn't be able to if the kernel driver that did attach is > in use, but I am not sure. You can attach even if a kernel driver is attached, though it is best to only have one driver attached at the same time. --HPS From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 6 18:46:02 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EFFDD106566B for ; Tue, 6 Sep 2011 18:46:02 +0000 (UTC) (envelope-from c.kworr@gmail.com) Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by mx1.freebsd.org (Postfix) with ESMTP id 7BBAA8FC15 for ; Tue, 6 Sep 2011 18:46:02 +0000 (UTC) Received: by eye4 with SMTP id 4so4003152eye.31 for ; Tue, 06 Sep 2011 11:46:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=iBLnrpOez55hPO0oJBAHyLY40t1VPWyrUWYhjf4/js8=; b=xplE28mB4hfd2pECki/9fft448x39EsvtpzWe4b8+uHTgjFvrpiekWCTfLdLlveIPu j3U7ADeQ7evUa2DI1UKt5MjRCQQmIpMsgvgfs+ykpNnoe5ytZTikbqpV6M+KtRCrzt5K Jh0FBPjOJul1rzSQ0Ov29v0g/RdxGKD50hn/Q= Received: by 10.213.8.80 with SMTP id g16mr1496532ebg.74.1315332937976; Tue, 06 Sep 2011 11:15:37 -0700 (PDT) Received: from limbo.lan ([195.225.157.86]) by mx.google.com with ESMTPS id e4sm1568499eec.10.2011.09.06.11.15.36 (version=SSLv3 cipher=OTHER); Tue, 06 Sep 2011 11:15:37 -0700 (PDT) Message-ID: <4E666347.5010603@gmail.com> Date: Tue, 06 Sep 2011 21:15:35 +0300 From: Volodymyr Kostyrko User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:6.0.1) Gecko/20110902 Thunderbird/6.0.1 MIME-Version: 1.0 To: Sean Hamilton References: <20110905194857.GC9801@dan.emsphone.com> In-Reply-To: <20110905194857.GC9801@dan.emsphone.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-hackers@freebsd.org Subject: Re: Recommended amount of swap X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Sep 2011 18:46:03 -0000 05.09.2011 22:48, Dan Nelson написав(ла): > In the last episode (Sep 05), Sean Hamilton said: >> What is the state of the art for the recommended amount of swap in >> FreeBSD? Both "normal" systems with 512 MB - 8 GB of RAM, and large >> database systems with around 128 - 256 GB. > > I suggest 2x RAM for systems less than 4gb or so. Anything more than 4GB of > swap is probably never going to be used, and if it is used, you're just > going to thrash your swap device. If you have 128GB of RAM and need to swap > to disk, you desperately need more RAM, not swap :) My +1 to wishlist, I want OpenOffice to not trash memory when reading large xlsx files. Mem: 1937M Active, 243M Inact, 672M Wired, 98M Cache, 9412K Free Swap: 36G Total, 21G Used, 15G Free, 59% Inuse, 252K In PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND 1912 arcade 5 45 1 23311M 1721M ucond 0 66:07 55.37% /usr/local/openoffice.org-3.3.0/openoffice.org3/program/so Different things happens. When I hardly need some swap I think about: 0. More RAM. 1. Spare flash or SSD. 2. Another disk. 3. Touching disk sizes. Also please note that system that uses at least 1G of swap actively (I don't mean tmp/mdfs or long running non active processes) is dripping slime and therefor is useless and should be upgraded. -- Sphinx of black quartz judge my vow. From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 6 22:01:15 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1233) id 647351065672; Tue, 6 Sep 2011 22:01:15 +0000 (UTC) Date: Tue, 6 Sep 2011 22:01:15 +0000 From: Alexander Best To: freebsd-hackers@freebsd.org Message-ID: <20110906220115.GA25048@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: excessive use of gettimeofday(2) and other syscalls X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Sep 2011 22:01:15 -0000 hi there, in a recent discussion on current@ [1], it was discovered that chromium makes excessive use of gettimeofday(2). while searching google, i found other software that is/was having the same issue [2]. although this is a programming error, it would still be nice, if freebsd could issue a warning in cases like these. would it be possible to instruct freebsd to issue a warning, when a process issues a certain amount of syscalls per second (maybe tuneable via sysctl)? while calling gettimeofday(2) excessively isn't causing any harm, it triggers a lot of context switches and reduces performance. having such warnings in place could help a user identify such a process without having to use debugging tools, such as ktrace or dtrace. cheers. alex [1] http://www.mail-archive.com/freebsd-current@freebsd.org/msg131040.html [1] https://forum.transmissionbt.com/viewtopic.php?f=2&t=11687 From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 6 23:07:05 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 07D2E1065675; Tue, 6 Sep 2011 23:07:05 +0000 (UTC) (envelope-from manishv@lineratesystems.com) Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by mx1.freebsd.org (Postfix) with ESMTP id B12A08FC08; Tue, 6 Sep 2011 23:07:04 +0000 (UTC) Received: by ywa17 with SMTP id 17so1018882ywa.13 for ; Tue, 06 Sep 2011 16:07:03 -0700 (PDT) MIME-Version: 1.0 Received: by 10.42.145.197 with SMTP id g5mr2954412icv.348.1315349088899; Tue, 06 Sep 2011 15:44:48 -0700 (PDT) Received: by 10.42.19.196 with HTTP; Tue, 6 Sep 2011 15:44:48 -0700 (PDT) In-Reply-To: <20110906220115.GA25048@freebsd.org> References: <20110906220115.GA25048@freebsd.org> Date: Tue, 6 Sep 2011 16:44:48 -0600 Message-ID: From: Manish Vachharajani To: Alexander Best Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-hackers@freebsd.org Subject: Re: excessive use of gettimeofday(2) and other syscalls X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Sep 2011 23:07:05 -0000 Under 7.3 (haven't checked 8 or 9) this issue crops up because the time system call calls gettimeofday under the hood (see lib/libc/gen/time.c). As a result, the kernel tries to get an accurate subsecond resolution time that simply gets chopped to the nearest second. Lots of libraries assume that time is fast because it is fast under Linux. Every instance where I have seen this as a performance issue, the call has been to time not a direct call to gettimeofday. The latest openssl (not the one from FreeBSD, but the one from openssl.org has this issue for example. Manish On Tue, Sep 6, 2011 at 4:01 PM, Alexander Best wrote: > hi there, > > in a recent discussion on current@ [1], it was discovered that chromium makes > excessive use of gettimeofday(2). while searching google, i found other > software that is/was having the same issue [2]. although this is a programming > error, it would still be nice, if freebsd could issue a warning in cases like > these. would it be possible to instruct freebsd to issue a warning, when a > process issues a certain amount of syscalls per second (maybe tuneable via > sysctl)? > > while calling gettimeofday(2) excessively isn't causing any harm, it triggers > a lot of context switches and reduces performance. having such warnings in > place could help a user identify such a process without having to use debugging > tools, such as ktrace or dtrace. > > cheers. > alex > > [1] http://www.mail-archive.com/freebsd-current@freebsd.org/msg131040.html > [1] https://forum.transmissionbt.com/viewtopic.php?f=2&t=11687 > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > -- Manish Vachharajani Founder LineRate Systems manishv@lineratesystems.com (609)635-9531 M From owner-freebsd-hackers@FreeBSD.ORG Wed Sep 7 00:41:56 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AE8E91065670 for ; Wed, 7 Sep 2011 00:41:56 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by mx1.freebsd.org (Postfix) with ESMTP id 1EEE58FC08 for ; Wed, 7 Sep 2011 00:41:55 +0000 (UTC) Received: by vws12 with SMTP id 12so8360883vws.17 for ; Tue, 06 Sep 2011 17:41:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=hqHUsODDLve7hiFrH/hzw1SvTJOnHFPJzTqJJ2ExXPQ=; b=W0KNkpeIRzUKT9eoYKZTzvuNzYmGbXoVDlu6FLR6oXW6ahqj2uV1vNFs7/c8+Cuxbz /JaYWF2r1CJgOakofaYdyLC3xCboThGvjJ993uizjTBS6iD3tPoyA8wic0Nj2FcDx3qb lbshKO3M2JELGnnHxHdGjGOohTPsFFyTodNR8= Received: by 10.52.187.40 with SMTP id fp8mr4491726vdc.42.1315356115071; Tue, 06 Sep 2011 17:41:55 -0700 (PDT) MIME-Version: 1.0 Received: by 10.220.180.72 with HTTP; Tue, 6 Sep 2011 17:41:25 -0700 (PDT) In-Reply-To: References: <20110906220115.GA25048@freebsd.org> From: Eitan Adler Date: Tue, 6 Sep 2011 20:41:25 -0400 Message-ID: To: Manish Vachharajani Content-Type: text/plain; charset=UTF-8 Cc: Alexander Best , freebsd-hackers@freebsd.org Subject: Re: excessive use of gettimeofday(2) and other syscalls X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Sep 2011 00:41:56 -0000 On Tue, Sep 6, 2011 at 6:44 PM, Manish Vachharajani wrote: > Lots of libraries assume that time is fast because it > is fast under Linux. Silly question, but why can't we make it fast too? -- Eitan Adler From owner-freebsd-hackers@FreeBSD.ORG Wed Sep 7 00:49:03 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 507D51065782; Wed, 7 Sep 2011 00:49:03 +0000 (UTC) (envelope-from manishv@lineratesystems.com) Received: from mail-yi0-f54.google.com (mail-yi0-f54.google.com [209.85.218.54]) by mx1.freebsd.org (Postfix) with ESMTP id 05AA28FC0C; Wed, 7 Sep 2011 00:49:02 +0000 (UTC) Received: by yib19 with SMTP id 19so5310947yib.13 for ; Tue, 06 Sep 2011 17:49:02 -0700 (PDT) MIME-Version: 1.0 Received: by 10.42.145.197 with SMTP id g5mr2987565icv.348.1315356541950; Tue, 06 Sep 2011 17:49:01 -0700 (PDT) Received: by 10.42.19.196 with HTTP; Tue, 6 Sep 2011 17:49:01 -0700 (PDT) In-Reply-To: References: <20110906220115.GA25048@freebsd.org> Date: Tue, 6 Sep 2011 18:49:01 -0600 Message-ID: From: Manish Vachharajani To: Eitan Adler Content-Type: text/plain; charset=ISO-8859-1 Cc: Alexander Best , freebsd-hackers@freebsd.org Subject: Re: excessive use of gettimeofday(2) and other syscalls X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Sep 2011 00:49:03 -0000 I believe that Linux uses a less precise clock that scales better across cores and is much faster than the precise clock FreeBSD uses even on one core. I don't know POSIX and other standards well enough to know if this is an acceptable solution on FreeBSD. However, there are less precise clocks on FreeBSD that are considerably faster (i.e., the _FAST variants). Someone with more expertise in these matters needs to comment on whether a change to using a _FAST clock is appropriate in libc. If it is acceptable, I think that it is easier to just make time use the FAST clock instead of getting programmers to change their programs. On Tue, Sep 6, 2011 at 6:41 PM, Eitan Adler wrote: > On Tue, Sep 6, 2011 at 6:44 PM, Manish Vachharajani > wrote: >> Lots of libraries assume that time is fast because it >> is fast under Linux. > > Silly question, but why can't we make it fast too? > > -- > Eitan Adler > Manish From owner-freebsd-hackers@FreeBSD.ORG Wed Sep 7 01:21:56 2011 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EC11B1065740 for ; Wed, 7 Sep 2011 01:21:56 +0000 (UTC) (envelope-from stephen.hocking@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 833278FC13 for ; Wed, 7 Sep 2011 01:21:56 +0000 (UTC) Received: by wwi36 with SMTP id 36so6962799wwi.31 for ; Tue, 06 Sep 2011 18:21:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=6xxBtTOwxKI/MKq1Ak6p0gDzqQC3SGxs4efYqtp4c9c=; b=TYY/Mpu2ebtTUS/N9y1kpxCwnpgMA68O5x/xWS79SLIWaQ9jpwWiLEAXiixyHJKruB eV6z0iZEYJCkXcSRoBtdPg/qBOLXI3ZKNoYKEaFvmlO01+9ytx6LuBjy4Ebf4B57s+Fr xTtjPGxj8GXETWShtWdNupERKzFsB1uV3Mmlk= MIME-Version: 1.0 Received: by 10.216.190.40 with SMTP id d40mr5689588wen.25.1315356628449; Tue, 06 Sep 2011 17:50:28 -0700 (PDT) Received: by 10.216.170.135 with HTTP; Tue, 6 Sep 2011 17:50:28 -0700 (PDT) Date: Wed, 7 Sep 2011 10:50:28 +1000 Message-ID: From: Stephen Hocking To: hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: Subject: VMWare/Virtualbox virtio network drivers? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Sep 2011 01:21:57 -0000 Hi all, Am wondering if anyone has done drivers the these sorts of network interfaces that are offered by VMWare & Virtual box. I know that on some Linux VMs I run, performance went from 20MB/s to 30MB/s to an NFS server which I swicthed to the virtio network interfaces. Stephen From owner-freebsd-hackers@FreeBSD.ORG Wed Sep 7 01:44:39 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8254F106564A for ; Wed, 7 Sep 2011 01:44:39 +0000 (UTC) (envelope-from raysonlogin@gmail.com) Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com [209.85.213.182]) by mx1.freebsd.org (Postfix) with ESMTP id 40DD88FC15 for ; Wed, 7 Sep 2011 01:44:38 +0000 (UTC) Received: by yxn22 with SMTP id 22so4039280yxn.13 for ; Tue, 06 Sep 2011 18:44:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=w3O7rqZ/7Ff+HKIcDXhPLbRHxYvyy6dfWak+1f376dQ=; b=il1q/jpRs1f4uoWvuJeWQXFwONVWo/UsTB+5b3dZD6SRfsLV4CzlGFXkRQ3IG7sAss QklsJV+gafMFJzHABP80e7tppWeRzCpZ8v3YQvwb9iaFLHbUJNATilgEwZBfiS/sR8cF 0crcLpBNaZvdSAy+QJOxpZqFPbjew6dZ6/bK0= MIME-Version: 1.0 Received: by 10.68.29.228 with SMTP id n4mr9258597pbh.380.1315358155575; Tue, 06 Sep 2011 18:15:55 -0700 (PDT) Received: by 10.143.42.19 with HTTP; Tue, 6 Sep 2011 18:15:55 -0700 (PDT) In-Reply-To: References: <20110906220115.GA25048@freebsd.org> Date: Tue, 6 Sep 2011 21:15:55 -0400 Message-ID: From: Rayson Ho To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: excessive use of gettimeofday(2) and other syscalls X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Sep 2011 01:44:39 -0000 There are some recent discussions on the freebsd-current list. The infrastructure is there to provide a common shared page for processes to mmap into the address space... but according to Kip's comment, libc support is not there yet: http://lists.freebsd.org/pipermail/freebsd-current/2011-June/025191.html Also, the kernel needs to update the variable in that shared page on each clock interrupt (depending on the resolution I believe), and I think that needs to be added too. IMO, the time returned by gettimeofday does not need to be high precision. There are higher resolution time APIs on Linux and I believe the application programmers know when to use the slower but more accurate clock API. (At least in Grid Engine we only need a quick way of getting the current time, and we don't care if it is precise to the nanosecond range.) See Linux security issue & solution: http://lwn.net/Articles/446528/ See also the Google SoC idea: http://wiki.freebsd.org/IdeasPage#Timecounter_Performance_Improvements_.28G= SoC.29 Rayson =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D Grid Engine / Open Grid Scheduler http://gridscheduler.sourceforge.net On Tue, Sep 6, 2011 at 8:49 PM, Manish Vachharajani wrote: > I believe that Linux uses a less precise clock that scales better > across cores and is much faster than the precise clock FreeBSD uses > even on one core. =A0I don't know POSIX and other standards well enough > to know if this is an acceptable solution on FreeBSD. =A0However, there > are less precise clocks on FreeBSD that are considerably faster (i.e., > the _FAST variants). =A0Someone with more expertise in these matters > needs to comment on whether a change to using a _FAST clock is > appropriate in libc. =A0If it is acceptable, I think that it is easier > to just make time use the FAST clock instead of getting programmers to > change their programs. > > On Tue, Sep 6, 2011 at 6:41 PM, Eitan Adler wrote: >> On Tue, Sep 6, 2011 at 6:44 PM, Manish Vachharajani >> wrote: >>> Lots of libraries assume that time is fast because it >>> is fast under Linux. >> >> Silly question, but why can't we make it fast too? >> >> -- >> Eitan Adler >> > > Manish > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org= " > --=20 Rayson =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Open Grid Scheduler - The Official Open Source Grid Engine http://gridscheduler.sourceforge.net/ From owner-freebsd-hackers@FreeBSD.ORG Wed Sep 7 01:58:58 2011 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C00AF1065670 for ; Wed, 7 Sep 2011 01:58:58 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 4D4698FC0C for ; Wed, 7 Sep 2011 01:58:57 +0000 (UTC) Received: by fxe4 with SMTP id 4so235498fxe.13 for ; Tue, 06 Sep 2011 18:58:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=NA3glR0gU7m1Y9WWHlF0LjzvcCsTJCE/+F4HvSHyReE=; b=IIdujxzhcn6SxWNBlgnNBuNohztlnglpyLNpztfP04IK940+okOEagxjeL2D6g5XxA LKx5HqNoI7q5TJXC/QkeuCwxdEGVI8Z640vpyVxTyzY6WerYghPEG8QcZIxT/QiRscpu DkrWeXp7HIbOXejptel4qTO5seg7d2JdK5xUw= MIME-Version: 1.0 Received: by 10.223.71.155 with SMTP id h27mr197294faj.126.1315359128610; Tue, 06 Sep 2011 18:32:08 -0700 (PDT) Received: by 10.223.120.72 with HTTP; Tue, 6 Sep 2011 18:32:08 -0700 (PDT) In-Reply-To: References: Date: Tue, 6 Sep 2011 20:32:08 -0500 Message-ID: From: Adam Vande More To: Stephen Hocking Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: hackers@freebsd.org Subject: Re: VMWare/Virtualbox virtio network drivers? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Sep 2011 01:58:58 -0000 On Tue, Sep 6, 2011 at 7:50 PM, Stephen Hocking wrote: > Am wondering if anyone has done drivers the these sorts of network > interfaces that are offered by VMWare & Virtual box. I know that on > some Linux VMs I run, performance went from 20MB/s to 30MB/s to an NFS > server which I swicthed to the virtio network interfaces. > There is this patch, but it didn't get committed for some reason. http://lists.freebsd.org/pipermail/freebsd-current/2011-January/022036.html -- Adam Vande More From owner-freebsd-hackers@FreeBSD.ORG Wed Sep 7 02:09:26 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9EE36106566B for ; Wed, 7 Sep 2011 02:09:26 +0000 (UTC) (envelope-from manishv@lineratesystems.com) Received: from mail-gw0-f49.google.com (mail-gw0-f49.google.com [74.125.83.49]) by mx1.freebsd.org (Postfix) with ESMTP id 630988FC0C for ; Wed, 7 Sep 2011 02:09:26 +0000 (UTC) Received: by gwb1 with SMTP id 1so4289941gwb.36 for ; Tue, 06 Sep 2011 19:09:25 -0700 (PDT) MIME-Version: 1.0 Received: by 10.43.53.68 with SMTP id vp4mr5136036icb.80.1315361365391; Tue, 06 Sep 2011 19:09:25 -0700 (PDT) Received: by 10.42.19.196 with HTTP; Tue, 6 Sep 2011 19:09:25 -0700 (PDT) In-Reply-To: References: <20110906220115.GA25048@freebsd.org> Date: Tue, 6 Sep 2011 20:09:25 -0600 Message-ID: From: Manish Vachharajani To: Rayson Ho Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-hackers@freebsd.org Subject: Re: excessive use of gettimeofday(2) and other syscalls X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Sep 2011 02:09:26 -0000 On Tue, Sep 6, 2011 at 7:15 PM, Rayson Ho wrote: > There are some recent discussions on the freebsd-current list. The > infrastructure is there to provide a common shared page for processes > to mmap into the address space... but according to Kip's comment, libc > support is not there yet: > > http://lists.freebsd.org/pipermail/freebsd-current/2011-June/025191.html > > Also, the kernel needs to update the variable in that shared page on > each clock interrupt (depending on the resolution I believe), and I > think that needs to be added too. This would address the system call overhead but this isn't even close to the bulk of the cost. Here is data for the average time for a call using various clocks (via clock_gettime) and gettimeofday. This is for a single process on a Xeon 5654 (2.4 GHz) machine running FreeBSD 7.3 for amd64. As you can see the system call cost is not the main issue as the _FAST calls complete at 7.7 million calls per second in a single process. CLOCK_MONOTONIC: 848716 per second CLOCK_MONOTONIC_FAST: 7.73687e+06 per second CLOCK_MONOTONIC_PRECISE: 848744 per second CLOCK_REALTIME: 850795 per second CLOCK_REALTIME_FAST: 7.81742e+06 per second CLOCK_REALTIME_PRECISE: 849574 per second CLOCK_UPTIME: 848736 per second CLOCK_UPTIME_FAST: 7.84147e+06 per second CLOCK_UPTIME_PRECISE(1 ways): 848637 per second gettimeofday: 848637 per second > IMO, the time returned by gettimeofday does not need to be high > precision. There are higher resolution time APIs on Linux and I > believe the application programmers know when to use the slower but > more accurate clock API. (At least in Grid Engine we only need a quick > way of getting the current time, and we don't care if it is precise to > the nanosecond range.) Indeed, time only returns time in seconds so precision per se is unnecessary. The question is are there any strange behaviors across cores that lead to incorrect behavior if the _FAST timers are used. That is the question . For example, is it possible (and if possible, ok) for a process to call time() and get 946,000,001, then get scheduled to another cpu, and then make another call to time and get 946,000,000, making it look like time has gone backwards. I don't think standard timers allow for this to happen but the _FAST timers may (I'm just not sure), especially on an overloaded VM where the kernel could be scheduled out for longer than a tick. > See Linux security issue & solution: http://lwn.net/Articles/446528/ > See also the Google SoC idea: > http://wiki.freebsd.org/IdeasPage#Timecounter_Performance_Improvements_.28GSoC.29 > > Rayson > > ================================= > Grid Engine / Open Grid Scheduler > http://gridscheduler.sourceforge.net > > Manish From owner-freebsd-hackers@FreeBSD.ORG Wed Sep 7 03:26:59 2011 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 11E5D106566C for ; Wed, 7 Sep 2011 03:26:59 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-yi0-f54.google.com (mail-yi0-f54.google.com [209.85.218.54]) by mx1.freebsd.org (Postfix) with ESMTP id C319E8FC17 for ; Wed, 7 Sep 2011 03:26:58 +0000 (UTC) Received: by yib19 with SMTP id 19so5409691yib.13 for ; Tue, 06 Sep 2011 20:26:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=gvvb33Hq9doNL4I1ndW6Xd6J+giXCmgN15IX99IrZOQ=; b=rm/Cvbj+jSu5e576kVdg6akeeRGpKic8HgWsV4FVj5j+MeY1yKb3ADLfYxunwm0bSt OhJbmYpbA6GfFnOVJ9lPr1ZZlaOQVJOfh+L5az8/ekAQ9sdAAqnWvtMD3qVGj6Fh/rCj W92QHCyhOT8phE3B7wMJJJmh7oNR+pzUn7VrE= MIME-Version: 1.0 Received: by 10.236.37.230 with SMTP id y66mr19052833yha.10.1315364611434; Tue, 06 Sep 2011 20:03:31 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.236.103.6 with HTTP; Tue, 6 Sep 2011 20:03:31 -0700 (PDT) In-Reply-To: References: Date: Wed, 7 Sep 2011 11:03:31 +0800 X-Google-Sender-Auth: tS1d-qX03T9lP-oT3r8l2RsVi14 Message-ID: From: Adrian Chadd To: Adam Vande More Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Stephen Hocking , hackers@freebsd.org Subject: Re: VMWare/Virtualbox virtio network drivers? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Sep 2011 03:26:59 -0000 On 7 September 2011 09:32, Adam Vande More wrote: > On Tue, Sep 6, 2011 at 7:50 PM, Stephen Hocking > wrote: > >> Am wondering if anyone has done drivers the these sorts of =A0network >> interfaces that are offered by VMWare & Virtual box. I know that on >> some Linux VMs I run, performance went from 20MB/s to 30MB/s to an NFS >> server which I swicthed to the virtio network interfaces. >> > > There is this patch, but it didn't get committed for some reason. > > http://lists.freebsd.org/pipermail/freebsd-current/2011-January/022036.ht= ml Has this been used/tested by others? I see a reply from you. Adrian From owner-freebsd-hackers@FreeBSD.ORG Wed Sep 7 06:17:45 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D4DB61065676 for ; Wed, 7 Sep 2011 06:17:45 +0000 (UTC) (envelope-from peterjeremy@acm.org) Received: from mail27.syd.optusnet.com.au (mail27.syd.optusnet.com.au [211.29.133.168]) by mx1.freebsd.org (Postfix) with ESMTP id 60A3A8FC15 for ; Wed, 7 Sep 2011 06:17:45 +0000 (UTC) Received: from server.vk2pj.dyndns.org (c220-239-116-103.belrs4.nsw.optusnet.com.au [220.239.116.103]) by mail27.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id p876HgkU020730 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 7 Sep 2011 16:17:43 +1000 X-Bogosity: Ham, spamicity=0.000000 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.4/8.14.4) with ESMTP id p876HfFu030747 for ; Wed, 7 Sep 2011 16:17:41 +1000 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.4/8.14.4/Submit) id p876Hf19030746 for freebsd-hackers@freebsd.org; Wed, 7 Sep 2011 16:17:41 +1000 (EST) (envelope-from peter) Date: Wed, 7 Sep 2011 16:17:41 +1000 From: Peter Jeremy To: freebsd-hackers@freebsd.org Message-ID: <20110907061741.GC96277@server.vk2pj.dyndns.org> References: <20110906220115.GA25048@freebsd.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="24zk1gE8NUlDmwG9" Content-Disposition: inline In-Reply-To: X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: excessive use of gettimeofday(2) and other syscalls X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Sep 2011 06:17:45 -0000 --24zk1gE8NUlDmwG9 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2011-Sep-06 16:44:48 -0600, Manish Vachharajani wrote: >Under 7.3 (haven't checked 8 or 9) this issue crops up because the >time system call calls gettimeofday under the hood (see >lib/libc/gen/time.c). As a result, the kernel tries to get an >accurate subsecond resolution time that simply gets chopped to the >nearest second. Under 8.x and later, time(3) uses clock_gettime(CLOCK_SECOND,...) rather than gettimeofday(). This is intended to be much cheaper than gettimeofday(). On 2011-Sep-06 21:15:55 -0400, Rayson Ho wrote: >IMO, the time returned by gettimeofday does not need to be high >precision. There are higher resolution time APIs on Linux and I >believe the application programmers know when to use the slower but >more accurate clock API. There are 3 standard APIs for returning time of day: time(3) provides second precision gettimeofday(2) provides microsecond precision clock_gettime(2) provides nanosecond precision By default, FreeBSD attempts to provide resolution as close as possible to the precision - which makes the 2 system calls fairly expensive. In order to reduce the cost where the resolution isn't important, FreeBSD provides several non-standard clock types for clock_gettime(2). This approach differs from Linux - and it seems that there is a non-trivial body of code that assumes that calling gettimeofday() is very cheap. There is probably a good case for an API that provides a resolution of the order of a tick but there is no standard for this. --=20 Peter Jeremy --24zk1gE8NUlDmwG9 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEARECAAYFAk5nDIUACgkQ/opHv/APuIduQQCggDolZcIxgmfW1vJz/75czqM/ r9gAni6p+QQ8d+mRGkOEQaaqowuNxURU =e7EY -----END PGP SIGNATURE----- --24zk1gE8NUlDmwG9-- From owner-freebsd-hackers@FreeBSD.ORG Wed Sep 7 07:54:38 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 12FDF106566C; Wed, 7 Sep 2011 07:54:38 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) by mx1.freebsd.org (Postfix) with ESMTP id 65D738FC19; Wed, 7 Sep 2011 07:54:37 +0000 (UTC) Received: from julian-mac.elischer.org (home-nat.elischer.org [67.100.89.137]) (authenticated bits=0) by vps1.elischer.org (8.14.4/8.14.4) with ESMTP id p877HMWC098605 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 7 Sep 2011 00:17:25 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <4E671A9D.2030902@freebsd.org> Date: Wed, 07 Sep 2011 00:17:49 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US; rv:1.9.2.21) Gecko/20110830 Thunderbird/3.1.13 MIME-Version: 1.0 To: Vlad Galu References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, "Bjoern A. Zeeb" , "Alexander V. Chernikov" , freebsd-net@freebsd.org Subject: Re: FIB separation X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Sep 2011 07:54:38 -0000 On 7/16/11 5:43 AM, Vlad Galu wrote: > Hello, > > A couple of years ago, Stef Walter proposed a patch[1] that enforced the scope of routing messages. The general consesus was that the best approach would be the OpenBSD way - transporting the FIB number in the message and letting the user applications filter out unwanted messages. > > Are there any plans to tackle this before 9.0? I haven't really been following this unfortunately but I see at least part got done. (ifconfig) is there anything we need to do before 9.0 that is small but would make a big difference? (i.e. fixes, tweaks) Julian One thing that I haven't done and I only recently remembered, was the ability to have a socket inherit it's fib from the incoming connection SYN instead of from the socket opening process. (at least I am pretty sure I never got that done. (must go check)). > Thanks, > Vlad > > [1] http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/134931_______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://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 Sep 7 06:24:37 2011 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C1C04106566B; Wed, 7 Sep 2011 06:24:37 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) by mx1.freebsd.org (Postfix) with ESMTP id 7CF478FC17; Wed, 7 Sep 2011 06:24:37 +0000 (UTC) Received: from julian-mac.elischer.org (home-nat.elischer.org [67.100.89.137]) (authenticated bits=0) by vps1.elischer.org (8.14.4/8.14.4) with ESMTP id p8768DlE098326 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 6 Sep 2011 23:08:14 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <4E670A67.5030505@freebsd.org> Date: Tue, 06 Sep 2011 23:08:39 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US; rv:1.9.2.21) Gecko/20110830 Thunderbird/3.1.13 MIME-Version: 1.0 To: Adrian Chadd References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Wed, 07 Sep 2011 11:18:34 +0000 Cc: Stephen Hocking , Adam Vande More , virtualization@freebsd.org Subject: Re: VMWare/Virtualbox virtio network drivers? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Sep 2011 06:24:37 -0000 On 9/6/11 8:03 PM, Adrian Chadd wrote: > On 7 September 2011 09:32, Adam Vande More wrote: >> On Tue, Sep 6, 2011 at 7:50 PM, Stephen Hocking >> wrote: >> >>> Am wondering if anyone has done drivers the these sorts of network >>> interfaces that are offered by VMWare& Virtual box. I know that on >>> some Linux VMs I run, performance went from 20MB/s to 30MB/s to an NFS >>> server which I swicthed to the virtio network interfaces. >>> >> There is this patch, but it didn't get committed for some reason. >> >> http://lists.freebsd.org/pipermail/freebsd-current/2011-January/022036.html > Has this been used/tested by others? I see a reply from you. The BHyve guys are implementing virtio drivers and have looked at both these drivers and others. I don't know what their plans are.. you should send to virtualization@freebsd.org (cc'd and redirected) to get up to date info. > > > Adrian > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://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 Sep 7 13:42:02 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A97EF106564A; Wed, 7 Sep 2011 13:42:02 +0000 (UTC) (envelope-from melifaro@ipfw.ru) Received: from mail.ipfw.ru (unknown [IPv6:2a01:4f8:120:6141::2]) by mx1.freebsd.org (Postfix) with ESMTP id 4605B8FC12; Wed, 7 Sep 2011 13:42:02 +0000 (UTC) Received: from dhcp170-36-red.yandex.net ([95.108.170.36]) by mail.ipfw.ru with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.76 (FreeBSD)) (envelope-from ) id 1R1IO7-0001Uv-RC; Wed, 07 Sep 2011 17:41:59 +0400 Message-ID: <4E677479.5040903@ipfw.ru> Date: Wed, 07 Sep 2011 17:41:13 +0400 From: "Alexander V. Chernikov" User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.16) Gecko/20110120 Thunderbird/3.0.11 MIME-Version: 1.0 To: Julian Elischer References: <4E671A9D.2030902@freebsd.org> In-Reply-To: <4E671A9D.2030902@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, "Bjoern A. Zeeb" , Vlad Galu , freebsd-net@freebsd.org Subject: Re: FIB separation X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Sep 2011 13:42:02 -0000 On 07.09.2011 11:17, Julian Elischer wrote: > On 7/16/11 5:43 AM, Vlad Galu wrote: >> Hello, >> Hello! >> A couple of years ago, Stef Walter proposed a patch[1] that enforced >> the scope of routing messages. The general consesus was that the best >> approach would be the OpenBSD way - transporting the FIB number in the >> message and letting the user applications filter out unwanted messages. >> >> Are there any plans to tackle this before 9.0? > > I haven't really been following this unfortunately but I see at least > part got done. (ifconfig) Yes, it is committed as r223735 and r223741. Unfortunately this is not (directly) related to routing socket. kern/134931 still remains as it is. > > is there anything we need to do before 9.0 that is small but would make > a big difference? > (i.e. fixes, tweaks) rtsock is a great candidate :) > > Julian > > One thing that I haven't done and I only recently remembered, was the > ability to have a socket inherit > it's fib from the incoming connection SYN instead of from the socket > opening process. It is a very good idea to have such possibility but it has to be controlled at least by some sort of sysctl or even per-socket ioctl (turned off by default) > (at least I am pretty sure I never got that done. (must go check)). > > >> Thanks, >> Vlad >> >> [1] >> http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/134931_______________________________________________ >> >> freebsd-hackers@freebsd.org mailing list >> http://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 Sep 7 13:55:17 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2AA061065677 for ; Wed, 7 Sep 2011 13:55:17 +0000 (UTC) (envelope-from jlpetz@internode.on.net) Received: from ipmail04.adl6.internode.on.net (ipmail04.adl6.internode.on.net [150.101.137.141]) by mx1.freebsd.org (Postfix) with ESMTP id 520FD8FC14 for ; Wed, 7 Sep 2011 13:55:16 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av4EADV3Z055LDo0/2dsb2JhbABDp2l5gUYBAQUIAh0BLjADAgYDMBYZIBABDQIEChQFv0uDZYMGBIc9lDiIZA Received: from ppp121-44-58-52.lns20.syd6.internode.on.net (HELO Minx) ([121.44.58.52]) by ipmail04.adl6.internode.on.net with ESMTP; 07 Sep 2011 23:25:14 +0930 From: "Jarrod Lee Petz" To: References: <007301cc6979$a690f9a0$f3b2ece0$@internode.on.net> <4E616D6E.4030903@FreeBSD.org> <001701cc69d3$aea9a0b0$0bfce210$@internode.on.net> <4E61BA37.2060204@FreeBSD.org> <20110903134634.GA55652@owl.midgard.homeip.net> <4E62B99C.6020707@FreeBSD.org> <001e01cc6a9d$8e62c870$ab285950$@internode.on.net> <20110905151146.GA10185@insomnia.benzedrine.cx> In-Reply-To: <20110905151146.GA10185@insomnia.benzedrine.cx> Date: Wed, 7 Sep 2011 23:55:09 +1000 Message-ID: <003a01cc6d65$c2784c50$4768e4f0$@internode.on.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQHuPCHqJDmDdIw669xIXvDN9LM1EADkjGxsAa6N1kUCHwUDBgGXq6DUAa0cmgEBYbJsPAKzPzumlJ3fNQA= Content-Language: en-au Subject: RE: TIME_WAIT Assassination in FreeBSD??? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: petz@nisshoko.net List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Sep 2011 13:55:17 -0000 Hi All, Thanks everyone for your input. As promised(although a bit late), I = tested this on FreeBSD to see how it would react. As I suspected it did = encounter the same problem. There is a few exceptions though. 1. The port randomization seems a bit less likely to choose the same = port twice on FreeBSD compared to AIX. This could simply be because the = FreeBSD system is not loaded/busy though. Remember the comment on algorithm 1. = in RFC6056 "is biased towards the first available port after a sequence of unavailable port numbers." So on a system which has more network connections the chance of re-using a recent port goes up. However my = test definitely takes longer to encounter the issue on FreeBSD. 2. I had to modify my test script on FreeBSD. FreeBSD's ftp client by default tries to use passive ftp mode and then fails over to active if = it is unavailable. As such I had to add the additional command line switch=20 '-A' to force the use of active mode. 3. When the problem is encountered FreeBSD is only delayed for 60 = seconds, AIX by default is delayed by 90 seconds. 4. When the port a port is re-used and the Windows ftp server(IIS) still has the port in TIME_WAIT from a previous connection. FreeBSD ftp = behaves differently to AIX ftp(with fixes to prevent hang). tcpdump on AIX shows ----------------------------- 1. -> Request: PORT ftp request gets sent. 2. <- Response: 200 Port command successful received. 3. -> Request: NLST ftp request gets sent. 4. <- Response: 150 Opening ASCII mode data connection. 5. -> ACK 6. <- Response: 425 Can't open data connection. 7 -> ACK 8. Now I see packets 3(NLST) through to 7(ACK) repeat over & over until the ftp client gives up(90 seconds) and just moves on to the next operation in the script. If the windows system has the port become available(CLOSED instead of TIME_WAIT). Then it might be successful, but the default TIME_WAIT on windows is 120 seconds(I think) so more often it doesn't. tcpdump on FreeBSD shows ----------------------------- 1. -> Request: PORT ftp request gets sent. 2. <- Response: 200 Port command successful received. 3. -> Request: NLST ftp request gets sent. 4. <- Response: 150 Opening ASCII mode data connection. 5. -> ACK 6. <- Response: 425 Can't open data connection. 7. -> ACK 8. 60 Seconds of nothing!!!! 9. -> Request: XXX (I don't know what this is. Looks like an FTP command, WireShark just shows them as three 'X' characters that have a square box around them? HEX - FF F4 FF ). 10. -> Request: XABOR (again a funny 'X' character inside a box. This time followed by 'ABOR' HEX - F2 41 42 4F 52). 11. <- Response: 500 'XABOR' : command not understood. This is output from the ftp command on FreeBSD when it encounters the = issue -------------------------------------------------------------------------= -- Connected to djs326b. 220 Microsoft FTP Service ---> USER ftpprd 331 Password required for ftpprd. ---> PASS XXXX 230 User ftpprd logged in. ---> SYST 215 Windows_NT Remote system type is Windows_NT. ---> FEAT 211-FEAT SIZE MDTM 211 END features[FEAT_FEAT] =3D 1 features[FEAT_MDTM] =3D 1 features[FEAT_MLST] =3D 0 features[FEAT_REST_STREAM] =3D 0 features[FEAT_SIZE] =3D 1 features[FEAT_TVFS] =3D 0 Connected and logged into djs326b. No proxy connection. Gate ftp: off, server (none), port ftpgate. Passive mode: off; fallback to active mode: off. Mode: stream; Type: ascii; Form: non-print; Structure: file. Verbose: on; Bell: off; Prompting: off; Globbing: on. Store unique: off; Receive unique: off. Preserve modification times: on. Case: off; CR stripping: on. Ntrans: off. Nmap: off. Hash mark printing: off; Mark count: 1024; Progress bar: on. Get transfer rate throttle: off; maximum: 0; increment 1024. Put transfer rate throttle: off; maximum: 0; increment 1024. Socket buffer sizes: send 32768, receive 65536. Use of PORT cmds: on. Use of EPSV/EPRT cmds for IPv4: on. Command line editing: off. Version: NetBSD-ftp 20050514 ---> CWD acrinput/data 250 CWD command successful. ---> PWD 257 "/acrinput/data" is current directory. got remotecwd as `/acrinput/data' ---> EPRT |1|10.10.0.100|56666| 'EPRT |1|10.10.0.100|56666|': command not understood disabling epsv4 for this connection ---> PORT 10,10,0,100,221,90 ---> NLST testingtrans.* ---> PORT 10,10,0,100,60,157 ---> NLST testingtrans.* ftp: poll timeout waiting before accept: Bad file descriptor '=F2ABOR': command not understood ---> PORT 10,10,0,100,50,50 ---> NLST TESTINGTRANS.* ---> PORT 10,10,0,100,126,65 ---> NLST TESTINGTRANS.* ---> QUIT 221 This is some the output from my test script. It simply runs an 'ftp -nidv -A djs326b < ftpscript.txt' command in an endless loop. If a run of the script takes longer than 5 seconds I capture the log & tcpdump. As shown below loop 112 & 131 = reused port 58047(PORT 10,10,0,100,226,191) -------------------------------------------------------------------------= -- FTP - RUN - 112 ---> EPRT |1|10.10.0.100|58047| < 'EPRT |1|10.10.0.100|58047|': command not understood < ---> PORT 10,10,0,100,226,191 < ---> PORT 10,10,0,100,194,40 < ---> PORT 10,10,0,100,61,191 < ---> PORT 10,10,0,100,60,206 < FTP - END - 112 - 0 FTP - TME - 112 - 1 FTP - RUN - 131 ---> EPRT |1|10.10.0.100|52690| < 'EPRT |1|10.10.0.100|52690|': command not understood < ---> PORT 10,10,0,100,205,210 < ---> PORT 10,10,0,100,249,153 < ---> PORT 10,10,0,100,88,249 < ---> PORT 10,10,0,100,226,191 < ftp: poll timeout waiting before accept: Bad file descriptor < '=F2ABOR': command not understood < FTP - END - 131 - 0 FTP - TME - 131 - 61 Hang detected. Verify Log - 131_1315187050 !!!! Regards Jarrod From owner-freebsd-hackers@FreeBSD.ORG Wed Sep 7 15:15:43 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1233) id C52591065673; Wed, 7 Sep 2011 15:15:43 +0000 (UTC) Date: Wed, 7 Sep 2011 15:15:43 +0000 From: Alexander Best To: Peter Jeremy Message-ID: <20110907151543.GA63310@freebsd.org> References: <20110906220115.GA25048@freebsd.org> <20110907061741.GC96277@server.vk2pj.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110907061741.GC96277@server.vk2pj.dyndns.org> Cc: freebsd-hackers@freebsd.org Subject: Re: excessive use of gettimeofday(2) and other syscalls X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Sep 2011 15:15:43 -0000 On Wed Sep 7 11, Peter Jeremy wrote: > On 2011-Sep-06 16:44:48 -0600, Manish Vachharajani wrote: > >Under 7.3 (haven't checked 8 or 9) this issue crops up because the > >time system call calls gettimeofday under the hood (see > >lib/libc/gen/time.c). As a result, the kernel tries to get an > >accurate subsecond resolution time that simply gets chopped to the > >nearest second. > > Under 8.x and later, time(3) uses clock_gettime(CLOCK_SECOND,...) > rather than gettimeofday(). This is intended to be much cheaper > than gettimeofday(). > > On 2011-Sep-06 21:15:55 -0400, Rayson Ho wrote: > >IMO, the time returned by gettimeofday does not need to be high > >precision. There are higher resolution time APIs on Linux and I > >believe the application programmers know when to use the slower but > >more accurate clock API. > > There are 3 standard APIs for returning time of day: > time(3) provides second precision > gettimeofday(2) provides microsecond precision > clock_gettime(2) provides nanosecond precision > > By default, FreeBSD attempts to provide resolution as close as > possible to the precision - which makes the 2 system calls fairly > expensive. In order to reduce the cost where the resolution isn't > important, FreeBSD provides several non-standard clock types for > clock_gettime(2). This approach differs from Linux - and it seems > that there is a non-trivial body of code that assumes that calling > gettimeofday() is very cheap. > > There is probably a good case for an API that provides a resolution > of the order of a tick but there is no standard for this. chromium is triggering ~20.000 gettimeofday(2) calls per second on my machine. i'm running CURRENT on amd64. cheers. alex > > -- > Peter Jeremy From owner-freebsd-hackers@FreeBSD.ORG Wed Sep 7 18:08:37 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D21A11065673 for ; Wed, 7 Sep 2011 18:08:37 +0000 (UTC) (envelope-from crmartin@sgi.com) Received: from relay.sgi.com (relay1.sgi.com [192.48.179.29]) by mx1.freebsd.org (Postfix) with ESMTP id 4DC9E8FC18 for ; Wed, 7 Sep 2011 18:08:37 +0000 (UTC) Received: from xmail.sgi.com (pv-excas3-dc21-nlb.corp.sgi.com [137.38.102.207]) by relay1.corp.sgi.com (Postfix) with ESMTP id BDAB88F8040 for ; Wed, 7 Sep 2011 11:08:36 -0700 (PDT) Received: from [10.3.0.220] (10.3.0.220) by xmail.sgi.com (137.38.102.30) with Microsoft SMTP Server (TLS) id 14.1.289.1; Wed, 7 Sep 2011 13:08:36 -0500 Message-ID: <4E67B323.8000602@sgi.com> Date: Wed, 7 Sep 2011 12:08:35 -0600 From: Charlie Martin User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.21) Gecko/20110831 Lightning/1.0b2 Thunderbird/3.1.13 MIME-Version: 1.0 To: Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [10.3.0.220] Subject: Understanding panic and exit in the kernel X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Sep 2011 18:08:37 -0000 I'm still pursuing a FreeBSD bug in "7.2-PRERELEASE FreeBSD" -- and yes, we know this is wildly out of date, but it's not feasible to upgrade right now -- and while trying to backport a fix suggested here http://permalink.gmane.org/gmane.os.freebsd.current/134266 I got a situation where the panic calls in one of these two macros from sys/queue.h #define QMD_LIST_CHECK_NEXT(elm, field) do { \ if (LIST_NEXT((elm), field) != NULL && \ LIST_NEXT((elm), field)->field.le_prev != \ &((elm)->field.le_next)) \ panic("Bad link elm %p next->prev != elm", (elm)); \ } while (0) #define QMD_LIST_CHECK_PREV(elm, field) do { \ if (*(elm)->field.le_prev != (elm)) \ panic("Bad link elm %p prev->next != elm", (elm)); \ } while (0) print the message, but *don't* then proceed to drop to the debugger -- instead the system hangs, with the CPU running but I had no luck getting its attention to force it to the debugger. I'm not clear just what could be causing the hangup. For my immediate purposes, I'd be happy with any way in which I could brutally kill the kernel and force it to the debugger, say by replacing the panic call with a printf followed by "1/0;". But I'm a little confused by the panic.c code -- it prints the arguments using a var_args, and then calls "exit(1);' So my questions: (1) will my brutal method actually force what I want or am I misunderstanding something (2) *which* of the several implementations of "int exit(int)" or similar is the one called in the FreeBSD kernel? (3) and how then does exit work? -- Charles R. (Charlie) Martin Senior Software Engineer SGI logo 1900 Pike Road Longmont, CO 80501 Phone: 303-532-0209 E-Mail: CRMartin@sgi.com Website: www.sgi.com From owner-freebsd-hackers@FreeBSD.ORG Wed Sep 7 18:41:55 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C95D4106566B for ; Wed, 7 Sep 2011 18:41:55 +0000 (UTC) (envelope-from manishv@lineratesystems.com) Received: from mail-gx0-f179.google.com (mail-gx0-f179.google.com [209.85.161.179]) by mx1.freebsd.org (Postfix) with ESMTP id 8E3DB8FC14 for ; Wed, 7 Sep 2011 18:41:55 +0000 (UTC) Received: by gxk1 with SMTP id 1so129626gxk.10 for ; Wed, 07 Sep 2011 11:41:54 -0700 (PDT) MIME-Version: 1.0 Received: by 10.42.141.193 with SMTP id p1mr5336127icu.281.1315420914545; Wed, 07 Sep 2011 11:41:54 -0700 (PDT) Received: by 10.42.19.196 with HTTP; Wed, 7 Sep 2011 11:41:54 -0700 (PDT) In-Reply-To: <20110907061741.GC96277@server.vk2pj.dyndns.org> References: <20110906220115.GA25048@freebsd.org> <20110907061741.GC96277@server.vk2pj.dyndns.org> Date: Wed, 7 Sep 2011 12:41:54 -0600 Message-ID: From: Manish Vachharajani To: Peter Jeremy Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@freebsd.org Subject: Re: excessive use of gettimeofday(2) and other syscalls X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Sep 2011 18:41:55 -0000 This is great info, thanks. Is it worth having some kind of environment variable tunable (or even compile time tunable) to have a "fast" gettimeofday then? Is there a complimentary body of code that assumes gettimeofday is precise? Manish On Wed, Sep 7, 2011 at 12:17 AM, Peter Jeremy wrote: > On 2011-Sep-06 16:44:48 -0600, Manish Vachharajani wrote: >>Under 7.3 (haven't checked 8 or 9) this issue crops up because the >>time system call calls gettimeofday under the hood (see >>lib/libc/gen/time.c). =A0As a result, the kernel tries to get an >>accurate subsecond resolution time that simply gets chopped to the >>nearest second. > > Under 8.x and later, time(3) uses clock_gettime(CLOCK_SECOND,...) > rather than gettimeofday(). =A0This is intended to be much cheaper > than gettimeofday(). > > On 2011-Sep-06 21:15:55 -0400, Rayson Ho wrote: >>IMO, the time returned by gettimeofday does not need to be high >>precision. There are higher resolution time APIs on Linux and I >>believe the application programmers know when to use the slower but >>more accurate clock API. > > There are 3 standard APIs for returning time of day: > time(3) provides second precision > gettimeofday(2) provides microsecond precision > clock_gettime(2) provides nanosecond precision > > By default, FreeBSD attempts to provide resolution as close as > possible to the precision - which makes the 2 system calls fairly > expensive. =A0In order to reduce the cost where the resolution isn't > important, FreeBSD provides several non-standard clock types for > clock_gettime(2). =A0This approach differs from Linux - and it seems > that there is a non-trivial body of code that assumes that calling > gettimeofday() is very cheap. > > There is probably a good case for an API that provides a resolution > of the order of a tick but there is no standard for this. > > -- > Peter Jeremy > --=20 Manish Vachharajani Founder LineRate Systems manishv@lineratesystems.com (609)635-9531 M From owner-freebsd-hackers@FreeBSD.ORG Wed Sep 7 18:53:25 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C9EEF106566B for ; Wed, 7 Sep 2011 18:53:25 +0000 (UTC) (envelope-from mdf356@gmail.com) Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by mx1.freebsd.org (Postfix) with ESMTP id 87EDE8FC17 for ; Wed, 7 Sep 2011 18:53:25 +0000 (UTC) Received: by qwg2 with SMTP id 2so723785qwg.17 for ; Wed, 07 Sep 2011 11:53:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=YTOT8+7sooRt5TcbAfNq1VNfjJ2v7Nma69PHPZRdOPo=; b=YYCtQfLjM88pMSIZBCveQwSoaBE8gGv/44tnu6zqvCTvc1NUc1Yfl7BAzZkOnULgPt RTYUla48vfPN0ibCzUbqEK6XeMza/VL/i08sq5fyEuXqWjyxjNUD52wK9OIBF0oEDDKj yUjC7G+lwppuz6acQ7bsuTU9lN9fiDhDpzV44= MIME-Version: 1.0 Received: by 10.229.87.137 with SMTP id w9mr5030605qcl.284.1315421604813; Wed, 07 Sep 2011 11:53:24 -0700 (PDT) Sender: mdf356@gmail.com Received: by 10.229.190.194 with HTTP; Wed, 7 Sep 2011 11:53:24 -0700 (PDT) In-Reply-To: <4E67B323.8000602@sgi.com> References: <4E67B323.8000602@sgi.com> Date: Wed, 7 Sep 2011 11:53:24 -0700 X-Google-Sender-Auth: WgzFHkKRw642JXc5IKpMF0XdB8g Message-ID: From: mdf@FreeBSD.org To: Charlie Martin Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@freebsd.org Subject: Re: Understanding panic and exit in the kernel X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Sep 2011 18:53:25 -0000 On Wed, Sep 7, 2011 at 11:08 AM, Charlie Martin wrote: > I'm still pursuing a FreeBSD bug in "7.2-PRERELEASE FreeBSD" -- and yes, = we > know this is wildly out of date, but it's not feasible to upgrade right n= ow > -- and while trying to backport a fix suggested here > http://permalink.gmane.org/gmane.os.freebsd.current/134266 I got a situat= ion > where the panic calls in one of =A0these two macros from sys/queue.h > > #define =A0 =A0QMD_LIST_CHECK_NEXT(elm, field) do { =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0\ > =A0 =A0if (LIST_NEXT((elm), field) !=3D NULL && =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0\ > =A0 =A0 =A0 =A0LIST_NEXT((elm), field)->field.le_prev !=3D =A0 =A0 =A0 = =A0 =A0 =A0\ > &((elm)->field.le_next)) =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0\ > =A0 =A0 =A0 =A0 =A0 =A0 panic("Bad link elm %p next->prev !=3D elm", (elm= )); =A0 =A0\ > } while (0) > > #define =A0 =A0QMD_LIST_CHECK_PREV(elm, field) do { =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0\ > =A0 =A0if (*(elm)->field.le_prev !=3D (elm)) =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0\ > =A0 =A0 =A0 =A0panic("Bad link elm %p prev->next !=3D elm", (elm)); =A0 = =A0\ > } while (0) > > print the message, but *don't* then proceed to drop to the debugger -- > instead the system hangs, with the CPU running but I had no luck getting = its > attention to force it to the debugger. > > I'm not clear just what could be causing the hangup. > > For my immediate purposes, I'd be happy with any way in which I could > brutally kill the kernel and force it to the debugger, say by replacing t= he > panic call with a printf followed by "1/0;". =A0But I'm a little confused= by > the panic.c code -- it prints the arguments using a var_args, and then ca= lls > "exit(1);' What file are you looking in? The kernel panic() is in sys/kern/kern_shutdown.c, not sys/boot/common/panic.c. It will optionally call kdb_enter_why() and then boot(). Do you have the debug.debugger_on_panic sysctl set to 1? Thanks, matthew > So my questions: > > (1) will my brutal method actually force what I want or am I > misunderstanding something > (2) *which* of the several implementations of "int exit(int)" or similar = is > the one called in the FreeBSD kernel? > (3) and how then does exit work? From owner-freebsd-hackers@FreeBSD.ORG Wed Sep 7 19:24:49 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BCC1D106566B for ; Wed, 7 Sep 2011 19:24:49 +0000 (UTC) (envelope-from crmartin@sgi.com) Received: from relay.sgi.com (relay2.sgi.com [192.48.179.30]) by mx1.freebsd.org (Postfix) with ESMTP id 917708FC14 for ; Wed, 7 Sep 2011 19:24:49 +0000 (UTC) Received: from xmail.sgi.com (pv-excas3-dc21-nlb.corp.sgi.com [137.38.102.207]) by relay2.corp.sgi.com (Postfix) with ESMTP id B6EDA304071; Wed, 7 Sep 2011 12:24:48 -0700 (PDT) Received: from [10.3.0.220] (10.3.0.220) by xmail.sgi.com (137.38.102.30) with Microsoft SMTP Server (TLS) id 14.1.289.1; Wed, 7 Sep 2011 14:24:35 -0500 Message-ID: <4E67C4E6.40009@sgi.com> Date: Wed, 7 Sep 2011 13:24:22 -0600 From: Charlie Martin User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.21) Gecko/20110831 Lightning/1.0b2 Thunderbird/3.1.13 MIME-Version: 1.0 To: References: <4E67B323.8000602@sgi.com> In-Reply-To: Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [10.3.0.220] Cc: freebsd-hackers@freebsd.org Subject: Re: Understanding panic and exit in the kernel X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Sep 2011 19:24:49 -0000 On 2011-09-07 12:53, mdf@FreeBSD.org wrote: >> For my immediate purposes, I'd be happy with any way in which I could >> > brutally kill the kernel and force it to the debugger, say by replacing the >> > panic call with a printf followed by "1/0;". But I'm a little confused by >> > the panic.c code -- it prints the arguments using a var_args, and then calls >> > "exit(1);' > What file are you looking in? The kernel panic() is in > sys/kern/kern_shutdown.c, not sys/boot/common/panic.c. It will > optionally call kdb_enter_why() and then boot(). Bingo, that's got to help. This makes a lot more sense. > Do you have the debug.debugger_on_panic sysctl set to 1? Yes -- and panic does so *except* in the version with those changes to queue.h. > Thanks, > matthew > -- Charles R. (Charlie) Martin Senior Software Engineer SGI logo 1900 Pike Road Longmont, CO 80501 Phone: 303-532-0209 E-Mail: CRMartin@sgi.com Website: www.sgi.com From owner-freebsd-hackers@FreeBSD.ORG Wed Sep 7 19:50:51 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0A3001065670 for ; Wed, 7 Sep 2011 19:50:51 +0000 (UTC) (envelope-from mdf356@gmail.com) Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by mx1.freebsd.org (Postfix) with ESMTP id BAE898FC0C for ; Wed, 7 Sep 2011 19:50:50 +0000 (UTC) Received: by qwg2 with SMTP id 2so12839qwg.17 for ; Wed, 07 Sep 2011 12:50:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=OaHr1A1FdcpVlOjls0HIH/mAfMAGxb1oP+N/xQy9keM=; b=aa9E+5DXUynAiifDoEeZBPuB3qdOIWwHKTAOeDhGPbb7JmeXzjFEa+vt/OAXSMOnrs lX9Bay41dEUGyiV7n4rQ0dhcoHjo5sOYyC0Dy/Z4XOdr8+5epMqXTN4Ox2ShJijVJqIp GTChzigJfzWLtdJUwjkmvyttv/CmfGjkn8tjo= MIME-Version: 1.0 Received: by 10.229.87.137 with SMTP id w9mr5073593qcl.284.1315425049919; Wed, 07 Sep 2011 12:50:49 -0700 (PDT) Sender: mdf356@gmail.com Received: by 10.229.190.194 with HTTP; Wed, 7 Sep 2011 12:50:49 -0700 (PDT) In-Reply-To: <4E67C4E6.40009@sgi.com> References: <4E67B323.8000602@sgi.com> <4E67C4E6.40009@sgi.com> Date: Wed, 7 Sep 2011 12:50:49 -0700 X-Google-Sender-Auth: jHfiRpExJPo8C3AAHALp-5OSnM4 Message-ID: From: mdf@FreeBSD.org To: Charlie Martin Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@freebsd.org Subject: Re: Understanding panic and exit in the kernel X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Sep 2011 19:50:51 -0000 On Wed, Sep 7, 2011 at 12:24 PM, Charlie Martin wrote: > > > On 2011-09-07 12:53, mdf@FreeBSD.org wrote: >>> >>> For my immediate purposes, I'd be happy with any way in which I could >>> > =A0brutally kill the kernel and force it to the debugger, say by >>> > replacing the >>> > =A0panic call with a printf followed by "1/0;". =A0But I'm a little >>> > confused by >>> > =A0the panic.c code -- it prints the arguments using a var_args, and = then >>> > calls >>> > =A0"exit(1);' >> >> What file are you looking in? =A0The kernel panic() is in >> sys/kern/kern_shutdown.c, not sys/boot/common/panic.c. =A0It will >> optionally call kdb_enter_why() and then boot(). > > Bingo, that's got to help. =A0This makes a lot more sense. > >> Do you have the debug.debugger_on_panic sysctl set to 1? > > Yes -- and panic does so *except* in the version with those changes to > queue.h. If all you need to get started is a backtrace then debug.trace_on_panic=3D1 may be sufficient. I'm not sure of the timeline when 7.2-prerelease was issued, but there have been some reliability improvements to panic handling including marking that a CPU is in panic, etc., that may have come after 7.2-prerelease. You may want to look at the svn history for kern_shutdown.c and locally apply those changes to see if it changes your result. Cheers, matthew From owner-freebsd-hackers@FreeBSD.ORG Thu Sep 8 10:00:48 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 992C61065672 for ; Thu, 8 Sep 2011 10:00:48 +0000 (UTC) (envelope-from stas@FreeBSD.org) Received: from mx0.deglitch.com (cl-414.sto-01.se.sixxs.net [IPv6:2001:16d8:ff00:19d::2]) by mx1.freebsd.org (Postfix) with ESMTP id 4615C8FC0A for ; Thu, 8 Sep 2011 10:00:48 +0000 (UTC) Received: from orion.SpringDaemons.com (c-98-234-217-95.hsd1.ca.comcast.net [98.234.217.95]) by mx0.deglitch.com (Postfix) with ESMTPA id DE64E8FC2E; Thu, 8 Sep 2011 14:00:45 +0400 (MSD) Received: from orion (localhost [127.0.0.1]) by orion.SpringDaemons.com (Postfix) with SMTP id 3ECF53A12E; Thu, 8 Sep 2011 03:01:23 -0700 (PDT) Date: Thu, 8 Sep 2011 03:01:22 -0700 From: Stanislav Sedov To: James Jones Message-Id: <20110908030122.e28473f0.stas@FreeBSD.org> In-Reply-To: <565C98BA-9B92-4F07-A747-DDA5DC3D7703@freedomnet.co.nz> References: <565C98BA-9B92-4F07-A747-DDA5DC3D7703@freedomnet.co.nz> Organization: The FreeBSD Project X-Mailer: carrier-pigeon Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="PGP-SHA1"; boundary="Signature=_Thu__8_Sep_2011_03_01_22_-0700_RLWC0HtICRcWf1HH" Cc: "freebsd-hackers@freebsd.org" Subject: Re: MIPS toolchain X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Sep 2011 10:00:48 -0000 --Signature=_Thu__8_Sep_2011_03_01_22_-0700_RLWC0HtICRcWf1HH Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, 29 Jul 2011 11:12:35 -0400 James Jones mentioned: > Does anyone have a prebuilt MIPS tool chain? >=20 If you're looking to build standalone applications (like uboot), try devel/mips-rtems-gcc (or devel/cross-gcc if you don't like rtems patches). It should work fine for building uboot or other bare-metal stuff. There're also packages for this. --=20 Stanislav Sedov ST4096-RIPE () ascii ribbon campaign - against html e-mail=20 /\ www.asciiribbon.org - against proprietary attachments --Signature=_Thu__8_Sep_2011_03_01_22_-0700_RLWC0HtICRcWf1HH Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- iQIcBAEBAgAGBQJOaJJzAAoJEL8lojEJL9nwjicP/jZjVPo0ieLI7q/M6s+eJeg2 m7XYElecMZQ8aPT2H1bBRm1+2fAfIgLDJ3FvQsZBlOUoWuBYFJvWr81BJgwgmVFX hB0IXfP4i3R/LFyLzSoGVJacTpJC9qjsAO63rBTlERmX8uCs2byAy4GZdLkJkOqS sPDDg8GW9k34S7bRhKURYf2A/sfIDCg/o3UdSB/nSj5wG5WEUs/64IiDzw2Ph5y8 zrD+n4qslguY5YbpZxRiWszISuXGT3ppppJWAGXFyvQIwG+jEpjw6U+r644f2gLT ZVSxSgQBFZ9BCCNTu/2sbQ1p9BtWZzApiaDnW+/2myis5/gqWGbDsujT1vP3fQQm sWaKDzKJLJTfo9JjsUMAwdoVNrGrBu9vdXOqhJHFbQOBbECoikbHCDH9zL0GcgiT zJ89mWo+WTqAg0bA5n0XDw9vY+MH4/11JAKuRoQ7jDDQWMYPRaX6EDrTYra+P5dT rIdSsDvk2IjahZD2ko5XohPTG7NJyOP2oq+eTVjHY7uPyPWGFK5dTLR6/4K8/omn +1/oGHM6gzKLlQs03MDCyY9OS/AkKDci4sL4y6RSVcXp8PTsWS3/zGVIRMYwZaCQ BeugKIHWkeOBO30xvURFwr9U3dKx1s8AJNEW8vZZr10Y1Yr5iTYi6923MlTJHMhD I8rLqmxz5G38mJL7DlWF =3TR6 -----END PGP SIGNATURE----- --Signature=_Thu__8_Sep_2011_03_01_22_-0700_RLWC0HtICRcWf1HH-- From owner-freebsd-hackers@FreeBSD.ORG Thu Sep 8 10:14:42 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 87638106566B for ; Thu, 8 Sep 2011 10:14:42 +0000 (UTC) (envelope-from stas@FreeBSD.org) Received: from mx0.deglitch.com (cl-414.sto-01.se.sixxs.net [IPv6:2001:16d8:ff00:19d::2]) by mx1.freebsd.org (Postfix) with ESMTP id 33EB48FC14 for ; Thu, 8 Sep 2011 10:14:42 +0000 (UTC) Received: from orion.SpringDaemons.com (c-98-234-217-95.hsd1.ca.comcast.net [98.234.217.95]) by mx0.deglitch.com (Postfix) with ESMTPA id 0CBD88FC39; Thu, 8 Sep 2011 14:14:41 +0400 (MSD) Received: from orion (localhost [127.0.0.1]) by orion.SpringDaemons.com (Postfix) with SMTP id 74CDD3A12E; Thu, 8 Sep 2011 03:15:18 -0700 (PDT) Date: Thu, 8 Sep 2011 03:15:18 -0700 From: Stanislav Sedov To: "Ilya Bakulin" Message-Id: <20110908031518.481d8a78.stas@FreeBSD.org> In-Reply-To: <2c9d3cc8a0b85313f55f53ca573af81a.squirrel@zugang.kibab.com> References: <4E167C94.70300@kibab.com> <4E1685D8.403@gmail.com> <2c9d3cc8a0b85313f55f53ca573af81a.squirrel@zugang.kibab.com> Organization: The FreeBSD Project X-Mailer: carrier-pigeon Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Matt , freebsd-hackers@freebsd.org, "Robert N. M. Watson" , Jonathan Anderson , Ben Laurie Subject: Re: Capsicum project: Ideas needed X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Sep 2011 10:14:42 -0000 On Fri, 8 Jul 2011 15:09:52 +0400 "Ilya Bakulin" mentioned: > [CCing Ben, Robert and Jonathan as it's very important for me to receive > their feedback about my thoughts] > > Let me focus on those application ideas that you've mentioned. All the > following are my thoughts and this may be incorrect, in this case please > correct me. > > > -any server software > Yes, server software is a good candidate for bringing cap.mode in. Though > this applies to servers that do not include in-process support for > interpreters (ie Apache + mod_php), see later why. Such software as nginx, > lighttpd is OK. Speaking about base system components, this list includes > inetd daemons (but modification of inetd itself is NOT sufficient and > ineffective, capability support implies modifying code of daemons) I would also suggest our Heimdal Kerberos implementation as it performs a lot of non-trivial ASN.1 and GSSAPI decapsulation/encapsulation when processing packets and we saw a lot of vulenrabilities in the past in these areas. Unfortunately, Heimdal will be probably to large to break into compartments. -- Stanislav Sedov ST4096-RIPE () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments From owner-freebsd-hackers@FreeBSD.ORG Thu Sep 8 13:58:01 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D42111065673 for ; Thu, 8 Sep 2011 13:58:01 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:131:60a2::2]) by mx1.freebsd.org (Postfix) with ESMTP id 9A35F8FC15 for ; Thu, 8 Sep 2011 13:58:01 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:14f9:cfdf:caf2:2c18]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id 56BC94AC59 for ; Thu, 8 Sep 2011 17:58:00 +0400 (MSD) Date: Thu, 8 Sep 2011 17:57:56 +0400 From: Lev Serebryakov Organization: FreeBSD X-Priority: 3 (Normal) Message-ID: <899261441.20110908175756@serebryakov.spb.ru> To: "freebsd-hackers@freebsd.org" MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: quoted-printable Subject: How to include without "device_if.h" and "bus_if.h"? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: lev@FreeBSD.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Sep 2011 13:58:01 -0000 Hello, Freebsd-hackers. I need to include in my kernel module to use devctl_notify(). But my module doesn't have device_if.h or bus_if.h, which are required by . What should I do? --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-hackers@FreeBSD.ORG Thu Sep 8 14:44:39 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4DDA01065670; Thu, 8 Sep 2011 14:44:39 +0000 (UTC) (envelope-from kmacybsd@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id E98918FC18; Thu, 8 Sep 2011 14:44:38 +0000 (UTC) Received: by vxi39 with SMTP id 39so654928vxi.13 for ; Thu, 08 Sep 2011 07:44:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=rlis0DakBvl8yqlsqWbWtPAxFRhvkH1B7DJKgAtHiTU=; b=B5n5ZAzZFQl7SAn67lHiAG6A0pSrcCYwei25GNf5jUOlTEAkBHaBhxb5f+yh7zqZfp Bo/bSI6yEiBvtGH+SSw1KtNAkaIkCcTpD/XFs1pnXdu+c+L3Ey6XfXE8F7ykfVOEPSOP JCkBZZzXsEsIJOENr/TqaFdO1HQDpeyqf2VU8= MIME-Version: 1.0 Received: by 10.52.6.163 with SMTP id c3mr750291vda.163.1315491731560; Thu, 08 Sep 2011 07:22:11 -0700 (PDT) Sender: kmacybsd@gmail.com Received: by 10.52.113.169 with HTTP; Thu, 8 Sep 2011 07:22:11 -0700 (PDT) In-Reply-To: <899261441.20110908175756@serebryakov.spb.ru> References: <899261441.20110908175756@serebryakov.spb.ru> Date: Thu, 8 Sep 2011 16:22:11 +0200 X-Google-Sender-Auth: Mxueb7hnqixCWnUZ68Q_NvlE5lA Message-ID: From: "K. Macy" To: lev@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: "freebsd-hackers@freebsd.org" Subject: Re: How to include without "device_if.h" and "bus_if.h"? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Sep 2011 14:44:39 -0000 Just add them to the makefile. They'll be automatically created as dependencies. 2011/9/8 Lev Serebryakov : > Hello, Freebsd-hackers. > > =A0I need to include in my kernel module to use > devctl_notify(). But my module doesn't have device_if.h or bus_if.h, > which are required by . > =A0What should I do? > > -- > // Black Lion AKA Lev Serebryakov > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org= " > From owner-freebsd-hackers@FreeBSD.ORG Thu Sep 8 14:54:24 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DD427106566C; Thu, 8 Sep 2011 14:54:24 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:131:60a2::2]) by mx1.freebsd.org (Postfix) with ESMTP id A00598FC0C; Thu, 8 Sep 2011 14:54:24 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:14f9:cfdf:caf2:2c18]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id C9D524AC31; Thu, 8 Sep 2011 18:54:23 +0400 (MSD) Date: Thu, 8 Sep 2011 18:54:19 +0400 From: Lev Serebryakov Organization: FreeBSD X-Priority: 3 (Normal) Message-ID: <510582218.20110908185419@serebryakov.spb.ru> To: "K. Macy" In-Reply-To: References: <899261441.20110908175756@serebryakov.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: quoted-printable Cc: "freebsd-hackers@freebsd.org" Subject: Re: How to include without "device_if.h" and "bus_if.h"? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: lev@FreeBSD.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Sep 2011 14:54:24 -0000 Hello, K.. You wrote 8 =F1=E5=ED=F2=FF=E1=F0=FF 2011 =E3., 18:22:11: > Just add them to the makefile. They'll be automatically created as > dependencies. Is it good idea to create these empty files only for one prototype from ? Why devctl_notify() is bound to bus, anyway? It is used, for example, for notifications about network cable plug/unplug, which doesn't look like something bus-related. --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-hackers@FreeBSD.ORG Thu Sep 8 14:58:33 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0B8DA1065670; Thu, 8 Sep 2011 14:58:33 +0000 (UTC) (envelope-from kmacybsd@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id A3E638FC1F; Thu, 8 Sep 2011 14:58:32 +0000 (UTC) Received: by vxi39 with SMTP id 39so671994vxi.13 for ; Thu, 08 Sep 2011 07:58:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=YPHHVBy+/4fZoOhwf2PHDpinoGBK3HiidkZRqCBsgig=; b=LRKXk0B8aVJ5RT0DoRYY+oOQzDzzjm5atG6fEK1muj9i1EdXlDINEtMpfr+Wbz9lD1 fMcJZcemVdeENJ9RPDWW6VeOYIBo1zSnhzHVfwrqyEY3KFnNSoDIXDb2U94dZjX4kN7H pl/179hLqP1VnujgbRo1aevOWULBqXQXpEOBM= MIME-Version: 1.0 Received: by 10.52.28.206 with SMTP id d14mr754156vdh.498.1315493911894; Thu, 08 Sep 2011 07:58:31 -0700 (PDT) Sender: kmacybsd@gmail.com Received: by 10.52.113.169 with HTTP; Thu, 8 Sep 2011 07:58:31 -0700 (PDT) In-Reply-To: <510582218.20110908185419@serebryakov.spb.ru> References: <899261441.20110908175756@serebryakov.spb.ru> <510582218.20110908185419@serebryakov.spb.ru> Date: Thu, 8 Sep 2011 16:58:31 +0200 X-Google-Sender-Auth: PWqEObiQ7iqWRD3u0aNQzoxppMI Message-ID: From: "K. Macy" To: lev@freebsd.org Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable Cc: "freebsd-hackers@freebsd.org" Subject: Re: How to include without "device_if.h" and "bus_if.h"? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Sep 2011 14:58:33 -0000 2011/9/8 Lev Serebryakov : > Hello, K.. > You wrote 8 =D3=C5=CE=D4=D1=C2=D2=D1 2011 =C7., 18:22:11: > >> Just add them to the makefile. They'll be automatically created =9Aas >> dependencies. > =9AIs it good idea to create these empty files only for one prototype > from ? I can't comment on whether or not it is good or bad. It is simply how things are done. > =9AWhy devctl_notify() is bound to bus, anyway? It is used, for > example, for notifications about network cable plug/unplug, which > doesn't look like something bus-related. If you look at it you'll see that bus.h covers a range of areas, general device instantiation being one of them. > > -- > // Black Lion AKA Lev Serebryakov > > From owner-freebsd-hackers@FreeBSD.ORG Thu Sep 8 21:57:19 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D183B1065672 for ; Thu, 8 Sep 2011 21:57:19 +0000 (UTC) (envelope-from aduane@juniper.net) Received: from exprod7og113.obsmtp.com (exprod7og113.obsmtp.com [64.18.2.179]) by mx1.freebsd.org (Postfix) with ESMTP id 71CC38FC17 for ; Thu, 8 Sep 2011 21:57:19 +0000 (UTC) Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob113.postini.com ([64.18.6.12]) with SMTP ID DSNKTmk6Ph9oWrGMDMQDW1//B4UPo4N4rzzE@postini.com; Thu, 08 Sep 2011 14:57:19 PDT Received: from p-emfe01-wf.jnpr.net (172.28.145.24) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.2.254.0; Thu, 8 Sep 2011 14:55:05 -0700 Received: from EMBX01-WF.jnpr.net ([fe80::8002:d3e7:4146:af5f]) by p-emfe01-wf.jnpr.net ([fe80::d0d1:653d:5b91:a123%11]) with mapi; Thu, 8 Sep 2011 17:55:04 -0400 From: Andrew Duane To: "freebsd-hackers@freebsd.org" , "freebsd-arch@freebsd.org" Date: Thu, 8 Sep 2011 17:55:02 -0400 Thread-Topic: Soliciting opinions on an extension of the bootinfo structure Thread-Index: AQHMbnH2giQRxi0m50uyS6Evz0JaPw== Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: Subject: Soliciting opinions on an extension of the bootinfo structure X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Sep 2011 21:57:19 -0000 I'm proposing an extension framework for the bootinfo structure used to pas= s information from the bootstrap/loader to the kernel. Although I'm only pr= oposing this for the MIPS bootinfo, it's completely applicable to any of th= em. What I propose is adding an optional platform extension structure: bootinfo= _pext, surrounded by #ifdef BOOTINFO_PEXT struct bootinfo { .... u_int32_t bi_kernend; /* end of kernel space */ u_int32_t bi_envp; /* environment */ u_int32_t bi_modulep; /* preloaded modules */ +#ifdef BOOTINFO_PEXT + struct bootinfo_pext bi_pext; /* platform extensions if d= efined */ +#endif }; Then, any vendor, platform, architecture, family, or developer could define= a new header file (or expand an existing one) with a definition of struct = bootinfo_pext, and a #define BOOTINFO_PEXT. Include the new (or existing) h= eader file in your source, and you have whatever extensions you want, witho= ut affecting other platforms, architectures, families, or developers. The f= ile we're looking to add is sys/mips/cavium/bootinfo_octeon.h: +/* + * Platform bootinfo extensions for OCTEON bootinfo structure + * + * Specific vendors can add their own bootinfo_pext structures + * surrounded by #ifdef OCTEON_VENDOR_XXX + */ + +#include "opt_cvmx.h" /* For OCTEON_VENDOR_XXX definitions */ + +#ifdef OCTEON_VENDOR_JUNIPER +#define BOOTINFO_PEXT /* include bootinfo_pext in main structure = */ +#define BOOTINFO_PEXT_MAGIC 0xCADECADE +#define BOOTINFO_PEXT_VERSION 1 + +struct bootinfo_pext { + int pext_i2cid; + u_int32_t pext_flags; + u_int32_t pext_magic; /* Magic number for octeon= pext */ + u_int32_t pext_version; /* Version of pext */ + u_int16_t pext_uboot_major_rev; + u_int16_t pext_uboot_minor_rev; + u_int16_t pext_loader_major_rev; + u_int16_t pext_loader_minor_rev; +}; +#endif /* OCTEON_VENDOR_JUNIPER */ Reasonable? Unreasonable? Insane? -- Andrew Duane Juniper Networks 978-589-0551 10 Technology Park Dr aduane@juniper.net Westford, MA 01886-3418 From owner-freebsd-hackers@FreeBSD.ORG Thu Sep 8 22:11:57 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from [127.0.0.1] (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id 4B9001065670 for ; Thu, 8 Sep 2011 22:11:56 +0000 (UTC) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-hackers@freebsd.org Date: Thu, 8 Sep 2011 18:11:45 -0400 User-Agent: KMail/1.6.2 MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201109081811.47776.jkim@FreeBSD.org> Subject: Porting PathScale's EKOPath Compiler Suite X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Sep 2011 22:11:57 -0000 I have done preliminary porting work of PathScale's open-sourced EKOPath Compiler Suite (https://github.com/pathscale). http://people.freebsd.org/~jkim/ekopath-devel.tar.bz2 This includes experimental OpenMP support and PathDB. Unfortuntely, PathDB builds fine but just crashes ATM. Both options are turned off by default for now. Although it seems working fine for many non-trivial C/C++/Fortran sources, please do not use it for any serious project because I have seen few internal compiler errors and crashes. Be aware of ugly hacks! ;-) I just wanted to share it now because it was on the WantedPorts list on Wiki for a while. If anyone with more clues want to pick it up from here, please feel free. Cheers, Jung-uk Kim From owner-freebsd-hackers@FreeBSD.ORG Thu Sep 8 22:44:00 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DB3AF106564A; Thu, 8 Sep 2011 22:44:00 +0000 (UTC) (envelope-from grehan@freebsd.org) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id 996E48FC15; Thu, 8 Sep 2011 22:44:00 +0000 (UTC) Received: from dommail.onthenet.com.au (dommail.OntheNet.com.au [203.13.70.57]) by alto.onthenet.com.au (Postfix) with ESMTPS id 98341116AC; Fri, 9 Sep 2011 08:25:26 +1000 (EST) Received: from vpn2ntap-47744.hq.netapp.com (pos-ext.netapp.com [198.95.226.40]) by dommail.onthenet.com.au (MOS 4.1.10-GA) with ESMTP id AYE93285 (AUTH peterg@ptree32.com.au); Fri, 9 Sep 2011 08:25:25 +1000 Message-ID: <4E6940D3.4070801@freebsd.org> Date: Thu, 08 Sep 2011 16:25:23 -0600 From: Peter Grehan User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.21) Gecko/20110830 Thunderbird/3.1.13 MIME-Version: 1.0 To: Andrew Duane References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-hackers@freebsd.org" , "freebsd-arch@freebsd.org" Subject: Re: Soliciting opinions on an extension of the bootinfo structure X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Sep 2011 22:44:01 -0000 > I'm proposing an extension framework for the bootinfo structure used > to pass information from the bootstrap/loader to the kernel. Although > I'm only proposing this for the MIPS bootinfo, it's completely > applicable to any of them. > > What I propose is adding an optional platform extension structure: > bootinfo_pext, surrounded by #ifdef BOOTINFO_PEXT Any reason not to put the vendor bits into another piece of loader metadata ? That seems the extensible way to add additional info from the loader, rather than extending bootinfo (as was the case pre-loader days). later, Peter. From owner-freebsd-hackers@FreeBSD.ORG Thu Sep 8 22:51:48 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 39FA2106564A; Thu, 8 Sep 2011 22:51:48 +0000 (UTC) (envelope-from cbergstrom@pathscale.com) Received: from mail-gx0-f179.google.com (mail-gx0-f179.google.com [209.85.161.179]) by mx1.freebsd.org (Postfix) with ESMTP id DF2BD8FC0A; Thu, 8 Sep 2011 22:51:46 +0000 (UTC) Received: by gxk1 with SMTP id 1so560299gxk.10 for ; Thu, 08 Sep 2011 15:51:45 -0700 (PDT) Received: by 10.42.152.6 with SMTP id g6mr523729icw.517.1315520772571; Thu, 08 Sep 2011 15:26:12 -0700 (PDT) Received: from [192.168.1.34] (ppp-61-90-34-212.revip.asianet.co.th [61.90.34.212]) by mx.google.com with ESMTPS id a11sm6168613ibg.3.2011.09.08.15.26.09 (version=SSLv3 cipher=OTHER); Thu, 08 Sep 2011 15:26:11 -0700 (PDT) Message-ID: <4E694173.9010009@pathscale.com> Date: Fri, 09 Sep 2011 05:28:03 +0700 From: =?ISO-8859-1?Q?=22C=2E_Bergstr=F6m=22?= User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.9.2.7) Gecko/20101031 Lightning/1.0b2 Thunderbird/3.1.1 MIME-Version: 1.0 To: Jung-uk Kim References: <201109081811.47776.jkim@FreeBSD.org> In-Reply-To: <201109081811.47776.jkim@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: Porting PathScale's EKOPath Compiler Suite X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Sep 2011 22:51:48 -0000 On 09/ 9/11 05:11 AM, Jung-uk Kim wrote: > I have done preliminary porting work of PathScale's open-sourced > EKOPath Compiler Suite (https://github.com/pathscale). > > http://people.freebsd.org/~jkim/ekopath-devel.tar.bz2 > > This includes experimental OpenMP support and PathDB. Unfortuntely, > PathDB builds fine but just crashes ATM. Both options are turned off > by default for now. Although it seems working fine for many > non-trivial C/C++/Fortran sources, please do not use it for any > serious project because I have seen few internal compiler errors and > crashes. Be aware of ugly hacks! ;-) > > I just wanted to share it now because it was on the WantedPorts list > on Wiki for a while. If anyone with more clues want to pick it up > from here, please feel free. Would it be possible to work with upstream on the changes you've made? If you do a github pull request we should be able to review/comment/merge any changes back upstream efficiently. From owner-freebsd-hackers@FreeBSD.ORG Thu Sep 8 23:18:31 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7E5C3106564A; Thu, 8 Sep 2011 23:18:31 +0000 (UTC) (envelope-from peter@wemm.org) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 0C8148FC14; Thu, 8 Sep 2011 23:18:30 +0000 (UTC) Received: by vxi39 with SMTP id 39so1190128vxi.13 for ; Thu, 08 Sep 2011 16:18:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wemm.org; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=cOhUiQ1BAxZW7puz/Zf4hMeUm4VfCNH0JWvGJltzhtY=; b=33dii+pMDGyyETakLJH6/X9MHsRkScAOJfgil8QpHtaFFl2ipX0nAPO2u6fe8r7qZp TL5tdht273vrvlBmuvfFqX9WpWWCqTRj3cLH8mv/C+7rcE5EOZ3iyGz1WUTKjvRuZCFN LRI8gP0naeotzHKW16uAd85TXq22XUo2xubSM= MIME-Version: 1.0 Received: by 10.52.92.233 with SMTP id cp9mr400569vdb.513.1315522099155; Thu, 08 Sep 2011 15:48:19 -0700 (PDT) Received: by 10.220.185.13 with HTTP; Thu, 8 Sep 2011 15:48:19 -0700 (PDT) In-Reply-To: <4E6940D3.4070801@freebsd.org> References: <4E6940D3.4070801@freebsd.org> Date: Thu, 8 Sep 2011 15:48:19 -0700 Message-ID: From: Peter Wemm To: Peter Grehan Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Mailman-Approved-At: Thu, 08 Sep 2011 23:24:08 +0000 Cc: "freebsd-hackers@freebsd.org" , "freebsd-arch@freebsd.org" Subject: Re: Soliciting opinions on an extension of the bootinfo structure X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Sep 2011 23:18:31 -0000 On Thu, Sep 8, 2011 at 3:25 PM, Peter Grehan wrote: >> I'm proposing an extension framework for the bootinfo structure used >> to pass information from the bootstrap/loader to the kernel. Although >> I'm only proposing this for the MIPS bootinfo, it's completely >> applicable to any of them. >> >> What I propose is adding an optional platform extension structure: >> bootinfo_pext, surrounded by #ifdef BOOTINFO_PEXT > > =A0Any reason not to put the vendor bits into another piece of loader met= adata > ? That seems the extensible way to add additional info from the loader, > rather than extending bootinfo (as was the case pre-loader days). > > later, It sounds like they're not using loader, which is probably a reasonable thing for their environment. --=20 Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com; KI6FJV "All of this is for nothing if we don't go to the stars" - JMS/B5 "If Java had true garbage collection, most programs would delete themselves upon execution." -- Robert Sewell From owner-freebsd-hackers@FreeBSD.ORG Fri Sep 9 07:57:41 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AEA611065672 for ; Fri, 9 Sep 2011 07:57:41 +0000 (UTC) (envelope-from decke@bluelife.at) Received: from groupware.itac.at (groupware.itac.at [91.205.172.99]) by mx1.freebsd.org (Postfix) with ESMTP id 0C2498FC0A for ; Fri, 9 Sep 2011 07:57:39 +0000 (UTC) Received: from home.bluelife.at (93.104.210.95) by groupware.itac.at (Axigen) with (AES256-SHA encrypted) ESMTPSA id 1E43E0; Fri, 9 Sep 2011 09:42:38 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Date: Fri, 09 Sep 2011 09:42:34 +0200 From: Bernhard Froehlich To: Jung-uk Kim In-Reply-To: <201109081811.47776.jkim@FreeBSD.org> References: <201109081811.47776.jkim@FreeBSD.org> Message-ID: <07100640b290b03063c14e064907494e@bluelife.at> X-Sender: decke@bluelife.at User-Agent: Roundcube Webmail/0.5.4 X-AxigenSpam-Level: 1 X-CTCH-RefID: str=0001.0A0B020D.4E69C369.00D1,ss=1,fgs=0 X-CTCH-VOD: Unknown X-CTCH-Spam: Unknown X-Mailman-Approved-At: Fri, 09 Sep 2011 10:33:00 +0000 Cc: freebsd-hackers@freebsd.org Subject: Re: Porting PathScale's EKOPath Compiler Suite X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Sep 2011 07:57:41 -0000 On Thu, 8 Sep 2011 18:11:45 -0400, Jung-uk Kim wrote: > I have done preliminary porting work of PathScale's open-sourced > EKOPath Compiler Suite (https://github.com/pathscale). > > http://people.freebsd.org/~jkim/ekopath-devel.tar.bz2 > > This includes experimental OpenMP support and PathDB. Unfortuntely, > PathDB builds fine but just crashes ATM. Both options are turned off > by default for now. Although it seems working fine for many > non-trivial C/C++/Fortran sources, please do not use it for any > serious project because I have seen few internal compiler errors and > crashes. Be aware of ugly hacks! ;-) > > I just wanted to share it now because it was on the WantedPorts list > on Wiki for a while. If anyone with more clues want to pick it up > from here, please feel free. Thanks a lot. I've updated the WantedPorts entry and added a link to the mail so that people find your work. -- Bernhard Fröhlich http://www.bluelife.at/ From owner-freebsd-hackers@FreeBSD.ORG Fri Sep 9 12:06:09 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6BDD2106566C for ; Fri, 9 Sep 2011 12:06:09 +0000 (UTC) (envelope-from peterjeremy@acm.org) Received: from mail34.syd.optusnet.com.au (mail34.syd.optusnet.com.au [211.29.133.218]) by mx1.freebsd.org (Postfix) with ESMTP id EC3788FC08 for ; Fri, 9 Sep 2011 12:06:08 +0000 (UTC) Received: from server.vk2pj.dyndns.org (c220-239-116-103.belrs4.nsw.optusnet.com.au [220.239.116.103]) by mail34.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id p89C64SG011051 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 9 Sep 2011 22:06:06 +1000 X-Bogosity: Ham, spamicity=0.000000 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.5/8.14.4) with ESMTP id p89C63iB065299; Fri, 9 Sep 2011 22:06:03 +1000 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.5/8.14.4/Submit) id p89C62fW065175; Fri, 9 Sep 2011 22:06:02 +1000 (EST) (envelope-from peter) Date: Fri, 9 Sep 2011 22:06:01 +1000 From: Peter Jeremy To: Manish Vachharajani Message-ID: <20110909120601.GA40207@server.vk2pj.dyndns.org> References: <20110906220115.GA25048@freebsd.org> <20110907061741.GC96277@server.vk2pj.dyndns.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="FL5UXtIhxfXey3p5" Content-Disposition: inline In-Reply-To: X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-hackers@freebsd.org Subject: Re: excessive use of gettimeofday(2) and other syscalls X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Sep 2011 12:06:09 -0000 --FL5UXtIhxfXey3p5 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2011-Sep-07 12:41:54 -0600, Manish Vachharajani wrote: >This is great info, thanks. Is it worth having some kind of >environment variable tunable (or even compile time tunable) to have a >"fast" gettimeofday then? Maybe. rwatson@ produced a preloadable .so to do this - see http://www.watson.org/~robert/freebsd/clock/ > Is there a complimentary body of code that >assumes gettimeofday is precise? I'm not aware of any but it's not necessarily trivial to identify such code - it's unlikely to fail outright but instead may deliver results that may not be as accurate as the author intended. I think a better way of looking at the problem is that some code was designed on the assumption that certain operations were cheap and therefore uses those operations more freely than it would have had those operations been more expensive. --=20 Peter Jeremy --FL5UXtIhxfXey3p5 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEARECAAYFAk5qASkACgkQ/opHv/APuIdg7wCePFYfNxkvqHlFoKgEE2PctPCI M/YAoKCLIvPpSPXM5GgitK11RmiC/8SH =mjFy -----END PGP SIGNATURE----- --FL5UXtIhxfXey3p5-- From owner-freebsd-hackers@FreeBSD.ORG Fri Sep 9 12:10:26 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AF999106566B; Fri, 9 Sep 2011 12:10:26 +0000 (UTC) (envelope-from aduane@juniper.net) Received: from exprod7og124.obsmtp.com (exprod7og124.obsmtp.com [64.18.2.26]) by mx1.freebsd.org (Postfix) with ESMTP id E33738FC1E; Fri, 9 Sep 2011 12:10:23 +0000 (UTC) Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob124.postini.com ([64.18.6.12]) with SMTP ID DSNKTmoCL6kXCHrgXle/ERquSMJfSE15xhhm@postini.com; Fri, 09 Sep 2011 05:10:25 PDT Received: from p-emfe01-wf.jnpr.net (172.28.145.24) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server (TLS) id 8.2.254.0; Fri, 9 Sep 2011 05:09:07 -0700 Received: from EMBX01-WF.jnpr.net ([fe80::8002:d3e7:4146:af5f]) by p-emfe01-wf.jnpr.net ([fe80::d0d1:653d:5b91:a123%11]) with mapi; Fri, 9 Sep 2011 08:09:06 -0400 From: Andrew Duane To: Peter Wemm , Peter Grehan Date: Fri, 9 Sep 2011 08:09:06 -0400 Thread-Topic: Soliciting opinions on an extension of the bootinfo structure Thread-Index: AcxueWlemEuOTorHT2+anNRGAHt0GQAb6YZA Message-ID: References: <4E6940D3.4070801@freebsd.org> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "freebsd-hackers@freebsd.org" , "freebsd-arch@freebsd.org" Subject: RE: Soliciting opinions on an extension of the bootinfo structure X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Sep 2011 12:10:26 -0000 That's correct. This is actually part of a larger effort to open up the MIP= S code to a range of new bootstraps. Some bootstraps use the bootinfo facil= ity extensively. It's an easy way to pass some simple information to the ke= rnel without the clutter of metadata and other such things. =A0................................... Andrew Duane Juniper Networks o=A0=A0=A0+1 978 589 0551 m=A0 +1 603-770-7088 aduane@juniper.net =A0 -----Original Message----- From: Peter Wemm [mailto:peter@wemm.org]=20 Sent: Thursday, September 08, 2011 6:48 PM To: Peter Grehan Cc: Andrew Duane; freebsd-hackers@freebsd.org; freebsd-arch@freebsd.org Subject: Re: Soliciting opinions on an extension of the bootinfo structure On Thu, Sep 8, 2011 at 3:25 PM, Peter Grehan wrote: >> I'm proposing an extension framework for the bootinfo structure used >> to pass information from the bootstrap/loader to the kernel. Although >> I'm only proposing this for the MIPS bootinfo, it's completely >> applicable to any of them. >> >> What I propose is adding an optional platform extension structure: >> bootinfo_pext, surrounded by #ifdef BOOTINFO_PEXT > > =A0Any reason not to put the vendor bits into another piece of loader met= adata > ? That seems the extensible way to add additional info from the loader, > rather than extending bootinfo (as was the case pre-loader days). > > later, It sounds like they're not using loader, which is probably a reasonable thing for their environment. --=20 Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com; KI6FJV "All of this is for nothing if we don't go to the stars" - JMS/B5 "If Java had true garbage collection, most programs would delete themselves upon execution." -- Robert Sewell From owner-freebsd-hackers@FreeBSD.ORG Fri Sep 9 12:22:40 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B2F7D106566C; Fri, 9 Sep 2011 12:22:40 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 89CF38FC16; Fri, 9 Sep 2011 12:22:40 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 3F96C46B0C; Fri, 9 Sep 2011 08:22:40 -0400 (EDT) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id CFE628A02E; Fri, 9 Sep 2011 08:22:39 -0400 (EDT) From: John Baldwin To: freebsd-hackers@freebsd.org Date: Fri, 9 Sep 2011 08:20:21 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110617; KDE/4.5.5; amd64; ; ) References: <4E6940D3.4070801@freebsd.org> In-Reply-To: <4E6940D3.4070801@freebsd.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201109090820.21116.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Fri, 09 Sep 2011 08:22:39 -0400 (EDT) Cc: Peter Grehan , "freebsd-arch@freebsd.org" Subject: Re: Soliciting opinions on an extension of the bootinfo structure X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Sep 2011 12:22:40 -0000 On Thursday, September 08, 2011 6:25:23 pm Peter Grehan wrote: > > I'm proposing an extension framework for the bootinfo structure used > > to pass information from the bootstrap/loader to the kernel. Although > > I'm only proposing this for the MIPS bootinfo, it's completely > > applicable to any of them. > > > > What I propose is adding an optional platform extension structure: > > bootinfo_pext, surrounded by #ifdef BOOTINFO_PEXT > > Any reason not to put the vendor bits into another piece of loader > metadata ? That seems the extensible way to add additional info from the > loader, rather than extending bootinfo (as was the case pre-loader days). I agree. The metadata appended to the end of the kernel is a better way to manage this. -- John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Fri Sep 9 12:32:23 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B4C04106564A; Fri, 9 Sep 2011 12:32:23 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 896CA8FC13; Fri, 9 Sep 2011 12:32:23 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 3FD1F46B0D; Fri, 9 Sep 2011 08:32:23 -0400 (EDT) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id B4DC38A02E; Fri, 9 Sep 2011 08:32:22 -0400 (EDT) From: John Baldwin To: freebsd-arch@freebsd.org Date: Fri, 9 Sep 2011 08:32:20 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110617; KDE/4.5.5; amd64; ; ) References: <4E6940D3.4070801@freebsd.org> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201109090832.20770.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Fri, 09 Sep 2011 08:32:22 -0400 (EDT) Cc: "freebsd-hackers@freebsd.org" , Peter Grehan , Peter Wemm Subject: Re: Soliciting opinions on an extension of the bootinfo structure X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Sep 2011 12:32:23 -0000 On Thursday, September 08, 2011 6:48:19 pm Peter Wemm wrote: > On Thu, Sep 8, 2011 at 3:25 PM, Peter Grehan wrote: > >> I'm proposing an extension framework for the bootinfo structure used > >> to pass information from the bootstrap/loader to the kernel. Although > >> I'm only proposing this for the MIPS bootinfo, it's completely > >> applicable to any of them. > >> > >> What I propose is adding an optional platform extension structure: > >> bootinfo_pext, surrounded by #ifdef BOOTINFO_PEXT > > > > Any reason not to put the vendor bits into another piece of loader metadata > > ? That seems the extensible way to add additional info from the loader, > > rather than extending bootinfo (as was the case pre-loader days). > > > > later, > > It sounds like they're not using loader, which is probably a > reasonable thing for their environment. That doesn't stop you from adding metadata to the kernel. It is just an array of variable length blobs appended after 'end'. Any boot loader can support adding metadata. -- John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Fri Sep 9 13:43:49 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3757B106566B for ; Fri, 9 Sep 2011 13:43:49 +0000 (UTC) (envelope-from ambrosehua@gmail.com) Received: from mail-gx0-f179.google.com (mail-gx0-f179.google.com [209.85.161.179]) by mx1.freebsd.org (Postfix) with ESMTP id E6A9D8FC08 for ; Fri, 9 Sep 2011 13:43:48 +0000 (UTC) Received: by gxk1 with SMTP id 1so1261750gxk.10 for ; Fri, 09 Sep 2011 06:43:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=if8McSCcnum/uPiV0PppMP8Mfpdydb9uHzpXQGAbbKE=; b=oZcHym22pHEF+PPO73R8u2vPkUFG918Zble/XXv1kokfiogaCz2GVq8BBh61VW0qY+ /DL1TCyiSseEiHpC8UEFNaFRTnE0Bntx+Lih2rBTxQmUnKND4Su197U6Rhlc1owEWO7n toGPvwd8j7xJhlyiCyN9kozAVNx9HVkHLeJYM= MIME-Version: 1.0 Received: by 10.42.147.194 with SMTP id o2mr656452icv.120.1315575827335; Fri, 09 Sep 2011 06:43:47 -0700 (PDT) Received: by 10.42.222.129 with HTTP; Fri, 9 Sep 2011 06:43:47 -0700 (PDT) In-Reply-To: <20110907151543.GA63310@freebsd.org> References: <20110906220115.GA25048@freebsd.org> <20110907061741.GC96277@server.vk2pj.dyndns.org> <20110907151543.GA63310@freebsd.org> Date: Fri, 9 Sep 2011 21:43:47 +0800 Message-ID: From: Paul Ambrose To: Alexander Best Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hackers@freebsd.org Subject: Re: excessive use of gettimeofday(2) and other syscalls X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Sep 2011 13:43:49 -0000 what version of chromium are you using? I use chromium-13.0.782.215 on amd64 8.2-stable, the gettimeofday call is far less than 20000 per second, about 20 per second, but I notice old version has this bug, but latest version has fixed it. Maybe you should update your chromium and try again. Firefox 5 and 6 has more gettimeofday call than 20000 per second on my amd64-8.2-stable box. 2011/9/7 Alexander Best > On Wed Sep 7 11, Peter Jeremy wrote: > > On 2011-Sep-06 16:44:48 -0600, Manish Vachharajani < > manishv@lineratesystems.com> wrote: > > >Under 7.3 (haven't checked 8 or 9) this issue crops up because the > > >time system call calls gettimeofday under the hood (see > > >lib/libc/gen/time.c). As a result, the kernel tries to get an > > >accurate subsecond resolution time that simply gets chopped to the > > >nearest second. > > > > Under 8.x and later, time(3) uses clock_gettime(CLOCK_SECOND,...) > > rather than gettimeofday(). This is intended to be much cheaper > > than gettimeofday(). > > > > On 2011-Sep-06 21:15:55 -0400, Rayson Ho wrote: > > >IMO, the time returned by gettimeofday does not need to be high > > >precision. There are higher resolution time APIs on Linux and I > > >believe the application programmers know when to use the slower but > > >more accurate clock API. > > > > There are 3 standard APIs for returning time of day: > > time(3) provides second precision > > gettimeofday(2) provides microsecond precision > > clock_gettime(2) provides nanosecond precision > > > > By default, FreeBSD attempts to provide resolution as close as > > possible to the precision - which makes the 2 system calls fairly > > expensive. In order to reduce the cost where the resolution isn't > > important, FreeBSD provides several non-standard clock types for > > clock_gettime(2). This approach differs from Linux - and it seems > > that there is a non-trivial body of code that assumes that calling > > gettimeofday() is very cheap. > > > > There is probably a good case for an API that provides a resolution > > of the order of a tick but there is no standard for this. > > chromium is triggering ~20.000 gettimeofday(2) calls per second on my > machine. > i'm running CURRENT on amd64. > > cheers. > alex > > > > > -- > > Peter Jeremy > > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://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 Sep 9 14:32:00 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1233) id 89C441065673; Fri, 9 Sep 2011 14:32:00 +0000 (UTC) Date: Fri, 9 Sep 2011 14:32:00 +0000 From: Alexander Best To: Paul Ambrose Message-ID: <20110909143200.GA26573@freebsd.org> References: <20110906220115.GA25048@freebsd.org> <20110907061741.GC96277@server.vk2pj.dyndns.org> <20110907151543.GA63310@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Cc: freebsd-hackers@freebsd.org Subject: Re: excessive use of gettimeofday(2) and other syscalls X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Sep 2011 14:32:00 -0000 On Fri Sep 9 11, Paul Ambrose wrote: > what version of chromium are you using? > I use chromium-13.0.782.215 on amd64 8.2-stable, the gettimeofday call is > far less than 20000 per second, about 20 per second, but I notice old > version has this bug, but latest version has fixed it. Maybe you should > update your chromium and try again. i'm running chromium-13.0.782.220 and sudo ktrace -di -tc -p1758; sleep 1; sudo ktrace -C; sudo kdump|grep gettimeofday|wc -l gives me 3056. so the number has decresed, yet i don't see why chromium needs to call gettimeofday(2) or any library function that triggers it more than 3000 times a second. also sudo ktrace -di -tc -p1758; sleep 1; sudo ktrace -C; sudo kdump|wc -l is returning 16695. that also seems like a pretty high syscall count in general for only 1 second. cheers. alex > > Firefox 5 and 6 has more gettimeofday call than 20000 per second on my > amd64-8.2-stable box. > > 2011/9/7 Alexander Best > > > On Wed Sep 7 11, Peter Jeremy wrote: > > > On 2011-Sep-06 16:44:48 -0600, Manish Vachharajani < > > manishv@lineratesystems.com> wrote: > > > >Under 7.3 (haven't checked 8 or 9) this issue crops up because the > > > >time system call calls gettimeofday under the hood (see > > > >lib/libc/gen/time.c). As a result, the kernel tries to get an > > > >accurate subsecond resolution time that simply gets chopped to the > > > >nearest second. > > > > > > Under 8.x and later, time(3) uses clock_gettime(CLOCK_SECOND,...) > > > rather than gettimeofday(). This is intended to be much cheaper > > > than gettimeofday(). > > > > > > On 2011-Sep-06 21:15:55 -0400, Rayson Ho wrote: > > > >IMO, the time returned by gettimeofday does not need to be high > > > >precision. There are higher resolution time APIs on Linux and I > > > >believe the application programmers know when to use the slower but > > > >more accurate clock API. > > > > > > There are 3 standard APIs for returning time of day: > > > time(3) provides second precision > > > gettimeofday(2) provides microsecond precision > > > clock_gettime(2) provides nanosecond precision > > > > > > By default, FreeBSD attempts to provide resolution as close as > > > possible to the precision - which makes the 2 system calls fairly > > > expensive. In order to reduce the cost where the resolution isn't > > > important, FreeBSD provides several non-standard clock types for > > > clock_gettime(2). This approach differs from Linux - and it seems > > > that there is a non-trivial body of code that assumes that calling > > > gettimeofday() is very cheap. > > > > > > There is probably a good case for an API that provides a resolution > > > of the order of a tick but there is no standard for this. > > > > chromium is triggering ~20.000 gettimeofday(2) calls per second on my > > machine. > > i'm running CURRENT on amd64. > > > > cheers. > > alex > > > > > > > > -- > > > Peter Jeremy > > > > > > _______________________________________________ > > freebsd-hackers@freebsd.org mailing list > > http://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 Sep 9 16:21:16 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E941F10657AA; Fri, 9 Sep 2011 16:21:16 +0000 (UTC) (envelope-from 6yearold@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 444C08FC08; Fri, 9 Sep 2011 16:21:16 +0000 (UTC) Received: by fxe4 with SMTP id 4so3596018fxe.13 for ; Fri, 09 Sep 2011 09:21:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=TU44aXuP6ZCwMGuWy1S6ninAh3oF3AQAnFi0dEvxVqc=; b=FNclo6uPWIIyAZ5T2c5n3ubX7L5AGTbYcewURGlWu2LveYC/+YH9Nysja4bcs5x453 wwp8PH0a3emVb9O/tsmQH10vHz0MR4xuUK7xCW3q1CuoiWVsuCUNkSF19F1JeGHvbwDO c7JaU0ZyAl0el5eMvoR41KjBXZOIM/Ex8BnU4= Received: by 10.223.22.15 with SMTP id l15mr1286812fab.85.1315583627265; Fri, 09 Sep 2011 08:53:47 -0700 (PDT) MIME-Version: 1.0 Received: by 10.152.38.229 with HTTP; Fri, 9 Sep 2011 08:53:27 -0700 (PDT) In-Reply-To: <201109081811.47776.jkim@FreeBSD.org> References: <201109081811.47776.jkim@FreeBSD.org> From: arrowdodger <6yearold@gmail.com> Date: Fri, 9 Sep 2011 19:53:27 +0400 Message-ID: To: Jung-uk Kim Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hackers@freebsd.org Subject: Re: Porting PathScale's EKOPath Compiler Suite X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Sep 2011 16:21:17 -0000 On Fri, Sep 9, 2011 at 2:11 AM, Jung-uk Kim wrote: > I have done preliminary porting work of PathScale's open-sourced > EKOPath Compiler Suite (https://github.com/pathscale). > > http://people.freebsd.org/~jkim/ekopath-devel.tar.bz2 > > This includes experimental OpenMP support and PathDB. Unfortuntely, > PathDB builds fine but just crashes ATM. Both options are turned off > by default for now. Although it seems working fine for many > non-trivial C/C++/Fortran sources, please do not use it for any > serious project because I have seen few internal compiler errors and > crashes. Be aware of ugly hacks! ;-) > > I just wanted to share it now because it was on the WantedPorts list > on Wiki for a while. If anyone with more clues want to pick it up > from here, please feel free. > > Cheers, > > Jung-uk Kim > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > I've tried to build your port on 8-STABLE and got this: [ 30%] Generating pscrt-static-x86_64/memcpy_em64t_c.o Error: Invalid target group option -TARG:processor=nocona !!! DevWarn during Reading WHIRL file: TODO: implement *skip* option !!! DevWarn during Reading WHIRL file: IPA_NODE::Skip is not yet implemented After removing CPUTYPE=nocona from /etc/make.conf i got: [ 45%] Generating openmp-static-x86_64/thread_c.o /usr/home/arr/ports/ekopath-devel/work/path64-suite/compiler/compiler/src/libopenmp/thread.c: In function 'gettid': /usr/home/arr/ports/ekopath-devel/work/path64-suite/compiler/compiler/src/libopenmp/thread.c:74: warning: implicit declaration of function 'thr_self' /usr/home/arr/ports/ekopath-devel/work/path64-suite/compiler/compiler/src/libopenmp/thread.c: In function '__pmp_thread_create': /usr/home/arr/ports/ekopath-devel/work/path64-suite/compiler/compiler/src/libopenmp/thread.c:515: error: 'MAP_ANONYMOUS' undeclared From owner-freebsd-hackers@FreeBSD.ORG Fri Sep 9 16:31:34 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E04E0106566B for ; Fri, 9 Sep 2011 16:31:34 +0000 (UTC) (envelope-from dieterbsd@engineer.com) Received: from mailout-us.gmx.com (mailout-us.gmx.com [74.208.5.67]) by mx1.freebsd.org (Postfix) with SMTP id 8B6008FC08 for ; Fri, 9 Sep 2011 16:31:34 +0000 (UTC) Received: (qmail 16148 invoked by uid 0); 9 Sep 2011 16:25:38 -0000 Received: from 67.206.186.142 by rms-us016 with HTTP Content-Type: text/plain; charset="utf-8" Date: Fri, 09 Sep 2011 12:25:36 -0400 From: "Dieter BSD" Message-ID: <20110909162537.183770@gmx.com> MIME-Version: 1.0 To: freebsd-hackers@freebsd.org X-Authenticated: #74169980 X-Flags: 0001 X-Mailer: GMX.com Web Mailer x-registered: 0 Content-Transfer-Encoding: 8bit X-GMX-UID: TksLKqAmzVK0IR3RHjUzURM/Njh6dI54 Subject: Re: excessive use of gettimeofday(2) and other syscalls X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Sep 2011 16:31:35 -0000 >> Firefox 5 and 6 has more gettimeofday call than 20000 per second on my >> amd64-8.2-stable box. > i don't see why chromium needs > to call gettimeofday(2) or any library function that triggers it more > than 3000 times a second. What the are web browsers doing that they "need" the clock so often? I suspect the answer is the same as why firefox uses significant amounts of CPU when it should be idle, why it uses memory without bound (I actually had to add ulimit to my shell's rc file :-( ), and so on. Using "links -g", "ktrace -di -tc -p6951; sleep 1; ktrace -C; kdump|wc -l" gives a typical count of 300-400, highest count seen: 1454. What we need, is a sanely written web browser that has the features we need. Unfortunately the last time I checked, links and dillo both lacked features needed for online shopping/banking. From owner-freebsd-hackers@FreeBSD.ORG Fri Sep 9 16:47:25 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 02DEC106566C; Fri, 9 Sep 2011 16:47:25 +0000 (UTC) (envelope-from cbergstrom@pathscale.com) Received: from mail-gw0-f49.google.com (mail-gw0-f49.google.com [74.125.83.49]) by mx1.freebsd.org (Postfix) with ESMTP id A75B08FC12; Fri, 9 Sep 2011 16:47:24 +0000 (UTC) Received: by gwb1 with SMTP id 1so1712342gwb.36 for ; Fri, 09 Sep 2011 09:47:24 -0700 (PDT) Received: by 10.68.11.232 with SMTP id t8mr516856pbb.384.1315586843467; Fri, 09 Sep 2011 09:47:23 -0700 (PDT) Received: from [192.168.1.34] (ppp-58-8-58-6.revip2.asianet.co.th. [58.8.58.6]) by mx.google.com with ESMTPS id i4sm21158587pbr.4.2011.09.09.09.47.21 (version=SSLv3 cipher=OTHER); Fri, 09 Sep 2011 09:47:22 -0700 (PDT) Message-ID: <4E6A438F.7020504@pathscale.com> Date: Fri, 09 Sep 2011 23:49:19 +0700 From: =?UTF-8?B?IkMuIEJlcmdzdHLDtm0i?= User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.9.2.7) Gecko/20101031 Lightning/1.0b2 Thunderbird/3.1.1 MIME-Version: 1.0 To: arrowdodger <6yearold@gmail.com> References: <201109081811.47776.jkim@FreeBSD.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, Jung-uk Kim Subject: Re: Porting PathScale's EKOPath Compiler Suite X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Sep 2011 16:47:25 -0000 On 09/ 9/11 10:53 PM, arrowdodger wrote: > On Fri, Sep 9, 2011 at 2:11 AM, Jung-uk Kim wrote: > >> I have done preliminary porting work of PathScale's open-sourced >> EKOPath Compiler Suite (https://github.com/pathscale). >> >> http://people.freebsd.org/~jkim/ekopath-devel.tar.bz2 >> >> This includes experimental OpenMP support and PathDB. Unfortuntely, >> PathDB builds fine but just crashes ATM. Both options are turned off >> by default for now. Although it seems working fine for many >> non-trivial C/C++/Fortran sources, please do not use it for any >> serious project because I have seen few internal compiler errors and >> crashes. Be aware of ugly hacks! ;-) >> >> I just wanted to share it now because it was on the WantedPorts list >> on Wiki for a while. If anyone with more clues want to pick it up >> from here, please feel free. >> >> Cheers, >> >> Jung-uk Kim >> _______________________________________________ >> freebsd-hackers@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" >> > I've tried to build your port on 8-STABLE and got this: > > [ 30%] Generating > pscrt-static-x86_64/memcpy_em64t_c.o > > Error: Invalid target group option > -TARG:processor=nocona > > !!! DevWarn during Reading WHIRL file: TODO: implement *skip* option > !!! DevWarn during Reading WHIRL file: IPA_NODE::Skip is not yet implemented > > After removing CPUTYPE=nocona from /etc/make.conf i got: > > [ 45%] Generating openmp-static-x86_64/thread_c.o > /usr/home/arr/ports/ekopath-devel/work/path64-suite/compiler/compiler/src/libopenmp/thread.c: > In function 'gettid': > /usr/home/arr/ports/ekopath-devel/work/path64-suite/compiler/compiler/src/libopenmp/thread.c:74: > warning: implicit declaration of function 'thr_self' > /usr/home/arr/ports/ekopath-devel/work/path64-suite/compiler/compiler/src/libopenmp/thread.c: > In function '__pmp_thread_create': > /usr/home/arr/ports/ekopath-devel/work/path64-suite/compiler/compiler/src/libopenmp/thread.c:515: > error: 'MAP_ANONYMOUS' undeclared Why do I feel like I'm not being heard at all? Do you people want to work with upstream and get your issues resolved or not? If so report bugs to *upstream* and please send any patches for review. http://bugs.pathscale.com # New JIRA and not 100% tested for community https://github.com/path64/compiler/issues # Github issues sucks, but there's people watching this space We also have mailing lists, irc and you can even bug me if you need help/have questions ./C From owner-freebsd-hackers@FreeBSD.ORG Fri Sep 9 17:26:06 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from [127.0.0.1] (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id 2C326106566B; Fri, 9 Sep 2011 17:26:06 +0000 (UTC) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: arrowdodger <6yearold@gmail.com> Date: Fri, 9 Sep 2011 13:25:54 -0400 User-Agent: KMail/1.6.2 References: <201109081811.47776.jkim@FreeBSD.org> In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201109091325.58322.jkim@FreeBSD.org> Cc: freebsd-hackers@freebsd.org Subject: Re: Porting PathScale's EKOPath Compiler Suite X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Sep 2011 17:26:06 -0000 On Friday 09 September 2011 11:53 am, arrowdodger wrote: > On Fri, Sep 9, 2011 at 2:11 AM, Jung-uk Kim wrote: > > I have done preliminary porting work of PathScale's open-sourced > > EKOPath Compiler Suite (https://github.com/pathscale). > > > > http://people.freebsd.org/~jkim/ekopath-devel.tar.bz2 > > > > This includes experimental OpenMP support and PathDB. > > Unfortuntely, PathDB builds fine but just crashes ATM. Both > > options are turned off by default for now. Although it seems > > working fine for many non-trivial C/C++/Fortran sources, please > > do not use it for any serious project because I have seen few > > internal compiler errors and crashes. Be aware of ugly hacks! > > ;-) > > > > I just wanted to share it now because it was on the WantedPorts > > list on Wiki for a while. If anyone with more clues want to pick > > it up from here, please feel free. > > > > Cheers, > > > > Jung-uk Kim > > _______________________________________________ > > freebsd-hackers@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > > To unsubscribe, send any mail to > > "freebsd-hackers-unsubscribe@freebsd.org" > > I've tried to build your port on 8-STABLE and got this: > > [ 30%] Generating > pscrt-static-x86_64/memcpy_em64t_c.o > > Error: Invalid target group option > -TARG:processor=nocona > > !!! DevWarn during Reading WHIRL file: TODO: implement *skip* > option !!! DevWarn during Reading WHIRL file: IPA_NODE::Skip is not > yet implemented > > After removing CPUTYPE=nocona from /etc/make.conf i got: > > [ 45%] Generating openmp-static-x86_64/thread_c.o > /usr/home/arr/ports/ekopath-devel/work/path64-suite/compiler/compil >er/src/libopenmp/thread.c: In function 'gettid': > /usr/home/arr/ports/ekopath-devel/work/path64-suite/compiler/compil >er/src/libopenmp/thread.c:74: warning: implicit declaration of > function 'thr_self' > /usr/home/arr/ports/ekopath-devel/work/path64-suite/compiler/compil >er/src/libopenmp/thread.c: In function '__pmp_thread_create': > /usr/home/arr/ports/ekopath-devel/work/path64-suite/compiler/compil >er/src/libopenmp/thread.c:515: error: 'MAP_ANONYMOUS' undeclared Please try this: http://people.freebsd.org/~jkim/ekopath-devel_2.tar.bz2 Jung-uk Kim From owner-freebsd-hackers@FreeBSD.ORG Fri Sep 9 17:33:00 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from [127.0.0.1] (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id B2247106564A; Fri, 9 Sep 2011 17:33:00 +0000 (UTC) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-hackers@freebsd.org Date: Fri, 9 Sep 2011 13:32:51 -0400 User-Agent: KMail/1.6.2 References: <201109081811.47776.jkim@FreeBSD.org> <4E6A438F.7020504@pathscale.com> In-Reply-To: <4E6A438F.7020504@pathscale.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Message-Id: <201109091332.53594.jkim@FreeBSD.org> Cc: "C. =?iso-8859-1?q?Bergstr=F6m?=" , arrowdodger <6yearold@gmail.com> Subject: Re: Porting PathScale's EKOPath Compiler Suite X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Sep 2011 17:33:00 -0000 On Friday 09 September 2011 12:49 pm, "C. Bergstrm" wrote: > On 09/ 9/11 10:53 PM, arrowdodger wrote: > > On Fri, Sep 9, 2011 at 2:11 AM, Jung-uk Kim wrote: > >> I have done preliminary porting work of PathScale's open-sourced > >> EKOPath Compiler Suite (https://github.com/pathscale). > >> > >> http://people.freebsd.org/~jkim/ekopath-devel.tar.bz2 > >> > >> This includes experimental OpenMP support and PathDB. > >> Unfortuntely, PathDB builds fine but just crashes ATM. Both > >> options are turned off by default for now. Although it seems > >> working fine for many non-trivial C/C++/Fortran sources, please > >> do not use it for any serious project because I have seen few > >> internal compiler errors and crashes. Be aware of ugly hacks! > >> ;-) > >> > >> I just wanted to share it now because it was on the WantedPorts > >> list on Wiki for a while. If anyone with more clues want to > >> pick it up from here, please feel free. > >> > >> Cheers, > >> > >> Jung-uk Kim > >> _______________________________________________ > >> freebsd-hackers@freebsd.org mailing list > >> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > >> To unsubscribe, send any mail to > >> "freebsd-hackers-unsubscribe@freebsd.org" > > > > I've tried to build your port on 8-STABLE and got this: > > > > [ 30%] Generating > > pscrt-static-x86_64/memcpy_em64t_c.o > > > > Error: Invalid target group option > > -TARG:processor=nocona > > > > !!! DevWarn during Reading WHIRL file: TODO: implement *skip* > > option !!! DevWarn during Reading WHIRL file: IPA_NODE::Skip is > > not yet implemented > > > > After removing CPUTYPE=nocona from /etc/make.conf i got: > > > > [ 45%] Generating openmp-static-x86_64/thread_c.o > > /usr/home/arr/ports/ekopath-devel/work/path64-suite/compiler/comp > >iler/src/libopenmp/thread.c: In function 'gettid': > > /usr/home/arr/ports/ekopath-devel/work/path64-suite/compiler/comp > >iler/src/libopenmp/thread.c:74: warning: implicit declaration of > > function 'thr_self' > > /usr/home/arr/ports/ekopath-devel/work/path64-suite/compiler/comp > >iler/src/libopenmp/thread.c: In function '__pmp_thread_create': > > /usr/home/arr/ports/ekopath-devel/work/path64-suite/compiler/comp > >iler/src/libopenmp/thread.c:515: error: 'MAP_ANONYMOUS' undeclared > > Why do I feel like I'm not being heard at all? Don't worry, I hear you. > Do you people want to work with upstream and get your issues > resolved or not? If so report bugs to *upstream* and please send > any patches for review. > > http://bugs.pathscale.com # New JIRA and not 100% tested for > community https://github.com/path64/compiler/issues # Github issues > sucks, but there's people watching this space > > We also have mailing lists, irc and you can even bug me if you need > help/have questions Please relax, it's *preliminary* work in progress. When I feel I have enough patches to submit, I will. Jung-uk Kim From owner-freebsd-hackers@FreeBSD.ORG Fri Sep 9 18:46:53 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1233) id B2BA91065670; Fri, 9 Sep 2011 18:46:53 +0000 (UTC) Date: Fri, 9 Sep 2011 18:46:53 +0000 From: Alexander Best To: Dieter BSD Message-ID: <20110909184653.GA64971@freebsd.org> References: <20110909162537.183770@gmx.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110909162537.183770@gmx.com> Cc: freebsd-hackers@freebsd.org Subject: Re: excessive use of gettimeofday(2) and other syscalls X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Sep 2011 18:46:53 -0000 On Fri Sep 9 11, Dieter BSD wrote: > >> Firefox 5 and 6 has more gettimeofday call than 20000 per second on my > >> amd64-8.2-stable box. > > > i don't see why chromium needs > > to call gettimeofday(2) or any library function that triggers it more > > than 3000 times a second. > > What the are web browsers doing that they "need" the clock > so often? > > I suspect the answer is the same as why firefox uses significant amounts > of CPU when it should be idle, why it uses memory without bound > (I actually had to add ulimit to my shell's rc file :-( ), and > so on. > > Using "links -g", > "ktrace -di -tc -p6951; sleep 1; ktrace -C; kdump|wc -l" > gives a typical count of 300-400, highest count seen: 1454. well that measurement is probably unfair. my measurements included all opened tabs (~ 15), running plugins and extensions. if i disable all of those extra stuff and use only a single tab, chromium produces less syscalls than links: 270 cheers. alex > > What we need, is a sanely written web browser that has the > features we need. Unfortunately the last time I checked, > links and dillo both lacked features needed for online > shopping/banking. From owner-freebsd-hackers@FreeBSD.ORG Fri Sep 9 18:59:09 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1233) id 429371065670; Fri, 9 Sep 2011 18:59:09 +0000 (UTC) Date: Fri, 9 Sep 2011 18:59:09 +0000 From: Alexander Best To: Dieter BSD Message-ID: <20110909185909.GA66131@freebsd.org> References: <20110909162537.183770@gmx.com> <20110909184653.GA64971@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110909184653.GA64971@freebsd.org> Cc: freebsd-hackers@freebsd.org Subject: Re: excessive use of gettimeofday(2) and other syscalls X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Sep 2011 18:59:09 -0000 On Fri Sep 9 11, Alexander Best wrote: > On Fri Sep 9 11, Dieter BSD wrote: > > >> Firefox 5 and 6 has more gettimeofday call than 20000 per second on my > > >> amd64-8.2-stable box. > > > > > i don't see why chromium needs > > > to call gettimeofday(2) or any library function that triggers it more > > > than 3000 times a second. > > > > What the are web browsers doing that they "need" the clock > > so often? > > > > I suspect the answer is the same as why firefox uses significant amounts > > of CPU when it should be idle, why it uses memory without bound > > (I actually had to add ulimit to my shell's rc file :-( ), and > > so on. > > > > Using "links -g", > > "ktrace -di -tc -p6951; sleep 1; ktrace -C; kdump|wc -l" > > gives a typical count of 300-400, highest count seen: 1454. > > well that measurement is probably unfair. my measurements included all opened > tabs (~ 15), running plugins and extensions. if i disable all of those extra > stuff and use only a single tab, chromium produces less syscalls than links: > > 270 ...however sites such as facebook produce a much higher syscall peek under chromium. with only one tab opened with youtube.com in it, chromium has a typical syscall count of 700-2000. i guess this is due to stuff like js, html5 and friends. if i enable the flash plugins with only 1 single tab (youtube.com), the syscall count climbs to ~ 8000 with a peak at 19000 when youtube.com wasn't completely loaded. so the high syscall count is not only chromiums fault, but a combination of chromium, flash and the linuxulator. i believe further linuxulator improvements might reduce syscalls in this scenario. also with chromium 15, the syscall count is supposed to drop quite noticably (as mentioned in a previous message). cheers. alex > > cheers. > alex > > > > > What we need, is a sanely written web browser that has the > > features we need. Unfortunately the last time I checked, > > links and dillo both lacked features needed for online > > shopping/banking. From owner-freebsd-hackers@FreeBSD.ORG Fri Sep 9 22:38:40 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from [127.0.0.1] (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id 916EF1065670 for ; Fri, 9 Sep 2011 22:38:39 +0000 (UTC) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-hackers@freebsd.org Date: Fri, 9 Sep 2011 18:38:17 -0400 User-Agent: KMail/1.6.2 References: <201109081811.47776.jkim@FreeBSD.org> In-Reply-To: <201109081811.47776.jkim@FreeBSD.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201109091838.24867.jkim@FreeBSD.org> Subject: Re: Porting PathScale's EKOPath Compiler Suite X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Sep 2011 22:38:40 -0000 On Thursday 08 September 2011 06:11 pm, Jung-uk Kim wrote: > I have done preliminary porting work of PathScale's open-sourced > EKOPath Compiler Suite (https://github.com/pathscale). > > http://people.freebsd.org/~jkim/ekopath-devel.tar.bz2 I just uploaded a new tarball, ekopath-devel-20110909.bz2. The above URL is now symlinked to it. This includes PATHAS option (which enables yasm-based assembler) and other minor improvements. > Unfortuntely, PathDB builds fine but just crashes ATM. When PathDB is compiled with GCC, it doesn't crash, BTW. I haven't done any investigation yet. Cheers, Jung-uk Kim From owner-freebsd-hackers@FreeBSD.ORG Fri Sep 9 23:01:23 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from [127.0.0.1] (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id 003A11065670 for ; Fri, 9 Sep 2011 23:01:22 +0000 (UTC) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-hackers@freebsd.org Date: Fri, 9 Sep 2011 19:01:12 -0400 User-Agent: KMail/1.6.2 References: <201109081811.47776.jkim@FreeBSD.org> <201109091838.24867.jkim@FreeBSD.org> In-Reply-To: <201109091838.24867.jkim@FreeBSD.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201109091901.15060.jkim@FreeBSD.org> Subject: Re: Porting PathScale's EKOPath Compiler Suite X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Sep 2011 23:01:23 -0000 On Friday 09 September 2011 06:38 pm, Jung-uk Kim wrote: > On Thursday 08 September 2011 06:11 pm, Jung-uk Kim wrote: > > I have done preliminary porting work of PathScale's open-sourced > > EKOPath Compiler Suite (https://github.com/pathscale). > > > > http://people.freebsd.org/~jkim/ekopath-devel.tar.bz2 > > I just uploaded a new tarball, ekopath-devel-20110909.bz2. The real path is http://people.freebsd.org/~jkim/ekopath-devel-20110909.tar.bz2 Sorry for the typo. Jung-uk Kim From owner-freebsd-hackers@FreeBSD.ORG Sat Sep 10 08:09:40 2011 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D620D106564A for ; Sat, 10 Sep 2011 08:09:40 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from tower.berklix.org (tower.berklix.org [83.236.223.114]) by mx1.freebsd.org (Postfix) with ESMTP id 6AB0D8FC0A for ; Sat, 10 Sep 2011 08:09:39 +0000 (UTC) Received: from mart.js.berklix.net (p5DCBE045.dip.t-dialin.net [93.203.224.69]) (authenticated bits=0) by tower.berklix.org (8.14.2/8.14.2) with ESMTP id p8A89ZCP047583; Sat, 10 Sep 2011 08:09:36 GMT (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by mart.js.berklix.net (8.14.3/8.14.3) with ESMTP id p8A89Tbs081087; Sat, 10 Sep 2011 10:09:29 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.4/8.14.4) with ESMTP id p8A89AbU098767; Sat, 10 Sep 2011 08:09:29 GMT (envelope-from jhs@fire.js.berklix.net) Message-Id: <201109100809.p8A89AbU098767@fire.js.berklix.net> To: hackers@freebsd.org From: "Julian H. Stacey" Organization: http://www.berklix.com BSD Linux Unix Consultancy, Munich Germany User-agent: EXMH on FreeBSD http://www.berklix.com/free/ X-URL: http://www.berklix.com/~jhs/cv/ Date: Sat, 10 Sep 2011 10:09:10 +0200 Sender: jhs@berklix.com Cc: kubito@gmail.com, Julian Seward Subject: man bzip2 - suggest we add to See Also X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Sep 2011 08:09:40 -0000 [ Resend as I missed an '@' in address of author jseward@ I suggest we should add a See Also section to man bzip2, FreeBSD-8.2-RELEASE & current man bzip2 .../-current/src/contrib/bzip2/bzip2.1 adding URLs http://www.7-zip.org/download.html -> http://www.freshports.org/archivers/p7zip/ as currently no reference is made to 7zip or 7-zip Quote from: http://www.minix3.org/download/ The best known lossless compression algorithm is implemented in the bzip2 program. It also has extremely fast decompression. The popular 7zip archiver for Windows supports it too. No send-pr done as others cc'd know more about this: Julian Seward, jseward@bzip.org author in man bzip2 kubito@gmail.com ports/archiver/p7zip Easiest if jseward@ adds it ? Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Reply below, not above; Indent with "> "; Cumulative like a play script. Format: Plain text. Not HTML, multipart/alternative, base64, quoted-printable. http://www.softwarefreedomday.org 17th Sept, http://berklix.org/sfd/ Oct. From owner-freebsd-hackers@FreeBSD.ORG Sat Sep 10 18:08:47 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D0B37106564A for ; Sat, 10 Sep 2011 18:08:47 +0000 (UTC) (envelope-from cattaneo.riccardo@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 6A1328FC0C for ; Sat, 10 Sep 2011 18:08:47 +0000 (UTC) Received: by fxe4 with SMTP id 4so4630714fxe.13 for ; Sat, 10 Sep 2011 11:08:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:content-type:content-transfer-encoding:subject:date:message-id :to:mime-version:x-mailer; bh=/eYgZOf8t40TSyltio5cGF44iqhbRSlx0u475R8Uras=; b=Z8zDQ54eXBSLmYAH6l5l1ARu/c7+lEis/vtzSzLwb9XF/MeEUql42tYbEOV276673R ZE6TB+sJPNuEUiPc/2z0PCiez2eDyC/t3QqVd36A2rv9MA6sTJniG7QlC5uOl1NCtwOb w0t61eb+EuZKKziF5N63tL7mEyyxviTo3G0oA= Received: by 10.223.55.209 with SMTP id v17mr361349fag.77.1315676384875; Sat, 10 Sep 2011 10:39:44 -0700 (PDT) Received: from [192.168.129.137] ([79.171.164.133]) by mx.google.com with ESMTPS id l21sm4828132fac.8.2011.09.10.10.39.36 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 10 Sep 2011 10:39:43 -0700 (PDT) From: Riccardo Cattaneo Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Sat, 10 Sep 2011 19:39:19 +0200 Message-Id: <023BD0FF-053C-4DCB-81EA-5D69B2411819@gmail.com> To: freebsd-hackers@freebsd.org Mime-Version: 1.0 (Apple Message framework v1084) X-Mailer: Apple Mail (2.1084) Subject: Re: Kernel timers infrastructure X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Sep 2011 18:08:47 -0000 Hi all, Me in the same situation: university project, freebsd os, required to = call a certain function X times/second (say, uprintf). Got no luck till now :( Thanks Riccardo= From owner-freebsd-hackers@FreeBSD.ORG Sat Sep 10 20:35:09 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 327FD106566B for ; Sat, 10 Sep 2011 20:35:09 +0000 (UTC) (envelope-from freebsd-hackers@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id E38EC8FC0A for ; Sat, 10 Sep 2011 20:35:08 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1R2UGY-0005TR-2A for freebsd-hackers@freebsd.org; Sat, 10 Sep 2011 22:35:06 +0200 Received: from 187.101.120.126 ([187.101.120.126]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 10 Sep 2011 22:35:06 +0200 Received: from rakuco by 187.101.120.126 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 10 Sep 2011 22:35:06 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-hackers@freebsd.org From: Raphael Kubo da Costa Date: Sat, 10 Sep 2011 17:28:44 -0300 Lines: 30 Message-ID: <8762l087lv.fsf@FreeBSD.org> References: <201109100809.p8A89AbU098767@fire.js.berklix.net> Mime-Version: 1.0 Content-Type: text/plain X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: 187.101.120.126 User-Agent: Gnus/5.110018 (No Gnus v0.18) Emacs/23.3 (berkeley-unix) Cancel-Lock: sha1:4eVS6RxQmwxBr47pKkOQwSK9ex8= Subject: Re: man bzip2 - suggest we add to See Also X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Sep 2011 20:35:09 -0000 Resending the answer to hackers@ with my subscribed mail address. "Julian H. Stacey" writes: > I suggest we should add a See Also section to man bzip2, > > FreeBSD-8.2-RELEASE & current man bzip2 > .../-current/src/contrib/bzip2/bzip2.1 > > adding URLs > http://www.7-zip.org/download.html -> > http://www.freshports.org/archivers/p7zip/ > > as currently no reference is made to 7zip or 7-zip > > Quote from: http://www.minix3.org/download/ > The best known lossless compression algorithm is implemented > in the bzip2 program. It also has extremely fast decompression. > The popular 7zip archiver for Windows supports it too. Speaking with my p7zip maintainer hat on, I don't have anything to add to the proposal (any kind of change wouldn't involve that port anyway). As a user, though, I don't really see this being really necessary (dunno if there's some documentation policy with regards to recommending ports software in a base man page). 7zip itself is a Windows program, p7zip is done by a guy who looks at the 7zip code after it's released and tunes it to run on Unix. In the end, it's Julian's call IMO.