From owner-freebsd-hackers@FreeBSD.ORG Sun Jan 15 08:09:51 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C550716A41F for ; Sun, 15 Jan 2006 08:09:51 +0000 (GMT) (envelope-from ashok.shrestha@gmail.com) Received: from uproxy.gmail.com (uproxy.gmail.com [66.249.92.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3128F43D46 for ; Sun, 15 Jan 2006 08:09:51 +0000 (GMT) (envelope-from ashok.shrestha@gmail.com) Received: by uproxy.gmail.com with SMTP id o2so338573uge for ; Sun, 15 Jan 2006 00:09:50 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:mime-version:content-type:content-transfer-encoding:content-disposition; b=q5Tu3eivXGMQ8wTr/t0HWVD7/Qpn+Dz+8TTZaE9VzOwDX2PQdRYPzh5XvmIB3+X0kfFNpW2IiOlvE02D4uS3KcAJiu8lY1wjpR26+etCau+hZkmlrDwn8wqBkW0p2EpeM5CzAeVoapjS2FkOvXz8snKx484D6udn7IyCZH0GeBI= Received: by 10.48.30.20 with SMTP id d20mr159308nfd; Sat, 14 Jan 2006 23:45:30 -0800 (PST) Received: by 10.49.20.15 with HTTP; Sat, 14 Jan 2006 23:45:30 -0800 (PST) Message-ID: <79e2026f0601142345x1a9269bdl3153d1bb110be08d@mail.gmail.com> Date: Sun, 15 Jan 2006 02:45:30 -0500 From: Ashok Shrestha To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Cc: Brandon Flowers Subject: speed up port compiling using RAM (tmpfs) ??? 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, 15 Jan 2006 08:09:51 -0000 Hi, I am curious to know if there is a way to compile a port such as X11 or KDE faster. I know in Gentoo, you can mount a part of RAM and compile in that. This substantially decreases the compile time. Reference: http://gentoo-wiki.com/TIP_Speeding_up_portage_with_tmpfs Does anyone know how to do this in Freebsd? -- Ashok Shrestha From owner-freebsd-hackers@FreeBSD.ORG Sun Jan 15 09:32:37 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CEAD216A41F for ; Sun, 15 Jan 2006 09:32:37 +0000 (GMT) (envelope-from anupamdeshpande@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 580B843D45 for ; Sun, 15 Jan 2006 09:32:37 +0000 (GMT) (envelope-from anupamdeshpande@gmail.com) Received: by wproxy.gmail.com with SMTP id 71so958578wri for ; Sun, 15 Jan 2006 01:32:36 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=Uaf36JJL0xlOvUFugd79ZPepymlpePfkF5IHkWhKALirn4kryzWrCQrkpgc+PmUYy6y2xolXsGSkK44iujj8FdQ+ZQLZi1ZKxC+KPRGwREmZywmote+ldeEDUco0CpHexAXx2N0CvC/fAf50i5pNtw8XLAZnil3Dx9bvM+jcqaI= Received: by 10.65.177.10 with SMTP id e10mr2407995qbp; Sun, 15 Jan 2006 01:32:36 -0800 (PST) Received: by 10.65.236.12 with HTTP; Sun, 15 Jan 2006 01:32:36 -0800 (PST) Message-ID: <25da4ac50601150132y642ca77bq539f4fb49e517e8d@mail.gmail.com> Date: Sun, 15 Jan 2006 15:02:36 +0530 From: Anupam Deshpande To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Taking a process of the runqueue. 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, 15 Jan 2006 09:32:37 -0000 Hello, How can i take a process of the runqueue ? i do not want that process and contained threads to be scheduled for some time.Then i may again put that process in the runqueue. TIA. Regards, Anupam From owner-freebsd-hackers@FreeBSD.ORG Sun Jan 15 09:34:53 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DFA8516A422 for ; Sun, 15 Jan 2006 09:34:53 +0000 (GMT) (envelope-from victor@bsdes.net) Received: from alf.dyndns.ws (244.Red-217-126-240.staticIP.rima-tde.net [217.126.240.244]) by mx1.FreeBSD.org (Postfix) with ESMTP id DB0E943D4C for ; Sun, 15 Jan 2006 09:34:52 +0000 (GMT) (envelope-from victor@bsdes.net) Received: from alf.dyndns.ws (pato.euesrg02.net [192.168.0.3]) by alf.dyndns.ws (8.13.1/8.13.1) with ESMTP id k0F9Yo9L031796 for ; Sun, 15 Jan 2006 10:34:50 +0100 (CET) (envelope-from victor@bsdes.net) Date: Sun, 15 Jan 2006 10:34:49 +0100 From: Victor Balada Diaz To: freebsd-hackers@freebsd.org Message-ID: <20060115093449.GA655@pato.euesrg02.net> References: <79e2026f0601142345x1a9269bdl3153d1bb110be08d@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <79e2026f0601142345x1a9269bdl3153d1bb110be08d@mail.gmail.com> User-Agent: Mutt/1.4.2.1i Subject: Re: speed up port compiling using RAM (tmpfs) ??? 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, 15 Jan 2006 09:34:54 -0000 On Sun, Jan 15, 2006 at 02:45:30AM -0500, Ashok Shrestha wrote: > Hi, > > I am curious to know if there is a way to compile a port such as X11 > or KDE faster. > > I know in Gentoo, you can mount a part of RAM and compile in that. > This substantially decreases the compile time. Reference: > http://gentoo-wiki.com/TIP_Speeding_up_portage_with_tmpfs > > Does anyone know how to do this in Freebsd? You should take a look at mdconfig(8) and ports(7). With mdconfig you create the ram-based disk and with WRKDIRPREFIX you tell the ports to use that disk instead of the default workdir. -- La prueba mas fehaciente de que existe vida inteligente en otros planetas, es que no han intentado contactar con nosotros. From owner-freebsd-hackers@FreeBSD.ORG Sun Jan 15 09:46:08 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E522516A41F for ; Sun, 15 Jan 2006 09:46:08 +0000 (GMT) (envelope-from kjelderg@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 683E043D45 for ; Sun, 15 Jan 2006 09:46:08 +0000 (GMT) (envelope-from kjelderg@gmail.com) Received: by zproxy.gmail.com with SMTP id 9so915425nzo for ; Sun, 15 Jan 2006 01:46:08 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:from:to:subject:date:user-agent:cc:references:in-reply-to:mime-version:content-type:content-transfer-encoding:message-id; b=fJYuVBWHDfc4boIX+2tHv7qU5QhJ4WIiKYte5ti2x6vQ7sysXWgTC7yD2VN6GzBTgodc8bWYk5L7VM42tNDAjXWL9SE++4dvEiWD1FP8gAu4NTiJzFvpm1o0K+OnPVv+tRFmODDMro9kn7XHBHA/g6zUT/RcNjef/3FzfHP41AI= Received: by 10.36.119.20 with SMTP id r20mr3941000nzc; Sun, 15 Jan 2006 01:46:07 -0800 (PST) Received: from ?192.168.0.53? ( [221.186.3.89]) by mx.gmail.com with ESMTP id 38sm4422560nza.2006.01.15.01.46.06; Sun, 15 Jan 2006 01:46:07 -0800 (PST) From: Eric Kjeldergaard To: freebsd-hackers@freebsd.org Date: Sun, 15 Jan 2006 18:45:33 +0900 User-Agent: KMail/1.9.1 References: <79e2026f0601142345x1a9269bdl3153d1bb110be08d@mail.gmail.com> In-Reply-To: <79e2026f0601142345x1a9269bdl3153d1bb110be08d@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1239541.lUXa9qxA6j"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200601151845.39425.kjelderg@gmail.com> Cc: Ashok Shrestha , Brandon Flowers Subject: Re: speed up port compiling using RAM (tmpfs) ??? 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, 15 Jan 2006 09:46:09 -0000 --nextPart1239541.lUXa9qxA6j Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline =E6=97=A5=E6=9B=9C=E6=97=A5 15 1=E6=9C=88 2006 16:45=E3=80=81Ashok Shrestha= =E3=81=95=E3=82=93=E3=81=AF=E6=9B=B8=E3=81=8D=E3=81=BE=E3=81=97=E3=81=9F: > Hi, > > I am curious to know if there is a way to compile a port such as X11 > or KDE faster. > > I know in Gentoo, you can mount a part of RAM and compile in that. > This substantially decreases the compile time. Reference: > http://gentoo-wiki.com/TIP_Speeding_up_portage_with_tmpfs > > Does anyone know how to do this in Freebsd? Sure. Read the ports(7) man page paying special attention to the WRKDIRPRE= =46IX=20 variable. Then man mount_mfs and mdconfig. Those should do the trick. Eric =2D-=20 The signature is a location used to give a personalised feel to each E-mail= =20 without having to personalise each E-mail. --nextPart1239541.lUXa9qxA6j Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDyhnDSMnO3Fce5JgRAmdGAJsEYYOgy0tr+M5HMl9O3xKfLU9IEQCghhR/ Uar+K+9wd3y/GNcHhj9sxjU= =U+OS -----END PGP SIGNATURE----- --nextPart1239541.lUXa9qxA6j-- From owner-freebsd-hackers@FreeBSD.ORG Sun Jan 15 11:36:29 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D23F316A41F for ; Sun, 15 Jan 2006 11:36:29 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7DAE343D45 for ; Sun, 15 Jan 2006 11:36:29 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id BBDFF46B88; Sun, 15 Jan 2006 06:36:26 -0500 (EST) Date: Sun, 15 Jan 2006 11:36:52 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: prime In-Reply-To: <1fa17f810601141109u3e3a0586ud3b3cc86ebc6e80@mail.gmail.com> Message-ID: <20060115113523.O38874@fledge.watson.org> References: <1fa17f810601122232l25551bc5n4e4a01ff6b7921e@mail.gmail.com> <1fa17f810601130220h521590banff7d775a8bd4eaa6@mail.gmail.com> <1fa17f810601141109u3e3a0586ud3b3cc86ebc6e80@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-hackers@freebsd.org, Tiffany Snyder Subject: Re: How priority propagation works on read/write lock? 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, 15 Jan 2006 11:36:29 -0000 On Sun, 15 Jan 2006, prime wrote: > On 1/15/06, Tiffany Snyder wrote: >> >> Does FreeBSD support rwlocks? ... > FreeBSD supports sx now,see sx(9).sx has the same semanteme > as rwlock. While semantically they are very simila, John Baldwin has a work-in-progress implementation of rwlock's in Perforce. Given the progress he appears to be making, I imagine we'll see it in CVS within a week or two. Robert N M Watson From owner-freebsd-hackers@FreeBSD.ORG Sun Jan 15 15:02:55 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 49B7316A41F for ; Sun, 15 Jan 2006 15:02:55 +0000 (GMT) (envelope-from keramida@ceid.upatras.gr) Received: from nic.ach.sch.gr (nic.sch.gr [194.63.238.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 93D7843D46 for ; Sun, 15 Jan 2006 15:02:54 +0000 (GMT) (envelope-from keramida@ceid.upatras.gr) Received: (qmail 15202 invoked by uid 207); 15 Jan 2006 15:02:52 -0000 Received: from keramida@ceid.upatras.gr by nic by uid 201 with qmail-scanner-1.21 (sophie: 3.04/2.30/3.97. Clear:RC:1(81.186.70.138):. Processed in 0.086547 secs); 15 Jan 2006 15:02:52 -0000 Received: from dialup138.ach.sch.gr (HELO flame.pc) ([81.186.70.138]) (envelope-sender ) by nic.sch.gr (qmail-ldap-1.03) with SMTP for ; 15 Jan 2006 15:02:52 -0000 Received: by flame.pc (Postfix, from userid 1001) id 254131178E; Sun, 15 Jan 2006 17:01:13 +0200 (EET) Date: Sun, 15 Jan 2006 17:01:13 +0200 From: Giorgos Keramidas To: Anupam Deshpande Message-ID: <20060115150113.GA81172@flame.pc> References: <25da4ac50601150132y642ca77bq539f4fb49e517e8d@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <25da4ac50601150132y642ca77bq539f4fb49e517e8d@mail.gmail.com> Cc: freebsd-hackers@freebsd.org Subject: Re: Taking a process of the runqueue. 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, 15 Jan 2006 15:02:55 -0000 On 2006-01-15 15:02, Anupam Deshpande wrote: > Hello, > How can i take a process of the runqueue ? i do not want that > process and contained threads to be scheduled for some time.Then i may > again put that process in the runqueue. By sending a STOP signal to it? From owner-freebsd-hackers@FreeBSD.ORG Sun Jan 15 15:47:32 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2A58116A41F for ; Sun, 15 Jan 2006 15:47:32 +0000 (GMT) (envelope-from nike_d@cytexbg.com) Received: from mail.interbgc.com (mx03.interbgc.com [217.9.224.229]) by mx1.FreeBSD.org (Postfix) with SMTP id 19D7143D45 for ; Sun, 15 Jan 2006 15:47:30 +0000 (GMT) (envelope-from nike_d@cytexbg.com) Received: (qmail 50296 invoked from network); 15 Jan 2006 15:47:28 -0000 Received: from nike_d@cytexbg.com by keeper.interbgc.com by uid 1002 with qmail-scanner-1.14 (uvscan: v4.2.40/v4374. spamassassin: 2.63. Clear:SA:0(0.1/8.0):. Processed in 2.05381 secs); 15 Jan 2006 15:47:28 -0000 X-Spam-Status: No, hits=0.1 required=8.0 Received: from 213-240-218-143.1697748.ddns.cablebg.net (HELO tormentor.totalterror.net) (213.240.218.143) by mx03.interbgc.com with SMTP; 15 Jan 2006 15:47:26 -0000 Received: (qmail 47525 invoked from network); 15 Jan 2006 15:47:22 -0000 Received: from unknown (HELO ?10.0.0.3?) (10.0.0.3) by tormentor.totalterror.net with SMTP; 15 Jan 2006 15:47:22 -0000 Message-ID: <43CA6E89.3090605@cytexbg.com> Date: Sun, 15 Jan 2006 17:47:21 +0200 From: Niki Denev User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Ashok Shrestha References: <79e2026f0601142345x1a9269bdl3153d1bb110be08d@mail.gmail.com> In-Reply-To: <79e2026f0601142345x1a9269bdl3153d1bb110be08d@mail.gmail.com> X-Enigmail-Version: 0.94.0.0 OpenPGP: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: speed up port compiling using RAM (tmpfs) ??? 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, 15 Jan 2006 15:47:32 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ashok Shrestha wrote: > Hi, > > I am curious to know if there is a way to compile a port such as X11 > or KDE faster. > > I know in Gentoo, you can mount a part of RAM and compile in that. > This substantially decreases the compile time. Reference: > http://gentoo-wiki.com/TIP_Speeding_up_portage_with_tmpfs > > Does anyone know how to do this in Freebsd? > > -- > Ashok Shrestha You can also take a look at devel/ccache and devel/distcc from ports. - --niki -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFDym6JHNAJ/fLbfrkRAuV5AKCw01ZCh5/wmc5cBxXsY2NaOGCR6ACfc1VN 7Tx/hA8eUmS65P0Nf0tvF3Y= =uOVv -----END PGP SIGNATURE----- From owner-freebsd-hackers@FreeBSD.ORG Sun Jan 15 16:11:12 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 543D116A41F for ; Sun, 15 Jan 2006 16:11:12 +0000 (GMT) (envelope-from chris@i13i.com) Received: from admin.i13i.com (admin.i13i.com [66.90.92.83]) by mx1.FreeBSD.org (Postfix) with SMTP id C420243D46 for ; Sun, 15 Jan 2006 16:11:11 +0000 (GMT) (envelope-from chris@i13i.com) Received: (qmail 7749 invoked from network); 15 Jan 2006 16:32:36 -0000 Received: from mail.i13i.com (HELO webmail.i13i.com) (208.53.187.133) by admin.i13i.com with SMTP; 15 Jan 2006 16:32:36 -0000 Received: from 195.139.252.5 (proxying for 62.92.188.12) (SquirrelMail authenticated user chris@i13i.com) by webmail.i13i.com with HTTP; Sun, 15 Jan 2006 10:32:36 -0600 (CST) Message-ID: <35403.195.139.252.5.1137342756.squirrel@webmail.i13i.com> In-Reply-To: <43CA6E89.3090605@cytexbg.com> References: <79e2026f0601142345x1a9269bdl3153d1bb110be08d@mail.gmail.com> <43CA6E89.3090605@cytexbg.com> Date: Sun, 15 Jan 2006 10:32:36 -0600 (CST) From: chris@i13i.com To: "Niki Denev" User-Agent: SquirrelMail/1.4.5 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: Ashok Shrestha , freebsd-hackers@freebsd.org Subject: Re: speed up port compiling using RAM (tmpfs) ??? 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, 15 Jan 2006 16:11:12 -0000 you can mount a small memory filesystem think it's called mbfs or something and change the work dir to that then you should be able to compile KDE using ram instead of the HD > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Ashok Shrestha wrote: >> Hi, >> >> I am curious to know if there is a way to compile a port such as X11 >> or KDE faster. >> >> I know in Gentoo, you can mount a part of RAM and compile in that. >> This substantially decreases the compile time. Reference: >> http://gentoo-wiki.com/TIP_Speeding_up_portage_with_tmpfs >> >> Does anyone know how to do this in Freebsd? >> >> -- >> Ashok Shrestha > > You can also take a look at devel/ccache and devel/distcc from ports. > > - --niki > > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.2 (MingW32) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFDym6JHNAJ/fLbfrkRAuV5AKCw01ZCh5/wmc5cBxXsY2NaOGCR6ACfc1VN > 7Tx/hA8eUmS65P0Nf0tvF3Y= > =uOVv > -----END PGP SIGNATURE----- > _______________________________________________ > 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 Sun Jan 15 16:22:16 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 51F9A16A41F for ; Sun, 15 Jan 2006 16:22:16 +0000 (GMT) (envelope-from tiffany.snyder@gmail.com) Received: from uproxy.gmail.com (uproxy.gmail.com [66.249.92.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B75143D45 for ; Sun, 15 Jan 2006 16:22:15 +0000 (GMT) (envelope-from tiffany.snyder@gmail.com) Received: by uproxy.gmail.com with SMTP id o2so420103uge for ; Sun, 15 Jan 2006 08:22:14 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=CqMxTRD92Z8LY1W4gXt5zC2KGlWW6dGO54knT/WVwbIcWMD7EMvskUqfS+q39GonF72FSMOWv4ZhXQ3BFdH3bHQroUEb3Jr6eUv3BPxHrP5/OFa/ACFq+iUkEocMu+nWuu/FYqhGcfl9wFt0fePQNiz/9JkME3ALPX2Yqc2YC7k= Received: by 10.48.30.20 with SMTP id d20mr174863nfd; Sun, 15 Jan 2006 08:15:40 -0800 (PST) Received: by 10.49.65.12 with HTTP; Sun, 15 Jan 2006 08:15:40 -0800 (PST) Message-ID: Date: Sun, 15 Jan 2006 08:15:40 -0800 From: Tiffany Snyder To: Robert Watson In-Reply-To: <20060115113523.O38874@fledge.watson.org> MIME-Version: 1.0 References: <1fa17f810601122232l25551bc5n4e4a01ff6b7921e@mail.gmail.com> <1fa17f810601130220h521590banff7d775a8bd4eaa6@mail.gmail.com> <1fa17f810601141109u3e3a0586ud3b3cc86ebc6e80@mail.gmail.com> <20060115113523.O38874@fledge.watson.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hackers@freebsd.org, prime Subject: Re: How priority propagation works on read/write lock? 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, 15 Jan 2006 16:22:16 -0000 That's awesome. Thanks for the update. Tiffany. On 1/15/06, Robert Watson wrote: > > > On Sun, 15 Jan 2006, prime wrote: > > > On 1/15/06, Tiffany Snyder wrote: > >> > >> Does FreeBSD support rwlocks? > ... > > FreeBSD supports sx now,see sx(9).sx has the same semanteme > > as rwlock. > > While semantically they are very simila, John Baldwin has a > work-in-progress > implementation of rwlock's in Perforce. Given the progress he appears to > be > making, I imagine we'll see it in CVS within a week or two. > > Robert N M Watson > From owner-freebsd-hackers@FreeBSD.ORG Sun Jan 15 20:40:04 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D038E16A41F; Sun, 15 Jan 2006 20:40:04 +0000 (GMT) (envelope-from frank@exit.com) Received: from tinker.exit.com (tinker.exit.com [206.223.0.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 71B3443D46; Sun, 15 Jan 2006 20:40:04 +0000 (GMT) (envelope-from frank@exit.com) Received: from realtime.exit.com (realtime [206.223.0.5]) by tinker.exit.com (8.13.4/8.13.4) with ESMTP id k0FKe5CC038117; Sun, 15 Jan 2006 12:40:05 -0800 (PST) (envelope-from frank@exit.com) Received: from realtime.exit.com (localhost [127.0.0.1]) by realtime.exit.com (8.13.4/8.13.4) with ESMTP id k0FKe3P3001936; Sun, 15 Jan 2006 12:40:03 -0800 (PST) (envelope-from frank@exit.com) Received: (from frank@localhost) by realtime.exit.com (8.13.4/8.13.4/Submit) id k0FKe35t001935; Sun, 15 Jan 2006 12:40:03 -0800 (PST) (envelope-from frank@exit.com) X-Authentication-Warning: realtime.exit.com: frank set sender to frank@exit.com using -f From: Frank Mayhar To: hackers@freebsd.org Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Exit Consulting Date: Sun, 15 Jan 2006 12:40:02 -0800 Message-Id: <1137357602.1362.23.camel@realtime.exit.com> Mime-Version: 1.0 X-Mailer: Evolution 2.4.1 FreeBSD GNOME Team Port X-Virus-Scanned: ClamAV 0.87.1/1243/Sun Jan 15 10:35:18 2006 on tinker.exit.com X-Virus-Status: Clean Cc: FreeBSD-Current Subject: Panic in nfs_putpages() on 6-stable. X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: frank@exit.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Jan 2006 20:40:05 -0000 I've run into this panic a couple of times over the last few days, while trying to rebuild ports using an NFS-mounted /usr/ports filesystem. It happened again today and this time I had time to look at the dump. The problem is a null pointer dereference in nfs_putpages(), when it tries to look at np->n_size. It turns out that v_data is NULL on entry to this routine. Looking at the stack I see why: #6 0xc0674e4a in calltrap () at /usr/src/sys/i386/i386/exception.s:139 #7 0xc05eb030 in nfs_putpages (ap=0xe81c6a14) at /usr/src/sys/nfsclient/nfs_bio.c:301 #8 0xc0691148 in VOP_PUTPAGES_APV (vop=0x1000, a=0xe81c6a14) at vnode_if.c:2164 #9 0xc064fd8e in vnode_pager_putpages (object=0xcafaa840, m=0x1000, count=0x1000, sync=0x5, rtvals=0x1000) at vnode_if.h:1119 During symbol reading, Attribute value is not a constant (DW_FORM_ref4). #10 0xc064b99e in vm_pageout_flush (mc=0xe81c6ab0, count=0x1, flags=0x5) at vm_pager.h:147 #11 0xc0647d0c in vm_object_page_collect_flush (object=0xcafaa840, p=0xc19e5218, curgeneration=0x0, pagerflags=0x5) at /usr/src/sys/vm/vm_object.c:950 #12 0xc0647800 in vm_object_page_clean (object=0xcafaa840, start=0x0, end=Unhandled dwarf expression opcode 0x93 ) at /usr/src/sys/vm/vm_object.c:753 #13 0xc0647525 in vm_object_terminate (object=0xcafaa840) at /usr/src/sys/vm/vm_object.c:608 #14 0xc064e5ad in vnode_destroy_vobject (vp=0xcb58c110) at /usr/src/sys/vm/vnode_pager.c:166 #15 0xc05ee075 in nfs_reclaim (ap=0x1000) at /usr/src/sys/nfsclient/nfs_node.c:247 #16 0xc069095e in VOP_RECLAIM_APV (vop=0x1000, a=0xe81c6c90) at vnode_if.c:1589 #17 0xc0587aa5 in vgonel (vp=0xcb58c110) at vnode_if.h:818 #18 0xc0584ac2 in vlrureclaim (mp=0xc9b2e400) at /usr/src/sys/kern/vfs_subr.c:612 #19 0xc0584e8b in vnlru_proc () at /usr/src/sys/kern/vfs_subr.c:725 #20 0xc052034c in fork_exit (callout=0xc0584d00 , arg=0x0, frame=0xe81c6d38) at /usr/src/sys/kern/kern_fork.c:789 #21 0xc0674eac in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:208 In nfs_reclaim(), just before he calls vnode_destroy_vobject(), he zfrees and clears vp->v_data. When, down in the guts of vm_object.c, he tries to flush the associated pages, v_data is already NULL so he goes boom. Now, why does he do the zfree/clear before vnode_destroy_vobject()? Is he assuming that there are no pages associated with this vnode that need to be flushed? Should there be? I looked at some other file systems and they do the same thing. The obvious fix is to move the zfree/clear to after the vnode_destroy_vobject() but if there should be no pages that need to be flushed on the vnode at this point, that would just hide the problem. I can keep looking at the code to answer my question but I thought I would ask here first, in case there's someone who knows the answer right away. Thanks. -- Frank Mayhar frank@exit.com http://www.exit.com/ Exit Consulting http://www.gpsclock.com/ http://www.exit.com/blog/frank/ From owner-freebsd-hackers@FreeBSD.ORG Sun Jan 15 21:49:41 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 302E316A41F for ; Sun, 15 Jan 2006 21:49:41 +0000 (GMT) (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 0B26043D5A for ; Sun, 15 Jan 2006 21:49:37 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (ppp209-190.lns1.adl2.internode.on.net [203.122.209.190]) (authenticated bits=0) by cain.gsoft.com.au (8.13.5/8.13.4) with ESMTP id k0FLnXr3069832 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Mon, 16 Jan 2006 08:19:34 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-hackers@freebsd.org Date: Sun, 15 Jan 2006 19:07:00 +1030 User-Agent: KMail/1.8.3 References: <79e2026f0601142345x1a9269bdl3153d1bb110be08d@mail.gmail.com> In-Reply-To: <79e2026f0601142345x1a9269bdl3153d1bb110be08d@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1838399.n5YTgtV7IJ"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200601151907.01027.doconnor@gsoft.com.au> X-Spam-Score: 0.96 () DATE_IN_PAST_12_24 X-Scanned-By: MIMEDefang 2.54 on 203.31.81.10 Cc: Ashok Shrestha , Brandon Flowers Subject: Re: speed up port compiling using RAM (tmpfs) ??? 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, 15 Jan 2006 21:49:41 -0000 --nextPart1838399.n5YTgtV7IJ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Sunday 15 January 2006 18:15, Ashok Shrestha wrote: > I am curious to know if there is a way to compile a port such as X11 > or KDE faster. > > I know in Gentoo, you can mount a part of RAM and compile in that. > This substantially decreases the compile time. Reference: > http://gentoo-wiki.com/TIP_Speeding_up_portage_with_tmpfs > > Does anyone know how to do this in Freebsd? Make a RAM drive using mdconfig and the mount it somewhere. Then put WRKDIRPREFIX=3D/path/to/md in /etc/make.conf =2D-=20 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 --nextPart1838399.n5YTgtV7IJ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDygms5ZPcIHs/zowRAoWSAKCgI0+mXstj03gNMQkZG1qUyGOJQACfdTFI Db/WXgfeSgHRCn6bd/7c2Zc= =VxlU -----END PGP SIGNATURE----- --nextPart1838399.n5YTgtV7IJ-- From owner-freebsd-hackers@FreeBSD.ORG Sun Jan 15 22:03:51 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D12ED16A41F for ; Sun, 15 Jan 2006 22:03:51 +0000 (GMT) (envelope-from kamal_ckk@yahoo.com) Received: from web30002.mail.mud.yahoo.com (web30002.mail.mud.yahoo.com [68.142.200.65]) by mx1.FreeBSD.org (Postfix) with SMTP id 3810043D45 for ; Sun, 15 Jan 2006 22:03:51 +0000 (GMT) (envelope-from kamal_ckk@yahoo.com) Received: (qmail 37977 invoked by uid 60001); 15 Jan 2006 22:03:50 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=5MBgLsOOX2ZgEThkSZE03Aq1fDs9Q/0Rdf2mz6LOn/aMEI5BAKW2qkBtoBnrUljTJ3GdxV9yyFiATcebt+dEhIqdCTMMDe5fytAzmsGYR5qAVTvfcXhciErO/UU6qHlvXfjfWsUHna2dkC78mLv7Dib8wHA8tCydaRmA3CMgy1g= ; Message-ID: <20060115220350.37975.qmail@web30002.mail.mud.yahoo.com> Received: from [202.79.62.16] by web30002.mail.mud.yahoo.com via HTTP; Sun, 15 Jan 2006 14:03:50 PST Date: Sun, 15 Jan 2006 14:03:50 -0800 (PST) From: kamal kc To: freebsd MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: giving more cpu time to cpu intensive kernel daemon 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, 15 Jan 2006 22:03:51 -0000 dear all, i created a kernel daemon thread using the SYSINIT(). i want that daemon thread to do more cpu intensive tasks and that's why i want to give it more cpu time. my daemon thread get a priority of -84 and a nice value of 0. i guess when the nice value is 0 it affects its scheduling. how could i give it a good nice value ? are there any other options that i may have to look upon to ensure the daemon gets more of the cpu time ?? thanks, kamal __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From owner-freebsd-hackers@FreeBSD.ORG Sun Jan 15 22:45:21 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8504716A41F; Sun, 15 Jan 2006 22:45:21 +0000 (GMT) (envelope-from frank@exit.com) Received: from tinker.exit.com (tinker.exit.com [206.223.0.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 01EC043D5A; Sun, 15 Jan 2006 22:45:14 +0000 (GMT) (envelope-from frank@exit.com) Received: from realtime.exit.com (realtime [206.223.0.5]) by tinker.exit.com (8.13.4/8.13.4) with ESMTP id k0FMjDe6039088; Sun, 15 Jan 2006 14:45:13 -0800 (PST) (envelope-from frank@exit.com) Received: from realtime.exit.com (localhost [127.0.0.1]) by realtime.exit.com (8.13.4/8.13.4) with ESMTP id k0FMjCXx002584; Sun, 15 Jan 2006 14:45:12 -0800 (PST) (envelope-from frank@exit.com) Received: (from frank@localhost) by realtime.exit.com (8.13.4/8.13.4/Submit) id k0FMjB9c002583; Sun, 15 Jan 2006 14:45:11 -0800 (PST) (envelope-from frank@exit.com) X-Authentication-Warning: realtime.exit.com: frank set sender to frank@exit.com using -f From: Frank Mayhar To: hackers@freebsd.org In-Reply-To: <1137357602.1362.23.camel@realtime.exit.com> References: <1137357602.1362.23.camel@realtime.exit.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Exit Consulting Date: Sun, 15 Jan 2006 14:45:11 -0800 Message-Id: <1137365111.1942.18.camel@realtime.exit.com> Mime-Version: 1.0 X-Mailer: Evolution 2.4.1 FreeBSD GNOME Team Port X-Virus-Scanned: ClamAV 0.87.1/1243/Sun Jan 15 10:35:18 2006 on tinker.exit.com X-Virus-Status: Clean Cc: FreeBSD-Current Subject: Re: Panic in nfs_putpages() on 6-stable, more info. X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: frank@exit.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Jan 2006 22:45:21 -0000 A bit more data and another question. On Sun, 2006-01-15 at 12:40 -0800, Frank Mayhar wrote: > In nfs_reclaim(), just before he calls vnode_destroy_vobject(), he > zfrees and clears vp->v_data. When, down in the guts of vm_object.c, he > tries to flush the associated pages, v_data is already NULL so he goes > boom. > > Now, why does he do the zfree/clear before vnode_destroy_vobject()? Is > he assuming that there are no pages associated with this vnode that need > to be flushed? Should there be? I looked at some other file systems and > they do the same thing. The obvious fix is to move the zfree/clear to > after the vnode_destroy_vobject() but if there should be no pages that > need to be flushed on the vnode at this point, that would just hide the > problem. Looking further down, at vlrureclaim(), I see that the commentary for vlrureclaim() specifically says that a a flushed vnode may still have backing store, so it appears that yes, there may be pages associated with the vnode when he calls vgonel(). Between vgonel() and nfs_reclaim() there's just VOP stuff, so the flushing has to be done lower down. The nfs_reclaim() routine itself just does some bookkeeping and then calls vnode_destroy_vobject(). That routine can push pages out, which means that if the backing store is on NFS, nfs_putpages() can be called. But that routine will fault because he'll try to use v_data as an nfsnode. The reason for my confusion is that of the filesystems in the tree, the only one that doesn't zfree and clear v_data before calling vnode_destroy_vobject() is UFS. The commentary in ufs_reclaim() is clear, though: /* * Destroy the vm object and flush associated pages. */ vnode_destroy_vobject(vp); Then later he VI_LOCKS() and clears v_data. (And [indirectly] does the zfree only _after_ that, which is interesting but probably not important.) I'm going to go slightly out on a limb here and guess that the "flush associated pages" thing came in relatively recently and the other filesystems haven't caught up with it. This implies that the proper fix is to go through those other xxx_reclaim() routines and reorder the operations. That's easy enough to do, but I would like to make sure that my understanding of this (and my guess) is correct and that I'm not wasting my time. Thanks! -- Frank Mayhar frank@exit.com http://www.exit.com/ Exit Consulting http://www.gpsclock.com/ http://www.exit.com/blog/frank/ From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 16 05:08:49 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7AAEE16A41F for ; Mon, 16 Jan 2006 05:08:49 +0000 (GMT) (envelope-from kamalpr@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9610243D46 for ; Mon, 16 Jan 2006 05:08:48 +0000 (GMT) (envelope-from kamalpr@gmail.com) Received: by wproxy.gmail.com with SMTP id 70so1021166wra for ; Sun, 15 Jan 2006 21:08:47 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:references; b=mU5lvnLWE1XaF2Zdsrl8I0gU6nCJUgRzld1OuvkgIZehnZLDEWfwQIWJBuhhVmKAIQCadIqlPP2/NMiunFps52ylF9WgT5TDoHUWG/8SI6IlOT1reA9vUDQkPHdCKWPRAf2ESPSxJ9nc3k/DhDW7sSt2WWFg7FnwKf5zHW6h6FQ= Received: by 10.65.186.11 with SMTP id n11mr2564119qbp; Sun, 15 Jan 2006 21:08:47 -0800 (PST) Received: by 10.65.43.10 with HTTP; Sun, 15 Jan 2006 21:08:47 -0800 (PST) Message-ID: Date: Mon, 16 Jan 2006 10:38:47 +0530 From: "Kamal R. Prasad" To: John Baldwin In-Reply-To: <200601131422.15208.jhb@freebsd.org> MIME-Version: 1.0 References: <1fa17f810601122232l25551bc5n4e4a01ff6b7921e@mail.gmail.com> <1fa17f810601130220h521590banff7d775a8bd4eaa6@mail.gmail.com> <200601131422.15208.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hackers@freebsd.org, prime Subject: Re: How priority propagation works on read/write lock? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: kamalp@acm.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Jan 2006 05:08:49 -0000 you mean, boosting the priority of a reader would be required to avoid priority inversion, but difficult to implement? regards -kamal On 1/14/06, John Baldwin wrote: > I think you just kind of punt and do a best effort. Trying to manage a > list > of current read lock holders would be a bit PITA. From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 16 18:13:25 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 391A016A41F for ; Mon, 16 Jan 2006 18:13:25 +0000 (GMT) (envelope-from pranav.sawargaonkar@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id B588F43D55 for ; Mon, 16 Jan 2006 18:13:24 +0000 (GMT) (envelope-from pranav.sawargaonkar@gmail.com) Received: by wproxy.gmail.com with SMTP id i14so157788wra for ; Mon, 16 Jan 2006 10:13:24 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=S1SrVzF6cmW8OLxI6bnER5ZmpFwvYR/jEtxXu6uH5HGm8PMb/yIUvY1VYwZiAlrZosGf+V3m1GI6k47SUBXqvxgY7LL25pVm3H5PIfVQrVQgMFuKKsctxybD6kmbvWr9gtyaunOig3Edoh795zrgw+vNDiCY08CSoD2maLX3/xc= Received: by 10.54.105.7 with SMTP id d7mr2426588wrc; Mon, 16 Jan 2006 10:13:23 -0800 (PST) Received: by 10.54.125.1 with HTTP; Mon, 16 Jan 2006 10:13:23 -0800 (PST) Message-ID: <5007e1a40601161013q5692f79dge001ceac5de991df@mail.gmail.com> Date: Mon, 16 Jan 2006 23:43:23 +0530 From: Pranav Sawargaonkar To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Accessing Pagetable of a process 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, 16 Jan 2006 18:13:25 -0000 Hi I want to access pagetable of a perticular process. How i should get it?Is it possible to access by using pointer of type 'struct proc'? Also i want to access each page referenced in pagetable of that process by writing my module how i can achieve this? Thanks in advance. -Pranav From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 17 00:37:10 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F275216A41F for ; Tue, 17 Jan 2006 00:37:10 +0000 (GMT) (envelope-from antti.korpela@devnet.fi) Received: from mato.luukku.com (mato.luukku.com [193.209.83.251]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8EFFF43D46 for ; Tue, 17 Jan 2006 00:37:07 +0000 (GMT) (envelope-from antti.korpela@devnet.fi) Received: from localhost (mta3-o.i.luukku.com [10.0.1.132]) by mta3-o.i.luukku.com (Postfix) with ESMTP id 2DF01FF96D for ; Tue, 17 Jan 2006 02:37:06 +0200 (EET) Received: from [82.203.134.177] (b186.dsl.mtv3.fi [82.203.134.177]) by mato.luukku.com (Postfix) with ESMTP id 095B422EE8D for ; Tue, 17 Jan 2006 02:37:05 +0200 (EET) Message-ID: <43CC3C6B.4060703@devnet.fi> Date: Tue, 17 Jan 2006 02:38:03 +0200 From: Antti Korpela User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: FreeBSD 6.0 default pty/tty-limit (256) OFF! 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, 17 Jan 2006 00:37:11 -0000 Hi, I need patch to raise FreeBSD 6.0 default pty/tty-limit (256) UP or OFF. In shell-production usage, that limit is ridiculous, there must be stop to this and put PTY-limits off! I changed my servers operating systems moment ago from Linux to FreeBSD thinking that FreeBSD could be more better, but how this can be possible, that so important think like PTYs are limited to so low?? every UNIX has more ptys. I'm hoping fast reply from you.. Yours, Antti Korpela From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 17 01:09:18 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D4C0D16A41F for ; Tue, 17 Jan 2006 01:09:18 +0000 (GMT) (envelope-from chris@i13i.com) Received: from admin.i13i.com (admin.i13i.com [66.90.92.83]) by mx1.FreeBSD.org (Postfix) with SMTP id 5406443D46 for ; Tue, 17 Jan 2006 01:09:18 +0000 (GMT) (envelope-from chris@i13i.com) Received: (qmail 196 invoked from network); 17 Jan 2006 01:31:06 -0000 Received: from mail.i13i.com (HELO webmail.i13i.com) (208.53.187.133) by admin.i13i.com with SMTP; 17 Jan 2006 01:31:06 -0000 Received: from 195.139.252.5 (proxying for 62.92.188.11) (SquirrelMail authenticated user chris@i13i.com) by webmail.i13i.com with HTTP; Mon, 16 Jan 2006 19:31:06 -0600 (CST) Message-ID: <49431.195.139.252.5.1137461466.squirrel@webmail.i13i.com> In-Reply-To: <43CC3C6B.4060703@devnet.fi> References: <43CC3C6B.4060703@devnet.fi> Date: Mon, 16 Jan 2006 19:31:06 -0600 (CST) From: chris@i13i.com To: "Antti Korpela" User-Agent: SquirrelMail/1.4.5 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: freebsd-hackers@freebsd.org Subject: Re: FreeBSD 6.0 default pty/tty-limit (256) OFF! 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, 17 Jan 2006 01:09:18 -0000 Then change the default it isnt hard you cant just come on a mailing list and demand a patch be raised just becuase you think this is rediculous this is why we have man pages and all that google.com/bsd your english is pretty poor too if you dont like freebsd then dont use it but dont demand people a patch just becuase you find something rediculous. > Hi, > > > I need patch to raise FreeBSD 6.0 default pty/tty-limit (256) UP or OFF. > In shell-production usage, that limit is ridiculous, there must be stop to > this and put PTY-limits off! > I changed my servers operating systems moment ago from Linux to FreeBSD > thinking that FreeBSD could be more better, but how this can be possible, > that so important think like PTYs are limited to so low?? every UNIX has > more ptys. > > > I'm hoping fast reply from you.. > > > Yours, > Antti Korpela > > _______________________________________________ > 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 Tue Jan 17 01:35:17 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 689D816A41F for ; Tue, 17 Jan 2006 01:35:17 +0000 (GMT) (envelope-from kdk@daleco.biz) Received: from ezekiel.daleco.biz (southernuniform.com [66.76.92.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0078743D46 for ; Tue, 17 Jan 2006 01:35:16 +0000 (GMT) (envelope-from kdk@daleco.biz) Received: from [192.168.2.2] ([69.27.149.254]) by ezekiel.daleco.biz (8.13.1/8.13.1) with ESMTP id k0H1XRi5055696; Mon, 16 Jan 2006 19:33:47 -0600 (CST) (envelope-from kdk@daleco.biz) Message-ID: <43CC495C.5060005@daleco.biz> Date: Mon, 16 Jan 2006 19:33:16 -0600 From: Kevin Kinsey User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20051026 X-Accept-Language: en-us, en MIME-Version: 1.0 To: chris@i13i.com References: <43CC3C6B.4060703@devnet.fi> <49431.195.139.252.5.1137461466.squirrel@webmail.i13i.com> In-Reply-To: <49431.195.139.252.5.1137461466.squirrel@webmail.i13i.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, Antti Korpela Subject: Re: FreeBSD 6.0 default pty/tty-limit (256) OFF! 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, 17 Jan 2006 01:35:17 -0000 >>Hi, >> >> >>I need patch to raise FreeBSD 6.0 default pty/tty-limit (256) UP or OFF. >>In shell-production usage, that limit is ridiculous, there must be stop to >>this and put PTY-limits off! >>I changed my servers operating systems moment ago from Linux to FreeBSD >>thinking that FreeBSD could be more better, but how this can be possible, >>that so important think like PTYs are limited to so low?? every UNIX has >>more ptys. >> >> >>I'm hoping fast reply from you.. >> >> >>Yours, >>Antti Korpela >> >> >> >chris@i13i.com wrote: >Then change the default it isnt hard you cant just come on a mailing list >and demand a patch be raised just becuase you think this is rediculous >this is why we have man pages and all that google.com/bsd your english is >pretty poor too if you dont like freebsd then dont use it but dont demand >people a patch just becuase you find something rediculous. For starters, let be nice, and truthful. The community is known for this, and you've no leg to stand on. His English grammar isn't so great, but it is understandable; furthermore, he knows where the shift key is and is ahead of you in spelling, 0 to 2; plus, take a look at paragraph structure. For the most part, 4 sentences and 71 words beats one sentence of 66 for clarity. I am not an expert, but looking at pty(4), it seems he has a point. "/dev/pty[p-sP-S][0-9a-v]" sure looks like 2^8 to me. But I'll leave it to the experts to discuss the truth or fiction of the assumption and the difficulty of its reconciliation, if such can occur.... Kevin Kinsey -- I can hire one half of the working class to kill the other half. -- Jay Gould From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 17 02:43:55 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1570516A41F for ; Tue, 17 Jan 2006 02:43:55 +0000 (GMT) (envelope-from cheesiest@nano.net) Received: from mail.smallweb.com (mail.smallweb.com [216.85.125.111]) by mx1.FreeBSD.org (Postfix) with ESMTP id B31BA43D45 for ; Tue, 17 Jan 2006 02:43:54 +0000 (GMT) (envelope-from cheesiest@nano.net) Received: from [216.85.125.9] (sixpence.nano.net [216.85.125.9]) by mail.smallweb.com (Rockliffe SMTPRA 5.3.11) with ESMTP id for ; Mon, 16 Jan 2006 19:45:58 -0700 Message-ID: <43CC59E7.6080505@nano.net> Date: Mon, 16 Jan 2006 19:43:51 -0700 From: Steve Suhre User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Named requests filling up T1 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, 17 Jan 2006 02:43:55 -0000 Ugh...it's always something.... The T1 here is getting blasted by named requests, any suggestions would be appreciated... I turned on debugging and got the following, lots of them...so many that we're getting 30-50% packet loss across the T1: 16-Jan-2006 18:01:35.795 client @0x87d4800: udprecv 16-Jan-2006 18:01:35.795 client 64.18.133.103#5550: UDP request 16-Jan-2006 18:01:35.795 client 64.18.133.103#5550: using view '_default' 16-Jan-2006 18:01:35.795 client 64.18.133.103#5550: request is not signed 16-Jan-2006 18:01:35.795 client 64.18.133.103#5550: recursion available 16-Jan-2006 18:01:35.795 client 64.18.133.103#5550: query 16-Jan-2006 18:01:35.795 client 64.18.133.103#5550: query (cache) 'v.tn.co.za/ANY/IN' approved 16-Jan-2006 18:01:35.795 client 64.18.133.103#5550: send 16-Jan-2006 18:01:35.796 client 64.18.133.103#5550: sendto 16-Jan-2006 18:01:35.796 client 64.18.133.103#5550: senddone 16-Jan-2006 18:01:35.796 client 64.18.133.103#5550: next 16-Jan-2006 18:01:35.796 client 64.18.133.103#5550: endrequest Any suggestion on what it might be and how I might stop it? -- Steve Suhre steve@pasta.net 719.439.6052 Cell 719.632.2897 Home From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 17 03:23:38 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 86D5616A423 for ; Tue, 17 Jan 2006 03:23:38 +0000 (GMT) (envelope-from matt@gsicomp.on.ca) Received: from skippyii.compar.com (ns1.compar.com [216.208.38.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 082F343D5C for ; Tue, 17 Jan 2006 03:23:36 +0000 (GMT) (envelope-from matt@gsicomp.on.ca) Received: from hermes (CPE00062566c7bb-CM0011e6ede298.cpe.net.cable.rogers.com [70.28.254.189]) by skippyii.compar.com (8.13.1/8.13.1) with ESMTP id k0H3Pone091317; Mon, 16 Jan 2006 22:25:55 -0500 (EST) (envelope-from matt@gsicomp.on.ca) Message-ID: <015901c61b15$898648a0$1200a8c0@gsicomp.on.ca> From: "Matt Emmerton" To: "Steve Suhre" , References: <43CC59E7.6080505@nano.net> Date: Mon, 16 Jan 2006 22:24:27 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1506 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506 Cc: Subject: Re: Named requests filling up T1 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, 17 Jan 2006 03:23:38 -0000 > Ugh...it's always something.... > > The T1 here is getting blasted by named requests, any suggestions would > be appreciated... I turned on debugging and got the following, lots of > them...so many that we're getting 30-50% packet loss across the T1: > > 16-Jan-2006 18:01:35.795 client @0x87d4800: udprecv > 16-Jan-2006 18:01:35.795 client 64.18.133.103#5550: UDP request > 16-Jan-2006 18:01:35.795 client 64.18.133.103#5550: using view '_default' > 16-Jan-2006 18:01:35.795 client 64.18.133.103#5550: request is not signed > 16-Jan-2006 18:01:35.795 client 64.18.133.103#5550: recursion available > 16-Jan-2006 18:01:35.795 client 64.18.133.103#5550: query > 16-Jan-2006 18:01:35.795 client 64.18.133.103#5550: query (cache) > 'v.tn.co.za/ANY/IN' approved > 16-Jan-2006 18:01:35.795 client 64.18.133.103#5550: send > 16-Jan-2006 18:01:35.796 client 64.18.133.103#5550: sendto > 16-Jan-2006 18:01:35.796 client 64.18.133.103#5550: senddone > 16-Jan-2006 18:01:35.796 client 64.18.133.103#5550: next > 16-Jan-2006 18:01:35.796 client 64.18.133.103#5550: endrequest > > Any suggestion on what it might be and how I might stop it? Looks like someone is spamming your DNS server with queries. Two questions: 1) Is v.tn.co.za a domain that you are authorative for? 2) Are you an ISP and/or is client 64.18.133.103 authorized to use your DNS server? If the answer to 1) is NO, then there's no reason for these queries to be directed to your DNS server from the Internet. If the answer to 2) is NO, then there's no reason for these queries to be directed to your DNS server from the Internet. Source IP filtering is likely your best option, although it doesn't help with your T1 saturation, although it would give whoever is blasting these queries a clue. -- Matt Emmerton From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 17 03:34:25 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 472A616A41F for ; Tue, 17 Jan 2006 03:34:25 +0000 (GMT) (envelope-from cheesiest@nano.net) Received: from mail.smallweb.com (mail.smallweb.com [216.85.125.111]) by mx1.FreeBSD.org (Postfix) with ESMTP id 913C843D49 for ; Tue, 17 Jan 2006 03:34:24 +0000 (GMT) (envelope-from cheesiest@nano.net) Received: from [216.85.125.9] (sixpence.nano.net [216.85.125.9]) by mail.smallweb.com (Rockliffe SMTPRA 5.3.11) with ESMTP id ; Mon, 16 Jan 2006 20:36:28 -0700 Message-ID: <43CC65BC.9040005@nano.net> Date: Mon, 16 Jan 2006 20:34:20 -0700 From: Steve Suhre User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Matt Emmerton References: <43CC59E7.6080505@nano.net> <015901c61b15$898648a0$1200a8c0@gsicomp.on.ca> In-Reply-To: <015901c61b15$898648a0$1200a8c0@gsicomp.on.ca> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: Named requests filling up T1 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, 17 Jan 2006 03:34:25 -0000 >Looks like someone is spamming your DNS server with queries. > >Two questions: >1) Is v.tn.co.za a domain that you are authorative for? >2) Are you an ISP and/or is client 64.18.133.103 authorized to use your DNS >server? > >If the answer to 1) is NO, then there's no reason for these queries to be >directed to your DNS server from the Internet. >If the answer to 2) is NO, then there's no reason for these queries to be >directed to your DNS server from the Internet. > >Source IP filtering is likely your best option, although it doesn't help >with your T1 saturation, although it would give whoever is blasting these >queries a clue. > >-- >Matt Emmerton > > > Thanks Matt, The answer to both is no. The domain doesn't resolve either (v.tn.co.za). It looks like the source IP changes too...sigh.... I tried a whois on the source IP and it was not found, so it may be spoofed? Or someone has a very messed up server... -- Steve Suhre steve@pasta.net 719.439.6052 Cell 719.632.2897 Home From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 17 05:01:49 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C6D7B16A41F for ; Tue, 17 Jan 2006 05:01:49 +0000 (GMT) (envelope-from silby@silby.com) Received: from wbm7.pair.net (wbm7.pair.net [209.68.4.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3D10B43D72 for ; Tue, 17 Jan 2006 05:01:42 +0000 (GMT) (envelope-from silby@silby.com) Received: by wbm7.pair.net (Postfix, from userid 65534) id 6392A10560; Tue, 17 Jan 2006 00:01:38 -0500 (EST) Received: from 63.147.253.154 ([63.147.253.154]) (SquirrelMail authenticated user silby@silby.com) by webmail7.pair.com with HTTP; Tue, 17 Jan 2006 00:01:38 -0500 (EST) Message-ID: <44314.63.147.253.154.1137474098.squirrel@webmail7.pair.com> In-Reply-To: <43CC65BC.9040005@nano.net> References: <43CC59E7.6080505@nano.net> <015901c61b15$898648a0$1200a8c0@gsicomp.on.ca> <43CC65BC.9040005@nano.net> Date: Tue, 17 Jan 2006 00:01:38 -0500 (EST) From: "Mike Silbersack" To: "Steve Suhre" User-Agent: SquirrelMail/1.4.5 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: freebsd-hackers@freebsd.org Subject: Re: Named requests filling up T1 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, 17 Jan 2006 05:01:49 -0000 > Thanks Matt, > > The answer to both is no. The domain doesn't resolve either > (v.tn.co.za). It looks like the source IP changes too...sigh.... I tried > a whois on the source IP and it was not found, so it may be spoofed? Or > someone has a very messed up server... There was a thread on bugtraq about this, you're either being attacked or are being used to attack someone else. Reconfigure BIND so that it ignores recursive queries originating from outside your network - at least that will save your outbound bandwidth. Mike "Silby" Silbersack From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 17 06:06:14 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 52EA316A41F; Tue, 17 Jan 2006 06:06:14 +0000 (GMT) (envelope-from frank@exit.com) Received: from tinker.exit.com (tinker.exit.com [206.223.0.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 260F843D45; Tue, 17 Jan 2006 06:06:07 +0000 (GMT) (envelope-from frank@exit.com) Received: from realtime.exit.com (realtime [206.223.0.5]) by tinker.exit.com (8.13.4/8.13.4) with ESMTP id k0H668Kx063081; Mon, 16 Jan 2006 22:06:08 -0800 (PST) (envelope-from frank@exit.com) Received: from realtime.exit.com (localhost [127.0.0.1]) by realtime.exit.com (8.13.4/8.13.4) with ESMTP id k0H666Hu097157; Mon, 16 Jan 2006 22:06:06 -0800 (PST) (envelope-from frank@exit.com) Received: (from frank@localhost) by realtime.exit.com (8.13.4/8.13.4/Submit) id k0H6661K097156; Mon, 16 Jan 2006 22:06:06 -0800 (PST) (envelope-from frank@exit.com) X-Authentication-Warning: realtime.exit.com: frank set sender to frank@exit.com using -f From: Frank Mayhar To: hackers@freebsd.org In-Reply-To: <1137365111.1942.18.camel@realtime.exit.com> References: <1137357602.1362.23.camel@realtime.exit.com> <1137365111.1942.18.camel@realtime.exit.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Exit Consulting Date: Mon, 16 Jan 2006 22:06:05 -0800 Message-Id: <1137477965.95312.15.camel@realtime.exit.com> Mime-Version: 1.0 X-Mailer: Evolution 2.4.1 FreeBSD GNOME Team Port X-Virus-Scanned: ClamAV 0.87.1/1243/Sun Jan 15 10:35:18 2006 on tinker.exit.com X-Virus-Status: Clean Cc: FreeBSD-Current Subject: Re: Panic in nfs_putpages() on 6-stable, more info. X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: frank@exit.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jan 2006 06:06:14 -0000 On Sun, 2006-01-15 at 14:45 -0800, Frank Mayhar wrote: > That's easy enough to do, but I would like to make sure that my > understanding of this (and my guess) is correct and that I'm not wasting > my time. Sigh. Well, given the deafening silence I got in response to this, I went ahead and fixed it, or at least I hope it's the right fix. I've been running with it for over 24 hours now with no problems (and heavy NFS access), so it looks good. See http://www.freebsd.org/cgi/query-pr.cgi?pr=91879 for the patch. I went ahead and fixed all the filesystems I could find, since they all had nearly identical code. I trust that this will be committed, and subsequently MFC'd, relatively quickly. -- Frank Mayhar frank@exit.com http://www.exit.com/ Exit Consulting http://www.gpsclock.com/ http://www.exit.com/blog/frank/ From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 17 06:45:01 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E592516A41F for ; Tue, 17 Jan 2006 06:45:00 +0000 (GMT) (envelope-from kamalpr@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5DDD143D45 for ; Tue, 17 Jan 2006 06:45:00 +0000 (GMT) (envelope-from kamalpr@gmail.com) Received: by wproxy.gmail.com with SMTP id i7so1482010wra for ; Mon, 16 Jan 2006 22:44:59 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:references; b=GSAdePyV8cgqysaW+wmMsYw6HRc1rmHML0DDDf/dosCknRA4QGcXD4/JnzZ/OIn5OdY3RyuVcE4fV5+00POWfYPIRj+pTimQ+0sjmca+7b7focxxZ1JJx9UPVILDuN0u3Jgh6PrE7fqaSMujaXtU5SvssKwT2Fgnc//E+gZ+vVk= Received: by 10.64.204.6 with SMTP id b6mr457299qbg; Mon, 16 Jan 2006 22:44:59 -0800 (PST) Received: by 10.65.43.10 with HTTP; Mon, 16 Jan 2006 22:44:59 -0800 (PST) Message-ID: Date: Tue, 17 Jan 2006 12:14:59 +0530 From: "Kamal R. Prasad" Sender: kamalpr@gmail.com To: Pranav Sawargaonkar In-Reply-To: <5007e1a40601161013q5692f79dge001ceac5de991df@mail.gmail.com> MIME-Version: 1.0 References: <5007e1a40601161013q5692f79dge001ceac5de991df@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hackers@freebsd.org Subject: Re: Accessing Pagetable of a process 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, 17 Jan 2006 06:45:01 -0000 On 1/16/06, Pranav Sawargaonkar wrote: > > Hi > I want to access pagetable of a perticular process. > How i should get it?Is it possible to access by using pointer of type > 'struct proc'? by accessimg the vmspace for the process. Also i want to access each page referenced in > pagetable of that process by writing my module how i can achieve this? > Thanks in advance. the pagetable is for translating virtual to physical addresses If you want the contents of the page -you don't need to worry about the translation scheme. Im not sure I understand what you are looking for?? regards -kamal -Pranav > _______________________________________________ > 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 Tue Jan 17 09:09:13 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A2BFF16A41F for ; Tue, 17 Jan 2006 09:09:13 +0000 (GMT) (envelope-from pranav.sawargaonkar@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9BAD443D46 for ; Tue, 17 Jan 2006 09:09:12 +0000 (GMT) (envelope-from pranav.sawargaonkar@gmail.com) Received: by wproxy.gmail.com with SMTP id i14so291490wra for ; Tue, 17 Jan 2006 01:09:12 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=Dt3qJKZWmyg8mX/pYimhSJgnPtTMbaxGYIzq76+rKuxUgrbSBIBO1aoXCri8+Y4XnDvevpHzfZ/aFyQj9TYKmmCcRlegkbxORAWz6vOsy1rh8crtE4KRnn0Ty+f6fkWDK4B7NCDuXiNxP6W0EblL6AjMQGYVITiQzlTAumwMHOQ= Received: by 10.54.148.4 with SMTP id v4mr2167729wrd; Tue, 17 Jan 2006 01:09:11 -0800 (PST) Received: by 10.54.125.1 with HTTP; Tue, 17 Jan 2006 01:09:11 -0800 (PST) Message-ID: <5007e1a40601170109x6f8c7b03kb44f5f5a43ebe3be@mail.gmail.com> Date: Tue, 17 Jan 2006 14:39:11 +0530 From: Pranav Sawargaonkar To: "Kamal R. Prasad" In-Reply-To: MIME-Version: 1.0 References: <5007e1a40601161013q5692f79dge001ceac5de991df@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hackers@freebsd.org Subject: Re: Accessing Pagetable of a process 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, 17 Jan 2006 09:09:13 -0000 Hello, I wanted to save the whole context of the process, thats why I want the access to each page allocated to the process of our interest. And further I want to write all these pages on to swap. The final objective is to save the context of a stopped process on the swap and restore the context afterwards and resume the process.Whatfunctions can be used to read/write to swap ? I have succeeded in accessing the vmspace through the 'struct proc' type pointer. TIA. Best regards, Pranav On 1/17/06, Kamal R. Prasad wrote: > > > > On 1/16/06, Pranav Sawargaonkar wrote: > > > > Hi > > I want to access pagetable of a perticular process. > > How i should get it?Is it possible to access by using pointer of type > > 'struct proc'? > > > by accessimg the vmspace for the process. > > Also i want to access each page referenced in > > pagetable of that process by writing my module how i can achieve this? > > Thanks in advance. > > > the pagetable is for translating virtual to physical addresses If you > want the contents of the page -you don't need to worry about the translat= ion > scheme. Im not sure I understand what you are looking for?? > > regards > -kamal > > > -Pranav > > _______________________________________________ > > freebsd-hackers@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.o= rg > > " > > > > From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 17 09:37:13 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0C05E16A41F for ; Tue, 17 Jan 2006 09:37:13 +0000 (GMT) (envelope-from cheesiest@nano.net) Received: from mail.smallweb.com (mail.smallweb.com [216.85.125.111]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E54E43D4C for ; Tue, 17 Jan 2006 09:37:12 +0000 (GMT) (envelope-from cheesiest@nano.net) Received: from [216.85.125.9] (sixpence.nano.net [216.85.125.9]) by mail.smallweb.com (Rockliffe SMTPRA 5.3.11) with ESMTP id ; Tue, 17 Jan 2006 02:39:17 -0700 Message-ID: <43CCBAC5.4060809@nano.net> Date: Tue, 17 Jan 2006 02:37:09 -0700 From: Steve Suhre User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mike Silbersack References: <43CC59E7.6080505@nano.net> <015901c61b15$898648a0$1200a8c0@gsicomp.on.ca> <43CC65BC.9040005@nano.net> <44314.63.147.253.154.1137474098.squirrel@webmail7.pair.com> In-Reply-To: <44314.63.147.253.154.1137474098.squirrel@webmail7.pair.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: Named requests filling up T1 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, 17 Jan 2006 09:37:13 -0000 Thanks, I think that's what I was looking for. I expect the "ISP" is in another country somewhere and would be hard to reach, if they could be reached at all. And it's probably a bad reference somewhere to the server here, so shutting of recursive queries could help... If I shut named off for an hour or two they go away, so I'm guessing the offending server switches to the secondary and gets what it's looking for? Thanks! Mike Silbersack wrote: >>Thanks Matt, >> >>The answer to both is no. The domain doesn't resolve either >>(v.tn.co.za). It looks like the source IP changes too...sigh.... I tried >>a whois on the source IP and it was not found, so it may be spoofed? Or >>someone has a very messed up server... >> >> > >There was a thread on bugtraq about this, you're either being attacked or >are being used to attack someone else. > >Reconfigure BIND so that it ignores recursive queries originating from >outside your network - at least that will save your outbound bandwidth. > >Mike "Silby" Silbersack >_______________________________________________ >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" > > > > -- Steve Suhre steve@pasta.net 719.439.6052 Cell 719.632.2897 Home From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 17 09:50:33 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E02E916A41F for ; Tue, 17 Jan 2006 09:50:33 +0000 (GMT) (envelope-from kamalpr@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A24343D48 for ; Tue, 17 Jan 2006 09:50:33 +0000 (GMT) (envelope-from kamalpr@gmail.com) Received: by wproxy.gmail.com with SMTP id i31so1302779wra for ; Tue, 17 Jan 2006 01:50:32 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:references; b=Z6qo5GbbUUvsc+0Cfrb3UDLt6fxGJglGXX5b4XLeBjA8ae4CUmaTXA+9zrgU3oiCrmLpAsUR6PRAl+bH04Yx0Kii6AoVkYMzXVstp6qWfLqkWTcrsI4jhc7nfO73BNlKLgZjIZ2U38+tREbQAcf/POVe+XKH0nZtGeP5ClIXuQk= Received: by 10.64.204.1 with SMTP id b1mr3660304qbg; Tue, 17 Jan 2006 01:50:32 -0800 (PST) Received: by 10.65.43.10 with HTTP; Tue, 17 Jan 2006 01:50:32 -0800 (PST) Message-ID: Date: Tue, 17 Jan 2006 15:20:32 +0530 From: "Kamal R. Prasad" Sender: kamalpr@gmail.com To: Pranav Sawargaonkar In-Reply-To: <5007e1a40601170109x6f8c7b03kb44f5f5a43ebe3be@mail.gmail.com> MIME-Version: 1.0 References: <5007e1a40601161013q5692f79dge001ceac5de991df@mail.gmail.com> <5007e1a40601170109x6f8c7b03kb44f5f5a43ebe3be@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hackers@freebsd.org Subject: Re: Accessing Pagetable of a process 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, 17 Jan 2006 09:50:34 -0000 there is some code in dragonflybsd to checkpoint a process. It will write the pagetable to disk. Since the internal data structures aren't much different -you should be able to copy over that code to freebsd. But you will run into problems with file descriptors that are not of type vnode (eg fifo/sockets/pipes etc..). regards -kamal On 1/17/06, Pranav Sawargaonkar wrote: > > Hello, > I wanted to save the whole context of the process, thats why I wan= t > the access to each page allocated to the process of our interest. And > further I want to write all these pages on to swap. > The final objective is to save the context of a stopped process on > the swap and restore the context afterwards and resume the process.Whatfu= nctions can be used to read/write to swap ? I have succeeded > in accessing the vmspace through the 'struct proc' type pointer. > > TIA. > > Best regards, > Pranav > > On 1/17/06, Kamal R. Prasad wrote: > > > > > > > > On 1/16/06, Pranav Sawargaonkar < pranav.sawargaonkar@gmail.com> wrote: > > > > > > Hi > > > I want to access pagetable of a perticular process. > > > How i should get it?Is it possible to access by using pointer of type > > > 'struct proc'? > > > > > > by accessimg the vmspace for the process. > > > > Also i want to access each page referenced in > > > pagetable of that process by writing my module how i can achieve > > > this? > > > Thanks in advance. > > > > > > the pagetable is for translating virtual to physical addresses If you > > want the contents of the page -you don't need to worry about the transl= ation > > scheme. Im not sure I understand what you are looking for?? > > > > regards > > -kamal > > > > > > -Pranav > > > _______________________________________________ > > > 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 Tue Jan 17 13:14:04 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D019E16A469 for ; Tue, 17 Jan 2006 13:14:04 +0000 (GMT) (envelope-from corecode@fs.ei.tum.de) Received: from stella.fs.ei.tum.de (stella.fs.ei.tum.de [129.187.54.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4CE3E43D45 for ; Tue, 17 Jan 2006 13:14:01 +0000 (GMT) (envelope-from corecode@fs.ei.tum.de) Received: from localhost (localhost [127.0.0.1]) by localhost.fs.ei.tum.de (Postfix) with ESMTP id 2B99F8DCE3; Tue, 17 Jan 2006 14:14:00 +0100 (CET) Received: from stella.fs.ei.tum.de ([127.0.0.1]) by localhost (stella [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 32341-04; Tue, 17 Jan 2006 14:13:57 +0100 (CET) Received: from [IPv6:2001:4ca0:0:fe00:0:5efe:a96:b4b4] (unknown [IPv6:2001:4ca0:0:fe00:0:5efe:a96:b4b4]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by stella.fs.ei.tum.de (Postfix) with ESMTP id 8D28A8CAB0; Tue, 17 Jan 2006 14:13:57 +0100 (CET) Message-ID: <43CCED94.3020802@fs.ei.tum.de> Date: Tue, 17 Jan 2006 14:13:56 +0100 From: Simon 'corecode' Schubert User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050912) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Steve Suhre References: <43CC59E7.6080505@nano.net> <015901c61b15$898648a0$1200a8c0@gsicomp.on.ca> <43CC65BC.9040005@nano.net> <44314.63.147.253.154.1137474098.squirrel@webmail7.pair.com> <43CCBAC5.4060809@nano.net> In-Reply-To: <43CCBAC5.4060809@nano.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: by amavisd-new at fs.ei.tum.de Cc: freebsd-hackers@freebsd.org Subject: Re: Named requests filling up T1 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, 17 Jan 2006 13:14:04 -0000 Steve Suhre wrote: > Thanks, I think that's what I was looking for. I expect the "ISP" is in > another country somewhere and would be hard to reach, if they could be > reached at all. And it's probably a bad reference somewhere to the > server here, so shutting of recursive queries could help... If I shut > named off for an hour or two they go away, so I'm guessing the offending > server switches to the secondary and gets what it's looking for? In any case you should only allow recursive queries for your trusted clients and/or downstream nameservers which forward to you. Otherwise a) you produce outgoing traffic when some stranger wants to b) your dns cache can easily be poisoned because of a) cheers simon -- Serve - BSD +++ RENT this banner advert +++ ASCII Ribbon /"\ Work - Mac +++ space for low €€€ NOW!1 +++ Campaign \ / Party Enjoy Relax | http://dragonflybsd.org Against HTML \ Dude 2c 2 the max ! http://golden-apple.biz Mail + News / \ From owner-freebsd-hackers@FreeBSD.ORG Sat Jan 14 14:54:38 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B259216A41F for ; Sat, 14 Jan 2006 14:54:38 +0000 (GMT) (envelope-from tofik@oxygen.az) Received: from mail.alkar.net (mail.alkar.net [195.248.191.95]) by mx1.FreeBSD.org (Postfix) with ESMTP id DEA7543D5D for ; Sat, 14 Jan 2006 14:54:36 +0000 (GMT) (envelope-from tofik@oxygen.az) Received: from [213.227.193.75] (HELO [192.168.0.178]) by mail.alkar.net (CommuniGate Pro SMTP 4.3.9) with ESMTP id 425176987 for freebsd-hackers@freebsd.org; Sat, 14 Jan 2006 16:54:35 +0200 Message-ID: <43C92CF2.6030309@oxygen.az> Date: Sat, 14 Jan 2006 16:55:14 +0000 From: Tofik Suleymanov User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050404) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Tue, 17 Jan 2006 13:32:09 +0000 Subject: adding new sysctl 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, 14 Jan 2006 14:54:38 -0000 Could someone show me how to add new sysctl to the system ? From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 17 03:44:26 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 363BB16A41F for ; Tue, 17 Jan 2006 03:44:26 +0000 (GMT) (envelope-from phreaki@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id B94FA43D46 for ; Tue, 17 Jan 2006 03:44:25 +0000 (GMT) (envelope-from phreaki@gmail.com) Received: by zproxy.gmail.com with SMTP id 16so1305913nzp for ; Mon, 16 Jan 2006 19:44:25 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=QhOaLnOyrr/K0Id/ql5tVA36FEA+W3mJOkicxqMQjF03TFYOcsARyXAw+3SpmmNlh1CZUe017R9bREZ8CSCU4JycvF1/O4DbrDZ2WzF7cq6OxFu1Qc6t/xcQr57hCpTdY/2zbOyK3NtqPOMnOmkcziFRLSdHjuwQm/aM80LjNts= Received: by 10.65.141.6 with SMTP id t6mr3643381qbn; Mon, 16 Jan 2006 19:44:24 -0800 (PST) Received: by 10.65.160.14 with HTTP; Mon, 16 Jan 2006 19:44:24 -0800 (PST) Message-ID: <6fb2b4650601161944tce07ee1x78e2d8ea9d5982f9@mail.gmail.com> Date: Mon, 16 Jan 2006 22:44:24 -0500 From: Robert Atkinson To: Steve Suhre In-Reply-To: <43CC65BC.9040005@nano.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <43CC59E7.6080505@nano.net> <015901c61b15$898648a0$1200a8c0@gsicomp.on.ca> <43CC65BC.9040005@nano.net> X-Mailman-Approved-At: Tue, 17 Jan 2006 13:43:36 +0000 Cc: freebsd-hackers@freebsd.org Subject: Re: Named requests filling up T1 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, 17 Jan 2006 03:44:26 -0000 Then complain to their isp. That has solved most problems for me, and in any case it'll stop or you know it's your problem and not theirs. If you can query your domain by switching your default nameservers to your machine's default NS, and not see any debug messages, you should be fine and complain away. That's only if you are using the same .host files in question, then you should have a fine test bed. Otherwise, i'd do a passive scan on their ip's and identify the OS in question, and test it before I complain. .01 cents P On 1/16/06, Steve Suhre wrote: > > >Looks like someone is spamming your DNS server with queries. > > > >Two questions: > >1) Is v.tn.co.za a domain that you are authorative for? > >2) Are you an ISP and/or is client 64.18.133.103 authorized to use your = DNS > >server? > > > >If the answer to 1) is NO, then there's no reason for these queries to b= e > >directed to your DNS server from the Internet. > >If the answer to 2) is NO, then there's no reason for these queries to b= e > >directed to your DNS server from the Internet. > > > >Source IP filtering is likely your best option, although it doesn't help > >with your T1 saturation, although it would give whoever is blasting thes= e > >queries a clue. > > > >-- > >Matt Emmerton > > > > > > > > > Thanks Matt, > > The answer to both is no. The domain doesn't resolve either > (v.tn.co.za). It looks like the source IP changes too...sigh.... I tried > a whois on the source IP and it was not found, so it may be spoofed? Or > someone has a very messed up server... > > > > > > -- > > > > Steve Suhre > steve@pasta.net > 719.439.6052 Cell > 719.632.2897 Home > > _______________________________________________ > 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 Tue Jan 17 14:11:42 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CE45F16A420 for ; Tue, 17 Jan 2006 14:11:42 +0000 (GMT) (envelope-from victor@bsdes.net) Received: from alf.dyndns.ws (244.Red-217-126-240.staticIP.rima-tde.net [217.126.240.244]) by mx1.FreeBSD.org (Postfix) with ESMTP id 98D8143D45 for ; Tue, 17 Jan 2006 14:11:39 +0000 (GMT) (envelope-from victor@bsdes.net) Received: from alf.dyndns.ws (pato.euesrg02.net [192.168.0.3]) by alf.dyndns.ws (8.13.1/8.13.1) with ESMTP id k0HEBbOO092880 for ; Tue, 17 Jan 2006 15:11:38 +0100 (CET) (envelope-from victor@bsdes.net) Date: Tue, 17 Jan 2006 15:11:37 +0100 From: Victor Balada Diaz To: freebsd-hackers@freebsd.org Message-ID: <20060117141137.GC644@pato.euesrg02.net> References: <43C92CF2.6030309@oxygen.az> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43C92CF2.6030309@oxygen.az> User-Agent: Mutt/1.4.2.1i Subject: Re: adding new sysctl 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, 17 Jan 2006 14:11:42 -0000 On Sat, Jan 14, 2006 at 04:55:14PM +0000, Tofik Suleymanov wrote: > Could someone show me how to add new sysctl to the system ? You have an example in /usr/share/examples/kld/dyn_sysctl/. -- La prueba mas fehaciente de que existe vida inteligente en otros planetas, es que no han intentado contactar con nosotros. From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 17 14:20:05 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B63C916A41F for ; Tue, 17 Jan 2006 14:20:05 +0000 (GMT) (envelope-from evandro@blueone.com.br) Received: from mx1.tpa.com.br (mx1.tpa.com.br [200.203.183.108]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1D3B743D46 for ; Tue, 17 Jan 2006 14:20:03 +0000 (GMT) (envelope-from evandro@blueone.com.br) Received: from evandro (unknown [200.135.220.100]) by mx1.tpa.com.br (Postfix) with ESMTP id 05CA5100820 for ; Tue, 17 Jan 2006 11:54:11 -0200 (BRST) From: "Evandro Sestrem" To: Date: Tue, 17 Jan 2006 12:23:51 -0300 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506 X-AntiVirus-TPA-Information: anti-virus X-AntiVirus-TPA: Mensagem limpa X-TPA-From: evandro@blueone.com.br Subject: Lua 5.0 and FreeBSD 4.1 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, 17 Jan 2006 14:20:05 -0000 Hello, I'm trying compile a project using Lua 5.0 (www.lua.org) in FreePascal (2.0.2 [2005/11/17] for i386) in a FreeBSD 4.1. The Lua 5.0 is correctly installed. It compiles ok, but when it is linking I got these errors: /usr/local/lib//liblualib.a(lmathlib.o): In function 'math_sin': lmathlib.o(.text+0x52): undefined reference to 'sin' /usr/local/lib//liblualib.a(lmathlib.o): In function 'math_cos': lmathlib.o(.text+0x8e): undefined reference to 'cos' /usr/local/lib//liblualib.a(lmathlib.o): In function 'math_tan': lmathlib.o(.text+0xca): undefined reference to 'tan' /usr/local/lib//liblualib.a(lmathlib.o): In function 'math_asin': lmathlib.o(.text+0x106): undefined reference to 'asin' /usr/local/lib//liblualib.a(lmathlib.o): In function 'math_acos': lmathlib.o(.text+0x142): undefined reference to 'acos' /usr/local/lib//liblualib.a(lmathlib.o): In function 'math_atan': lmathlib.o(.text+0x17e): undefined reference to 'atan' /usr/local/lib//liblualib.a(lmathlib.o): In function 'math_atan': lmathlib.o(.text+0x1cb): undefined reference to 'atan2' /usr/local/lib//liblualib.a(lmathlib.o): In function 'math_ceil': lmathlib.o(.text+0x20a): undefined reference to 'ceil' /usr/local/lib//liblualib.a(lmathlib.o): In function 'math_floor': lmathlib.o(.text+0x246): undefined reference to 'floor' /usr/local/lib//liblualib.a(lmathlib.o): In function 'math_mod': lmathlib.o(.text+0x293): undefined reference to 'fmod' /usr/local/lib//liblualib.a(lmathlib.o): In function 'math_sqrt': lmathlib.o(.text+0x2d2): undefined reference to 'sqrt' /usr/local/lib//liblualib.a(lmathlib.o): In function 'math_pow': lmathlib.o(.text+0x31f): undefined reference to 'pow' /usr/local/lib//liblualib.a(lmathlib.o): In function 'math_log': lmathlib.o(.text+0x35e): undefined reference to 'log' /usr/local/lib//liblualib.a(lmathlib.o): In function 'math_log10': lmathlib.o(.text+0x39a): undefined reference to 'log10' /usr/local/lib//liblualib.a(lmathlib.o): In function 'math_exp': lmathlib.o(.text+0x3d6): undefined reference to 'exp' /usr/local/lib//liblualib.a(lmathlib.o): In function 'math_random': lmathlib.o(.text+0x6e1): undefined reference to 'floor' lmathlib.o(.text+0x78d): undefined reference to 'floor' In what version of FreeBSD (or libc) these functions (sin, cos, tan, ...) were implemented? Thanks for any help. Evandro Sestrem -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.371 / Virus Database: 267.14.18/230 - Release Date: 14/1/2006 From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 17 14:35:06 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E35F516A41F for ; Tue, 17 Jan 2006 14:35:05 +0000 (GMT) (envelope-from flz@xbsd.org) Received: from smtp.xbsd.org (xbsd.org [82.233.2.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 25EF043D45 for ; Tue, 17 Jan 2006 14:35:05 +0000 (GMT) (envelope-from flz@xbsd.org) Received: from localhost (localhost.xbsd.org [127.0.0.1]) by smtp.xbsd.org (Postfix) with ESMTP id 0E00D11A93; Tue, 17 Jan 2006 15:35:03 +0100 (CET) Received: from smtp.xbsd.org ([127.0.0.1]) by localhost (srv1.xbsd.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 72248-08; Tue, 17 Jan 2006 15:34:54 +0100 (CET) Received: from cream.xbsd.org (cream.xbsd.org [192.168.42.6]) by smtp.xbsd.org (Postfix) with ESMTP id 746DE11A53; Tue, 17 Jan 2006 15:34:54 +0100 (CET) From: Florent Thoumie To: freebsd-hackers@freebsd.org Date: Tue, 17 Jan 2006 15:34:40 +0100 User-Agent: KMail/1.8.2 References: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1605265.z9RpTi3FGz"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200601171534.50483.flz@xbsd.org> X-Virus-Scanned: amavisd-new at xbsd.org Cc: Evandro Sestrem Subject: Re: Lua 5.0 and FreeBSD 4.1 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, 17 Jan 2006 14:35:06 -0000 --nextPart1605265.z9RpTi3FGz Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tuesday 17 January 2006 16:23, Evandro Sestrem wrote: > Hello, > > I'm trying compile a project using Lua 5.0 (www.lua.org) in FreePascal > (2.0.2 [2005/11/17] for i386) in a FreeBSD 4.1. > > The Lua 5.0 is correctly installed. > > It compiles ok, but when it is linking I got these errors: > > /usr/local/lib//liblualib.a(lmathlib.o): In function 'math_sin': > lmathlib.o(.text+0x52): undefined reference to 'sin' > /usr/local/lib//liblualib.a(lmathlib.o): In function 'math_cos': > lmathlib.o(.text+0x8e): undefined reference to 'cos' > /usr/local/lib//liblualib.a(lmathlib.o): In function 'math_tan': > lmathlib.o(.text+0xca): undefined reference to 'tan' > /usr/local/lib//liblualib.a(lmathlib.o): In function 'math_asin': > lmathlib.o(.text+0x106): undefined reference to 'asin' > /usr/local/lib//liblualib.a(lmathlib.o): In function 'math_acos': > lmathlib.o(.text+0x142): undefined reference to 'acos' > /usr/local/lib//liblualib.a(lmathlib.o): In function 'math_atan': > lmathlib.o(.text+0x17e): undefined reference to 'atan' > /usr/local/lib//liblualib.a(lmathlib.o): In function 'math_atan': > lmathlib.o(.text+0x1cb): undefined reference to 'atan2' > /usr/local/lib//liblualib.a(lmathlib.o): In function 'math_ceil': > lmathlib.o(.text+0x20a): undefined reference to 'ceil' > /usr/local/lib//liblualib.a(lmathlib.o): In function 'math_floor': > lmathlib.o(.text+0x246): undefined reference to 'floor' > /usr/local/lib//liblualib.a(lmathlib.o): In function 'math_mod': > lmathlib.o(.text+0x293): undefined reference to 'fmod' > /usr/local/lib//liblualib.a(lmathlib.o): In function 'math_sqrt': > lmathlib.o(.text+0x2d2): undefined reference to 'sqrt' > /usr/local/lib//liblualib.a(lmathlib.o): In function 'math_pow': > lmathlib.o(.text+0x31f): undefined reference to 'pow' > /usr/local/lib//liblualib.a(lmathlib.o): In function 'math_log': > lmathlib.o(.text+0x35e): undefined reference to 'log' > /usr/local/lib//liblualib.a(lmathlib.o): In function 'math_log10': > lmathlib.o(.text+0x39a): undefined reference to 'log10' > /usr/local/lib//liblualib.a(lmathlib.o): In function 'math_exp': > lmathlib.o(.text+0x3d6): undefined reference to 'exp' > /usr/local/lib//liblualib.a(lmathlib.o): In function 'math_random': > lmathlib.o(.text+0x6e1): undefined reference to 'floor' > lmathlib.o(.text+0x78d): undefined reference to 'floor' > > > > In what version of FreeBSD (or libc) these functions (sin, cos, tan, ...) > were implemented? man sin says it's libm (-lm). =2D-=20 =46lorent Thoumie flz@FreeBSD.org =46reeBSD Committer --nextPart1605265.z9RpTi3FGz Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDzQCKMxEkbVFH3PQRApOyAKCL9FdU3+Ayt0+RT7ueP0HlkrASoACfe2xw 1PnfGrzZFKosbfLsxvFz83w= =Qdmc -----END PGP SIGNATURE----- --nextPart1605265.z9RpTi3FGz-- From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 17 14:38:41 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6CC6516A420 for ; Tue, 17 Jan 2006 14:38:41 +0000 (GMT) (envelope-from ghos@mail.ru) Received: from mx6.mail.ru (mx6.mail.ru [194.67.23.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id A5C5A43D70 for ; Tue, 17 Jan 2006 14:38:39 +0000 (GMT) (envelope-from ghos@mail.ru) Received: from [193.125.69.18] (port=33898 helo=[192.168.0.99]) by mx6.mail.ru with asmtp id 1Eyrym-000EXK-00; Tue, 17 Jan 2006 17:38:37 +0300 User-Agent: Microsoft-Outlook-Express-Macintosh-Edition/5.0.5 Date: Tue, 17 Jan 2006 17:40:53 +0300 From: Vyacheslav Anikin To: Evandro Sestrem , Message-ID: In-Reply-To: Mime-version: 1.0 X-Mobile: +79066102537 X-ICQ: 192-688-969 X-Uname: FreeBSD 6.0-R i386 beer X-PGP-Fingerprint: E060 8972 17A3 9914 650E 6D38 E270 4AEB 0B29 1911 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Cc: Subject: Re: Lua 5.0 and FreeBSD 4.1 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, 17 Jan 2006 14:38:41 -0000 on 17/1/06 18:23, Evandro Sestrem at evandro@blueone.com.br wrote: > > Hello, > > I'm trying compile a project using Lua 5.0 (www.lua.org) in FreePascal > (2.0.2 [2005/11/17] for i386) in a FreeBSD 4.1. > > The Lua 5.0 is correctly installed. > > It compiles ok, but when it is linking I got these errors: > > [snipped] > > In what version of FreeBSD (or libc) these functions (sin, cos, tan, ...) > were implemented? This lib is the math lib -- libm :-). > > Thanks for any help. > > Evandro Sestrem Regards -- Vyacheslav Anikin From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 17 14:44:30 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D070416A420 for ; Tue, 17 Jan 2006 14:44:30 +0000 (GMT) (envelope-from freebsd@rea.mbslab.kiae.ru) Received: from rea.mbslab.kiae.ru (rea.mbslab.kiae.ru [144.206.177.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4674E43D60 for ; Tue, 17 Jan 2006 14:44:21 +0000 (GMT) (envelope-from freebsd@rea.mbslab.kiae.ru) Received: from rea.mbslab.kiae.ru (localhost [127.0.0.1]) by rea.mbslab.kiae.ru (Postfix) with ESMTP id 12D8BBF26; Tue, 17 Jan 2006 17:44:20 +0300 (MSK) Received: by rea.mbslab.kiae.ru (Postfix, from userid 1000) id E08F8BF07; Tue, 17 Jan 2006 17:44:19 +0300 (MSK) Date: Tue, 17 Jan 2006 17:44:19 +0300 From: FreeLSD To: Evandro Sestrem Message-ID: <20060117144419.GZ53598@rea.mbslab.kiae.ru> References: Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.11 X-AV-Checked: Yes! Cc: freebsd-hackers@freebsd.org Subject: Re: Lua 5.0 and FreeBSD 4.1 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, 17 Jan 2006 14:44:30 -0000 > /usr/local/lib//liblualib.a(lmathlib.o): In function 'math_sin': > lmathlib.o(.text+0x52): undefined reference to 'sin' Hardly a hackers@ question, but you should link with the math library libm by using the '-lm' switch to the linker. -- rea BOFH excuse #55: Plumber mistook routing panel for decorative wall fixture From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 17 14:44:35 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0403816A420 for ; Tue, 17 Jan 2006 14:44:35 +0000 (GMT) (envelope-from joseph.koshy@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id B006F43D55 for ; Tue, 17 Jan 2006 14:44:31 +0000 (GMT) (envelope-from joseph.koshy@gmail.com) Received: by xproxy.gmail.com with SMTP id s9so1068025wxc for ; Tue, 17 Jan 2006 06:44:31 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=jlyzskJ7Tsee1uAQ4JMFvxrscsJI7EIL82aQWVP0stdEbgk6bcebdWbImRIfN9XbVIZEg81BzSpurX2Znyn3GpREJnFHiLklR2mdjAXpCc1NEOnv0rFLAzl8qNR+YcLalJunx2/bCmdVCtHRHij9SXu8c9QyssbOdDDImJx+67E= Received: by 10.70.110.9 with SMTP id i9mr9092937wxc; Tue, 17 Jan 2006 06:44:29 -0800 (PST) Received: by 10.70.105.2 with HTTP; Tue, 17 Jan 2006 06:44:27 -0800 (PST) Message-ID: <84dead720601170644u4ef07827l92bdda54b4f7cd55@mail.gmail.com> Date: Tue, 17 Jan 2006 20:14:27 +0530 From: Joseph Koshy To: Evandro Sestrem In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: Cc: freebsd-hackers@freebsd.org Subject: Re: Lua 5.0 and FreeBSD 4.1 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, 17 Jan 2006 14:44:35 -0000 > In what version of FreeBSD (or libc) these functions (sin, cos, > tan, ...) were implemented? Are you linking with libm? -- FreeBSD Volunteer, http://people.freebsd.org/~jkoshy From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 17 14:51:48 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0EA2416A41F for ; Tue, 17 Jan 2006 14:51:48 +0000 (GMT) (envelope-from joerg@britannica.bec.de) Received: from hydra.bec.de (www.ostsee-abc.de [62.206.222.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6BC5743D45 for ; Tue, 17 Jan 2006 14:51:47 +0000 (GMT) (envelope-from joerg@britannica.bec.de) Received: from britannica.bec.de (unknown [139.30.252.72]) by hydra.bec.de (Postfix) with ESMTP id C444435707 for ; Tue, 17 Jan 2006 15:51:45 +0100 (CET) Received: by britannica.bec.de (Postfix, from userid 1000) id 756116D17C; Tue, 17 Jan 2006 15:51:14 +0100 (CET) Date: Tue, 17 Jan 2006 15:51:14 +0100 From: joerg@britannica.bec.de To: freebsd-hackers@freebsd.org Message-ID: <20060117145114.GB9251@britannica.bec.de> Mail-Followup-To: freebsd-hackers@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.11 Subject: Re: Lua 5.0 and FreeBSD 4.1 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, 17 Jan 2006 14:51:48 -0000 On Tue, Jan 17, 2006 at 12:23:51PM -0300, Evandro Sestrem wrote: > > It compiles ok, but when it is linking I got these errors: -lm Joerg From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 17 15:49:00 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CA36316A41F for ; Tue, 17 Jan 2006 15:49:00 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 56C8243D46 for ; Tue, 17 Jan 2006 15:49:00 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 179AB20C2; Tue, 17 Jan 2006 16:48:55 +0100 (CET) X-Spam-Tests: AWL,BAYES_00,FORGED_RCVD_HELO X-Spam-Learn: ham X-Spam-Score: -3.2/3.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on tim.des.no Received: from xps.des.no (des.no [80.203.243.180]) by tim.des.no (Postfix) with ESMTP id 8CB4A20BD; Tue, 17 Jan 2006 16:48:54 +0100 (CET) Received: by xps.des.no (Postfix, from userid 1001) id 785A633C3E; Tue, 17 Jan 2006 16:48:54 +0100 (CET) To: Antti Korpela References: <43CC3C6B.4060703@devnet.fi> From: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=) Date: Tue, 17 Jan 2006 16:48:54 +0100 In-Reply-To: <43CC3C6B.4060703@devnet.fi> (Antti Korpela's message of "Tue, 17 Jan 2006 02:38:03 +0200") Message-ID: <86wtgyhn2x.fsf@xps.des.no> User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@freebsd.org Subject: Re: FreeBSD 6.0 default pty/tty-limit (256) OFF! 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, 17 Jan 2006 15:49:00 -0000 Antti Korpela writes: > I need patch to raise FreeBSD 6.0 default pty/tty-limit (256) UP or OFF. I already gave you a patch. Your unwillingness to provide the information necessary to figure out why my patch doesn't work for you is entirely *your* problem. > In shell-production usage, that limit is ridiculous, there must be > stop to this and put PTY-limits off! Remember that this ridiculous software was provided to you by us entirely free of charge. Show us a minimum of respect, and try to work *with* us to resolve issues instead of demanding solutions on a silver platter. > I changed my servers operating systems moment ago from Linux to > FreeBSD thinking that FreeBSD could be more better, but how this can > be possible, that so important think like PTYs are limited to so > low?? every UNIX has more ptys. We are not responsible for your failure to adequately test your systems before putting them in production, nor for your misconceptions about the nature of Unix[tm]. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 17 17:04:01 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 83AA216A41F for ; Tue, 17 Jan 2006 17:04:01 +0000 (GMT) (envelope-from mohan_srinivasan@yahoo.com) Received: from web31815.mail.mud.yahoo.com (web31815.mail.mud.yahoo.com [68.142.206.168]) by mx1.FreeBSD.org (Postfix) with SMTP id 90D2E43D5C for ; Tue, 17 Jan 2006 17:04:00 +0000 (GMT) (envelope-from mohan_srinivasan@yahoo.com) Received: (qmail 73778 invoked by uid 60001); 17 Jan 2006 17:03:59 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=GiVLLzmD5AApTpgmrXwZE5MoFL13vZjbf046KxadioRbBa2RoGXkhry5uzSOE5fZ6tP7vb9PCDDQRcSiPeeWtkawSTKLbuzSAnjZ9F+cAPwIlPqB60GndacZPE/4HxbHnRGwZokkg4F0/go3etSfWFuqdMjHARAyJd1IAZeLW4Q= ; Message-ID: <20060117170359.73776.qmail@web31815.mail.mud.yahoo.com> Received: from [71.139.6.191] by web31815.mail.mud.yahoo.com via HTTP; Tue, 17 Jan 2006 09:03:59 PST Date: Tue, 17 Jan 2006 09:03:59 -0800 (PST) From: Mohan Srinivasan To: frank@exit.com, hackers@freebsd.org In-Reply-To: <1137477965.95312.15.camel@realtime.exit.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailman-Approved-At: Tue, 17 Jan 2006 17:26:14 +0000 Cc: FreeBSD-Current Subject: Re: Panic in nfs_putpages() on 6-stable, more info. 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, 17 Jan 2006 17:04:01 -0000 > See http://www.freebsd.org/cgi/query-pr.cgi?pr=91879 for the patch. I > went ahead and fixed all the filesystems I could find, since they all > had nearly identical code. I just looked at your changes (and at ufs_reclaim()). I'll get this committed to current and it'll get MFC'ed. mohan From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 17 17:29:44 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1B64E16A41F; Tue, 17 Jan 2006 17:29:44 +0000 (GMT) (envelope-from saturnero@freesbie.org) Received: from jail1-fbsd4.consiagnet.it (jail1-fbsd4.consiagnet.it [83.149.128.151]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8ECC043D48; Tue, 17 Jan 2006 17:29:34 +0000 (GMT) (envelope-from saturnero@freesbie.org) Received: from jail1-fbsd4.consiagnet.it (jail1-fbsd4.consiagnet.it [83.149.128.151]) by jail1-fbsd4.consiagnet.it (Postfix) with ESMTP id 83BA75766; Tue, 17 Jan 2006 18:37:03 +0100 (CET) X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on cvs.freesbie.org X-Spam-Level: * X-Spam-Status: No, score=1.4 required=5.0 tests=AWL,BAYES_00, RCVD_IN_SORBS_DUL autolearn=no version=3.1.0 Received: from [192.168.99.16] (host14-150.pool875.interbusiness.it [87.5.150.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by jail1-fbsd4.consiagnet.it (Postfix) with ESMTP; Tue, 17 Jan 2006 18:37:03 +0100 (CET) Message-ID: <43CD2974.3030308@freesbie.org> Date: Tue, 17 Jan 2006 18:29:24 +0100 From: Dario Freni User-Agent: Mozilla Thunderbird 1.0.7 (Macintosh/20050923) X-Accept-Language: it, it-it, en-us, en MIME-Version: 1.0 To: Daichi GOTO References: <43BD1054.7020409@ongs.co.jp> <43C2472C.5070103@freebsd.org> <43C90A68.9000909@freebsd.org> In-Reply-To: <43C90A68.9000909@freebsd.org> X-Enigmail-Version: 0.92.0.0 OpenPGP: url=http://www.saturnero.net/saturnero.asc Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig76D6B12D56AD9896B771151E" X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org, ozawa@ongs.co.jp Subject: Re: [unionfs][patch] improvements of the unionfs - Problem Report, kern/91010 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, 17 Jan 2006 17:29:44 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig76D6B12D56AD9896B771151E Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Daichi GOTO ha scritto: > I have updated the patches: > > For 7-current patch > http://people.freebsd.org/~daichi/unionfs/unionfs-p5.diff > > For 6.x patch > http://people.freebsd.org/~daichi/unionfs/unionfs6-p5.diff > > Changes from -p4: > - fixed around "can't fifo/vnode bypass -1" panic problem > - added some comments into source-code for src-developer > - edited style as style(9) saye FreeSBIE test image with a debug kernel patched with -p5 patchset: http://torrent.freesbie.org/FreeSBIE-unionfs-i386-20060116.iso.torrent To obtain a panic, just do normal operations like login as freesbie (/usr/home/freesbie is under unionfs). If you log in as root, you should be able to inspect something in the filesystem without having a panic. The panic is triggered by the chdir syscall: panic: userret: Returning with 1 locks held. cpuid = 0 KDB: enter: panic [thread pid 592 tid 100063 ] Stopped at kdb_enter+0x2c: leave db> bt Tracing pid 592 tid 100063 td 0xc1a8a180 kdb_enter(c08fc650,100,c1a8a180,d,c1f2c000) at kdb_enter+0x2c panic(c08ff985,1,d,c1a8a180,c1f2c000) at panic+0x17f ast(c1a8a180,c83c5d38,43,2,43) at ast syscall(3b,3b,3b,3e8,bfbfe940) at syscall+0x186 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (13, FreeBSD ELF32, fchdir), eip = 0x28131cdb, esp = 0xbfbfe84c, ebp = 0xbfbfe8e8 --- db> Bye, Dario -- Dario Freni (saturnero@freesbie.org) FreeSBIE developer (http://www.freesbie.org) GPG Public key at http://www.saturnero.net/saturnero.asc --------------enig76D6B12D56AD9896B771151E Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFDzSl3ymi72IiShysRAmElAJ9617k4HCiLYOLyxYz68WA1u1tjQgCfY6ar PKZQPIAEAYYWGNPCmA6Iysc= =ZcQW -----END PGP SIGNATURE----- --------------enig76D6B12D56AD9896B771151E-- From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 17 18:41:16 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 720EC16A41F for ; Tue, 17 Jan 2006 18:41:16 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1BF1343D48 for ; Tue, 17 Jan 2006 18:41:14 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 6286306 for multiple; Tue, 17 Jan 2006 13:39:48 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k0HIf9kC039570; Tue, 17 Jan 2006 13:41:09 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: kamalp@acm.org Date: Tue, 17 Jan 2006 13:11:17 -0500 User-Agent: KMail/1.9.1 References: <1fa17f810601122232l25551bc5n4e4a01ff6b7921e@mail.gmail.com> <200601131422.15208.jhb@freebsd.org> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200601171311.20570.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1244/Tue Jan 17 03:46:07 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-1.4 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: freebsd-hackers@freebsd.org, prime Subject: Re: How priority propagation works on read/write lock? 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, 17 Jan 2006 18:41:16 -0000 On Monday 16 January 2006 00:08, Kamal R. Prasad wrote: > you mean, boosting the priority of a reader would be required to avoid > priority inversion, but difficult to implement? > > regards > -kamal > > On 1/14/06, John Baldwin wrote: > > I think you just kind of punt and do a best effort. Trying to manage a > > list > > of current read lock holders would be a bit PITA. Yes. The actual boosting is rather simple, it's keeping track of who has read locks that is ugly. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 17 19:00:32 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 772B816A41F; Tue, 17 Jan 2006 19:00:32 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6FB1743D48; Tue, 17 Jan 2006 19:00:26 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.ntplx.net (8.13.5/8.13.5/NETPLEX) with ESMTP id k0HJ0MKN011365; Tue, 17 Jan 2006 14:00:23 -0500 (EST) Date: Tue, 17 Jan 2006 14:00:22 -0500 (EST) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: John Baldwin In-Reply-To: <200601171311.20570.jhb@freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net) Cc: freebsd-hackers@freebsd.org, prime , kamalp@acm.org Subject: Re: How priority propagation works on read/write lock? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jan 2006 19:00:32 -0000 On Tue, 17 Jan 2006, John Baldwin wrote: > On Monday 16 January 2006 00:08, Kamal R. Prasad wrote: > > you mean, boosting the priority of a reader would be required to avoid > > priority inversion, but difficult to implement? > > > > regards > > -kamal > > > > On 1/14/06, John Baldwin wrote: > > > I think you just kind of punt and do a best effort. Trying to manage a > > > list > > > of current read lock holders would be a bit PITA. > > Yes. The actual boosting is rather simple, it's keeping track of who has read > locks that is ugly. Hmm, do you really care which or if all of the readers get their priority boosted? Can't you just boost the priority of [any] one of the readers, and when he releases the lock and the reader lock count is still positive, boost the priority of another reader? Keep doing this until all the current readers have released the lock. In a perfect world you'd like to boost all of the readers, but that's pretty hard without chaining together all the readers and allowing for nested locks. I'm assuming that this is only needed when a [higher priority] writer wants the read lock. -- DE From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 17 19:37:18 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 76D5216A420; Tue, 17 Jan 2006 19:37:18 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id AF6EB43D45; Tue, 17 Jan 2006 19:37:17 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 6290971 for multiple; Tue, 17 Jan 2006 14:35:54 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k0HJbFYa039971; Tue, 17 Jan 2006 14:37:15 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: Daniel Eischen Date: Tue, 17 Jan 2006 14:37:13 -0500 User-Agent: KMail/1.9.1 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200601171437.15995.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1244/Tue Jan 17 03:46:07 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-1.4 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: freebsd-hackers@freebsd.org, prime , kamalp@acm.org Subject: Re: How priority propagation works on read/write lock? 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, 17 Jan 2006 19:37:18 -0000 On Tuesday 17 January 2006 14:00, Daniel Eischen wrote: > On Tue, 17 Jan 2006, John Baldwin wrote: > > On Monday 16 January 2006 00:08, Kamal R. Prasad wrote: > > > you mean, boosting the priority of a reader would be required to avoid > > > priority inversion, but difficult to implement? > > > > > > regards > > > -kamal > > > > > > On 1/14/06, John Baldwin wrote: > > > > I think you just kind of punt and do a best effort. Trying to manage > > > > a list > > > > of current read lock holders would be a bit PITA. > > > > Yes. The actual boosting is rather simple, it's keeping track of who has > > read locks that is ugly. > > Hmm, do you really care which or if all of the readers get their > priority boosted? Can't you just boost the priority of [any] one > of the readers, and when he releases the lock and the reader lock > count is still positive, boost the priority of another reader? > Keep doing this until all the current readers have released the > lock. In a perfect world you'd like to boost all of the readers, > but that's pretty hard without chaining together all the readers > and allowing for nested locks. > > I'm assuming that this is only needed when a [higher priority] > writer wants the read lock. Yes, that is one possibility, and is a more complex method than what Solaris uses. For now I'm just not doing any propogation for read locks in the hopes of having a simpler and _working_ implementation first that can then be experimented with further. :) -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 17 21:22:38 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2FA9A16A41F; Tue, 17 Jan 2006 21:22:38 +0000 (GMT) (envelope-from julian@elischer.org) Received: from a50.ironport.com (a50.ironport.com [63.251.108.112]) by mx1.FreeBSD.org (Postfix) with ESMTP id D68C943D45; Tue, 17 Jan 2006 21:22:37 +0000 (GMT) (envelope-from julian@elischer.org) Received: from unknown (HELO [10.251.23.146]) ([10.251.23.146]) by a50.ironport.com with ESMTP; 17 Jan 2006 13:22:38 -0800 X-IronPort-Anti-Spam-Filtered: true Message-ID: <43CD601D.6040807@elischer.org> Date: Tue, 17 Jan 2006 13:22:37 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.11) Gecko/20050727 X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Baldwin References: <1fa17f810601122232l25551bc5n4e4a01ff6b7921e@mail.gmail.com> <200601131422.15208.jhb@freebsd.org> <200601171311.20570.jhb@freebsd.org> In-Reply-To: <200601171311.20570.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, prime , kamalp@acm.org Subject: Re: How priority propagation works on read/write lock? 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, 17 Jan 2006 21:22:38 -0000 John Baldwin wrote: >On Monday 16 January 2006 00:08, Kamal R. Prasad wrote: > > >>you mean, boosting the priority of a reader would be required to avoid >>priority inversion, but difficult to implement? >> >>regards >>-kamal >> >>On 1/14/06, John Baldwin wrote: >> >> >>>I think you just kind of punt and do a best effort. Trying to manage a >>>list >>>of current read lock holders would be a bit PITA. >>> >>> > >Yes. The actual boosting is rather simple, it's keeping track of who has read >locks that is ugly. > > > I do wonder if it is worth while. it would require an internediated structure that would be simultaneously linked into a number of structures.. it would be linked into a list of "read locks held by this thread, and it would be linked into a list of "threads currently reading on this read lock" it would however be a rathe small item, and I can imagine that a cache of a thousand or so of these would probably do enough for the system. Something like: struct rwlock_nexsus { SLIST_ENTRY( rwlock_nexus) by_thread; struct thread *owner; SLIST_ENTRY (rwlock_nexus) by_lock; struct rwlock *locked; } on a x86 this would be 16 bytes long.. on an amd64, 32 bytes in a page of 4k (x86) you get 256 of them. that's quite a few considerring that we have only 4 processers or so running code at a time and you probably shouldn't be unscheduled while holding one.. From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 18 09:39:29 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A2E1316A43A for ; Wed, 18 Jan 2006 09:39:27 +0000 (GMT) (envelope-from asmrookie@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5303043E4D for ; Wed, 18 Jan 2006 09:38:35 +0000 (GMT) (envelope-from asmrookie@gmail.com) Received: by zproxy.gmail.com with SMTP id 9so1576672nzo for ; Wed, 18 Jan 2006 01:38:35 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:references; b=VDP5FgZalcR8/MPPjjUpQdan/hQiwBVWY3SFGLrOnry2TB7LDO5DGYFG05Za5WPqPcbzdi7PgnMcvrY3lhgWUCPNnHWCnYC5Tq75gUYGqBHzqnwppHodszjFMJTtrM7esiEI4tUm2qk80oRN7ycq2nggszhXVG8VfFOCSr9FSEI= Received: by 10.36.39.5 with SMTP id m5mr6517700nzm; Wed, 18 Jan 2006 01:38:34 -0800 (PST) Received: by 10.36.43.4 with HTTP; Wed, 18 Jan 2006 01:38:34 -0800 (PST) Message-ID: <3bbf2fe10601180138m3a5ab67cx@mail.gmail.com> Date: Wed, 18 Jan 2006 10:38:34 +0100 From: rookie To: deischen@freebsd.org In-Reply-To: MIME-Version: 1.0 References: <3bbf2fe10601171111x7432a2aaj@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hackers@freebsd.org Subject: Re: How priority propagation works on read/write lock? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: rookie@gufi.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Jan 2006 09:39:30 -0000 >> This approach fails beacause you need to propagate priority for any blocking >> thread for any owners (if needed). > I'm not sure I follow -- got a simple example? > A writer won't be able to get the write lock until _all_ of the > current read lock owners have released the lock. It doesn't > matter which of the readers you propagate to, eventually all > of them will have their priority propagated. > > On a single CPU system, there is no advantage to propagating > priority to all of the current readers because only one can > run at a time. On an SMP system, the disadvantage is that you > lose the ability for multiple read lock owners to run at the > same time. Let's say: threads A, B, C own a read lock (RW1). After a while: - A blocks on a write lock (D thread owns) - B blocks on a read lock (owned by other threads, we say E1, E2, E3) - C blocks on a mutex (owned by F) Now if a thread G blocks on RW1 and its priority is higher than A,B,C (whic= h might have the same priority) priority propagation is needed to hit D, { E1= , E2, E3 } and F. If you just do priority propagation for one of them the other would not be updated. turnstiles don't hurts beacause some intrusive lists are defined involving turnstiles and threads so a sort of "chain" like that: turnstile->thread->turnstile->thread... is provided. In the case of multple thread we could have a situation like: thread1 thread1 turnstile->thread2->turnstile--------------->thread2 thread3->turnstile->thread thread3 And so on. I did a recursive algorithm for a new primitive (rwblock) which correctly implements priority propagation for multiple owners mechanism but there are 2 problems: 1) this algorithm is recursive and it's enough hard to change 2) With a new primitive some work of integration between existing (turnstiles) might be provided. Currently I'm working on both these problematics and I hope to do something better next times. Cheers, Attilio -- Peace can only be achieved by understanding - A. Einstein From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 18 14:31:40 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 69DCE16A41F for ; Wed, 18 Jan 2006 14:31:40 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 021D243D45 for ; Wed, 18 Jan 2006 14:31:39 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.ntplx.net (8.13.5/8.13.5/NETPLEX) with ESMTP id k0IEVcBU011508; Wed, 18 Jan 2006 09:31:38 -0500 (EST) Date: Wed, 18 Jan 2006 09:31:38 -0500 (EST) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: rookie@gufi.org In-Reply-To: <3bbf2fe10601180138m3a5ab67cx@mail.gmail.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net) Cc: freebsd-hackers@freebsd.org Subject: Re: How priority propagation works on read/write lock? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Jan 2006 14:31:40 -0000 On Wed, 18 Jan 2006, rookie wrote: > >> This approach fails beacause you need to propagate priority for any > blocking > >> thread for any owners (if needed). > > > I'm not sure I follow -- got a simple example? > > A writer won't be able to get the write lock until _all_ of the > > current read lock owners have released the lock. It doesn't > > matter which of the readers you propagate to, eventually all > > of them will have their priority propagated. > > > > On a single CPU system, there is no advantage to propagating > > priority to all of the current readers because only one can > > run at a time. On an SMP system, the disadvantage is that you > > lose the ability for multiple read lock owners to run at the > > same time. > > Let's say: threads A, B, C own a read lock (RW1). > > After a while: > - A blocks on a write lock (D thread owns) > - B blocks on a read lock (owned by other threads, we say E1, E2, E3) > - C blocks on a mutex (owned by F) > Now if a thread G blocks on RW1 and its priority is higher than A,B,C (which > might have the same priority) priority propagation is needed to hit D, { E1, > E2, E3 } and F. If you just do priority propagation for one of them the > other would not be updated. You will eventually do priority propagation for all of them (A, B, and C) until G's priority is <= the priority of RW1. It doesn't matter if you do one at a time or all of them at once. They all (A, B, C) have to release RW1 before G can run. > > turnstiles don't hurts beacause some intrusive lists are defined involving > turnstiles and threads so a sort of "chain" like that: > > turnstile->thread->turnstile->thread... > > is provided. In the case of multple thread we could have a situation like: > thread1 thread1 > turnstile->thread2->turnstile--------------->thread2 > thread3->turnstile->thread thread3 > > And so on. > > I did a recursive algorithm for a new primitive (rwblock) which correctly > implements priority propagation for multiple owners mechanism but there are > 2 problems: > > 1) this algorithm is recursive and it's enough hard to change > 2) With a new primitive some work of integration between existing > (turnstiles) might be provided. > > Currently I'm working on both these problematics and I hope to do something > better next times. -- DE From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 18 15:01:13 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 31A9016A41F for ; Wed, 18 Jan 2006 15:01:13 +0000 (GMT) (envelope-from ler@lerctr.org) Received: from lerami.lerctr.org (lerami.lerctr.org [192.147.25.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE85043D46 for ; Wed, 18 Jan 2006 15:01:10 +0000 (GMT) (envelope-from ler@lerctr.org) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=lerami; d=lerctr.org; b=iskGFNVEO9d1vcoCTPAab9xEupIMJKj+R1hR35J4aCyiEkaJxLFYAnnsMGk7EX2bdjvFl6wRAza2MgCGFp7E1NDHVnQoX7k1pHyhtgkrDqdes6bumJHtHD7MdIXAWJI7nRXj5uHCMvrmo72rG3PXLk3R2GH/XvINLAhK5tkPZUg=; Received: from 64-132-13-2.gen.twtelecom.net ([64.132.13.2]:46913 helo=LROSENMAC8010P) by lerami.lerctr.org with esmtpsa (TLSv1:RC4-MD5:128) (Exim 4.60) (envelope-from ) id 1EzEo7-000679-KA for freebsd-hackers@freebsd.org; Wed, 18 Jan 2006 09:01:10 -0600 From: "Larry Rosenman" To: Date: Wed, 18 Jan 2006 09:01:06 -0600 Message-ID: <00a201c61c40$02160500$0a0a0a0a@aus.pervasive.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670 Thread-Index: AcYcQAG9SvJAg7BwTeaXiNx1Fkr9RQ== X-Spam-Score: -4.4 (----) X-LERCTR-Spam-Score: -4.4 (----) X-Spam-Report: (-4.4 points, 5.0 required) ALL_TRUSTED=-1.8 BAYES_00=-2.599 DK_POLICY_SIGNSOME=0.001 X-LERCTR-Spam-Report: (-4.4 points, 5.0 required) ALL_TRUSTED=-1.8 BAYES_00=-2.599 DK_POLICY_SIGNSOME=0.001 DomainKey-Status: no signature Subject: CVSUP14.US.FREEBSD.ORG: Health Check? 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, 18 Jan 2006 15:01:13 -0000 I just tried to cvsup using cvsup14.us.freebsd.org, and got no updates. I know there were changes, so I tried cvsup15.us.freebsd.org, and got the desired changes. Can the cvsup14.us.freebsd.org maintainer check it's health? (if this isn't the right place, please direct me to the correct place. Thanks). LER -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: ler@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 18 15:15:42 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2306316A41F for ; Wed, 18 Jan 2006 15:15:42 +0000 (GMT) (envelope-from asmrookie@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4B7A643D48 for ; Wed, 18 Jan 2006 15:15:41 +0000 (GMT) (envelope-from asmrookie@gmail.com) Received: by zproxy.gmail.com with SMTP id 9so1644600nzo for ; Wed, 18 Jan 2006 07:15:40 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:references; b=M+A2M8IFMA9MwHivb1dK1aBUB2YXPGSWngMTJHxueI6L/zQkOIaSOrSb9NzfesOuT9U95mGxZKNCuYeoM/eURzMh5Dnk26t70zD/Tfmk7evC+Z2/3sayiyuSumqyD46LINHVst/EknHN9aK2MakFzVXDrzc7xPNHWYo1oTzaXwU= Received: by 10.37.14.38 with SMTP id r38mr6672217nzi; Wed, 18 Jan 2006 07:15:40 -0800 (PST) Received: by 10.36.43.4 with HTTP; Wed, 18 Jan 2006 07:15:40 -0800 (PST) Message-ID: <3bbf2fe10601180715k25297666y@mail.gmail.com> Date: Wed, 18 Jan 2006 16:15:40 +0100 From: rookie To: Daniel Eischen In-Reply-To: MIME-Version: 1.0 References: <3bbf2fe10601180138m3a5ab67cx@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hackers@freebsd.org Subject: Re: How priority propagation works on read/write lock? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: rookie@gufi.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Jan 2006 15:15:42 -0000 2006/1/18, Daniel Eischen : >You will eventually do priority propagation for all of them > (A, B, and C) until G's priority is <=3D the priority of RW1. > It doesn't matter if you do one at a time or all of them > at once. They all (A, B, C) have to release RW1 before > G can run You don't point out the problem. Here the problem is propagating priority to D, {E1, E2, E3} and F. If it doesn't happen the whole system will starve. Cheers, Attilio -- Peace can only be achieved by understanding - A. Einstein From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 18 16:11:14 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5B0A816A41F for ; Wed, 18 Jan 2006 16:11:14 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id BBBAA43D46 for ; Wed, 18 Jan 2006 16:11:13 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.ntplx.net (8.13.5/8.13.5/NETPLEX) with ESMTP id k0IGBCmN013419; Wed, 18 Jan 2006 11:11:12 -0500 (EST) Date: Wed, 18 Jan 2006 11:11:09 -0500 (EST) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: rookie@gufi.org In-Reply-To: <3bbf2fe10601180715k25297666y@mail.gmail.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net) Cc: freebsd-hackers@freebsd.org Subject: Re: How priority propagation works on read/write lock? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Jan 2006 16:11:14 -0000 On Wed, 18 Jan 2006, rookie wrote: > 2006/1/18, Daniel Eischen : > >You will eventually do priority propagation for all of them > > (A, B, and C) until G's priority is <= the priority of RW1. > > It doesn't matter if you do one at a time or all of them > > at once. They all (A, B, C) have to release RW1 before > > G can run > > You don't point out the problem. > Here the problem is propagating priority to D, {E1, E2, E3} and F. If it > doesn't happen the whole system will starve. I assume we already know how to propagate priority for mutexes, so once you know how to propagate for RWlocks, it all just works. Yes, once you choose a thread to propagate, you have to keep propagating through whatever it is blocked on or until you reach a point where the propagated priority is <= the priority of the next thread in the heirarchy. I never questioned that part of it, just the need to do it for all threads owning the RW lock at the same time. -- DE From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 18 16:31:25 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5132016A41F for ; Wed, 18 Jan 2006 16:31:25 +0000 (GMT) (envelope-from asmrookie@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id D102943D6E for ; Wed, 18 Jan 2006 16:31:19 +0000 (GMT) (envelope-from asmrookie@gmail.com) Received: by zproxy.gmail.com with SMTP id 9so1665256nzo for ; Wed, 18 Jan 2006 08:31:19 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:references; b=brDQ+MXkd5ok7/97lgf3ZOMSwi7hmNlcdTMEGJcQ0HycmNrn6yDREpybEXrCFU0fyeMJYUk5qzYfIhbtZNrC6Q4AC4bhV6boUv2d/JmzVLkT4/5QbMRnFKf3bUmiIEWfGKnKW/iTnwCJlgBrJfGmVd18dSFzxtrDGhLZvr2Ioko= Received: by 10.36.39.5 with SMTP id m5mr6742768nzm; Wed, 18 Jan 2006 08:31:19 -0800 (PST) Received: by 10.36.43.4 with HTTP; Wed, 18 Jan 2006 08:31:19 -0800 (PST) Message-ID: <3bbf2fe10601180831r69dbf1f9j@mail.gmail.com> Date: Wed, 18 Jan 2006 17:31:19 +0100 From: rookie To: Daniel Eischen In-Reply-To: MIME-Version: 1.0 References: <3bbf2fe10601180715k25297666y@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hackers@freebsd.org Subject: Re: How priority propagation works on read/write lock? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: rookie@gufi.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Jan 2006 16:31:25 -0000 2006/1/18, Daniel Eischen : > I assume we already know how to propagate priority for mutexes, so > once you know how to propagate for RWlocks, it all just works. As I can see, propagate priority for mutex needs a little modify to turnstiles code, that's not a great deal. > Yes, once you choose a thread to propagate, you have to keep > propagating through whatever it is blocked on or until you > reach a point where the propagated priority is <=3D the priority > of the next thread in the heirarchy. I never questioned that > part of it, just the need to do it for all threads owning the > RW lock at the same time. Maybe it's not "strictly" necessary but please consider that "blocking hierarchies" are never too long and a total priority propagation would be quicker (you however need to propagate to every owner in the end so doing i= t at the same time could craft a bottleneck if the hierarchy is too long, but it's a rare case and in the opposite way you need to rule 'what thread need= s to be update' every time a blocking thread is unblocked). Cheers, Attilio -- Peace can only be achieved by understanding - A. Einstein From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 18 17:35:31 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 16D6316A41F for ; Wed, 18 Jan 2006 17:35:31 +0000 (GMT) (envelope-from user@dhp.com) Received: from shell.dhp.com (shell.dhp.com [199.245.105.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 97E5943D45 for ; Wed, 18 Jan 2006 17:35:30 +0000 (GMT) (envelope-from user@dhp.com) Received: by shell.dhp.com (Postfix, from userid 896) id B08DE3133D; Wed, 18 Jan 2006 12:35:29 -0500 (EST) Date: Wed, 18 Jan 2006 12:35:29 -0500 (EST) From: Ensel Sharon To: freebsd-hackers@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Mailman-Approved-At: Wed, 18 Jan 2006 17:56:54 +0000 Subject: tuning to run large (1000+) numbers of null_mounts 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, 18 Jan 2006 17:35:31 -0000 I am running over 2000 null mounts on a FreeBSD 6.0-RELEASE system. I am well aware of the status of the null_mount code, as advertised in the mount_nullfs man page: THIS FILE SYSTEM TYPE IS NOT YET FULLY SUPPORTED (READ: IT DOESN'T WORK) AND USING IT MAY, IN FACT, DESTROY DATA ON YOUR SYSTEM. USE AT YOUR OWN RISK. BEWARE OF DOG. SLIPPERY WHEN WET. So, based on this, all of my null_mounts are actually mounted read-only. I am noticing both system instability and data corruption issues on disk following crashes. Both of these seem to be related to the null mounts. I have two very quick questions: 1. Is my theory that using only read-only null mounts is a good way to avoid data corruption a sound one ? Or can even a read-only null mount do bad things to underlying data ? 2. What system tunes / alterations would be appropriate for a system running several thousand (although, always less than 5000) null mounted filesystems ? Please relay _any and all_ comments, suggestions, war stories, rumors. They are very appreciated. From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 18 18:03:01 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6CB3316A422; Wed, 18 Jan 2006 18:03:01 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2C41D43D45; Wed, 18 Jan 2006 18:02:59 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 6374115 for multiple; Wed, 18 Jan 2006 13:03:57 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k0II2vZ5056163; Wed, 18 Jan 2006 13:02:57 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-hackers@freebsd.org, rookie@gufi.org Date: Wed, 18 Jan 2006 12:34:17 -0500 User-Agent: KMail/1.9.1 References: <3bbf2fe10601180715k25297666y@mail.gmail.com> <3bbf2fe10601180831r69dbf1f9j@mail.gmail.com> In-Reply-To: <3bbf2fe10601180831r69dbf1f9j@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200601181234.19349.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1245/Wed Jan 18 11:57:44 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-1.4 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: Daniel Eischen Subject: Re: How priority propagation works on read/write lock? 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, 18 Jan 2006 18:03:01 -0000 On Wednesday 18 January 2006 11:31, rookie wrote: > 2006/1/18, Daniel Eischen : > > I assume we already know how to propagate priority for mutexes, so > > once you know how to propagate for RWlocks, it all just works. > > As I can see, propagate priority for mutex needs a little modify to > turnstiles code, that's not a great deal. > > > Yes, once you choose a thread to propagate, you have to keep > > propagating through whatever it is blocked on or until you > > reach a point where the propagated priority is <= the priority > > of the next thread in the heirarchy. I never questioned that > > part of it, just the need to do it for all threads owning the > > RW lock at the same time. > > Maybe it's not "strictly" necessary but please consider that "blocking > hierarchies" are never too long and a total priority propagation would be > quicker (you however need to propagate to every owner in the end so doing > it at the same time could craft a bottleneck if the hierarchy is too long, > but it's a rare case and in the opposite way you need to rule 'what thread > needs to be update' every time a blocking thread is unblocked). One thing you need to think about is allowing for the fact that a thread might hold multiple read locks of the same lock (i.e., recursion) and it can hold read locks of more than one read lock. Your current use of a field in struct thread to link together the list of read owners for a lock won't work in the case of a thread holding a read lock of two different rw locks. This is why I think it is too hard to keep track of all the readers. Otherwise you have to provide storage somewhere else for the list of threads and it needs to not use malloc or rwlocks will be intolerably slow. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 18 18:21:49 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6D0BB16A41F for ; Wed, 18 Jan 2006 18:21:49 +0000 (GMT) (envelope-from david@madole.net) Received: from d.omd3.com (d.omd3.com [69.90.174.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id DB92243D48 for ; Wed, 18 Jan 2006 18:21:48 +0000 (GMT) (envelope-from david@madole.net) Received: from dhcp-66-212-201-164.myeastern.com ([66.212.201.164] helo=david) by d.omd3.com with esmtpa (Exim 4.54) id 1EzHwK-00016D-72; Wed, 18 Jan 2006 13:21:48 -0500 Message-ID: <1d4901c61c5c$0a9147a0$c3e7a8c0@david> From: "David S. Madole" To: "Ensel Sharon" , References: Date: Wed, 18 Jan 2006 13:21:43 -0500 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2670 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670 Cc: Subject: Re: tuning to run large (1000+) numbers of null_mounts 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, 18 Jan 2006 18:21:49 -0000 From: "Ensel Sharon" > > I am running over 2000 null mounts on a FreeBSD 6.0-RELEASE system. I > am > well aware of the status of the null_mount code, as advertised in the > mount_nullfs man page: > > I am noticing both system instability and data corruption issues on > disk > following crashes. Both of these seem to be related to the null > mounts. I have two very quick questions: For what it's worth, I have three null mounts on each of eight 5.4-RELEASE systems that are read/write and have extensive activity and I have not had a single filesystem problem in 15 months of this configuration. But 2000 of them? I don't know, I've never envisioned 2000 of any kind of mount. David From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 18 18:53:37 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 39E8B16A41F for ; Wed, 18 Jan 2006 18:53:37 +0000 (GMT) (envelope-from devon.odell@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id C2BA643D4C for ; Wed, 18 Jan 2006 18:53:36 +0000 (GMT) (envelope-from devon.odell@gmail.com) Received: by xproxy.gmail.com with SMTP id s9so8749wxc for ; Wed, 18 Jan 2006 10:53:36 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=VnQI4vII71yHGu1aemyWOeCzKmRgSG9bIa0Nv62f7ZGTwBO413RaKR692zUvh3/4Rodx7f8FDYOagRK9lKb8qbDa0dQFtDtAeLoClz5vu0++F9p55AbF+fZKZC2jtOEz7FnInk5SrJwgB73nPZNv38YVfGrMAVtdpCcHsRgw/fU= Received: by 10.70.69.10 with SMTP id r10mr10994490wxa; Wed, 18 Jan 2006 10:53:35 -0800 (PST) Received: by 10.70.65.4 with HTTP; Wed, 18 Jan 2006 10:53:35 -0800 (PST) Message-ID: <9ab217670601181053r41132634y@mail.gmail.com> Date: Wed, 18 Jan 2006 10:53:35 -0800 From: "Devon H. O'Dell" To: Ensel Sharon In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: Cc: freebsd-hackers@freebsd.org Subject: Re: tuning to run large (1000+) numbers of null_mounts 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, 18 Jan 2006 18:53:37 -0000 2006/1/18, Ensel Sharon : > > I am running over 2000 null mounts on a FreeBSD 6.0-RELEASE system. I am > well aware of the status of the null_mount code, as advertised in the > mount_nullfs man page: > > THIS FILE SYSTEM TYPE IS NOT YET FULLY SUPPORTED (READ: IT DOESN'T > WORK) > AND USING IT MAY, IN FACT, DESTROY DATA ON YOUR SYSTEM. USE AT YOUR > OWN > RISK. BEWARE OF DOG. SLIPPERY WHEN WET. This has been removed from the manpage because it's no longer accurate. I believe I recall seeing another thread with someone asking whether it still applied and the answer was, ``No.'' --Devon From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 18 19:03:10 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5D7C716A41F for ; Wed, 18 Jan 2006 19:03:10 +0000 (GMT) (envelope-from erdgeist@erdgeist.org) Received: from elektropost.org (elektropost.org [80.237.196.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 892AF43D46 for ; Wed, 18 Jan 2006 19:03:09 +0000 (GMT) (envelope-from erdgeist@erdgeist.org) Received: (qmail 61536 invoked by uid 0); 18 Jan 2006 19:03:02 -0000 Received: from erdgeist.org (erdgeist@erdgeist.org@80.237.196.15) by elektropost.org with AES256-SHA encrypted SMTP; 18 Jan 2006 19:03:02 -0000 Date: Wed, 18 Jan 2006 20:03:01 +0100 (CET) From: Dirk Engling To: Ensel Sharon In-Reply-To: <9ab217670601181053r41132634y@mail.gmail.com> Message-ID: <20060118195608.T46468@erdgeist.org> References: <9ab217670601181053r41132634y@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-hackers@freebsd.org Subject: Re: tuning to run large (1000+) numbers of null_mounts 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, 18 Jan 2006 19:03:10 -0000 On Wed, 18 Jan 2006, Devon H. O'Dell wrote: > This has been removed from the manpage because it's no longer > accurate. I believe I recall seeing another thread with someone asking > whether it still applied and the answer was, ``No.'' On a test installation I am running > 100 Jails with around 200 nullfs read only mount points and had had no problems with nullfs for 7:59pm up 54 days, 22:46, 5 users, load averages: 0,25 0,37 0,38 Regards erdgeist From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 18 19:18:33 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5E0BC16A41F for ; Wed, 18 Jan 2006 19:18:33 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id BC9B643D55 for ; Wed, 18 Jan 2006 19:18:32 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id A00721A3C1F; Wed, 18 Jan 2006 11:18:32 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id DB0FF5140B; Wed, 18 Jan 2006 14:18:31 -0500 (EST) Date: Wed, 18 Jan 2006 14:18:31 -0500 From: Kris Kennaway To: Ensel Sharon Message-ID: <20060118191831.GA47747@xor.obsecurity.org> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="jRHKVT23PllUwdXP" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: freebsd-hackers@freebsd.org Subject: Re: tuning to run large (1000+) numbers of null_mounts 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, 18 Jan 2006 19:18:33 -0000 --jRHKVT23PllUwdXP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jan 18, 2006 at 12:35:29PM -0500, Ensel Sharon wrote: >=20 > I am running over 2000 null mounts on a FreeBSD 6.0-RELEASE system. I am > well aware of the status of the null_mount code, as advertised in the > mount_nullfs man page: >=20 > THIS FILE SYSTEM TYPE IS NOT YET FULLY SUPPORTED (READ: IT DOESN'T > WORK) > AND USING IT MAY, IN FACT, DESTROY DATA ON YOUR SYSTEM. USE AT YOUR > OWN > RISK. BEWARE OF DOG. SLIPPERY WHEN WET. >=20 > So, based on this, all of my null_mounts are actually mounted read-only. As others have said, this is no longer applicable to FreeBSD 6.0, and it's been removed from HEAD. > I am noticing both system instability and data corruption issues on disk > following crashes. Both of these seem to be related to the null > mounts. I have two very quick questions: I've not used 2000 null mounts, but I commonly use ~100 of them at once on a number of systems and have not observed problems relating to this. However, it's possible you're finding new bugs, so you should report them in the usual way (gdb backtrace of panics, etc). Kris --jRHKVT23PllUwdXP Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDzpSHWry0BWjoQKURAgx/AJ9jAyfazE7NA8tdb2obqzpKgig6xgCbBjbw HwUzh8Cs7zbKsY1FtJ84bc0= =kBat -----END PGP SIGNATURE----- --jRHKVT23PllUwdXP-- From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 18 19:54:07 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2771716A41F for ; Wed, 18 Jan 2006 19:54:07 +0000 (GMT) (envelope-from user@dhp.com) Received: from shell.dhp.com (shell.dhp.com [199.245.105.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id D0C9F43D49 for ; Wed, 18 Jan 2006 19:54:06 +0000 (GMT) (envelope-from user@dhp.com) Received: by shell.dhp.com (Postfix, from userid 896) id 7321A3133D; Wed, 18 Jan 2006 14:54:04 -0500 (EST) Date: Wed, 18 Jan 2006 14:54:04 -0500 (EST) From: Ensel Sharon To: Kris Kennaway In-Reply-To: <20060118191831.GA47747@xor.obsecurity.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Mailman-Approved-At: Wed, 18 Jan 2006 20:01:33 +0000 Cc: freebsd-hackers@freebsd.org Subject: Re: tuning to run large (1000+) numbers of null_mounts 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, 18 Jan 2006 19:54:07 -0000 On Wed, 18 Jan 2006, Kris Kennaway wrote: > > RISK. BEWARE OF DOG. SLIPPERY WHEN WET. > > > > So, based on this, all of my null_mounts are actually mounted read-only. > > As others have said, this is no longer applicable to FreeBSD 6.0, and > it's been removed from HEAD. hmmm...the cut and paste of that loud warning was from a 6.0-RELEASE man page ... if I need to be CURRENT to get the updated man page, do I also need to be CURRENT to get the safe null_mount code itself ? Or is 6.0-RELEASE safe ? (re: null_mount) Thanks a lot. From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 18 20:14:16 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D964516A424 for ; Wed, 18 Jan 2006 20:14:16 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mail2.fluidhosting.com [204.14.90.12]) by mx1.FreeBSD.org (Postfix) with SMTP id EF2AD43D4C for ; Wed, 18 Jan 2006 20:14:15 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: (qmail 73772 invoked by uid 399); 18 Jan 2006 20:14:15 -0000 Received: from localhost (HELO ?192.168.1.101?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 18 Jan 2006 20:14:15 -0000 Message-ID: <43CEA195.5000708@FreeBSD.org> Date: Wed, 18 Jan 2006 12:14:13 -0800 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 1.5 (X11/20060112) MIME-Version: 1.0 To: Ensel Sharon References: In-Reply-To: X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, Kris Kennaway Subject: Re: tuning to run large (1000+) numbers of null_mounts 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, 18 Jan 2006 20:14:17 -0000 Ensel Sharon wrote: > hmmm...the cut and paste of that loud warning was from a 6.0-RELEASE man > page ... if I need to be CURRENT to get the updated man page, do I also > need to be CURRENT to get the safe null_mount code itself ? > > Or is 6.0-RELEASE safe ? (re: null_mount) It probably wouldn't hurt to try upgrading to 6-stable. -- This .signature sanitized for your protection From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 18 20:19:42 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E431716A41F for ; Wed, 18 Jan 2006 20:19:42 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8DC1943D53 for ; Wed, 18 Jan 2006 20:19:42 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 6B1201A3C22; Wed, 18 Jan 2006 12:19:42 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 92B8A5154A; Wed, 18 Jan 2006 15:19:41 -0500 (EST) Date: Wed, 18 Jan 2006 15:19:41 -0500 From: Kris Kennaway To: Ensel Sharon Message-ID: <20060118201941.GA48904@xor.obsecurity.org> References: <20060118191831.GA47747@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="0F1p//8PRICkK4MW" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: freebsd-hackers@freebsd.org, Kris Kennaway Subject: Re: tuning to run large (1000+) numbers of null_mounts 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, 18 Jan 2006 20:19:43 -0000 --0F1p//8PRICkK4MW Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jan 18, 2006 at 02:54:04PM -0500, Ensel Sharon wrote: >=20 >=20 > On Wed, 18 Jan 2006, Kris Kennaway wrote: >=20 > > > RISK. BEWARE OF DOG. SLIPPERY WHEN WET. > > >=20 > > > So, based on this, all of my null_mounts are actually mounted read-on= ly. > >=20 > > As others have said, this is no longer applicable to FreeBSD 6.0, and > > it's been removed from HEAD. >=20 >=20 > hmmm...the cut and paste of that loud warning was from a 6.0-RELEASE man > page ... if I need to be CURRENT to get the updated man page, do I also > need to be CURRENT to get the safe null_mount code itself ? >=20 > Or is 6.0-RELEASE safe ? (re: null_mount) >=20 > Thanks a lot. 6.0-RELEASE is also safe. I only just removed the warning the other day, but I'll also be merging it to 6.0-STABLE. Kris --0F1p//8PRICkK4MW Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDzqLdWry0BWjoQKURAmkyAJ0RZAw/6wUQBijIdmYvsnK+cRu3fwCfdpAG c+FgryPADAnqFcHAkyvsous= =HqKo -----END PGP SIGNATURE----- --0F1p//8PRICkK4MW-- From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 18 22:40:34 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8084516A420 for ; Wed, 18 Jan 2006 22:40:34 +0000 (GMT) (envelope-from so14k@so14k.com) Received: from ender.liquidneon.com (ender.liquidneon.com [64.78.150.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0B1F043D4C for ; Wed, 18 Jan 2006 22:40:33 +0000 (GMT) (envelope-from so14k@so14k.com) Received: from localhost (localhost [127.0.0.1]) by ender.liquidneon.com (Postfix) with ESMTP id 4825CA6CC7 for ; Wed, 18 Jan 2006 15:40:33 -0700 (MST) Received: from ender.liquidneon.com ([127.0.0.1]) by localhost (ender.liquidneon.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 78985-07 for ; Wed, 18 Jan 2006 15:40:32 -0700 (MST) Received: by ender.liquidneon.com (Postfix, from userid 1000) id D8901A6CC5; Wed, 18 Jan 2006 15:40:32 -0700 (MST) Date: Wed, 18 Jan 2006 15:40:31 -0700 From: Brad Davis To: freebsd-hackers@freebsd.org Message-ID: <20060118224031.GA79110@ender.liquidneon.com> References: <43CEBB93.5040804@bsdhacker.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43CEBB93.5040804@bsdhacker.org> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: by amavisd-new at ender.liquidneon.com Subject: Re: CVSUP14.US.FREEBSD.ORG: Health Check? 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, 18 Jan 2006 22:40:34 -0000 > I just tried to cvsup using cvsup14.us.freebsd.org, and got no > updates. I know there were changes, so I tried cvsup15.us.freebsd.org, and > got the desired changes. > > Can the cvsup14.us.freebsd.org maintainer check it's health? > > (if this isn't the right place, please direct me to the correct place. > Thanks). Thanks, it has been fixed.. I'm replacing the machine and I had to pull the new machine back out of service temporarily and put the original back in place. Regards, Brad Davis From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 19 03:21:44 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0F33A16A41F for ; Thu, 19 Jan 2006 03:21:44 +0000 (GMT) (envelope-from matt@gsicomp.on.ca) Received: from skippyii.compar.com (old.compar.com [216.208.38.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7A78243D45 for ; Thu, 19 Jan 2006 03:21:43 +0000 (GMT) (envelope-from matt@gsicomp.on.ca) Received: from hermes (CPE00062566c7bb-CM0011e6ede298.cpe.net.cable.rogers.com [70.28.254.189]) by skippyii.compar.com (8.13.1/8.13.1) with ESMTP id k0J3OMSH066354 for ; Wed, 18 Jan 2006 22:24:23 -0500 (EST) (envelope-from matt@gsicomp.on.ca) Message-ID: <001501c61ca7$9c1d7450$1200a8c0@gsicomp.on.ca> From: "Matt Emmerton" To: Date: Wed, 18 Jan 2006 22:22:42 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1506 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506 Subject: Config(8) dependency checking - first patches 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, 19 Jan 2006 03:21:44 -0000 Folks, I've written up some patches to add dependency checking to config(8). This will help prevent link errors when compiling kernels with an incomplete kernel config (things like fxp without miibus; umass without da/scbus, etc.) The current set of patches add support to config(8) to read, parse and use dependency information; however, no dependency meta-data has been generated yet. Notes and patches against 7-CURRENT are at http://www.gsicomp.on.ca/projects/freebsd/configdep.html. Comments and suggestions appreciated. Regards, -- Matt Emmerton From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 19 06:59:38 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A046B16A41F for ; Thu, 19 Jan 2006 06:59:38 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 565D043D48 for ; Thu, 19 Jan 2006 06:59:38 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 350391A3C1B; Wed, 18 Jan 2006 22:59:38 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 8840D5125B; Thu, 19 Jan 2006 01:59:37 -0500 (EST) Date: Thu, 19 Jan 2006 01:59:37 -0500 From: Kris Kennaway To: Ensel Sharon Message-ID: <20060119065937.GA65484@xor.obsecurity.org> References: <20060118201941.GA48904@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="yrj/dFKFPuw6o+aM" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: freebsd-hackers@freebsd.org, Kris Kennaway Subject: Re: tuning to run large (1000+) numbers of null_mounts 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, 19 Jan 2006 06:59:38 -0000 --yrj/dFKFPuw6o+aM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jan 19, 2006 at 01:55:22AM -0500, Ensel Sharon wrote: >=20 >=20 > On Wed, 18 Jan 2006, Kris Kennaway wrote: >=20 > > > hmmm...the cut and paste of that loud warning was from a 6.0-RELEASE = man > > > page ... if I need to be CURRENT to get the updated man page, do I al= so > > > need to be CURRENT to get the safe null_mount code itself ? > > >=20 > > > Or is 6.0-RELEASE safe ? (re: null_mount) > > >=20 > > > Thanks a lot. > >=20 > > 6.0-RELEASE is also safe. I only just removed the warning the other > > day, but I'll also be merging it to 6.0-STABLE. >=20 >=20 > Ok, that is good to know. >=20 > However, I continue to see instability on this system with the 2000+ > null_mounts. Are there any system tunables / sysctls / kernel > configurations that I should be studying or experimenting with that are > relevant to this ? >=20 > Perhaps looking more broadly, are there any tunables related to large > numbers of mounted filesystems _period_, not just null mounts ? Not that I know of. You'll need to proceed down the debugging route I mentioned. > For what it is worth, the system also has several mdconfig'd and mounted > snapshots (more than 5, less than 10). Further, all of the null mounts > mount space from within a mounted snapshot into normal filesystem space. = =20 > With all the snapshots mounted and all the null mounts mounted, I find > that commencing an rsync from the filesystem that all these exist on locks > up the machine. I can still ping it, but it refuses all connections. It > requires a power cycle. >=20 > Comments ? Snapshots are a much more likely cause of system instability than nullfs mounts, IMO. Kris --yrj/dFKFPuw6o+aM Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDzzjYWry0BWjoQKURAtMzAJ9EtHfIfYy1/adjxzrT04pXciehyQCg9UtG 1SZlrtqyHfgQw5t4jl6CGq4= =90zd -----END PGP SIGNATURE----- --yrj/dFKFPuw6o+aM-- From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 19 08:37:40 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 053CE16A41F for ; Thu, 19 Jan 2006 08:37:40 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 882B743D48 for ; Thu, 19 Jan 2006 08:37:39 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 44C5220B7; Thu, 19 Jan 2006 09:37:32 +0100 (CET) X-Spam-Tests: AWL,BAYES_00,FORGED_RCVD_HELO X-Spam-Learn: ham X-Spam-Score: -3.2/3.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on tim.des.no Received: from xps.des.no (des.no [80.203.243.180]) by tim.des.no (Postfix) with ESMTP id 3752120B5; Thu, 19 Jan 2006 09:37:32 +0100 (CET) Received: by xps.des.no (Postfix, from userid 1001) id 2373A33C4C; Thu, 19 Jan 2006 09:37:32 +0100 (CET) To: Ashok Shrestha References: <79e2026f0601142345x1a9269bdl3153d1bb110be08d@mail.gmail.com> From: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=) Date: Thu, 19 Jan 2006 09:37:32 +0100 In-Reply-To: <79e2026f0601142345x1a9269bdl3153d1bb110be08d@mail.gmail.com> (Ashok Shrestha's message of "Sun, 15 Jan 2006 02:45:30 -0500") Message-ID: <86ek34d35f.fsf@xps.des.no> User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@freebsd.org, Brandon Flowers Subject: Re: speed up port compiling using RAM (tmpfs) ??? 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, 19 Jan 2006 08:37:40 -0000 Ashok Shrestha writes: > I am curious to know if there is a way to compile a port such as X11 > or KDE faster. > > I know in Gentoo, you can mount a part of RAM and compile in that. > This substantially decreases the compile time. Reference: > http://gentoo-wiki.com/TIP_Speeding_up_portage_with_tmpfs > > Does anyone know how to do this in Freebsd? I doubt it would help. You get faster disk accesses, but significantly reduce the amount of memory available for the buffer cache. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 19 06:55:24 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1841B16A41F for ; Thu, 19 Jan 2006 06:55:24 +0000 (GMT) (envelope-from user@dhp.com) Received: from shell.dhp.com (shell.dhp.com [199.245.105.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 968EA43D45 for ; Thu, 19 Jan 2006 06:55:23 +0000 (GMT) (envelope-from user@dhp.com) Received: by shell.dhp.com (Postfix, from userid 896) id DCE0E31313; Thu, 19 Jan 2006 01:55:22 -0500 (EST) Date: Thu, 19 Jan 2006 01:55:22 -0500 (EST) From: Ensel Sharon To: Kris Kennaway In-Reply-To: <20060118201941.GA48904@xor.obsecurity.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Mailman-Approved-At: Thu, 19 Jan 2006 12:35:34 +0000 Cc: freebsd-hackers@freebsd.org Subject: Re: tuning to run large (1000+) numbers of null_mounts 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, 19 Jan 2006 06:55:24 -0000 On Wed, 18 Jan 2006, Kris Kennaway wrote: > > hmmm...the cut and paste of that loud warning was from a 6.0-RELEASE man > > page ... if I need to be CURRENT to get the updated man page, do I also > > need to be CURRENT to get the safe null_mount code itself ? > > > > Or is 6.0-RELEASE safe ? (re: null_mount) > > > > Thanks a lot. > > 6.0-RELEASE is also safe. I only just removed the warning the other > day, but I'll also be merging it to 6.0-STABLE. Ok, that is good to know. However, I continue to see instability on this system with the 2000+ null_mounts. Are there any system tunables / sysctls / kernel configurations that I should be studying or experimenting with that are relevant to this ? Perhaps looking more broadly, are there any tunables related to large numbers of mounted filesystems _period_, not just null mounts ? For what it is worth, the system also has several mdconfig'd and mounted snapshots (more than 5, less than 10). Further, all of the null mounts mount space from within a mounted snapshot into normal filesystem space. With all the snapshots mounted and all the null mounts mounted, I find that commencing an rsync from the filesystem that all these exist on locks up the machine. I can still ping it, but it refuses all connections. It requires a power cycle. Comments ? From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 19 11:12:25 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4082616A41F for ; Thu, 19 Jan 2006 11:12:25 +0000 (GMT) (envelope-from bsdlists@celeritystorm.com) Received: from mail.celeritystorm.com (213-247-62-79.ip.netshark.nl [213.247.62.79]) by mx1.FreeBSD.org (Postfix) with ESMTP id B83DC43D48 for ; Thu, 19 Jan 2006 11:12:24 +0000 (GMT) (envelope-from bsdlists@celeritystorm.com) Received: by mail.celeritystorm.com (Postfix, from userid 106) id EAE2B3D8C3C; Thu, 19 Jan 2006 12:29:57 +0100 (CET) Received: from [192.168.0.1] (unknown [81.84.174.103]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.celeritystorm.com (Postfix) with ESMTP id A4E813D756B for ; Thu, 19 Jan 2006 12:29:54 +0100 (CET) Message-ID: <43CF7420.6090401@celeritystorm.com> Date: Thu, 19 Jan 2006 11:12:32 +0000 From: BSD User-Agent: Mozilla Thunderbird 0.7.2 (X11/20040724) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Thu, 19 Jan 2006 12:39:28 +0000 Subject: Apache & PV_ENTRY 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, 19 Jan 2006 11:12:25 -0000 Hello list, I am configuring a very heavily used apache webserver, that required some special needs. This particular configuration needs to have at least 1024 httpds always running. Reaching this number is not a problem, but whenever I stop apache via apachectl stop, I notice all the httpds take a long time (1 min) to vanish - and meanwhile, top shows most of them locked. The states I see in top are: *vm ob RUN while the header shows: 1038 processes:332 running, 12 sleeping, 694 lock The numbers vary a lot. Eventually, they get killed, but it takes too much time. After some searching, I found out the cause for this was running out of PVs. I've added the following relevant options to the kernel: options KVA_PAGES=768 options PMAP_SHPGPERPROC=5120 sysctl vm.zone | grep PV shows: (note: httpd stopped here) (limit) (used) (free) (requests) PV ENTRY: 24, 84410445, 5522, 1632543, 5381679 So, if my assumptions are correct, and running out of PVs was the cause (I did get that message about increasing PMAP_SHPGPERPROC before I placed that in the kernel), there is a problem now. If you look at the vm.zone output, there are 84,410,445 PVs that could exist, but the system shows only 1,632,543 free. This leads me to believe there is another thing to tune. I already have a high PVs limit, but according to this output, it's not going further than 1,6 millions. My question is, what can I do to make the system use the full 84 millions, as I have not found any way to do this. From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 19 16:54:12 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 706AB16A420 for ; Thu, 19 Jan 2006 16:54:12 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 638EA43D53 for ; Thu, 19 Jan 2006 16:54:07 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id C865320C7; Thu, 19 Jan 2006 17:54:02 +0100 (CET) X-Spam-Tests: AWL,BAYES_00,FORGED_RCVD_HELO X-Spam-Learn: ham X-Spam-Score: -3.2/3.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on tim.des.no Received: from xps.des.no (des.no [80.203.243.180]) by tim.des.no (Postfix) with ESMTP id B597F20B8; Thu, 19 Jan 2006 17:54:02 +0100 (CET) Received: by xps.des.no (Postfix, from userid 1001) id A691433C1D; Thu, 19 Jan 2006 17:54:02 +0100 (CET) To: Mike Meyer References: <79e2026f0601142345x1a9269bdl3153d1bb110be08d@mail.gmail.com> <86ek34d35f.fsf@xps.des.no> <17359.49899.183831.844670@bhuda.mired.org> From: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=) Date: Thu, 19 Jan 2006 17:54:02 +0100 In-Reply-To: <17359.49899.183831.844670@bhuda.mired.org> (Mike Meyer's message of "Thu, 19 Jan 2006 11:48:43 -0500") Message-ID: <86k6cww445.fsf@xps.des.no> User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Ashok Shrestha , Brandon Flowers , freebsd-hackers@freebsd.org Subject: Re: speed up port compiling using RAM (tmpfs) ??? 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, 19 Jan 2006 16:54:12 -0000 Mike Meyer writes: > Will using a swap-backed disk change anything? Not really. > How about the best way to configure things to use two disks for the > compile? I'm not sure what you are trying to achieve. Unlike the base system, the ports tree does not use separate source and object directories. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 19 17:51:13 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2BC8E16A41F for ; Thu, 19 Jan 2006 17:51:13 +0000 (GMT) (envelope-from wxs@syn.csh.rit.edu) Received: from syn.csh.rit.edu (syn.csh.rit.edu [129.21.60.158]) by mx1.FreeBSD.org (Postfix) with ESMTP id B30C343D46 for ; Thu, 19 Jan 2006 17:51:12 +0000 (GMT) (envelope-from wxs@syn.csh.rit.edu) Received: from syn.csh.rit.edu (localhost [127.0.0.1]) by syn.csh.rit.edu (8.13.4/8.13.4) with ESMTP id k0JHqTtR071849; Thu, 19 Jan 2006 12:52:29 -0500 (EST) (envelope-from wxs@syn.csh.rit.edu) Received: (from wxs@localhost) by syn.csh.rit.edu (8.13.4/8.13.4/Submit) id k0JHqOPj071848; Thu, 19 Jan 2006 12:52:24 -0500 (EST) (envelope-from wxs) Date: Thu, 19 Jan 2006 12:52:24 -0500 From: Wesley Shields To: Dag-Erling Sm?rgrav Message-ID: <20060119175224.GA71633@csh.rit.edu> References: <79e2026f0601142345x1a9269bdl3153d1bb110be08d@mail.gmail.com> <86ek34d35f.fsf@xps.des.no> <17359.49899.183831.844670@bhuda.mired.org> <86k6cww445.fsf@xps.des.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <86k6cww445.fsf@xps.des.no> User-Agent: Mutt/1.5.11 Cc: Ashok Shrestha , Brandon Flowers , Mike Meyer , freebsd-hackers@freebsd.org Subject: Re: speed up port compiling using RAM (tmpfs) ??? 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, 19 Jan 2006 17:51:13 -0000 On Thu, Jan 19, 2006 at 05:54:02PM +0100, Dag-Erling Sm?rgrav wrote: > Mike Meyer writes: > > Will using a swap-backed disk change anything? > > Not really. > > > How about the best way to configure things to use two disks for the > > compile? > > I'm not sure what you are trying to achieve. Unlike the base system, > the ports tree does not use separate source and object directories. I think he is trying to get at a scenario where WRKDIR is on a seperate disk from the one /usr/ports is on. To answer his question, assuming this is what he is going, for why not just add a new physical disk to the system per the handbook, and set WRKDIR to be where ever that disk is mounted. -- WXS From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 19 20:21:12 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1776C16A41F for ; Thu, 19 Jan 2006 20:21:12 +0000 (GMT) (envelope-from ashok.shrestha@gmail.com) Received: from uproxy.gmail.com (uproxy.gmail.com [66.249.92.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4F8A843D49 for ; Thu, 19 Jan 2006 20:21:11 +0000 (GMT) (envelope-from ashok.shrestha@gmail.com) Received: by uproxy.gmail.com with SMTP id o2so39023uge for ; Thu, 19 Jan 2006 12:21:09 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=l72OH3lSeTK0wRgY5fyC5eNN5eeQ2RLXORJ072kk6BkeHVR/qx9NDD2GJsSU4/+wh+hiXcxV1hzN6M5Pryi3MJmoCpVvHXYZKhLnbWm3hxUq/7grcP7ZgsTdSXeMQ4LpZ+hE5byOMLSErvGlcClUFiNxyt9qFMau06zgp0PEMpE= Received: by 10.48.14.12 with SMTP id 12mr79696nfn; Thu, 19 Jan 2006 12:15:08 -0800 (PST) Received: by 10.49.20.18 with HTTP; Thu, 19 Jan 2006 12:15:08 -0800 (PST) Message-ID: <79e2026f0601191215p117d78ebjbee2c4b710075154@mail.gmail.com> Date: Thu, 19 Jan 2006 15:15:08 -0500 From: Ashok Shrestha To: Wesley Shields In-Reply-To: <20060119175224.GA71633@csh.rit.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <79e2026f0601142345x1a9269bdl3153d1bb110be08d@mail.gmail.com> <86ek34d35f.fsf@xps.des.no> <17359.49899.183831.844670@bhuda.mired.org> <86k6cww445.fsf@xps.des.no> <20060119175224.GA71633@csh.rit.edu> Cc: Dag-Erling Sm?rgrav , Brandon Flowers , Mike Meyer , freebsd-hackers@freebsd.org Subject: Re: speed up port compiling using RAM (tmpfs) ??? 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, 19 Jan 2006 20:21:12 -0000 I mounted part of RAM as such: mdmfs -s 500m md /mnt Then put WRKDIRPREFIX=3D/path/to/md in /etc/make.conf. It substantially reduces compile time by about 5-10 times. Thanx to all ur replies. -Ashok Shrestha On 1/19/06, Wesley Shields wrote: > On Thu, Jan 19, 2006 at 05:54:02PM +0100, Dag-Erling Sm?rgrav wrote: > > Mike Meyer writes: > > > Will using a swap-backed disk change anything? > > > > Not really. > > > > > How about the best way to configure things to use two disks for the > > > compile? > > > > I'm not sure what you are trying to achieve. Unlike the base system, > > the ports tree does not use separate source and object directories. > > I think he is trying to get at a scenario where WRKDIR is on a seperate > disk from the one /usr/ports is on. > > To answer his question, assuming this is what he is going, for why not > just add a new physical disk to the system per the handbook, and set > WRKDIR to be where ever that disk is mounted. > > -- WXS > -- Ashok Shrestha From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 19 22:32:37 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7126F16A41F for ; Thu, 19 Jan 2006 22:32:37 +0000 (GMT) (envelope-from gthorpe@myrealbox.com) Received: from fe2.ryerson.ca (fe2.ryerson.ca [141.117.101.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id B76EC43D4C for ; Thu, 19 Jan 2006 22:32:36 +0000 (GMT) (envelope-from gthorpe@myrealbox.com) Received: from conversion-daemon.fe2.ryerson.ca by fe2.ryerson.ca (iPlanet Messaging Server 5.2 HotFix 2.02 (built Oct 21 2004)) id <0ITD004011Y4WC@fe2.ryerson.ca> (original mail from gthorpe@myrealbox.com) for freebsd-hackers@freebsd.org; Thu, 19 Jan 2006 17:32:35 -0500 (EST) Received: from [192.168.5.19] (fw.rnet.ryerson.ca [141.117.3.201]) by fe2.ryerson.ca (iPlanet Messaging Server 5.2 HotFix 2.02 (built Oct 21 2004)) with ESMTPS id <0ITD001ZV2MBE7@fe2.ryerson.ca>; Thu, 19 Jan 2006 17:32:35 -0500 (EST) Date: Thu, 19 Jan 2006 17:32:58 -0500 From: Gary Thorpe In-reply-to: <79e2026f0601191215p117d78ebjbee2c4b710075154@mail.gmail.com> To: Ashok Shrestha Message-id: <43D0139A.1040601@myrealbox.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=us-ascii Content-transfer-encoding: 7BIT X-Accept-Language: en, en-us User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 References: <79e2026f0601142345x1a9269bdl3153d1bb110be08d@mail.gmail.com> <86ek34d35f.fsf@xps.des.no> <17359.49899.183831.844670@bhuda.mired.org> <86k6cww445.fsf@xps.des.no> <20060119175224.GA71633@csh.rit.edu> <79e2026f0601191215p117d78ebjbee2c4b710075154@mail.gmail.com> Cc: Dag-Erling Sm?rgrav , Brandon Flowers , Mike Meyer , Wesley Shields , freebsd-hackers@freebsd.org Subject: Re: speed up port compiling using RAM (tmpfs) ??? 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, 19 Jan 2006 22:32:37 -0000 Ashok Shrestha wrote: > I mounted part of RAM as such: > > mdmfs -s 500m md /mnt > > Then put WRKDIRPREFIX=/path/to/md in /etc/make.conf. > > It substantially reduces compile time by about 5-10 times. > > > Thanx to all ur replies. > > -Ashok Shrestha An alternative is to try using the "-pipe" flag with GCC: this eliminates the need to use some temporary files by using a unix pipe for IPC. Setting another flag "-j 2" will allow 2 jobs to be done at the same time and should eliminate (by hiding) the I/O delays (this slows down the CPU slightly because of more task switches, but even with one job there are still lots of generated tasks). If you combine these, you should see your compilations becoming CPU-bound. From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 19 23:06:07 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2958E16A41F for ; Thu, 19 Jan 2006 23:06:07 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id C22D343D49 for ; Thu, 19 Jan 2006 23:06:06 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 926CD1A3C1B; Thu, 19 Jan 2006 15:06:06 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 704EE54A44; Thu, 19 Jan 2006 18:06:05 -0500 (EST) Date: Thu, 19 Jan 2006 18:06:05 -0500 From: Kris Kennaway To: Gary Thorpe Message-ID: <20060119230604.GA98670@xor.obsecurity.org> References: <79e2026f0601142345x1a9269bdl3153d1bb110be08d@mail.gmail.com> <86ek34d35f.fsf@xps.des.no> <17359.49899.183831.844670@bhuda.mired.org> <86k6cww445.fsf@xps.des.no> <20060119175224.GA71633@csh.rit.edu> <79e2026f0601191215p117d78ebjbee2c4b710075154@mail.gmail.com> <43D0139A.1040601@myrealbox.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="C7zPtVaVf+AK4Oqc" Content-Disposition: inline In-Reply-To: <43D0139A.1040601@myrealbox.com> User-Agent: Mutt/1.4.2.1i Cc: Wesley Shields , Ashok Shrestha , Brandon Flowers , Mike Meyer , freebsd-hackers@freebsd.org, Dag-Erling Sm?rgrav Subject: Re: speed up port compiling using RAM (tmpfs) ??? 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, 19 Jan 2006 23:06:07 -0000 --C7zPtVaVf+AK4Oqc Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jan 19, 2006 at 05:32:58PM -0500, Gary Thorpe wrote: > Ashok Shrestha wrote: > >I mounted part of RAM as such: > > > >mdmfs -s 500m md /mnt > > > >Then put WRKDIRPREFIX=3D/path/to/md in /etc/make.conf. > > > >It substantially reduces compile time by about 5-10 times. > > > > > >Thanx to all ur replies. > > > >-Ashok Shrestha >=20 > An alternative is to try using the "-pipe" flag with GCC: this=20 > eliminates the need to use some temporary files by using a unix pipe for= =20 > IPC. Setting another flag "-j 2" will allow 2 jobs to be done at the=20 > same time and should eliminate (by hiding) the I/O delays (this slows=20 > down the CPU slightly because of more task switches, but even with one=20 > job there are still lots of generated tasks). -j is not safe to use with port builds since many ported software contain race conditions in the build. Kris --C7zPtVaVf+AK4Oqc Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFD0BtcWry0BWjoQKURAu+3AKDE0S5hMyJ7hfqRklEk7ZKQFgNGPwCdFME1 qC/z3ZSqOMysnT6L87cG79Q= =vsyI -----END PGP SIGNATURE----- --C7zPtVaVf+AK4Oqc-- From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 20 01:42:42 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 78CC116A420 for ; Fri, 20 Jan 2006 01:42:42 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from mail16.syd.optusnet.com.au (mail16.syd.optusnet.com.au [211.29.132.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4320443D49 for ; Fri, 20 Jan 2006 01:42:40 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail16.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k0K1gH6S024363 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 20 Jan 2006 12:42:18 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1]) by cirb503493.alcatel.com.au (8.12.10/8.12.10) with ESMTP id k0K1gHHh027732; Fri, 20 Jan 2006 12:42:17 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost) by cirb503493.alcatel.com.au (8.12.10/8.12.9/Submit) id k0K1gGp1027731; Fri, 20 Jan 2006 12:42:16 +1100 (EST) (envelope-from pjeremy) Date: Fri, 20 Jan 2006 12:42:16 +1100 From: Peter Jeremy To: Andrew Gordon Message-ID: <20060120014216.GF25397@cirb503493.alcatel.com.au> References: <20060109183738.GA4822@odin.ac.hmc.edu> <001401c61676$3fa0c290$672a15ac@smiley> <20060110.234350.82839919.imp@bsdimp.com> <20060111103350.H91662@server.arg.sj.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060111103350.H91662@server.arg.sj.co.uk> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.11 Cc: freebsd-hackers@freebsd.org Subject: Re: Ricoh PCI to SD device? 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, 20 Jan 2006 01:42:42 -0000 On Wed, 2006-Jan-11 10:40:11 +0000, Andrew Gordon wrote: >Have you seen this datasheet from TI? > >http://focus.ti.com/docs/apps/catalog/resources/appnoteabstract.jhtml?abstractName=sprue30 I get "The information that you have requested is not available" but http://focus.ti.com/docs/apps/catalog/resources/appnoteabstract.jhtml?abstractName=scpu022 contains some information as does the data manual for the PCI17x21. I'm not sure if there is sufficient information to write a driver. -- Peter Jeremy From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 20 01:43:12 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2D86B16A41F; Fri, 20 Jan 2006 01:43:12 +0000 (GMT) (envelope-from craig@tobuj.gank.org) Received: from ion.gank.org (ion.gank.org [69.55.238.164]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB75443D46; Fri, 20 Jan 2006 01:43:11 +0000 (GMT) (envelope-from craig@tobuj.gank.org) Received: by ion.gank.org (mail, from userid 1001) id 3AFF22AA01; Thu, 19 Jan 2006 19:43:11 -0600 (CST) Date: Thu, 19 Jan 2006 19:43:07 -0600 From: Craig Boston To: freebsd-hackers@freebsd.org Message-ID: <20060120014307.GA3118@nowhere> Mail-Followup-To: Craig Boston , freebsd-hackers@freebsd.org, jhb@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Cc: Subject: Weird PCI interrupt delivery problem (resolution, sort of) 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, 20 Jan 2006 01:43:12 -0000 After trying everything I could think of to do to the I/O APIC code and coming up empty, tonight I went back to the local APIC. I had previously ruled it out since the lapic timer interrupt continued to work fine even when the others stopped. However, adding some DELAY(1) calls at key points caused it to work, much like adding WITNESS does. I managed to get it down to a single change that makes APIC mode work on this laptop: --- local_apic.c.orig Thu Jan 19 18:32:37 2006 +++ local_apic.c Thu Jan 19 18:32:28 2006 @@ -599,4 +599,5 @@ lapic_eoi(void) { lapic->eoi = 0; + lapic->eoi = 0; } ...and welcome to bizarro world. There's absolutely no reason I can think of why that would change anything, other than buggy hardware. I looked at what Linux was doing, and they're also using a single write to EOI interrupts, so long as the X86_GOOD_APIC config option is enabled (and it is for P5/MMX or newer). Otherwise it does an extra read before writing to any APIC register. I don't know if linux works on this hardware or not -- the live CD I tried wasn't compiled for APIC support. At this point, since AFAIK nobody else has reported the same problem, I'm content with a local workaround. It's just... wierd. Craig From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 20 03:57:40 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 09E9C16A41F for ; Fri, 20 Jan 2006 03:57:40 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E2BE43D49 for ; Fri, 20 Jan 2006 03:57:39 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id k0K3sic6042826; Thu, 19 Jan 2006 20:54:44 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Thu, 19 Jan 2006 20:54:56 -0700 (MST) Message-Id: <20060119.205456.64802994.imp@bsdimp.com> To: PeterJeremy@optushome.com.au From: "M. Warner Losh" In-Reply-To: <20060120014216.GF25397@cirb503493.alcatel.com.au> References: <20060110.234350.82839919.imp@bsdimp.com> <20060111103350.H91662@server.arg.sj.co.uk> <20060120014216.GF25397@cirb503493.alcatel.com.au> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Thu, 19 Jan 2006 20:54:44 -0700 (MST) Cc: freebsd-hackers@freebsd.org, arg-bsd@arg.me.uk Subject: Re: Ricoh PCI to SD device? 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, 20 Jan 2006 03:57:40 -0000 In message: <20060120014216.GF25397@cirb503493.alcatel.com.au> Peter Jeremy writes: : http://focus.ti.com/docs/apps/catalog/resources/appnoteabstract.jhtml?abstractName=scpu022 : contains some information as does the data manual for the PCI17x21. : : I'm not sure if there is sufficient information to write a driver. No. There isn't. Warner From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 20 05:17:45 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0AF9F16A41F for ; Fri, 20 Jan 2006 05:17:45 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id BCA2943D55 for ; Fri, 20 Jan 2006 05:17:43 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.14] (imini.samsco.home [192.168.254.14]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k0K5Hdr8087803; Thu, 19 Jan 2006 22:17:39 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <43D07273.6030804@samsco.org> Date: Thu, 19 Jan 2006 22:17:39 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.7) Gecko/20050416 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Craig Boston References: <20060120014307.GA3118@nowhere> In-Reply-To: <20060120014307.GA3118@nowhere> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: freebsd-hackers@freebsd.org Subject: Re: Weird PCI interrupt delivery problem (resolution, sort of) 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, 20 Jan 2006 05:17:45 -0000 Craig Boston wrote: > After trying everything I could think of to do to the I/O APIC code and > coming up empty, tonight I went back to the local APIC. I had > previously ruled it out since the lapic timer interrupt continued to > work fine even when the others stopped. However, adding some DELAY(1) > calls at key points caused it to work, much like adding WITNESS does. > I managed to get it down to a single change that makes APIC mode work on > this laptop: > > --- local_apic.c.orig Thu Jan 19 18:32:37 2006 > +++ local_apic.c Thu Jan 19 18:32:28 2006 > @@ -599,4 +599,5 @@ > lapic_eoi(void) > { > lapic->eoi = 0; > + lapic->eoi = 0; > } > > ...and welcome to bizarro world. There's absolutely no reason I can > think of why that would change anything, other than buggy hardware. > > I looked at what Linux was doing, and they're also using a single write > to EOI interrupts, so long as the X86_GOOD_APIC config option is enabled > (and it is for P5/MMX or newer). Otherwise it does an extra read before > writing to any APIC register. I don't know if linux works on this > hardware or not -- the live CD I tried wasn't compiled for APIC support. > > At this point, since AFAIK nobody else has reported the same problem, > I'm content with a local workaround. It's just... wierd. > > Craig This points to a bus coherency problem. I wonder if your BIOS is incorrectly setting the memory region of the apics as cachable. You'll want to bug Baldwin about this. Scott From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 20 06:08:06 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 659E616A41F; Fri, 20 Jan 2006 06:08:06 +0000 (GMT) (envelope-from k-choy@ics.es.osaka-u.ac.jp) Received: from mir.ics.es.osaka-u.ac.jp (mir.ics.es.osaka-u.ac.jp [133.1.12.154]) by mx1.FreeBSD.org (Postfix) with ESMTP id E8F6E43D45; Fri, 20 Jan 2006 06:08:05 +0000 (GMT) (envelope-from k-choy@ics.es.osaka-u.ac.jp) Received: from [127.0.0.1] (serg32.ics.es.osaka-u.ac.jp [192.168.144.160]) by mir.ics.es.osaka-u.ac.jp (8.13.3/8.12.10) with ESMTP id k0K683tk014660; Fri, 20 Jan 2006 15:08:05 +0900 (JST) (envelope-from k-choy@ics.es.osaka-u.ac.jp) Message-ID: <43D07E3E.6080707@ics.es.osaka-u.ac.jp> Date: Fri, 20 Jan 2006 15:07:58 +0900 From: Choy Kho Yee User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit Cc: Subject: Newly developed mailling list search engine needs testing 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, 20 Jan 2006 06:08:06 -0000 Hi, everybody. Firstly, let me introduce myself. I am Choy Kho Yee, an comp. sci. undergraduate student in Osaka University. For my final year thesis, I have developed a mailing list archive management system called "MLwiki". The name MLwiki is made up from the words "Mailing List" and "Wiki". It was developed to overcome some weaknesses of the existing mailing list archiving and searching system and to combine the power of wiki and the huge amount of information in the mailing list archive. With MLwiki, it is hoped that users can get the information they want faster and easier. More information about MLwiki is available on the main page of this system, which is located at MLwiki http://noanoa.ics.es.osaka-u.ac.jp/~k-choy/mlwiki-test/mlwiki.php The questionnaire http://noanoa.ics.es.osaka-u.ac.jp/~k-choy/mlwiki-test/mlwiki_questionaire.html Please read the introduction on the main page before testing the system as it provides some vital information to fully utilize MLwiki. After testing out the system, I would be glad if you can help me out by filling in the questionnaire about this system, which can be accessed through the above address or from MLwiki's main page. Please understand that MLwiki is in its early stage of development and therefore there might be many bugs hidden in it. Bugs reports are welcome. And please remember that this system is still in an experimental stage, all changes you submit might be lost in the future release. But do feel free to test around. This website will be available until 10 February 2006. Accessibility after that will be re-considered depends on the response and the condition of the system. Thanks a lot. --- Choy Kho Yee E-mail: k-choy at ics dot es dot osaka-u dot ac dot jp From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 20 10:46:41 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B3AAA16A45F for ; Fri, 20 Jan 2006 10:46:41 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id C4EFC43D45 for ; Fri, 20 Jan 2006 10:46:40 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id A602B2087; Fri, 20 Jan 2006 11:46:33 +0100 (CET) X-Spam-Tests: AWL,BAYES_00,FORGED_RCVD_HELO X-Spam-Learn: ham X-Spam-Score: -3.2/3.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on tim.des.no Received: from xps.des.no (des.no [80.203.243.180]) by tim.des.no (Postfix) with ESMTP id 9381F2085; Fri, 20 Jan 2006 11:46:33 +0100 (CET) Received: by xps.des.no (Postfix, from userid 1001) id 61CAF33C1D; Fri, 20 Jan 2006 11:46:33 +0100 (CET) To: Wesley Shields References: <79e2026f0601142345x1a9269bdl3153d1bb110be08d@mail.gmail.com> <86ek34d35f.fsf@xps.des.no> <17359.49899.183831.844670@bhuda.mired.org> <86k6cww445.fsf@xps.des.no> <20060119175224.GA71633@csh.rit.edu> From: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=) Date: Fri, 20 Jan 2006 11:46:33 +0100 In-Reply-To: <20060119175224.GA71633@csh.rit.edu> (Wesley Shields's message of "Thu, 19 Jan 2006 12:52:24 -0500") Message-ID: <863bjjw512.fsf@xps.des.no> User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Ashok Shrestha , Brandon Flowers , Mike Meyer , freebsd-hackers@freebsd.org Subject: Re: speed up port compiling using RAM (tmpfs) ??? 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, 20 Jan 2006 10:46:41 -0000 Wesley Shields writes: > I think he is trying to get at a scenario where WRKDIR is on a seperate > disk from the one /usr/ports is on. There is no performance advantage in doing that. I can only see two possible reasons for pointing WRKDIRPREFIX to another disk: - insufficient space on /usr (but then again, you could just move the ports tree to that other disk and mount it on /usr/ports) - /usr/ports on NFS (I do that myself to facilitate testing changes on different platforms) DES --=20 Dag-Erling Sm=F8rgrav - des@des.no From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 20 15:27:37 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D66C716A41F for ; Fri, 20 Jan 2006 15:27:37 +0000 (GMT) (envelope-from craig@tobuj.gank.org) Received: from ion.gank.org (ion.gank.org [69.55.238.164]) by mx1.FreeBSD.org (Postfix) with ESMTP id A349143D45 for ; Fri, 20 Jan 2006 15:27:37 +0000 (GMT) (envelope-from craig@tobuj.gank.org) Received: by ion.gank.org (mail, from userid 1001) id F38E72AB1B; Fri, 20 Jan 2006 09:27:36 -0600 (CST) Date: Fri, 20 Jan 2006 09:27:31 -0600 From: Craig Boston To: Scott Long Message-ID: <20060120152731.GA5660@nowhere> Mail-Followup-To: Craig Boston , Scott Long , freebsd-hackers@freebsd.org References: <20060120014307.GA3118@nowhere> <43D07273.6030804@samsco.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43D07273.6030804@samsco.org> User-Agent: Mutt/1.4.2.1i Cc: freebsd-hackers@freebsd.org Subject: Re: Weird PCI interrupt delivery problem (resolution, sort of) 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, 20 Jan 2006 15:27:38 -0000 On Thu, Jan 19, 2006 at 10:17:39PM -0700, Scott Long wrote: > This points to a bus coherency problem. I wonder if your BIOS is > incorrectly setting the memory region of the apics as cachable. You'll > want to bug Baldwin about this. I CC-ed him on my post since he was working with me on the problem before. For some reason the Cc: header got wiped out when it went to the list (but I checked my server logs and it did deliver a copy of the message to him). Craig From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 20 16:49:14 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B854E16A41F for ; Fri, 20 Jan 2006 16:49:14 +0000 (GMT) (envelope-from gthorpe@myrealbox.com) Received: from fe2.ryerson.ca (fe2.ryerson.ca [141.117.101.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id 051D343D75 for ; Fri, 20 Jan 2006 16:49:07 +0000 (GMT) (envelope-from gthorpe@myrealbox.com) Received: from conversion-daemon.fe2.ryerson.ca by fe2.ryerson.ca (iPlanet Messaging Server 5.2 HotFix 2.02 (built Oct 21 2004)) id <0ITE00101H5CXE@fe2.ryerson.ca> (original mail from gthorpe@myrealbox.com) for freebsd-hackers@freebsd.org; Fri, 20 Jan 2006 11:49:06 -0500 (EST) Received: from [192.168.5.19] (fw.rnet.ryerson.ca [141.117.3.201]) by fe2.ryerson.ca (iPlanet Messaging Server 5.2 HotFix 2.02 (built Oct 21 2004)) with ESMTPS id <0ITE00EC7HDT9F@fe2.ryerson.ca>; Fri, 20 Jan 2006 11:49:06 -0500 (EST) Date: Fri, 20 Jan 2006 11:49:29 -0500 From: Gary Thorpe In-reply-to: <20060119230604.GA98670@xor.obsecurity.org> To: Kris Kennaway Message-id: <43D11499.8040808@myrealbox.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=us-ascii Content-transfer-encoding: 7BIT X-Accept-Language: en, en-us User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 References: <79e2026f0601142345x1a9269bdl3153d1bb110be08d@mail.gmail.com> <86ek34d35f.fsf@xps.des.no> <17359.49899.183831.844670@bhuda.mired.org> <86k6cww445.fsf@xps.des.no> <20060119175224.GA71633@csh.rit.edu> <79e2026f0601191215p117d78ebjbee2c4b710075154@mail.gmail.com> <43D0139A.1040601@myrealbox.com> <20060119230604.GA98670@xor.obsecurity.org> Cc: Wesley Shields , Ashok Shrestha , Brandon Flowers , Mike Meyer , freebsd-hackers@freebsd.org, Dag-Erling Sm?rgrav Subject: Re: speed up port compiling using RAM (tmpfs) ??? 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, 20 Jan 2006 16:49:14 -0000 Kris Kennaway wrote: > On Thu, Jan 19, 2006 at 05:32:58PM -0500, Gary Thorpe wrote: > >>Ashok Shrestha wrote: >> >>>I mounted part of RAM as such: >>> >>>mdmfs -s 500m md /mnt >>> >>>Then put WRKDIRPREFIX=/path/to/md in /etc/make.conf. >>> >>>It substantially reduces compile time by about 5-10 times. >>> >>> >>>Thanx to all ur replies. >>> >>>-Ashok Shrestha >> >>An alternative is to try using the "-pipe" flag with GCC: this >>eliminates the need to use some temporary files by using a unix pipe for >>IPC. Setting another flag "-j 2" will allow 2 jobs to be done at the >>same time and should eliminate (by hiding) the I/O delays (this slows >>down the CPU slightly because of more task switches, but even with one >>job there are still lots of generated tasks). > > > -j is not safe to use with port builds since many ported software > contain race conditions in the build. > > Kris This effectively means that you cannot take advantage of SMP to compile FreeBSD's ports collection. That sounds like a big limitation...especially for people trying to speed up bulk builds. Is "-pipe" still a good idea? It should provide a significant performance boost, if the process is spending a lot of time doing disk I/O, without using up a lot of memory. From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 20 16:57:28 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7EF9516A41F for ; Fri, 20 Jan 2006 16:57:28 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id A845443D49 for ; Fri, 20 Jan 2006 16:57:27 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 4C2882082; Fri, 20 Jan 2006 17:57:22 +0100 (CET) X-Spam-Tests: AWL,BAYES_00,FORGED_RCVD_HELO X-Spam-Learn: ham X-Spam-Score: -3.2/3.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on tim.des.no Received: from xps.des.no (des.no [80.203.243.180]) by tim.des.no (Postfix) with ESMTP id C03C22081; Fri, 20 Jan 2006 17:57:21 +0100 (CET) Received: by xps.des.no (Postfix, from userid 1001) id 9EEFB33C1D; Fri, 20 Jan 2006 17:57:21 +0100 (CET) To: Gary Thorpe References: <79e2026f0601142345x1a9269bdl3153d1bb110be08d@mail.gmail.com> <86ek34d35f.fsf@xps.des.no> <17359.49899.183831.844670@bhuda.mired.org> <86k6cww445.fsf@xps.des.no> <20060119175224.GA71633@csh.rit.edu> <79e2026f0601191215p117d78ebjbee2c4b710075154@mail.gmail.com> <43D0139A.1040601@myrealbox.com> <20060119230604.GA98670@xor.obsecurity.org> <43D11499.8040808@myrealbox.com> From: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=) Date: Fri, 20 Jan 2006 17:57:21 +0100 In-Reply-To: <43D11499.8040808@myrealbox.com> (Gary Thorpe's message of "Fri, 20 Jan 2006 11:49:29 -0500") Message-ID: <861wz2u9am.fsf@xps.des.no> User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Wesley Shields , Ashok Shrestha , Brandon Flowers , Kris Kennaway , Mike Meyer , freebsd-hackers@freebsd.org Subject: Re: speed up port compiling using RAM (tmpfs) ??? 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, 20 Jan 2006 16:57:28 -0000 Gary Thorpe writes: > This effectively means that you cannot take advantage of SMP to > compile FreeBSD's ports collection. That sounds like a big > limitation...especially for people trying to speed up bulk builds. We cannot be held responsible for race conditions in the Makefiles of third-party software. > Is "-pipe" still a good idea? It should provide a significant > performance boost, if the process is spending a lot of time doing disk > I/O, without using up a lot of memory. -pipe is fine. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 20 17:25:35 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 020F916A41F for ; Fri, 20 Jan 2006 17:25:35 +0000 (GMT) (envelope-from babkin@verizon.net) Received: from vms046pub.verizon.net (vms046pub.verizon.net [206.46.252.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id AAF3943D48 for ; Fri, 20 Jan 2006 17:25:34 +0000 (GMT) (envelope-from babkin@verizon.net) Received: from vms075.mailsrvcs.net ([192.168.1.4]) by vms046.mailsrvcs.net (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) with ESMTPA id <0ITE009FMJ2LXCO4@vms046.mailsrvcs.net> for freebsd-hackers@freebsd.org; Fri, 20 Jan 2006 11:25:33 -0600 (CST) Date: Fri, 20 Jan 2006 11:25:33 -0600 (CST) From: Sergey Babkin To: =?ISO646-US?Q?Dag-Erling_Sm=3Frgrav?= , Gary Thorpe Message-id: <2209162.1137777933811.JavaMail.root@vms075.mailsrvcs.net> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit X-Mailman-Approved-At: Fri, 20 Jan 2006 18:11:25 +0000 Cc: Wesley Shields , Ashok Shrestha , Brandon Flowers , Kris Kennaway , Mike Meyer , freebsd-hackers@freebsd.org Subject: Re: Re: speed up port compiling using RAM (tmpfs) ??? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: babkin@users.sf.net List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Jan 2006 17:25:35 -0000 >From: =?ISO646-US?Q?Dag-Erling_Sm=3Frgrav?= >Gary Thorpe writes: >> This effectively means that you cannot take advantage of SMP to >> compile FreeBSD's ports collection. That sounds like a big >> limitation...especially for people trying to speed up bulk builds. > >We cannot be held responsible for race conditions in the Makefiles of >third-party software. Well, maybe we can then build multiple ports in parallel. I guess the way to do it would be to run the top-level make with -j but then disable it when calling the makefiles of the individual ports. Not that I have any idea how to actually do that. -SB From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 20 19:37:53 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4AD4D16A41F for ; Fri, 20 Jan 2006 19:37:53 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6987A43D72 for ; Fri, 20 Jan 2006 19:37:42 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 4BC341A3C1C; Fri, 20 Jan 2006 11:37:42 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 9401F5190B; Fri, 20 Jan 2006 14:37:41 -0500 (EST) Date: Fri, 20 Jan 2006 14:37:41 -0500 From: Kris Kennaway To: babkin@users.sf.net Message-ID: <20060120193741.GC39932@xor.obsecurity.org> References: <2209162.1137777933811.JavaMail.root@vms075.mailsrvcs.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="hOcCNbCCxyk/YU74" Content-Disposition: inline In-Reply-To: <2209162.1137777933811.JavaMail.root@vms075.mailsrvcs.net> User-Agent: Mutt/1.4.2.1i Cc: Wesley Shields , freebsd-hackers@freebsd.org, Ashok Shrestha , Brandon Flowers , Mike Meyer , Gary Thorpe , Kris Kennaway , Dag-Erling Sm?rgrav Subject: Re: Re: speed up port compiling using RAM (tmpfs) ??? 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, 20 Jan 2006 19:37:53 -0000 --hOcCNbCCxyk/YU74 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jan 20, 2006 at 11:25:33AM -0600, Sergey Babkin wrote: > >From: =3D?ISO646-US?Q?Dag-Erling_Sm=3D3Frgrav?=3D >=20 > >Gary Thorpe writes: > >> This effectively means that you cannot take advantage of SMP to > >> compile FreeBSD's ports collection. That sounds like a big > >> limitation...especially for people trying to speed up bulk builds. > > > >We cannot be held responsible for race conditions in the Makefiles of > >third-party software. >=20 > Well, maybe we can then build multiple ports in parallel. > I guess the way to do it would be to run the top-level make with > -j but then disable it when calling the makefiles of the > individual ports. Not that I have any idea how to actually > do that. It's harder than that, because you need to impose dependency information and mutual exclusion between different makes. e.g. they can't both be compiling the same port at the same time, which will happen if you just do the naive thing. Kris --hOcCNbCCxyk/YU74 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFD0TwEWry0BWjoQKURAmYdAKDDlVkBMNvQxUjhwe/x6tjUqrYRcwCbB3J8 Ia5oOIBCmSH/4VFyiQJMe6E= =xRyl -----END PGP SIGNATURE----- --hOcCNbCCxyk/YU74-- From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 20 19:47:11 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7897B16A41F for ; Fri, 20 Jan 2006 19:47:11 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A6F443D5A for ; Fri, 20 Jan 2006 19:47:01 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 46D751A3C1E; Fri, 20 Jan 2006 11:47:01 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 982CB54CB0; Fri, 20 Jan 2006 14:47:00 -0500 (EST) Date: Fri, 20 Jan 2006 14:47:00 -0500 From: Kris Kennaway To: Gary Thorpe Message-ID: <20060120194700.GB41039@xor.obsecurity.org> References: <79e2026f0601142345x1a9269bdl3153d1bb110be08d@mail.gmail.com> <86ek34d35f.fsf@xps.des.no> <17359.49899.183831.844670@bhuda.mired.org> <86k6cww445.fsf@xps.des.no> <20060119175224.GA71633@csh.rit.edu> <79e2026f0601191215p117d78ebjbee2c4b710075154@mail.gmail.com> <43D0139A.1040601@myrealbox.com> <20060119230604.GA98670@xor.obsecurity.org> <43D11499.8040808@myrealbox.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="EuxKj2iCbKjpUGkD" Content-Disposition: inline In-Reply-To: <43D11499.8040808@myrealbox.com> User-Agent: Mutt/1.4.2.1i Cc: Wesley Shields , Ashok Shrestha , Brandon Flowers , Kris Kennaway , Mike Meyer , freebsd-hackers@freebsd.org, Dag-Erling Sm?rgrav Subject: Re: speed up port compiling using RAM (tmpfs) ??? 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, 20 Jan 2006 19:47:11 -0000 --EuxKj2iCbKjpUGkD Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jan 20, 2006 at 11:49:29AM -0500, Gary Thorpe wrote: > >-j is not safe to use with port builds since many ported software > >contain race conditions in the build. > > > >Kris >=20 > This effectively means that you cannot take advantage of SMP to compile= =20 > FreeBSD's ports collection. That sounds like a big=20 > limitation...especially for people trying to speed up bulk builds. Yeah, but what do you propose to do about it? We have 14000 ports that need to be inspected for build race conditions and fixed before you can turn on -j by default. Kris --EuxKj2iCbKjpUGkD Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFD0T4zWry0BWjoQKURAmXWAKCvjoH4A6/q1APE+QJJYiox2wU8dQCeOFDX bZ3sHAuxfAZu+1flfRQNU6w= =KWMC -----END PGP SIGNATURE----- --EuxKj2iCbKjpUGkD-- From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 20 20:52:24 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 968CD16A41F for ; Fri, 20 Jan 2006 20:52:24 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from mail25.syd.optusnet.com.au (mail25.syd.optusnet.com.au [211.29.133.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id DB65E43D48 for ; Fri, 20 Jan 2006 20:52:23 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail25.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k0KKqKxa011561 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sat, 21 Jan 2006 07:52:21 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1]) by cirb503493.alcatel.com.au (8.12.10/8.12.10) with ESMTP id k0KKqKHh031784; Sat, 21 Jan 2006 07:52:20 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost) by cirb503493.alcatel.com.au (8.12.10/8.12.9/Submit) id k0KKqK9w031783; Sat, 21 Jan 2006 07:52:20 +1100 (EST) (envelope-from pjeremy) Date: Sat, 21 Jan 2006 07:52:20 +1100 From: Peter Jeremy To: Kris Kennaway Message-ID: <20060120205219.GK25397@cirb503493.alcatel.com.au> References: <79e2026f0601142345x1a9269bdl3153d1bb110be08d@mail.gmail.com> <86ek34d35f.fsf@xps.des.no> <17359.49899.183831.844670@bhuda.mired.org> <86k6cww445.fsf@xps.des.no> <20060119175224.GA71633@csh.rit.edu> <79e2026f0601191215p117d78ebjbee2c4b710075154@mail.gmail.com> <43D0139A.1040601@myrealbox.com> <20060119230604.GA98670@xor.obsecurity.org> <43D11499.8040808@myrealbox.com> <20060120194700.GB41039@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060120194700.GB41039@xor.obsecurity.org> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.11 Cc: freebsd-hackers@freebsd.org Subject: Re: speed up port compiling using RAM (tmpfs) ??? 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, 20 Jan 2006 20:52:24 -0000 On Fri, 2006-Jan-20 14:47:00 -0500, Kris Kennaway wrote: >On Fri, Jan 20, 2006 at 11:49:29AM -0500, Gary Thorpe wrote: > >> >-j is not safe to use with port builds since many ported software >> >contain race conditions in the build. >> > >> >Kris >> >> This effectively means that you cannot take advantage of SMP to compile >> FreeBSD's ports collection. That sounds like a big >> limitation...especially for people trying to speed up bulk builds. > >Yeah, but what do you propose to do about it? We have 14000 ports >that need to be inspected for build race conditions and fixed before >you can turn on -j by default. There are some areas of the FreeBSD port building infrastructure that could be enhanced to make it possible to run multiple top-level makes in parallel, even if individual ports can't be build with '-j'. IMHO, the biggest problem (as des pointed out) is that there's nothing to prevent two makes attempting to build the same port (this can easily happen when both ports A and B depend on port C). One possible solution would be to create another status file in the work directory and hold a file lock (flock/lockf) on it whilst a make is in progress. Any parallel attempt to make that port would block. If the above was implemented, an enhancement would then be to process the port's dependency list in parallel, rather than serially. This would allow a make that was blocked on one dependency to continue with a different dependency. -- Peter Jeremy From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 20 20:56:57 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1157E16A41F for ; Fri, 20 Jan 2006 20:56:57 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id B73C443D45 for ; Fri, 20 Jan 2006 20:56:56 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 9198B1A3C1B; Fri, 20 Jan 2006 12:56:56 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id CF1A651FBC; Fri, 20 Jan 2006 15:56:55 -0500 (EST) Date: Fri, 20 Jan 2006 15:56:55 -0500 From: Kris Kennaway To: Peter Jeremy Message-ID: <20060120205655.GA42732@xor.obsecurity.org> References: <86ek34d35f.fsf@xps.des.no> <17359.49899.183831.844670@bhuda.mired.org> <86k6cww445.fsf@xps.des.no> <20060119175224.GA71633@csh.rit.edu> <79e2026f0601191215p117d78ebjbee2c4b710075154@mail.gmail.com> <43D0139A.1040601@myrealbox.com> <20060119230604.GA98670@xor.obsecurity.org> <43D11499.8040808@myrealbox.com> <20060120194700.GB41039@xor.obsecurity.org> <20060120205219.GK25397@cirb503493.alcatel.com.au> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="y0ulUmNC+osPPQO6" Content-Disposition: inline In-Reply-To: <20060120205219.GK25397@cirb503493.alcatel.com.au> User-Agent: Mutt/1.4.2.1i Cc: freebsd-hackers@freebsd.org, Kris Kennaway Subject: Re: speed up port compiling using RAM (tmpfs) ??? 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, 20 Jan 2006 20:56:57 -0000 --y0ulUmNC+osPPQO6 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jan 21, 2006 at 07:52:20AM +1100, Peter Jeremy wrote:5C > IMHO, the biggest problem (as des pointed out) is that there's nothing > to prevent two makes attempting to build the same port (this can > easily happen when both ports A and B depend on port C). One possible > solution would be to create another status file in the work directory > and hold a file lock (flock/lockf) on it whilst a make is in progress. > Any parallel attempt to make that port would block. >=20 > If the above was implemented, an enhancement would then be to process > the port's dependency list in parallel, rather than serially. This > would allow a make that was blocked on one dependency to continue with > a different dependency. There have been a couple of half-hearted attempts to implement this, but no complete ones (see an old portmgr PR for details + discussion). I'd welcome a complete version :) Kris --y0ulUmNC+osPPQO6 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD4DBQFD0U6XWry0BWjoQKURAla0AKCNelxuoYaf09Yt7V0I2hr1IVcg7wCUD6Il SHf0zIAnjooTpauOnJ0Ggg== =SYag -----END PGP SIGNATURE----- --y0ulUmNC+osPPQO6-- From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 20 21:05:27 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 177BD16A41F for ; Fri, 20 Jan 2006 21:05:27 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A12543D46 for ; Fri, 20 Jan 2006 21:05:26 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 6568401 for multiple; Fri, 20 Jan 2006 16:06:28 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k0KL5Kqa073073; Fri, 20 Jan 2006 16:05:22 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-hackers@freebsd.org Date: Fri, 20 Jan 2006 15:42:21 -0500 User-Agent: KMail/1.9.1 References: <20060120014307.GA3118@nowhere> <43D07273.6030804@samsco.org> <20060120152731.GA5660@nowhere> In-Reply-To: <20060120152731.GA5660@nowhere> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200601201542.23464.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1246/Thu Jan 19 16:44:42 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-1.4 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: Craig Boston , Scott Long Subject: Re: Weird PCI interrupt delivery problem (resolution, sort of) 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, 20 Jan 2006 21:05:27 -0000 On Friday 20 January 2006 10:27, Craig Boston wrote: > On Thu, Jan 19, 2006 at 10:17:39PM -0700, Scott Long wrote: > > This points to a bus coherency problem. I wonder if your BIOS is > > incorrectly setting the memory region of the apics as cachable. You'll > > want to bug Baldwin about this. > > I CC-ed him on my post since he was working with me on the problem > before. For some reason the Cc: header got wiped out when it went to > the list (but I checked my server logs and it did deliver a copy of the > message to him). Hmm, well, you can actually try the PAT patch if you are feeling brave as it maps all devices (including APICs) as uncacheable. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 20 21:27:12 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7109B16A41F; Fri, 20 Jan 2006 21:27:12 +0000 (GMT) (envelope-from craig@tobuj.gank.org) Received: from ion.gank.org (ion.gank.org [69.55.238.164]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE97843D81; Fri, 20 Jan 2006 21:26:55 +0000 (GMT) (envelope-from craig@tobuj.gank.org) Received: by ion.gank.org (mail, from userid 1001) id 193772AB34; Fri, 20 Jan 2006 15:26:53 -0600 (CST) Date: Fri, 20 Jan 2006 15:26:47 -0600 From: Craig Boston To: John Baldwin Message-ID: <20060120212647.GB5660@nowhere> Mail-Followup-To: Craig Boston , John Baldwin , freebsd-hackers@freebsd.org References: <20060120014307.GA3118@nowhere> <43D07273.6030804@samsco.org> <20060120152731.GA5660@nowhere> <200601201542.23464.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200601201542.23464.jhb@freebsd.org> User-Agent: Mutt/1.4.2.1i Cc: freebsd-hackers@freebsd.org Subject: Re: Weird PCI interrupt delivery problem (resolution, sort of) 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, 20 Jan 2006 21:27:12 -0000 On Fri, Jan 20, 2006 at 03:42:21PM -0500, John Baldwin wrote: > Hmm, well, you can actually try the PAT patch if you are feeling brave as it > maps all devices (including APICs) as uncacheable. Heh, took me a minute to find. I first found the one at http://people.freebsd.org/~jhb/patches/pat.patch but it maps devices as write-back. I'm guessing you mean to use the version in perforce? I'll give it a try tonight. Could hardy make things worse -- I just noticed that X now randomly locks up hard, ever since I bumped up the memory from 256Mb to 2G -- though text mode still works fine. (yes, I tried reverting all my local patches and testing the memory) Craig From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 20 21:54:41 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5852616A41F for ; Fri, 20 Jan 2006 21:54:41 +0000 (GMT) (envelope-from babkin@verizon.net) Received: from vms048pub.verizon.net (vms048pub.verizon.net [206.46.252.48]) by mx1.FreeBSD.org (Postfix) with ESMTP id D396D43D5D for ; Fri, 20 Jan 2006 21:54:40 +0000 (GMT) (envelope-from babkin@verizon.net) Received: from verizon.net ([138.89.158.150]) by vms048.mailsrvcs.net (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) with ESMTPA id <0ITE003FDVIXXA60@vms048.mailsrvcs.net> for freebsd-hackers@freebsd.org; Fri, 20 Jan 2006 15:54:38 -0600 (CST) Date: Fri, 20 Jan 2006 16:54:33 -0500 From: Sergey Babkin Sender: root To: Kris Kennaway Message-id: <43D15C19.314EC346@verizon.net> MIME-version: 1.0 X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.7-RELEASE i386) Content-type: text/plain; charset=koi8-r Content-transfer-encoding: 7bit X-Accept-Language: en, ru References: <2209162.1137777933811.JavaMail.root@vms075.mailsrvcs.net> <20060120193741.GC39932@xor.obsecurity.org> X-Mailman-Approved-At: Fri, 20 Jan 2006 22:07:53 +0000 Cc: Wesley Shields , freebsd-hackers@freebsd.org, Brandon Flowers , Mike Meyer , Gary Thorpe , Ashok Shrestha , Dag-Erling Sm?rgrav Subject: Re: speed up port compiling using RAM (tmpfs) ??? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: babkin@users.sf.net List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Jan 2006 21:54:41 -0000 Kris Kennaway wrote: > > On Fri, Jan 20, 2006 at 11:25:33AM -0600, Sergey Babkin wrote: > > >From: =?ISO646-US?Q?Dag-Erling_Sm=3Frgrav?= > > > > >Gary Thorpe writes: > > >> This effectively means that you cannot take advantage of SMP to > > >> compile FreeBSD's ports collection. That sounds like a big > > >> limitation...especially for people trying to speed up bulk builds. > > > > > >We cannot be held responsible for race conditions in the Makefiles of > > >third-party software. > > > > Well, maybe we can then build multiple ports in parallel. > > I guess the way to do it would be to run the top-level make with > > -j but then disable it when calling the makefiles of the > > individual ports. Not that I have any idea how to actually > > do that. > > It's harder than that, because you need to impose dependency > information and mutual exclusion between different makes. e.g. they > can't both be compiling the same port at the same time, which will > happen if you just do the naive thing. That's the part that "make -j" is supposed to take care of, since it should build in parallel only the targets independent of each other. -SB From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 20 22:26:31 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0444B16A41F for ; Fri, 20 Jan 2006 22:26:31 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC81243D45 for ; Fri, 20 Jan 2006 22:26:30 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 6AA0D1A3C1B; Fri, 20 Jan 2006 14:26:30 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 9F85F54C16; Fri, 20 Jan 2006 17:26:29 -0500 (EST) Date: Fri, 20 Jan 2006 17:26:29 -0500 From: Kris Kennaway To: babkin@users.sf.net Message-ID: <20060120222629.GA43985@xor.obsecurity.org> References: <2209162.1137777933811.JavaMail.root@vms075.mailsrvcs.net> <20060120193741.GC39932@xor.obsecurity.org> <43D15C19.314EC346@verizon.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="h31gzZEtNLTqOjlF" Content-Disposition: inline In-Reply-To: <43D15C19.314EC346@verizon.net> User-Agent: Mutt/1.4.2.1i Cc: Wesley Shields , freebsd-hackers@freebsd.org, Brandon Flowers , Kris Kennaway , Mike Meyer , Gary Thorpe , Ashok Shrestha , Dag-Erling Sm?rgrav Subject: Re: speed up port compiling using RAM (tmpfs) ??? 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, 20 Jan 2006 22:26:31 -0000 --h31gzZEtNLTqOjlF Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jan 20, 2006 at 04:54:33PM -0500, Sergey Babkin wrote: > Kris Kennaway wrote: > >=20 > > On Fri, Jan 20, 2006 at 11:25:33AM -0600, Sergey Babkin wrote: > > > >From: =3D?ISO646-US?Q?Dag-Erling_Sm=3D3Frgrav?=3D > > > > > > >Gary Thorpe writes: > > > >> This effectively means that you cannot take advantage of SMP to > > > >> compile FreeBSD's ports collection. That sounds like a big > > > >> limitation...especially for people trying to speed up bulk builds. > > > > > > > >We cannot be held responsible for race conditions in the Makefiles of > > > >third-party software. > > > > > > Well, maybe we can then build multiple ports in parallel. > > > I guess the way to do it would be to run the top-level make with > > > -j but then disable it when calling the makefiles of the > > > individual ports. Not that I have any idea how to actually > > > do that. > >=20 > > It's harder than that, because you need to impose dependency > > information and mutual exclusion between different makes. e.g. they > > can't both be compiling the same port at the same time, which will > > happen if you just do the naive thing. >=20 > That's the part that "make -j" is supposed to take care of, > since it should build in parallel only the targets independent > of each other. If (as I said) you impose the correct dependency information. Currently there is no such information provided. kris --h31gzZEtNLTqOjlF Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFD0WOVWry0BWjoQKURAmg7AJ4x5OFpC9huDmKvSmSO6ovToDyeVQCdEzeF 3tYtPn2aB3jjCMKdXO4E4ag= =0PRL -----END PGP SIGNATURE----- --h31gzZEtNLTqOjlF-- From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 20 23:27:27 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7ECB716A41F for ; Fri, 20 Jan 2006 23:27:27 +0000 (GMT) (envelope-from gayn.winters@bristolsystems.com) Received: from fed1rmmtao10.cox.net (fed1rmmtao10.cox.net [68.230.241.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id BF84043D48 for ; Fri, 20 Jan 2006 23:27:26 +0000 (GMT) (envelope-from gayn.winters@bristolsystems.com) Received: from workdog ([68.5.182.86]) by fed1rmmtao10.cox.net (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP id <20060120232605.HPSS20441.fed1rmmtao10.cox.net@workdog>; Fri, 20 Jan 2006 18:26:05 -0500 From: "Gayn Winters" To: "'Kris Kennaway'" , "'Gary Thorpe'" Date: Fri, 20 Jan 2006 15:28:08 -0800 Organization: Bristol Systems Inc. Message-ID: <02c901c61e19$2efd3680$6501a8c0@workdog> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4024 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 In-Reply-To: <20060120194700.GB41039@xor.obsecurity.org> Importance: Normal Cc: 'Wesley Shields' , 'Ashok Shrestha' , 'Brandon Flowers' , 'Mike Meyer' , freebsd-hackers@freebsd.org, 'Dag-Erling Sm?rgrav' Subject: RE: speed up port compiling using RAM (tmpfs) ??? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: gayn.winters@bristolsystems.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Jan 2006 23:27:27 -0000 > [mailto:owner-freebsd-hackers@freebsd.org] On Behalf Of Kris Kennaway > Sent: Friday, January 20, 2006 11:47 AM > To: Gary Thorpe > Cc: Wesley Shields; Ashok Shrestha; Brandon Flowers; Kris > Kennaway; Mike Meyer; freebsd-hackers@freebsd.org; Dag-Erling Sm?rgrav > Subject: Re: speed up port compiling using RAM (tmpfs) ??? > > > On Fri, Jan 20, 2006 at 11:49:29AM -0500, Gary Thorpe wrote: > > > >-j is not safe to use with port builds since many ported software > > >contain race conditions in the build. > > > > > >Kris > > > > This effectively means that you cannot take advantage of SMP to compile > > FreeBSD's ports collection. That sounds like a big > > limitation...especially for people trying to speed up bulk builds. > > Yeah, but what do you propose to do about it? We have 14000 ports > that need to be inspected for build race conditions and fixed before > you can turn on -j by default. > > Kris With a dual processor (even dual core?) is there a way to assign the big make to one processor and to assign the foreground activity (email, edits, etc) to another? Is SMP somehow smart enough to do this automagically? -gayn From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 20 23:41:56 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6018F16A41F for ; Fri, 20 Jan 2006 23:41:56 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0F1C643D49 for ; Fri, 20 Jan 2006 23:41:56 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id D652A1A3C1B; Fri, 20 Jan 2006 15:41:55 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id A8A1D51AD6; Fri, 20 Jan 2006 18:41:54 -0500 (EST) Date: Fri, 20 Jan 2006 18:41:54 -0500 From: Kris Kennaway To: Gayn Winters Message-ID: <20060120234154.GA45159@xor.obsecurity.org> References: <20060120194700.GB41039@xor.obsecurity.org> <02c901c61e19$2efd3680$6501a8c0@workdog> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="T4sUOijqQbZv57TR" Content-Disposition: inline In-Reply-To: <02c901c61e19$2efd3680$6501a8c0@workdog> User-Agent: Mutt/1.4.2.1i Cc: 'Wesley Shields' , freebsd-hackers@freebsd.org, 'Ashok Shrestha' , 'Brandon Flowers' , 'Mike Meyer' , 'Gary Thorpe' , 'Kris Kennaway' , 'Dag-Erling Sm?rgrav' Subject: Re: speed up port compiling using RAM (tmpfs) ??? 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, 20 Jan 2006 23:41:56 -0000 --T4sUOijqQbZv57TR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jan 20, 2006 at 03:28:08PM -0800, Gayn Winters wrote: > > [mailto:owner-freebsd-hackers@freebsd.org] On Behalf Of Kris Kennaway > > Sent: Friday, January 20, 2006 11:47 AM > > To: Gary Thorpe > > Cc: Wesley Shields; Ashok Shrestha; Brandon Flowers; Kris=20 > > Kennaway; Mike Meyer; freebsd-hackers@freebsd.org; Dag-Erling Sm?rgrav > > Subject: Re: speed up port compiling using RAM (tmpfs) ??? > >=20 > >=20 > > On Fri, Jan 20, 2006 at 11:49:29AM -0500, Gary Thorpe wrote: > >=20 > > > >-j is not safe to use with port builds since many ported software > > > >contain race conditions in the build. > > > > > > > >Kris > > >=20 > > > This effectively means that you cannot take advantage of SMP to > compile=20 > > > FreeBSD's ports collection. That sounds like a big=20 > > > limitation...especially for people trying to speed up bulk builds. > >=20 > > Yeah, but what do you propose to do about it? We have 14000 ports > > that need to be inspected for build race conditions and fixed before > > you can turn on -j by default. > >=20 > > Kris >=20 >=20 > With a dual processor (even dual core?) is there a way to assign the big > make to one processor and to assign the foreground activity (email, > edits, etc) to another? Is SMP somehow smart enough to do this > automagically? Yes, this is what will happen, more or less. Kris --T4sUOijqQbZv57TR Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFD0XVCWry0BWjoQKURAiiCAJ9w6Nxh3WRSQ3aMTFVzV9TYFi2A9wCeL4bI ooTecvFlnfI3HY1yeb2O6kE= =45l6 -----END PGP SIGNATURE----- --T4sUOijqQbZv57TR-- From owner-freebsd-hackers@FreeBSD.ORG Sat Jan 21 00:27:19 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E7BB416A425 for ; Sat, 21 Jan 2006 00:27:19 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from fallbackmx02.syd.optusnet.com.au (fallbackmx02.syd.optusnet.com.au [211.29.133.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8D89B43D4C for ; Sat, 21 Jan 2006 00:27:17 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from mail01.syd.optusnet.com.au (mail01.syd.optusnet.com.au [211.29.132.182]) by fallbackmx02.syd.optusnet.com.au (8.11.6/8.11.6) with ESMTP id k0L0RGv12990 for ; Sat, 21 Jan 2006 11:27:16 +1100 Received: from cirb503493.alcatel.com.au (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail01.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k0L0QE8G011152 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sat, 21 Jan 2006 11:26:15 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1]) by cirb503493.alcatel.com.au (8.12.10/8.12.10) with ESMTP id k0L0QEHh032006; Sat, 21 Jan 2006 11:26:14 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost) by cirb503493.alcatel.com.au (8.12.10/8.12.9/Submit) id k0L0QEpn032005; Sat, 21 Jan 2006 11:26:14 +1100 (EST) (envelope-from pjeremy) Date: Sat, 21 Jan 2006 11:26:14 +1100 From: Peter Jeremy To: babkin@users.sourceforge.net Message-ID: <20060121002614.GL25397@cirb503493.alcatel.com.au> References: <2209162.1137777933811.JavaMail.root@vms075.mailsrvcs.net> <20060120193741.GC39932@xor.obsecurity.org> <43D15C19.314EC346@verizon.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43D15C19.314EC346@verizon.net> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.11 Cc: freebsd-hackers@freebsd.org Subject: Re: speed up port compiling using RAM (tmpfs) ??? 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, 21 Jan 2006 00:27:20 -0000 On Fri, 2006-Jan-20 16:54:33 -0500, Sergey Babkin wrote: >Kris Kennaway wrote: >> It's harder than that, because you need to impose dependency >> information and mutual exclusion between different makes. e.g. they >> can't both be compiling the same port at the same time, which will >> happen if you just do the naive thing. > >That's the part that "make -j" is supposed to take care of, >since it should build in parallel only the targets independent >of each other. It doesn't quite work like that. A single make execution will correctly parallelize independent targets (as long as the makefile dependency tree is correct - which is not true for all ports). The problem occurs when the targets are sub-makes. In this case, you have multiple sub-makes running in parallel with no knowledge of the dependency trees of the other sub-makes. Unless the top-level makefile has full knowledge of all the dependencies (which is not practical), it is quite likely that the sub-makes will collide. -- Peter Jeremy From owner-freebsd-hackers@FreeBSD.ORG Sat Jan 21 01:36:22 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5B87F16A41F for ; Sat, 21 Jan 2006 01:36:22 +0000 (GMT) (envelope-from babkin@verizon.net) Received: from vms040pub.verizon.net (vms040pub.verizon.net [206.46.252.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id E69B043D45 for ; Sat, 21 Jan 2006 01:36:21 +0000 (GMT) (envelope-from babkin@verizon.net) Received: from verizon.net ([138.89.156.25]) by vms040.mailsrvcs.net (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) with ESMTPA id <0ITF00JNQ5SHK1Z1@vms040.mailsrvcs.net> for freebsd-hackers@freebsd.org; Fri, 20 Jan 2006 19:36:21 -0600 (CST) Date: Fri, 20 Jan 2006 20:36:17 -0500 From: Sergey Babkin Sender: root To: Kris Kennaway Message-id: <43D19011.D15F8462@verizon.net> MIME-version: 1.0 X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.7-RELEASE i386) Content-type: text/plain; charset=koi8-r Content-transfer-encoding: 7bit X-Accept-Language: en, ru References: <2209162.1137777933811.JavaMail.root@vms075.mailsrvcs.net> <20060120193741.GC39932@xor.obsecurity.org> <43D15C19.314EC346@verizon.net> <20060120222629.GA43985@xor.obsecurity.org> Cc: Wesley Shields , freebsd-hackers@freebsd.org, Brandon Flowers , Mike Meyer , Gary Thorpe , Ashok Shrestha , Dag-Erling Sm?rgrav Subject: Re: speed up port compiling using RAM (tmpfs) ??? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: babkin@freebsd.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Jan 2006 01:36:22 -0000 Kris Kennaway wrote: > > On Fri, Jan 20, 2006 at 04:54:33PM -0500, Sergey Babkin wrote: > > Kris Kennaway wrote: > > > > > > On Fri, Jan 20, 2006 at 11:25:33AM -0600, Sergey Babkin wrote: > > > > >From: =?ISO646-US?Q?Dag-Erling_Sm=3Frgrav?= > > > > > > > > >Gary Thorpe writes: > > > > >> This effectively means that you cannot take advantage of SMP to > > > > >> compile FreeBSD's ports collection. That sounds like a big > > > > >> limitation...especially for people trying to speed up bulk builds. > > > > > > > > > >We cannot be held responsible for race conditions in the Makefiles of > > > > >third-party software. > > > > > > > > Well, maybe we can then build multiple ports in parallel. > > > > I guess the way to do it would be to run the top-level make with > > > > -j but then disable it when calling the makefiles of the > > > > individual ports. Not that I have any idea how to actually > > > > do that. > > > > > > It's harder than that, because you need to impose dependency > > > information and mutual exclusion between different makes. e.g. they > > > can't both be compiling the same port at the same time, which will > > > happen if you just do the naive thing. > > > > That's the part that "make -j" is supposed to take care of, > > since it should build in parallel only the targets independent > > of each other. > > If (as I said) you impose the correct dependency information. > Currently there is no such information provided. Ah, so we don't have any reliable information about dependencies between the ports either (not just between files inside each particular port)? Hm, I think it would present a problem even when building them sequentially. -SB From owner-freebsd-hackers@FreeBSD.ORG Sat Jan 21 01:53:13 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C62BF16A41F; Sat, 21 Jan 2006 01:53:13 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 868E243D53; Sat, 21 Jan 2006 01:53:12 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 61E361A3C1E; Fri, 20 Jan 2006 17:53:12 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 93F2351AD6; Fri, 20 Jan 2006 20:53:11 -0500 (EST) Date: Fri, 20 Jan 2006 20:53:11 -0500 From: Kris Kennaway To: babkin@freebsd.org Message-ID: <20060121015311.GA46753@xor.obsecurity.org> References: <2209162.1137777933811.JavaMail.root@vms075.mailsrvcs.net> <20060120193741.GC39932@xor.obsecurity.org> <43D15C19.314EC346@verizon.net> <20060120222629.GA43985@xor.obsecurity.org> <43D19011.D15F8462@verizon.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="lrZ03NoBR/3+SXJZ" Content-Disposition: inline In-Reply-To: <43D19011.D15F8462@verizon.net> User-Agent: Mutt/1.4.2.1i Cc: Wesley Shields , Ashok Shrestha , freebsd-hackers@freebsd.org, Brandon Flowers , Mike Meyer , Gary Thorpe , Kris Kennaway , Dag-Erling Sm?rgrav Subject: Re: speed up port compiling using RAM (tmpfs) ??? 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, 21 Jan 2006 01:53:13 -0000 --lrZ03NoBR/3+SXJZ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jan 20, 2006 at 08:36:17PM -0500, Sergey Babkin wrote: > > If (as I said) you impose the correct dependency information. > > Currently there is no such information provided. >=20 > Ah, so we don't have any reliable information about dependencies=20 > between the ports either (not just between files inside each=20 > particular port)? Hm, I think it would present a problem even=20 > when building them sequentially. The port dependency checking of one port upon other ports doesn't really use the make(1) dependency system. Instead there is a shell script in bsd.port.mk that looks for the file listed in the *_DEPENDS variable and goes and explicitly spawns a new make to build the port if it is not found. This is fine for building ports serially, but it's not trivially parallelizable since it only has local knowledge: In order to do better you either have to: 1a) construct an enormous make(1) dependency web of the entire ports collection (in order to have global knowledge and be able to direct makes to avoid collisions), and 1b) somehow keep it up-to-date each time the ports tree is modified. or 2) Introduce mutual exclusion to prevent conflicts from two makes trying to operate on the same port at once. You also need to serialize in other places, e.g. modifying the database state in /var/db. This won't be as efficient as 1) since the second make will block instead of going off to build some other dependency in the meantime, which you could do with 1) if you could manage to implement it. Kris --lrZ03NoBR/3+SXJZ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFD0ZQHWry0BWjoQKURAj0oAKDffSa6Rw8XwSbEXTlE8/HWhpLkJACgucjl cFTTIW7EEBYUq/KmkmQ6uXA= =5klC -----END PGP SIGNATURE----- --lrZ03NoBR/3+SXJZ-- From owner-freebsd-hackers@FreeBSD.ORG Sat Jan 21 05:24:39 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0898C16A41F for ; Sat, 21 Jan 2006 05:24:39 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 85F6843D48 for ; Sat, 21 Jan 2006 05:24:38 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id k0L5MFtx059600; Fri, 20 Jan 2006 22:22:15 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Fri, 20 Jan 2006 22:22:31 -0700 (MST) Message-Id: <20060120.222231.82100775.imp@bsdimp.com> To: matt@gsicomp.on.ca From: "M. Warner Losh" In-Reply-To: <001501c61ca7$9c1d7450$1200a8c0@gsicomp.on.ca> References: <001501c61ca7$9c1d7450$1200a8c0@gsicomp.on.ca> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Fri, 20 Jan 2006 22:22:15 -0700 (MST) Cc: freebsd-hackers@freebsd.org Subject: Re: Config(8) dependency checking - first patches 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, 21 Jan 2006 05:24:39 -0000 : Notes and patches against 7-CURRENT are at : http://www.gsicomp.on.ca/projects/freebsd/configdep.html. How would you encode ed's dependencies? The ed driver only depends on mii when built with pccard enabled. Warner From owner-freebsd-hackers@FreeBSD.ORG Sat Jan 21 16:07:41 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9968916A420; Sat, 21 Jan 2006 16:07:41 +0000 (GMT) (envelope-from fullermd@over-yonder.net) Received: from mail.localelinks.com (web.localelinks.com [64.39.75.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 428C043D45; Sat, 21 Jan 2006 16:07:41 +0000 (GMT) (envelope-from fullermd@over-yonder.net) Received: from draco.over-yonder.net (adsl-072-148-013-213.sip.jan.bellsouth.net [72.148.13.213]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.localelinks.com (Postfix) with ESMTP id A350CAD; Sat, 21 Jan 2006 10:07:40 -0600 (CST) Received: by draco.over-yonder.net (Postfix, from userid 100) id B022F61C21; Sat, 21 Jan 2006 10:07:39 -0600 (CST) Date: Sat, 21 Jan 2006 10:07:39 -0600 From: "Matthew D. Fuller" To: Kris Kennaway Message-ID: <20060121160739.GH63244@over-yonder.net> References: <2209162.1137777933811.JavaMail.root@vms075.mailsrvcs.net> <20060120193741.GC39932@xor.obsecurity.org> <43D15C19.314EC346@verizon.net> <20060120222629.GA43985@xor.obsecurity.org> <43D19011.D15F8462@verizon.net> <20060121015311.GA46753@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060121015311.GA46753@xor.obsecurity.org> X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.5.11-fullermd.2 Cc: freebsd-hackers@freebsd.org Subject: Re: speed up port compiling using RAM (tmpfs) ??? 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, 21 Jan 2006 16:07:41 -0000 [ Cc trim a bit ] On Fri, Jan 20, 2006 at 08:53:11PM -0500 I heard the voice of Kris Kennaway, and lo! it spake thus: > > In order to do better you either have to: This is something that may be easier to: 3) Implement in portupgrade or portmanager or some such higher-level tool in a language that gives a little more flexibility than make, and which is already apparently pulling in most of the information it may need to do the job. -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. From owner-freebsd-hackers@FreeBSD.ORG Sat Jan 21 20:23:25 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4917716A41F; Sat, 21 Jan 2006 20:23:25 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id BD26C43D45; Sat, 21 Jan 2006 20:23:24 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 314421A3C1F; Sat, 21 Jan 2006 12:23:23 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id BDB0C51FBC; Sat, 21 Jan 2006 15:23:21 -0500 (EST) Date: Sat, 21 Jan 2006 15:23:21 -0500 From: Kris Kennaway To: "Matthew D. Fuller" Message-ID: <20060121202321.GA83848@xor.obsecurity.org> References: <2209162.1137777933811.JavaMail.root@vms075.mailsrvcs.net> <20060120193741.GC39932@xor.obsecurity.org> <43D15C19.314EC346@verizon.net> <20060120222629.GA43985@xor.obsecurity.org> <43D19011.D15F8462@verizon.net> <20060121015311.GA46753@xor.obsecurity.org> <20060121160739.GH63244@over-yonder.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="mYCpIKhGyMATD0i+" Content-Disposition: inline In-Reply-To: <20060121160739.GH63244@over-yonder.net> User-Agent: Mutt/1.4.2.1i Cc: freebsd-hackers@freebsd.org, Kris Kennaway Subject: Re: speed up port compiling using RAM (tmpfs) ??? 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, 21 Jan 2006 20:23:25 -0000 --mYCpIKhGyMATD0i+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jan 21, 2006 at 10:07:39AM -0600, Matthew D. Fuller wrote: > [ Cc trim a bit ] >=20 > On Fri, Jan 20, 2006 at 08:53:11PM -0500 I heard the voice of > Kris Kennaway, and lo! it spake thus: > >=20 > > In order to do better you either have to: >=20 > This is something that may be easier to: >=20 > 3) Implement in portupgrade or portmanager or some such higher-level > tool in a language that gives a little more flexibility than make, > and which is already apparently pulling in most of the information > it may need to do the job. You still have the same issue as 1). Kris --mYCpIKhGyMATD0i+ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFD0pg4Wry0BWjoQKURAk0LAJ0c5bHRK2f46zpp7iA7GRSthyhuTACglfWq AZ69iF7yUUWeBXNoqDR3v9I= =Q1rC -----END PGP SIGNATURE----- --mYCpIKhGyMATD0i+-- From owner-freebsd-hackers@FreeBSD.ORG Sat Jan 21 20:31:04 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5158D16A41F for ; Sat, 21 Jan 2006 20:31:04 +0000 (GMT) (envelope-from fullermd@over-yonder.net) Received: from mail.localelinks.com (web.localelinks.com [64.39.75.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id BC35143D68 for ; Sat, 21 Jan 2006 20:30:58 +0000 (GMT) (envelope-from fullermd@over-yonder.net) Received: from draco.over-yonder.net (adsl-072-148-013-213.sip.jan.bellsouth.net [72.148.13.213]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.localelinks.com (Postfix) with ESMTP id 1E1ABAD; Sat, 21 Jan 2006 14:30:58 -0600 (CST) Received: by draco.over-yonder.net (Postfix, from userid 100) id 3550761C2B; Sat, 21 Jan 2006 14:30:57 -0600 (CST) Date: Sat, 21 Jan 2006 14:30:57 -0600 From: "Matthew D. Fuller" To: Kris Kennaway Message-ID: <20060121203057.GK63244@over-yonder.net> References: <2209162.1137777933811.JavaMail.root@vms075.mailsrvcs.net> <20060120193741.GC39932@xor.obsecurity.org> <43D15C19.314EC346@verizon.net> <20060120222629.GA43985@xor.obsecurity.org> <43D19011.D15F8462@verizon.net> <20060121015311.GA46753@xor.obsecurity.org> <20060121160739.GH63244@over-yonder.net> <20060121202321.GA83848@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060121202321.GA83848@xor.obsecurity.org> X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.5.11-fullermd.2 Cc: freebsd-hackers@freebsd.org Subject: Re: speed up port compiling using RAM (tmpfs) ??? 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, 21 Jan 2006 20:31:04 -0000 On Sat, Jan 21, 2006 at 03:23:21PM -0500 I heard the voice of Kris Kennaway, and lo! it spake thus: > On Sat, Jan 21, 2006 at 10:07:39AM -0600, Matthew D. Fuller wrote: > > > > This is something that may be easier to: > > > > 3) Implement in portupgrade or portmanager or some such higher-level > > tool in a language that gives a little more flexibility than make, > > and which is already apparently pulling in most of the information > > it may need to do the job. > > You still have the same issue as 1). [ 1 == building dependancy tree to know what depends on what ] Yes, but portupgrade and friends already do most of that, so they can upgrade stuff "in order". The biggest thing it seems like portupgrade (which is the only one I'm personally familiar with) lacks is that it doesn't of itself find out "which of these dependancies are already installed", and lets the ports tree itself recurse down. It sounds, from reading the emails, like the script dougb has been putting together does this, though. Given that capability, and the information portupgrade builds (from all-depends-list, I think?) to determine which order to upgrade things in, it seems like it would have right there most of what it needs. There are still issues like "after you start building something and it does the make config" and the like to handle (as well as terminal arbitration issues with multiple possibly interactive compiles going at once), of course. Not an easy or trivial thing to do even with all that, certainly, but probably easier in perl/ruby/C/etc than in make... -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. From owner-freebsd-hackers@FreeBSD.ORG Sat Jan 21 21:10:00 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9833D16A41F for ; Sat, 21 Jan 2006 21:10:00 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from mail05.syd.optusnet.com.au (mail05.syd.optusnet.com.au [211.29.132.186]) by mx1.FreeBSD.org (Postfix) with ESMTP id CF09843D45 for ; Sat, 21 Jan 2006 21:09:59 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail05.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k0LL9vPc017359 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 22 Jan 2006 08:09:58 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1]) by cirb503493.alcatel.com.au (8.12.10/8.12.10) with ESMTP id k0LL9uHh033716; Sun, 22 Jan 2006 08:09:56 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost) by cirb503493.alcatel.com.au (8.12.10/8.12.9/Submit) id k0LL9ueg033715; Sun, 22 Jan 2006 08:09:56 +1100 (EST) (envelope-from pjeremy) Date: Sun, 22 Jan 2006 08:09:56 +1100 From: Peter Jeremy To: "Matthew D. Fuller" Message-ID: <20060121210956.GU25397@cirb503493.alcatel.com.au> References: <2209162.1137777933811.JavaMail.root@vms075.mailsrvcs.net> <20060120193741.GC39932@xor.obsecurity.org> <43D15C19.314EC346@verizon.net> <20060120222629.GA43985@xor.obsecurity.org> <43D19011.D15F8462@verizon.net> <20060121015311.GA46753@xor.obsecurity.org> <20060121160739.GH63244@over-yonder.net> <20060121202321.GA83848@xor.obsecurity.org> <20060121203057.GK63244@over-yonder.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060121203057.GK63244@over-yonder.net> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.11 Cc: freebsd-hackers@freebsd.org Subject: Re: speed up port compiling using RAM (tmpfs) ??? 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, 21 Jan 2006 21:10:00 -0000 On Sat, 2006-Jan-21 14:30:57 -0600, Matthew D. Fuller wrote: >On Sat, Jan 21, 2006 at 03:23:21PM -0500 I heard the voice of >Kris Kennaway, and lo! it spake thus: >> On Sat, Jan 21, 2006 at 10:07:39AM -0600, Matthew D. Fuller wrote: >> > >> > This is something that may be easier to: >> > >> > 3) Implement in portupgrade or portmanager or some such higher-level >> > tool in a language that gives a little more flexibility than make, >> > and which is already apparently pulling in most of the information >> > it may need to do the job. >> >> You still have the same issue as 1). > > [ 1 == building dependancy tree to know what depends on what ] > >Yes, but portupgrade and friends already do most of that, so they can >upgrade stuff "in order". Actually, they rely on there being an up-to-date INDEX file and build their own dependency database from that. Actually building the INDEX file is non-trivial (it takes roughly an hour for me). Tools like p5-FreeBSD-Portindex-1.4 cache intermediate output from "make index" but still have the up-front "make index" cost (and the documentation recommends a full "make index" regularly). You can save time by fetching the INDEX, but then you can't be certain that it matches your ports tree or your port options. Given that a port's dependency tree can depend on the options it is invoked with, it would be nicer if the dependency tree was generated dynamically, rather than pulled out of the latest INDEX file. If the INDEX dependencies are used to generate a parallel build tree then it's still important that the actual build process has interlocks to prevent unforeseen dependencies causing clashes. -- Peter Jeremy From owner-freebsd-hackers@FreeBSD.ORG Sat Jan 21 21:41:09 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7CE8616A41F for ; Sat, 21 Jan 2006 21:41:09 +0000 (GMT) (envelope-from fullermd@over-yonder.net) Received: from mail.localelinks.com (web.localelinks.com [64.39.75.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id B982443D4C for ; Sat, 21 Jan 2006 21:41:08 +0000 (GMT) (envelope-from fullermd@over-yonder.net) Received: from draco.over-yonder.net (adsl-072-148-013-213.sip.jan.bellsouth.net [72.148.13.213]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.localelinks.com (Postfix) with ESMTP id ED99AAD; Sat, 21 Jan 2006 15:41:07 -0600 (CST) Received: by draco.over-yonder.net (Postfix, from userid 100) id 196DC61C21; Sat, 21 Jan 2006 15:41:07 -0600 (CST) Date: Sat, 21 Jan 2006 15:41:07 -0600 From: "Matthew D. Fuller" To: Peter Jeremy Message-ID: <20060121214106.GL63244@over-yonder.net> References: <2209162.1137777933811.JavaMail.root@vms075.mailsrvcs.net> <20060120193741.GC39932@xor.obsecurity.org> <43D15C19.314EC346@verizon.net> <20060120222629.GA43985@xor.obsecurity.org> <43D19011.D15F8462@verizon.net> <20060121015311.GA46753@xor.obsecurity.org> <20060121160739.GH63244@over-yonder.net> <20060121202321.GA83848@xor.obsecurity.org> <20060121203057.GK63244@over-yonder.net> <20060121210956.GU25397@cirb503493.alcatel.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060121210956.GU25397@cirb503493.alcatel.com.au> X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.5.11-fullermd.2 Cc: freebsd-hackers@freebsd.org Subject: Re: speed up port compiling using RAM (tmpfs) ??? 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, 21 Jan 2006 21:41:09 -0000 On Sun, Jan 22, 2006 at 08:09:56AM +1100 I heard the voice of Peter Jeremy, and lo! it spake thus: > > Given that a port's dependency tree can depend on the options it is > invoked with, it would be nicer if the dependency tree was generated > dynamically, rather than pulled out of the latest INDEX file. I'm pretty sure it _is_, since portupgrade finds things related to OPTIONS and such for me, and I don't blow multiple hours on INDEX builds. I'm pretty sure it uses all-depends-list (or one of its siblings). -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. From owner-freebsd-hackers@FreeBSD.ORG Sat Jan 21 23:04:09 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6A05E16A41F; Sat, 21 Jan 2006 23:04:09 +0000 (GMT) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id C946443D49; Sat, 21 Jan 2006 23:04:08 +0000 (GMT) (envelope-from max@love2party.net) Received: from [84.163.237.190] (helo=amd64.laiers.local) by mrelayeu.kundenserver.de (node=mrelayeu8) with ESMTP (Nemesis), id 0ML2ov-1F0RmB0oWV-0001vv; Sun, 22 Jan 2006 00:04:07 +0100 From: Max Laier Organization: FreeBSD To: freebsd-current@freebsd.org Date: Sun, 22 Jan 2006 00:04:17 +0100 User-Agent: KMail/1.9.1 References: <200601132019.41896.max@love2party.net> In-Reply-To: <200601132019.41896.max@love2party.net> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart4900154.L18kkaJxx6"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200601220004.23929.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de login:61c499deaeeba3ba5be80f48ecc83056 Cc: freebsd-hackers@freebsd.org Subject: Re: Call for FreeBSD Status Reports X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: monthly@freebsd.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Jan 2006 23:04:09 -0000 --nextPart4900154.L18kkaJxx6 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline All, On Friday 13 January 2006 20:19, I wrote: > no big news since 6.0, but in the background there are many interesting > projects: Just now the new malloc has hit current, we hear promising > numbers from the network performance crew, the first batch of security > advisories is out and I'm sure some of you spent the holidays doing exiti= ng > stuff for FreeBSD as well. Please tell us! > > This is the call for Status Reports of your project activity between > October and now. This is not limited to developers. We want a broad > spectrum of reports from everybody involved with FreeBSD. Check the Stat= us > Report homepage[1] for earlier reports. > > Submission deadline is a week from now, January 20th! I don't want to > delay the publication much this time, so please write your report now!=20 > Please use the XML-generator[2] or -template[3] and send your report to > monthly@freebsd.org by next Friday. Thanks a lot! to date we have received only 11 reports, which - compared to earlier round= s -=20 is a poor turnout. I am wondering if we just had a quiet period, if you=20 don't feel your projects are ready for prime-time or if you are just tiered= =20 of writting reports? In either case, please let me know so we can do something about it. If you= =20 want to submit a report - deadline is extended to Wednesday (25th). Thanks! =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --nextPart4900154.L18kkaJxx6 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBD0r33XyyEoT62BG0RArzsAJ9RYZDy/+BbqXHWjU+1JnCbFQoQjgCbBznN 0ln7Jm4DIqi2ad11law9L1o= =kbq1 -----END PGP SIGNATURE----- --nextPart4900154.L18kkaJxx6-- From owner-freebsd-hackers@FreeBSD.ORG Sat Jan 21 22:40:31 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C2FDB16A41F; Sat, 21 Jan 2006 22:40:31 +0000 (GMT) (envelope-from paf@pacbell.net) Received: from pacbell.net (adsl-63-199-179-203.dsl.snfc21.pacbell.net [63.199.179.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 596B443D5C; Sat, 21 Jan 2006 22:40:31 +0000 (GMT) (envelope-from paf@pacbell.net) Received: (from paf@localhost) by pacbell.net (8.11.0/8.9.3) id k0LMnqG13130; Sat, 21 Jan 2006 14:49:52 -0800 From: PAF Message-Id: <200601212249.k0LMnqG13130@pacbell.net> To: keramida@freebsd.org (Giorgos Keramidas) Date: Sat, 21 Jan 2006 14:49:51 -0800 (PST) In-Reply-To: <20050317222842.GA1646@gothmog.gr> from "Giorgos Keramidas" at Mar 18, 2005 12:28:42 AM X-Mailer: ELM [version 2.5 PL3] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Sat, 21 Jan 2006 23:28:54 +0000 Cc: freebsd-hackers@freebsd.org, Roman Kurakin Subject: Re: style(9) example :-) 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, 21 Jan 2006 22:40:31 -0000 > > On 2005-03-18 00:50, Roman Kurakin wrote: > >Giorgos Keramidas: > >>On 2005-03-17 19:33, Roman Kurakin wrote: > >>>I was unable to refrain from posting this :-) > >>> > >>>int i;main(){for(;i["] >>>o, world!\n",'/'/'/'));}read(j,i,p){write(j/p+p,i---j,i/i);} > >> > >>I've written stuff that's probably a bit harder to read, but in Perl :P > >> > >>% cat filter.pl > >>#/usr/bin/perl > >>while(){chomp;print(join('',(map{my($b,$j,$t,$o)=(65,128,90,ord($_));(( > >>$o-$b)>=0&&($o-$b)<=($t-$b))?eval{$o=(($o-$b)+13)%26+$b;$j=11;}:eval{$b=97;$t= > >>122;(($b>$o)||($t<$o))?eval{$j=10;}:eval{$o=(($o-$b)+13)%26+$b;$j=1431;};};$_= > >>chr(int(int(($j%2)==(chr($o)==$_))?$o:ord($_)));}(split//,$_)))."\n");} > >>% > > > > I saw smth like that, which run rm -rf /. I hope this one word greeting ;-) > > Probably one such code could be added to fortunes. > > This one is a rot13 filter. But no need to run it. It's was fun > writing, but very very useless. Other than as an example of how ugly > Perl can be, I guess... > _______________________________________________ > 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" >