From owner-freebsd-hackers Sun Jul 23 0:39:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id E45B737B9A6 for ; Sun, 23 Jul 2000 00:39:09 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id DAA37081 for ; Sun, 23 Jul 2000 03:39:08 -0400 (EDT) Message-Id: <200007230739.DAA37081@cs.rpi.edu> To: freebsd-hackers@freebsd.org Subject: 4.1-RC + SBLive + ECC = NMI Date: Sun, 23 Jul 2000 03:39:07 -0400 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I upgraded to 4.1-RC1 today; attempted to fire up esound and my system hung. I rebooted into X, fired up esound from text mode and system hung again with a message that an NMI was caught. I remember that the SBLive has some issues with ECC systems, resulting in some NMIs being thrown. It would appear that some of the recent fixes in emu10k1.c v1.6.2.1 tickle this behavior. I am going to try to back-out to 1.6 and see if this resolves the issue. Has anyone else experienced this? Can I whap creative for producing such great hardware? :) -- David Cross | email: crossd@cs.rpi.edu Lab Director | Rm: 308 Lally Hall Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 23 1:42:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id CCE8B37B68F for ; Sun, 23 Jul 2000 01:42:17 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id EAA38167; Sun, 23 Jul 2000 04:42:14 -0400 (EDT) Message-Id: <200007230842.EAA38167@cs.rpi.edu> To: "David E. Cross" Cc: freebsd-hackers@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: 4.1-RC + SBLive + ECC = NMI In-Reply-To: Message from "David E. Cross" of "Sun, 23 Jul 2000 03:39:07 EDT." <200007230739.DAA37081@cs.rpi.edu> Date: Sun, 23 Jul 2000 04:42:13 -0400 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hmm... backing out to emu10k1.c version 1.6 did not fix my problem. Does anyone else have a SBLive! in an ECC machine that is throwing an NMI whenever you try to use xmms or esd? If not, I will try to binary search the dates to see if I can find when the change that tickeled the NMI bug on the SBLive! was introduced. -- David Cross | email: crossd@cs.rpi.edu Lab Director | Rm: 308 Lally Hall Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 23 2: 6:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.mtelecom.ru (host3.mtelecom.ru [212.44.147.3]) by hub.freebsd.org (Postfix) with ESMTP id 3357D37B8AC for ; Sun, 23 Jul 2000 02:06:46 -0700 (PDT) (envelope-from s@gw2.mtelecom.ru) Received: from gw2.mtelecom.ru (gw2.mtelecom.ru [192.168.3.2]) by ns.mtelecom.ru (8.8.5/8.8.5) with ESMTP id NAA10688 for ; Sun, 23 Jul 2000 13:06:04 +0400 (MSD) Received: from localhost (s@localhost) by gw2.mtelecom.ru (8.9.1a/8.9.1) with SMTP id NAA15985 for ; Sun, 23 Jul 2000 13:06:55 +0400 (MSD) Date: Sun, 23 Jul 2000 13:06:54 +0400 (MSD) From: Vsevolod Semenov X-Sender: s@gw2 Reply-To: seva@mtelecom.ru To: freebsd-hackers@FreeBSD.ORG Subject: 4.0-RELEASE/tail/st_rdev Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I used "tail -F /var/log/local3" in my little shell script to scan log for some string. When i change release from 3.X to 4.0 tail sometimes (may be once in a day or hours) rescan log from begining and alarm me about problem which has being occurred hours before. It was coz " sb2.st_rdev != sbp->st_rdev" in /usr/src/usr.bin/tail/forward.c. I've commented this out and became happy. Q: Wtf is st_rdev in regular files in FreeBSD 4.0-RELEASE? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 23 7:22:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from danbala.tuwien.ac.at (danbala.ifoer.tuwien.ac.at [128.130.168.64]) by hub.freebsd.org (Postfix) with ESMTP id D15C337B757; Sun, 23 Jul 2000 07:22:16 -0700 (PDT) (envelope-from wiz@danbala.tuwien.ac.at) Received: (from wiz@localhost) by danbala.tuwien.ac.at (8.8.8/8.8.8) id QAA17137; Sun, 23 Jul 2000 16:21:48 +0200 (MEST) Date: Sun, 23 Jul 2000 16:21:48 +0200 From: Thomas Klausner To: Jason R Thorpe , freebsd-arch@freebsd.org, freebsd-hackers@freebsd.org, tech-kern@netbsd.org, tech@openbsd.org Cc: wiz@netbsd.org Subject: Re: minherit(2) API Message-ID: <20000723162148.D16217@danbala.tuwien.ac.at> References: <20000709150924.N23637@danbala.tuwien.ac.at> <20000711221235.W11576@dr-evil.shagadelic.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000711221235.W11576@dr-evil.shagadelic.org>; from thorpej@zembu.com on Tue, Jul 11, 2000 at 10:12:36PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mutt made be believe that Jason R Thorpe wrote: > DONATE_COPY is not implemented in UVM. I'm not sure it was ever > implemented anywhere. "Copy and delete" is really "move", right? > Anyway, it's not clear those semantics are really useful at all. Okay, so let's skip that one. Any other comments? I think I can change it in NetBSD -- anyone willing to do the necessary changes in FreeBSD and OpenBSD? Bye, Thomas -- Thomas Klausner - wiz@danbala.tuwien.ac.at I wanted to emulate some of my heroes, but I didn't know their op-codes. --dowe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 23 7:32:51 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id CAC0B37BA97 for ; Sun, 23 Jul 2000 07:32:46 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p18-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.147]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id XAA12762; Sun, 23 Jul 2000 23:32:35 +0900 (JST) Message-ID: <397B0214.46379EE6@newsguy.com> Date: Sun, 23 Jul 2000 23:32:52 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Mario Sergio Fujikawa Ferreira Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: sysutils/memtest and FreeBSD References: <20000721175757.B319@Fedaykin.here> <3979B777.A8AD8511@newsguy.com> <20000722181330.A404@Fedaykin.here> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mario Sergio Fujikawa Ferreira wrote: > > Besides, a failing malloc should return NULL, shouldn't > it? I would have expected core if I had malloc_options="X" which > I do not (in fact, I have no malloc_options). IF the malloc fails, it should return NULL. But this only happens in the case of artificial limits. > ps: Perhaps you could check the code, it is only 11K long. Sure, send it. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@white.bunnies.bsdconspiracy.net Satan was once an angel, Gates started by writing a BASIC interpreter. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 23 11:54:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mout2.silyn-tek.de (mout2.silyn-tek.de [194.25.165.70]) by hub.freebsd.org (Postfix) with ESMTP id 37FA537B6C8; Sun, 23 Jul 2000 11:54:44 -0700 (PDT) (envelope-from alex@big.endian.de) Received: from [192.168.32.34] (helo=mx2.silyn-tek.de) by mout2.silyn-tek.de with esmtp (Exim 3.13 #1) id 13GQtc-000287-00; Sun, 23 Jul 2000 20:54:40 +0200 Received: from p3e9d38dd.dip0.t-ipconnect.de ([62.157.56.221] helo=neutron.cichlids.com) by mx2.silyn-tek.de with esmtp (Exim 3.13 #1) id 13GQtZ-0004by-00; Sun, 23 Jul 2000 20:54:37 +0200 Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by neutron.cichlids.com (Postfix) with ESMTP id 21D3CAB91; Sun, 23 Jul 2000 20:56:33 +0200 (CEST) Received: by cichlids.cichlids.com (Postfix, from userid 1001) id 3A75D14BAF; Sun, 23 Jul 2000 20:54:37 +0200 (CEST) Date: Sun, 23 Jul 2000 20:54:37 +0200 To: bde@freebsd.org, phk@freebsd.org, hackers@freebsd.org Subject: type of _BSD_TIME_T_ in machine/ansi.h Message-ID: <20000723205437.A10537@cichlids.cichlids.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. From: alex@big.endian.de (Alexander Langer) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! Currently, I see the following: root@parca /sys $ grep _BSD_TIME_T {alpha,i386}/include/ansi.h alpha/include/ansi.h:#define _BSD_TIME_T_ int /* time() */ i386/include/ansi.h:#define _BSD_TIME_T_ long /* time()... */ I wonder if we want to change that to __int32_t in both files? Additionally, I have the following patch, which is needed at the moment to suppress warnings (on alpha): Index: kern_shutdown.c =================================================================== RCS file: /usr/home/ncvs/src/sys/kern/kern_shutdown.c,v retrieving revision 1.76 diff -u -r1.76 kern_shutdown.c --- kern_shutdown.c 2000/07/04 11:25:22 1.76 +++ kern_shutdown.c 2000/07/23 18:20:22 @@ -175,21 +175,37 @@ printf("Uptime: "); f = 0; if (ts.tv_sec >= 86400) { +#ifdef __alpha__ + printf("%dd", ts.tv_sec / 86400); +#else printf("%ldd", ts.tv_sec / 86400); +#endif ts.tv_sec %= 86400; f = 1; } if (f || ts.tv_sec >= 3600) { +#ifdef __alpha__ + printf("%dh", ts.tv_sec / 3600); +#else printf("%ldh", ts.tv_sec / 3600); +#endif ts.tv_sec %= 3600; f = 1; } if (f || ts.tv_sec >= 60) { +#ifdef __alpha__ + printf("%dm", ts.tv_sec / 60); +#else printf("%ldm", ts.tv_sec / 60); +#endif ts.tv_sec %= 60; f = 1; } +#ifdef __alpha__ + printf("%ds\n", ts.tv_sec); +#else printf("%lds\n", ts.tv_sec); +#endif } /* -- cat: /home/alex/.sig: No such file or directory To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 23 13:12:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mtiwmhc23.worldnet.att.net (mtiwmhc23.worldnet.att.net [204.127.131.48]) by hub.freebsd.org (Postfix) with ESMTP id 2E3AF37B7DC for ; Sun, 23 Jul 2000 13:12:26 -0700 (PDT) (envelope-from hspio@worldnet.att.net) Received: from default ([12.77.203.176]) by mtiwmhc23.worldnet.att.net (InterMail vM.4.01.02.39 201-229-119-122) with ESMTP id <20000723201207.DNOR3652.mtiwmhc23.worldnet.att.net@default> for ; Sun, 23 Jul 2000 20:12:07 +0000 From: hspio@worldnet.att.net To: hackers@FreeBSD.ORG Date: Sun, 23 Jul 2000 16:09:12 -0400 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Remove Message-ID: <397B18A8.5713.3D69341@localhost> In-reply-to: X-mailer: Pegasus Mail for Win32 (v3.12c) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 23 Jul 2000, at 7:22, freebsd-hackers-digest wrote: > > freebsd-hackers-digest Sunday, July 23 2000 Volume 04 : Number 901 > > > > In this issue: > Re: Multiple ro mounts of vinum volume > Re: Multiple ro mounts of vinum volume > Re: Intel 840 Chipset Discontinue > Re: sysutils/memtest and FreeBSD > Re: /etc/defaults/make.conf:LEAPSECONDS= true? > Re: clearing pages in the idle loop > Re: sysutils/memtest and FreeBSD > 4.1-RC + SBLive + ECC = NMI > Re: 4.1-RC + SBLive + ECC = NMI > 4.0-RELEASE/tail/st_rdev > Re: minherit(2) API > > ---------------------------------------------------------------------- > > Date: Sat, 22 Jul 2000 15:52:38 +0200 > From: Bernd Walter > Subject: Re: Multiple ro mounts of vinum volume > > On Thu, Jul 20, 2000 at 06:33:42PM +0930, Greg Lehey wrote: > > On Thursday, 20 July 2000 at 9:55:13 +0100, Geoff Buckingham wrote: > > A thing that might bite you here is that ufs is currently limited to 1 > > TB per volume. Vinum doesn't have that restriction: if you want to > > create a 20 TB volume, and you know how to use the space, Vinum should > > work. The problem with ufs is that the block numbers in the inodes > > are 32 bit signed values. With 512 byte sectors, the only we can do > > it, that means a total address space of 2**9 * 2*31, or 1 TB. At some > > time I suspect we're going to need to fix that. > > Block numbers in inodes are not physical blocks (named sectorsize in > UFS source) but logical which is equal to the size of an fragment and > thus defaults to 1k. > The problem is the driver and VM layer. > If vinum would simulate 2k "physical" blocksize it may go up to 4TB > if you set the fragment size to 4k. I don't know if any > middle calculation might harm or VM is missbehaving. > The point I never digged deeper here is because you already sugested > changing the driver layer to 64bit byte numbers which was accepted if > I remember right. > Some of the systems I've setup are near this Limit so I spend some time > to find out where the show stoppers are. > > - -- > B.Walter COSMO-Project http://www.cosmo-project.de > ticso@cicely.de Usergroup info@cosmo-project.de > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Sat, 22 Jul 2000 16:01:59 +0200 > From: Poul-Henning Kamp > Subject: Re: Multiple ro mounts of vinum volume > > In message <20000722155238.A27452@cicely8.cicely.de>, Bernd Walter writes: > > >The point I never digged deeper here is because you already sugested > >changing the driver layer to 64bit byte numbers which was accepted if > >I remember right. > > Yes, I have this on my plate. > > - -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > phk@FreeBSD.ORG | TCP/IP since RFC 956 > FreeBSD coreteam member | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by incompetence. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Sat, 22 Jul 2000 10:22:08 -0400 (EDT) > From: Andrew Gallatin > Subject: Re: Intel 840 Chipset Discontinue > > Mike Smith writes: > > > I was told by several of my distributors that all motherboards based off > > > of the Intel 840 chipset are being discontinued. That means the Supermicro > > > PIIDM3 and PIIIDME, and any other 840 board. > > Hurray! ;-) > > > I have mixed feelings about this, but on the whole I think it's probably > > for the best. I've had really patchy results with the i840, and > > performance hasn't been impressive. > > While, on the other hand, I cannot say enough good things about the > performance of our Dell PowerEdge 2400 & 4400 machines (both use RCC > chipsets). What else can you say about machines that will serve NFS > over via gig ether at over 70MB/sec and not break a sweat ;) > > > > Supermicro has two new boards, 370DL3 and 370DLE. Identical in specs to > > > the 840 boards, but using some kind of "ServerWork LE" chipset. However, I > > > have also been hearing bad news about these boards as well. > > > > We've had some issues with the RCC chipsets in Dell systems, yes. > > All of these are now resolved, aren't they? > > > > Has anyone worked with these boards? Supermicro SAYS that they work fine > > > under Linux and Solaris. However, one of my distributors says thay they > > > are extremely touchy when it comes to memory. Only Registered PC133 ECC > > > memory will work. > > This memory requirement probably explains why they perform so well ;) > The RCC chipsets, especially those which use interleaved memory like > in the PE4400, have stunningly good I/O bandwidth for a PC. They have > over 440MB/sec of I/O bandwidth to a 64-bit 66MHz PCI bus (I've > actually measured it, yes). They run gig ether at 950Mb/sec with > stock kernels and I've run protype Myrinet boards at over 2Gb/sec > end-to-end with TCP using the zero-copy sockets framework that Ken > Merry has been talking about. > > > > If someone at freebsd.org wants to seriously test these boards, let me > > > know, and I'll donate one. Without the 840 boards, server configs are now > > > back to the 440GX days! > > We've got a big purchase coming up & I'd love to get my hands on one > of them for testing, but FreeBSD test labs should get priority. > FWIW, I'm mainly an alpha port committer, but I'm the one who fixed > the RCC peer bus probing issues when we got our Dell 2400 a few months > back.. > > Anyway, we're looking to replace some of our cluster & would be > looking for 16-24 nodes of them. We were originally planning to get > Alpha DS10Ls, but the availability of RCC chipsets in a small form > factor may change our minds as the RCC chipset is the only thing that > can compete with the alpha's Tsunami chipset for I/O bandwidth. > > Do you know of anybody building 1U or 2U rackmount systems for a > reasonable price ($2000/node or less) around these motherboards? It > looks like most integrators are using the L44GX & its broken 32-bit > 66MHz slot which runs at the wrong voltage (Myrinet claims they're > violating the PCI spec). > > Cheers, > > Drew > > - ------------------------------------------------------------------------------ > Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin > Duke University Email: gallatin@cs.duke.edu > Department of Computer Science Phone: (919) 660-6590 > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Sun, 23 Jul 2000 00:02:15 +0900 > From: "Daniel C. Sobral" > Subject: Re: sysutils/memtest and FreeBSD > > Mario Sergio Fujikawa Ferreira wrote: > > > > Backtracing showed that the problem was due > > to the malloc function inside the get_mem function. > > get_mem() is used to find out the largest possible memory segment. > > It incrementaly reduces the segment passed to malloc to alloc. > > It is the malloc function allright. It core dumps on the > > 1st pass on get_mem(), there is no time to do_reduce. Very weird. ;( > > Because FreeBSD overcommits, malloc() will only fail in case of > artificial limits being reached (like those of login.conf). If FreeBSD > suddenly finds itself in a position of not being able to meet the > previous commitments wrt to memory allocation, it will kill the > application with the largest memory allocations. > > I'll bet you the fifth season of Babylon 5 this is what's happening. :-) > > Try limiting the maximum memory allocation to the total physical RAM. > > - -- > Daniel C. Sobral (8-DCS) > dcs@newsguy.com > dcs@freebsd.org > capo@white.bunnies.bsdconspiracy.net > > Satan was once an angel, Gates started by writing a BASIC interpreter. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Sun, 23 Jul 2000 00:04:41 +0900 > From: "Daniel C. Sobral" > Subject: Re: /etc/defaults/make.conf:LEAPSECONDS= true? > > Mario Sergio Fujikawa Ferreira wrote: > > > > I was wondering if this should go inside > > /etc/defaults/make.conf. > > Submit a PR. > > > --- /usr/src/etc/defaults/make.conf Sun Jul 16 05:30:30 2000 > > +++ /tmp/make.conf Fri Jul 21 18:42:35 2000 > > @@ -41,6 +41,9 @@ > > # To build perl with thread support > > #PERL_THREADED= true > > # > > +# Compile zoneinfo with correct leap second handling > > +#LEAPSECONDS= true > > +# > > # To avoid building various parts of the base system: > > #NO_CVS= true # do not build CVS > > #NO_BIND= true # do not build BIND > > > > If it does not, where in the handbook should > > I drop a note about it, besides FAQ (of course). > > > > Regards, > > Mario Ferreira > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > - -- > Daniel C. Sobral (8-DCS) > dcs@newsguy.com > dcs@freebsd.org > capo@white.bunnies.bsdconspiracy.net > > Satan was once an angel, Gates started by writing a BASIC interpreter. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Sat, 22 Jul 2000 10:39:08 -0700 (PDT) > From: Matt Dillon > Subject: Re: clearing pages in the idle loop > > :> Since the only effect of a cache miss is less efficient use of > :> the cpu, and since the page zeroing only occurs when the cpu is idle, > :> I would not expect to see much improvement from attempts to refine > :> the page-zeroing operation (beyond the simple hysteresis that FreeBSD > :> uses now and perhaps being able to bypass the cache). > : > :The reason why I'm interested in Cort's results is that I'd like to extend > :processing in the idle loop to other things (see my other mail). Cort > :measured a performance decrease of foreground processing, due to polluted > :caches after idle-time processing. We're discussing if disabling caches > :during the idle loop may prevent that. > > I think what you are observing may not be cache-related at all, but may > simply be the fact that zeroing a page takes a minimum amount of time > during which another task will not be scheduled, verses that other task > being scheduled instantly if all the idle loop were doing was checking > for new tasks to run. > > :> The real benefit occurs on a medium-to-heavily loaded machine which is > :> NOT cpu bound. Since nearly all page allocations require zero'd pages, > :> having a pool of pre-zero'd pages significantly reduces allocation > :> latency at just the time the process doing the allocation can best > :> benefit from it. In a cpu-bound system, the idle loop does not run > :> as often (or at all) and no pre-zeroing occurs anyway. > : > :I agree. However, on a medium-to-heavily loaded CPU, you'd probably see the > :largest decrease of foreground performance, as the idle times are short and > :bursty, and so your caches may get polluted more frequently. (Assuming > :cache pollution is in fact a problem; Allan seems to not think so.) > : > :If Allan still has his patches, I'll run some experiments, so we have some > :numbers to talk about. Maybe it doesn't matter. > > Another alternative is to have an idle process rather then try to do > things in the idle loop. This has the advantage of being instantly > interruptable if a 'real' process becomes runnable, but the disadvantage > of having to do a context switch (albeit a relatively cheap one). > > The FreeBSD page zeroing code in the idle loop typically does not run > all that often with an interactive load because interactive loads tend > not to allocate memory at a high rate, so the hysteresis points do not > get hit as often. Hmm. Maybe there's a bug in the hysteresis > calculation, I'll check it out. > > -Matt > > :> In regards to just zeroing the pieces of a page that need zeroing - this > :> is NOT an optimization designed for the idle-loop page-zeroing code. > : > :I made a mistake tracing through the code. Sorry. > : > :But it may be interesting to speculate if this would speed things up. Would > :probably require MMU support though. > : > :Lars > :-- > :Lars Eggert Information Sciences Institute > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Sat, 22 Jul 2000 18:13:30 -0300 > From: "Mario Sergio Fujikawa Ferreira" > Subject: Re: sysutils/memtest and FreeBSD > > Daniel, > > On Sun, Jul 23, 2000 at 12:01:53AM +0900, Daniel C. Sobral wrote: > > Mario Sergio Fujikawa Ferreira wrote: > > > > > > Backtracing showed that the problem was due > > > to the malloc function inside the get_mem function. > > > get_mem() is used to find out the largest possible memory segment. > > > It incrementaly reduces the segment passed to malloc to alloc. > > > It is the malloc function allright. It core dumps on the > > > 1st pass on get_mem(), there is no time to do_reduce. Very weird. ;( > > > > Because FreeBSD overcommits, malloc() will only fail in case of > > artificial limits being reached (like those of login.conf). If FreeBSD > > suddenly finds itself in a position of not being able to meet the > > previous commitments wrt to memory allocation, it will kill the > > application with the largest memory allocations. > > > > I'll bet you the fifth season of Babylon 5 this is what's happening. :-) > > Are you willing to bet the 3rd and 4th seasons as well? > The 4th season rocks. ;-) > > > Try limiting the maximum memory allocation to the total physical RAM. > > The code sets limits appropriatily with RLIMIT_MEMLOCK and > RLIMIT_RSS with setrlimit(). > Furthermore, I am not using any limits for the user testing > the program (a can do it all user :). > Besides, a failing malloc should return NULL, shouldn't > it? I would have expected core if I had malloc_options="X" which > I do not (in fact, I have no malloc_options). > > Regards, > Mario Ferreira > > ps: Perhaps you could check the code, it is only 11K long. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Sun, 23 Jul 2000 03:39:07 -0400 > From: "David E. Cross" > Subject: 4.1-RC + SBLive + ECC = NMI > > I upgraded to 4.1-RC1 today; attempted to fire up esound and my system hung. > > I rebooted into X, fired up esound from text mode and system hung again > with a message that an NMI was caught. > > I remember that the SBLive has some issues with ECC systems, resulting in > some NMIs being thrown. It would appear that some of the recent fixes in > emu10k1.c v1.6.2.1 tickle this behavior. I am going to try to back-out to > 1.6 and see if this resolves the issue. Has anyone else experienced this? > Can I whap creative for producing such great hardware? :) > > - -- > David Cross | email: crossd@cs.rpi.edu > Lab Director | Rm: 308 Lally Hall > Rensselaer Polytechnic Institute, | Ph: 518.276.2860 > Department of Computer Science | Fax: 518.276.4033 > I speak only for myself. | WinNT:Linux::Linux:FreeBSD > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Sun, 23 Jul 2000 04:42:13 -0400 > From: "David E. Cross" > Subject: Re: 4.1-RC + SBLive + ECC = NMI > > Hmm... backing out to emu10k1.c version 1.6 did not fix my problem. Does > anyone else have a SBLive! in an ECC machine that is throwing an NMI > whenever you try to use xmms or esd? If not, I will try to binary search > the dates to see if I can find when the change that tickeled the NMI bug on > the SBLive! was introduced. > > - -- > David Cross | email: crossd@cs.rpi.edu > Lab Director | Rm: 308 Lally Hall > Rensselaer Polytechnic Institute, | Ph: 518.276.2860 > Department of Computer Science | Fax: 518.276.4033 > I speak only for myself. | WinNT:Linux::Linux:FreeBSD > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Sun, 23 Jul 2000 13:06:54 +0400 (MSD) > From: Vsevolod Semenov > Subject: 4.0-RELEASE/tail/st_rdev > > I used "tail -F /var/log/local3" in my little shell script > to scan log for some string. > When i change release from 3.X to 4.0 > tail sometimes (may be once in a day or hours) > rescan log from begining and alarm me about problem > which has being occurred hours before. > > It was coz " sb2.st_rdev != sbp->st_rdev" > in /usr/src/usr.bin/tail/forward.c. > I've commented this out and became happy. > > > Q: Wtf is st_rdev in regular files in FreeBSD 4.0-RELEASE? > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Sun, 23 Jul 2000 16:21:48 +0200 > From: Thomas Klausner > Subject: Re: minherit(2) API > > Mutt made be believe that Jason R Thorpe wrote: > > DONATE_COPY is not implemented in UVM. I'm not sure it was ever > > implemented anywhere. "Copy and delete" is really "move", right? > > Anyway, it's not clear those semantics are really useful at all. > > Okay, so let's skip that one. > > Any other comments? > > I think I can change it in NetBSD -- anyone willing to do the > necessary changes in FreeBSD and OpenBSD? > > Bye, > Thomas > > - -- > Thomas Klausner - wiz@danbala.tuwien.ac.at > I wanted to emulate some of my heroes, but I didn't know their > op-codes. --dowe > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > End of freebsd-hackers-digest V4 #901 > ************************************* > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 23 13:30:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mercury.mich.com (mercury.mich.com [64.79.64.32]) by hub.freebsd.org (Postfix) with ESMTP id 48DCD37B7DC for ; Sun, 23 Jul 2000 13:30:13 -0700 (PDT) (envelope-from will@almanac.yi.org) Received: from argon.gryphonsoft.com (pm004-005.dialup.bignet.net [64.79.80.149]) by mercury.mich.com (8.9.3/8.9.3) with ESMTP id QAA16716; Sun, 23 Jul 2000 16:28:54 -0400 Received: by argon.gryphonsoft.com (Postfix, from userid 1000) id 8D308197E; Sun, 23 Jul 2000 16:27:21 -0400 (EDT) Date: Sun, 23 Jul 2000 16:27:21 -0400 From: Will Andrews To: hspio@worldnet.att.net Cc: hackers@FreeBSD.ORG Subject: Re: Remove Message-ID: <20000723162721.D47967@argon.gryphonsoft.com> References: <397B18A8.5713.3D69341@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <397B18A8.5713.3D69341@localhost>; from hspio@worldnet.att.net on Sun, Jul 23, 2000 at 04:09:12PM -0400 X-Operating-System: FreeBSD 5.0-CURRENT i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jul 23, 2000 at 04:09:12PM -0400, hspio@worldnet.att.net wrote: [.. 480 lines of spam snipped ..] Why don't you remove yourself and save everybody else the bandwidth, time, and money you just wasted by posting this cruft to this list?? -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 23 15:33:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id DF0E137BAA2; Sun, 23 Jul 2000 15:33:45 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e6NMXjj10639; Sun, 23 Jul 2000 15:33:45 -0700 (PDT) Date: Sun, 23 Jul 2000 15:33:45 -0700 From: Alfred Perlstein To: hackers@freebsd.org Cc: wollman@freebsd.org Subject: kern.ipc.maxsockbuf vs reality? Message-ID: <20000723153345.P13979@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have some code that does a sysctlbyname to pull in "kern.ipc.maxsockbuf", I then use that value to setsockopt the SNDBUF to that amount, but I get ENOBUFS back from the kernel. I think I'm failing here in uipc_socket2.c" line 432 in the function sbreserve(): if ((u_quad_t)cc > (u_quad_t)sb_max * MCLBYTES / (MSIZE + MCLBYTES)) return (0); I'm not sure why the sysctl seems to lie about it: u_long sb_max = SB_MAX; /* XXX should be static */ shouldn't it be: u_long sb_max = SB_MAX > (u_quad_t)SB_MAX * MCLBYTES / (MSIZE + MCLBYTES) ? (u_quad_t)SB_MAX * MCLBYTES / (MSIZE + MCLBYTES) : SB_MAX; ? Also, if sb_max is to remain a read/write sysctl we'll need to cap it so that kern.ipc.maxsockbuf is always true and we don't allow sysadmins to shoot thier feet by scaling it too high or low, the only problem is that I can't for the life of me figure out the magic to keep sb_max (kern.ipc.maxsockbuf) as a ulong (which it should be, instead of an int) as well as provide a filtering function. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 23 15:44:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-51.dsl.snfc21.pacbell.net [63.202.177.51]) by hub.freebsd.org (Postfix) with ESMTP id 8738437BB77 for ; Sun, 23 Jul 2000 15:44:09 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id PAA17665 for ; Sun, 23 Jul 2000 15:53:40 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200007232253.PAA17665@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: hackers@freebsd.org Subject: Driver for Adaptec/Dell/HP PCI:SCSI RAID adapters available Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 23 Jul 2000 15:53:40 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The first BETA version of the 'aac' driver for the Adaptec AAC-364 'Jalapeno' and AAC-3642 'Jalapeno II' RAID adapters is available from http://people.freebsd.org/~msmith/RAID/index.html#adaptec These adapters are OEMed by Dell as the PERC 2/QC and by HP as the HP NetRAID-4m. The driver has been tested on FreeBSD 5.0-CURRENT, but is known to build and should function just fine on 4.0-STABLE as well. Testers are encouraged to contact me for assistance, or to report on progress. Thanks go to BSDi for funding the development of this driver, and Adaptec for supplying me with a profusion of sample adapters and the source for their Linux driver to work from. Particular thanks to Justin Gibbs for finding the right person at Adaptec to make all this happen. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 23 16:19: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gateway.posi.net (c1096725-a.smateo1.sfba.home.com [24.20.139.104]) by hub.freebsd.org (Postfix) with ESMTP id 4C37B37B5C3; Sun, 23 Jul 2000 16:18:56 -0700 (PDT) (envelope-from kbyanc@posi.net) Received: from localhost (kbyanc@localhost) by gateway.posi.net (8.9.3/8.9.3) with ESMTP id QAA40238; Sun, 23 Jul 2000 16:23:51 -0700 (PDT) (envelope-from kbyanc@posi.net) Date: Sun, 23 Jul 2000 16:23:46 -0700 (PDT) From: Kelly Yancey To: Alfred Perlstein Cc: hackers@FreeBSD.ORG, wollman@FreeBSD.ORG Subject: Re: kern.ipc.maxsockbuf vs reality? In-Reply-To: <20000723153345.P13979@fw.wintelcom.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 23 Jul 2000, Alfred Perlstein wrote: > Also, if sb_max is to remain a read/write sysctl we'll need to cap > it so that kern.ipc.maxsockbuf is always true and we don't allow > sysadmins to shoot thier feet by scaling it too high or low, the > only problem is that I can't for the life of me figure out the > magic to keep sb_max (kern.ipc.maxsockbuf) as a ulong (which it > should be, instead of an int) as well as provide a filtering > function. > You'de have to use SYSCTL_PROC with a fmt of "LU". Just let the handler do the sanity checking on sysctl writes. Kelly -- Kelly Yancey - kbyanc@posi.net - Belmont, CA System Administrator, eGroups.com http://www.egroups.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSD http://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 23 16:24:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-51.dsl.snfc21.pacbell.net [63.202.177.51]) by hub.freebsd.org (Postfix) with ESMTP id 9F13C37BBD8 for ; Sun, 23 Jul 2000 16:24:12 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id QAA17925 for ; Sun, 23 Jul 2000 16:33:42 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200007232333.QAA17925@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: hackers@freebsd.org Subject: Re: Driver for Adaptec/Dell/HP PCI:SCSI RAID adapters available In-reply-to: Your message of "Sun, 23 Jul 2000 15:53:40 PDT." <200007232253.PAA17665@mass.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 23 Jul 2000 16:33:42 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The first BETA version of the 'aac' driver for the Adaptec AAC-364 > 'Jalapeno' and AAC-3642 'Jalapeno II' RAID adapters is available from > > http://people.freebsd.org/~msmith/RAID/index.html#adaptec > > These adapters are OEMed by Dell as the PERC 2/QC and by HP as the HP > NetRAID-4m. Just in case anyone's interested, these also show up in the surplus channel quite often; www.scsistuff.com has the AAC-364 (4-channel LVD) going for $549. (By contrast, when these were available from Adaptec they were around $850 or so.) -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 23 19: 6: 6 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id B8C9F37B8AD for ; Sun, 23 Jul 2000 19:06:03 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id WAA98542; Sun, 23 Jul 2000 22:06:01 -0400 (EDT) (envelope-from wollman) Date: Sun, 23 Jul 2000 22:06:01 -0400 (EDT) From: Garrett Wollman Message-Id: <200007240206.WAA98542@khavrinen.lcs.mit.edu> To: Alfred Perlstein Cc: hackers@freebsd.org Subject: kern.ipc.maxsockbuf vs reality? In-Reply-To: <20000723153345.P13979@fw.wintelcom.net> References: <20000723153345.P13979@fw.wintelcom.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > if ((u_quad_t)cc > (u_quad_t)sb_max * MCLBYTES / (MSIZE + MCLBYTES)) > return (0); I think the code here should clip the requested size into range rather than failing the allocation. That way, a program could just specify a ridiculously-large buffer size and get whatever is the configured maximum. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 23 20:43:53 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from camus.cybercable.fr (camus.cybercable.fr [212.198.0.200]) by hub.freebsd.org (Postfix) with SMTP id D888E37B8C6 for ; Sun, 23 Jul 2000 20:43:49 -0700 (PDT) (envelope-from clefevre@citeweb.net) Received: (qmail 1754492 invoked from network); 24 Jul 2000 03:43:48 -0000 Received: from r227m167.cybercable.tm.fr (HELO gits.dyndns.org) ([195.132.227.167]) (envelope-sender ) by camus.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 24 Jul 2000 03:43:48 -0000 Received: (from root@localhost) by gits.dyndns.org (8.9.3/8.9.3) id FAA23998; Mon, 24 Jul 2000 05:43:47 +0200 (CEST) (envelope-from clefevre@citeweb.net) To: alex@big.endian.de (Alexander Langer) Cc: bde@FreeBSD.ORG, phk@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: type of _BSD_TIME_T_ in machine/ansi.h References: <20000723205437.A10537@cichlids.cichlids.com> X-Face: V|+c;4!|B?E%BE^{E6);aI.[<97Zd*>^#%Y5Cxv;%Y[PT-LW3;A:fRrJ8+^k"e7@+30g0YD0*^^3jgyShN7o?a]C la*Zv'5NA,=963bM%J^o]C Reply-To: Cyrille Lefevre From: Cyrille Lefevre In-Reply-To: alex@big.endian.de's message of "Sun, 23 Jul 2000 20:54:37 +0200" Date: 24 Jul 2000 05:43:46 +0200 Message-ID: Lines: 20 User-Agent: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (Canyonlands) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG alex@big.endian.de (Alexander Langer) writes: > Currently, I see the following: > > root@parca /sys $ grep _BSD_TIME_T {alpha,i386}/include/ansi.h > alpha/include/ansi.h:#define _BSD_TIME_T_ int /* time() */ > i386/include/ansi.h:#define _BSD_TIME_T_ long /* time()... */ > > I wonder if we want to change that to __int32_t in both files? > > Additionally, I have the following patch, which is needed > at the moment to suppress warnings (on alpha): > [snip] did you send a PR ? man send-pr Cyrille. -- home: mailto:clefevre@citeweb.net work: mailto:Cyrille.Lefevre@edf.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 24 2: 3: 6 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from snafu.adept.org (adsl-63-201-63-44.dsl.snfc21.pacbell.net [63.201.63.44]) by hub.freebsd.org (Postfix) with ESMTP id 0180E37B5AC; Mon, 24 Jul 2000 02:02:55 -0700 (PDT) (envelope-from mike@adept.org) Received: by snafu.adept.org (Postfix, from userid 1000) id 2D0969EE01; Mon, 24 Jul 2000 02:02:36 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by snafu.adept.org (Postfix) with ESMTP id 24C989B001; Mon, 24 Jul 2000 02:02:36 -0700 (PDT) Date: Mon, 24 Jul 2000 02:02:36 -0700 (PDT) From: Mike Hoskins To: Mike Smith Cc: hackers@freebsd.org Subject: Re: Driver for Adaptec/Dell/HP PCI:SCSI RAID adapters available In-Reply-To: <200007232333.QAA17925@mass.osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 23 Jul 2000, Mike Smith wrote: > > These adapters are OEMed by Dell as the PERC 2/QC and by HP as the HP > > NetRAID-4m. FWIW, I've got a plethora of 2450's and 4350's at work... I think some have the PERC 3, but I'll check tomorrow... and grab any with the PERC 2 (or are the 2/3 models closely enough related to both be supported?). I'm definately up for some testing... Up to now, we've been using Linux on these with a Dell-provided, binary kernel module - ick (the PERC stuff isn't in Linux' standard RAID support)! Thanks for making my weekend. -mrh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 24 2:29:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-51.dsl.snfc21.pacbell.net [63.202.177.51]) by hub.freebsd.org (Postfix) with ESMTP id 0686137B796 for ; Mon, 24 Jul 2000 02:29:40 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id CAA21143; Mon, 24 Jul 2000 02:39:05 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200007240939.CAA21143@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Mike Hoskins Cc: hackers@freebsd.org Subject: Re: Driver for Adaptec/Dell/HP PCI:SCSI RAID adapters available In-reply-to: Your message of "Mon, 24 Jul 2000 02:02:36 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 24 Jul 2000 02:39:05 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sun, 23 Jul 2000, Mike Smith wrote: > > > > These adapters are OEMed by Dell as the PERC 2/QC and by HP as the HP > > > NetRAID-4m. > > FWIW, I've got a plethora of 2450's and 4350's at work... I think some > have the PERC 3, but I'll check tomorrow... and grab any with the PERC > 2 (or are the 2/3 models closely enough related to both be > supported?). I'm definately up for some testing... Up to now, we've been > using Linux on these with a Dell-provided, binary kernel module - ick (the > PERC stuff isn't in Linux' standard RAID support)! Ok, the deal is like this. There are two major PERC families; AMI-based and Adaptec-based. The AMI-based family constitutes the PERC, PERC 2/SC and PERC 2/DC. These are all supported by the 'amr' driver and probably aren't interesting to you. (Note that we seem to have firmware issues with the 2/DC at the moment.) The Adaptec-based family is divided into two sub-families; the StrongARM based controllers (PERC 2/QC) and the i960Rx based controllers (PERC 2/Si, PERC 3/Si, PERC 3/Di). I don't have any of the i960Rx-based controllers here to work with (yet, I have been promised some), so the driver currently only supports the StrongARM based controllers. They're easy to tell apart; the i960Rx controllers are the ones built into the motherboard (eg. on the PE2450), while the PERC 2/QC is a full-length PCI card with a large daughterboard. I don't know anything about the PE4350, so I don't know which controller it has. I know the 2400, 2450 and 4400 have the i960Rx-based models. The differences between these two families are quite small, and as soon as I can get my hands on an i960Rx-based controller I will make the requisite changes. I expect this won't take more than a couple of weeks. Keep in touch, thanks! -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 24 3:24:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mta6.snfc21.pbi.net (mta6.snfc21.pbi.net [206.13.28.240]) by hub.freebsd.org (Postfix) with ESMTP id 09BD537B55F for ; Mon, 24 Jul 2000 03:24:36 -0700 (PDT) (envelope-from jazepeda@pacbell.net) Received: from ppp-207-214-149-30.snrf01.pacbell.net ([207.214.149.30]) by mta6.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9) with ESMTP id <0FY7005QF684KV@mta6.snfc21.pbi.net> for hackers@freebsd.org; Mon, 24 Jul 2000 03:24:05 -0700 (PDT) Date: Mon, 24 Jul 2000 03:25:07 -0700 (PDT) From: Alex Zepeda Subject: ELF rtld and environment variables... X-Sender: alex@zippy.pacbell.net To: hackers@freebsd.org Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG So I find myself playing more and more with KDE, and more and more enjoying the nifty little hacks it does. But, most of the hacks depend on shlibs, including the requisite libtool horrors. Anyhow, one of the more "useful" features involves "pre-loading" a shared lib to replace a few X functions, so that once an application starts, you get an icon in the task bar that spins until the application maps its first window. Their other hack is for loading various applications contained in shared lib form, and involves setting LD_LIBRARY_PATH. This works great if you're using your average ELF binary. However, if you're like me and still somewhat attached to the idea of using Navigator which is an a.out binary (perhaps the only one I still have left), you're SOL as the variables tweak the a.out RTLD too. This perhaps doesn't sound too bad, until one realizes that the said shlib objets are ELF, and the a.out rtld doesn't grok any of them, meaning that one has to fire up an xterm, unset the said variables to start netscape. My question is this: is there any way to make the a.out rtld ignore these variables? 'Course after I figured this out, I realized I should have just used konqueror, and well I did (damn it's gonna give mozilla a run for its money... SSL equiped too). - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 24 7:35:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by hub.freebsd.org (Postfix) with ESMTP id 9AFCD37B619 for ; Mon, 24 Jul 2000 07:35:51 -0700 (PDT) (envelope-from andreasd@ifi.uio.no) Received: from tyrfing.ifi.uio.no (3034@tyrfing.ifi.uio.no [129.240.64.16]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id QAA10370 for ; Mon, 24 Jul 2000 16:35:48 +0200 (MET DST) Received: (from andreasd@localhost) by tyrfing.ifi.uio.no ; Mon, 24 Jul 2000 16:35:48 +0200 (MET DST) To: freebsd-hackers@freebsd.org Subject: Re: Funky scheduler stuff under heavy I/O. References: From: Andreas Dobloug X-Newsreader: Gnus v5.4.37/XEmacs 19.15 Date: 24 Jul 2000 16:35:48 +0200 In-Reply-To: Message-ID: Lines: 14 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Jaye Mathisen | 8 parallel DD's started at the same type creating 2GB cycbuffs (as fast as | & can put them in the background). (dd if=/dev/zero bs=1m count=2000 | of=blahblah) | | Any brilliant ideas? I've also experienced this on my scsi-drives (dual P2-350, adaptec2940u2w controller). When doing extensive writes, this always happens. The scan-rate (reported by vmstat) goes sky high, and the system becomes unresponsive. -- Andreas Dobloug : email: andreasd@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 24 8:13:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from shidahara1.planet.sci.kobe-u.ac.jp (shidahara1.planet.sci.kobe-u.ac.jp [133.30.50.200]) by hub.freebsd.org (Postfix) with ESMTP id BAD1537BAAB; Mon, 24 Jul 2000 08:13:00 -0700 (PDT) (envelope-from takawata@shidahara1.planet.sci.kobe-u.ac.jp) Received: from libr.scitec.kobe-u.ac.jp (aksh1031.ppp.infoweb.ne.jp [202.219.221.143]) by shidahara1.planet.sci.kobe-u.ac.jp (8.9.3/8.9.3) with ESMTP id AAA50788; Tue, 25 Jul 2000 00:13:07 +0900 (JST) (envelope-from takawata@shidahara1.planet.sci.kobe-u.ac.jp) Received: from shidahara1.planet.kobe-u.ac.jp (localhost [127.0.0.1]) by libr.scitec.kobe-u.ac.jp (8.9.1/3.5Wpl7) with ESMTP id AAA18428; Tue, 25 Jul 2000 00:05:34 +0900 (JST) From: takawata@shidahara1.planet.sci.kobe-u.ac.jp Message-Id: <200007241505.AAA18428@libr.scitec.kobe-u.ac.jp> To: jkh@FreeBSD.ORG Cc: hackers@FreeBSD.ORG, committers@FreeBSD.ORG, imp@FreeBSD.ORG, msmith@FreeBSD.ORG, dfr@FreeBSD.ORG, acpi-jp@jp.FreeBSD.ORG Subject: Device major number request for ACPI device. Date: Tue, 25 Jul 2000 00:05:33 +0900 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I want major number for ACPI device. I will use the device interface to enable/disable ACPI and access to switches defined in ACPI. Takanori Watanabe Public Key Key fingerprint = 2C 51 E2 78 2C E1 C5 2D 0F F1 20 A3 11 3A 62 2A To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 24 9: 6:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 360B837B5BB for ; Mon, 24 Jul 2000 09:06:35 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id JAA08765; Mon, 24 Jul 2000 09:06:14 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id JAA03633; Mon, 24 Jul 2000 09:06:13 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Mon, 24 Jul 2000 09:06:13 -0700 (PDT) Message-Id: <200007241606.JAA03633@vashon.polstra.com> To: hackers@freebsd.org Reply-To: hackers@freebsd.org Cc: jazepeda@pacbell.net Subject: Re: ELF rtld and environment variables... In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Alex Zepeda wrote: [LD_PRELOAD and LD_LIBRARY_PATH] > This works great if you're using your average ELF binary. However, if > you're like me and still somewhat attached to the idea of using Navigator > which is an a.out binary (perhaps the only one I still have left), you're > SOL as the variables tweak the a.out RTLD too. This perhaps doesn't sound > too bad, until one realizes that the said shlib objets are ELF, and the > a.out rtld doesn't grok any of them, meaning that one has to fire up an > xterm, unset the said variables to start netscape. > > My question is this: is there any way to make the a.out rtld ignore these > variables? No, there isn't. I don't plan to do anything more with the a.out dynamic linker, as I consider it obsolete at this point. I'd suggest making a script "run_aout" that looks something like this (untested): #! /bin/sh unset LD_PRELOAD unset LD_LIBRARY_PATH exec $0 "$@" BTW, it's generally not a good idea to set either of those environment variables globally. You should only set them in scripts which run specific executables that need them to be set. Besides the a.out problem, they affect programs run under Linux emulation too. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 24 10: 1: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id CA57C37B870; Mon, 24 Jul 2000 10:00:57 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id NAA45797; Mon, 24 Jul 2000 13:00:56 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Mon, 24 Jul 2000 13:00:56 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: freebsd-hackers@FreeBSD.org, freebsd-net@FreeBSD.org Subject: pass 2: Pittsburgh August IETF Meeting: FreeBSD dinner, et al? (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a resend of the original as we haven't picked up many people yet. Please reply to only appropriate addresses. :-) Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services ---------- Forwarded message ---------- Date: Fri, 14 Jul 2000 00:38:35 -0400 (EDT) From: Robert Watson To: freebsd-hackers@FreeBSD.org, freebsd-chat@FreeBSD.org Subject: Pittsburgh August IETF Meeting: FreeBSD dinner, et al? So it's coming up on that IETF time of year again, this time in beautiful (?) down-town Pittsburgh, in the first week of August. First, I'd like to encourage FreeBSD people to turn out for the event, as a strong showing in the standards community is great, and keeps the research projects coming to the platform (bring us things like industry-standard IP stacks). IETF meetings are a lot of fun, even if you don't have the technical background to participate fully. The hotels are filling fast, so book soon. Second, I'd like to bring up the topic of a FreeBSD dinner. We did one at the November IETF in DC with relatively good success, last year, although a reservation in advance is probably a good idea this time :-). With that in mind, I'd be glad to help organize things somewhat. The best day for me might actually be Monday evening, during the two-hour break, but I'm open to suggestions here if there are any serious BSD conflicts (i.e., a KAME meeting or something). If you're interested in participating, please feel free to send me an e-mail including: Your name Your preferred e-mail address Your preferred contact mechanism while at IETF (shout, for example, but preferably e-mail, or hotel information) Whether you would like to attend (obligatory: yes) Whether Monday would work for you or not, and if not, why Hope to see you all there! Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 24 10:10: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mercury.mich.com (mercury.mich.com [64.79.64.32]) by hub.freebsd.org (Postfix) with ESMTP id C4AEE37BB49 for ; Mon, 24 Jul 2000 10:09:48 -0700 (PDT) (envelope-from will@almanac.yi.org) Received: from argon.gryphonsoft.com (pm005-023.dialup.bignet.net [64.79.80.215]) by mercury.mich.com (8.9.3/8.9.3) with ESMTP id NAA02270; Mon, 24 Jul 2000 13:08:26 -0400 Received: by argon.gryphonsoft.com (Postfix, from userid 1000) id 9314619B1; Mon, 24 Jul 2000 13:06:53 -0400 (EDT) Date: Mon, 24 Jul 2000 13:06:53 -0400 From: Will Andrews To: Alex Zepeda Cc: hackers@FreeBSD.ORG Subject: Re: ELF rtld and environment variables... Message-ID: <20000724130653.B55929@argon.gryphonsoft.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from jazepeda@pacbell.net on Mon, Jul 24, 2000 at 03:25:07AM -0700 X-Operating-System: FreeBSD 5.0-CURRENT i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 24, 2000 at 03:25:07AM -0700, Alex Zepeda wrote: > you're like me and still somewhat attached to the idea of using Navigator > which is an a.out binary (perhaps the only one I still have left), you're Use the BSDI Netscape ports, which are ELF and don't require any emulation. They are also fast and seldom crash. IMNSHO, the FreeBSD Netscape ports should be axed if Netscape won't ever make ELF binaries. -- Will Andrews GCS/E/S @d- s+:+ a--- C++ UB++++$ P+ L- E--- W+ N-- !o ?K w--- O- M+ V- PS+ PE++ Y+ PGP+>+++ t++ 5 X+ R+ tv+ b++ DI+++ D+ G++ e>++++ h! r- y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 24 10:39:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from houston.matchlogic.com (houston.matchlogic.com [205.216.147.127]) by hub.freebsd.org (Postfix) with ESMTP id DC74137B869 for ; Mon, 24 Jul 2000 10:39:09 -0700 (PDT) (envelope-from crandall@matchlogic.com) Received: by houston.matchlogic.com with Internet Mail Service (5.5.2650.21) id ; Mon, 24 Jul 2000 11:39:01 -0600 Message-ID: <5FE9B713CCCDD311A03400508B8B301301C7846C@bdr-xcln.is.matchlogic.com> From: Charles Randall To: freebsd-hackers@freebsd.org Subject: RE: Funky scheduler stuff under heavy I/O. Date: Mon, 24 Jul 2000 11:38:58 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Could it be a boundary condition when the PCI bus gets saturated? Charles -----Original Message----- From: Andreas Dobloug [mailto:andreasd@ifi.uio.no] Sent: Monday, July 24, 2000 8:36 AM To: freebsd-hackers@freebsd.org Subject: Re: Funky scheduler stuff under heavy I/O. * Jaye Mathisen | 8 parallel DD's started at the same type creating 2GB cycbuffs (as fast as | & can put them in the background). (dd if=/dev/zero bs=1m count=2000 | of=blahblah) | | Any brilliant ideas? I've also experienced this on my scsi-drives (dual P2-350, adaptec2940u2w controller). When doing extensive writes, this always happens. The scan-rate (reported by vmstat) goes sky high, and the system becomes unresponsive. -- Andreas Dobloug : email: andreasd@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 24 11:15:47 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (Postfix) with ESMTP id 4F87D37BC61; Mon, 24 Jul 2000 11:15:33 -0700 (PDT) (envelope-from alc@cs.rice.edu) Received: (from alc@localhost) by cs.rice.edu (8.9.0/8.9.0) id NAA01939; Mon, 24 Jul 2000 13:15:27 -0500 (CDT) Date: Mon, 24 Jul 2000 13:15:27 -0500 From: Alan Cox To: Thomas Klausner Cc: freebsd-arch@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: minherit(2) API Message-ID: <20000724131527.A6681@cs.rice.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5us Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I think I can change it in NetBSD -- anyone willing to do the > necessary changes in FreeBSD and OpenBSD? I'll do it. Alan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 24 11:26:28 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by hub.freebsd.org (Postfix) with ESMTP id 1DDF337BBBE for ; Mon, 24 Jul 2000 11:26:19 -0700 (PDT) (envelope-from larse@ISI.EDU) Received: from isi.edu (hbo.isi.edu [128.9.160.75]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id LAA24649; Mon, 24 Jul 2000 11:26:10 -0700 (PDT) Message-ID: <397C8A42.BF52CC4D@isi.edu> Date: Mon, 24 Jul 2000 11:26:10 -0700 From: Lars Eggert Organization: USC Information Sciences Institute X-Mailer: Mozilla 4.73 [en] (X11; I; FreeBSD 4.1-RC i386) X-Accept-Language: en, de MIME-Version: 1.0 To: Matt Dillon Cc: Alan Cox , hackers@FreeBSD.ORG, cort@cs.nmt.edu Subject: Re: clearing pages in the idle loop References: <20000719234124.H14543@cs.rice.edu> <39788E48.60F8A59F@isi.edu> <200007211906.MAA19989@earth.backplane.com> <3978A802.E05CC45@isi.edu> <200007221739.KAA31376@earth.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matt Dillon wrote: > > :> Since the only effect of a cache miss is less efficient use of > :> the cpu, and since the page zeroing only occurs when the cpu is idle, > :> I would not expect to see much improvement from attempts to refine > :> the page-zeroing operation (beyond the simple hysteresis that FreeBSD > :> uses now and perhaps being able to bypass the cache). > : > :The reason why I'm interested in Cort's results is that I'd like to extend > :processing in the idle loop to other things (see my other mail). Cort > :measured a performance decrease of foreground processing, due to polluted > :caches after idle-time processing. We're discussing if disabling caches > :during the idle loop may prevent that. > > I think what you are observing may not be cache-related at all, but may > simply be the fact that zeroing a page takes a minimum amount of time > during which another task will not be scheduled, verses that other task > being scheduled instantly if all the idle loop were doing was checking > for new tasks to run. The way Cort implemented it in Linux was so that there's a check for new processes in the loop that clears a page. This is of course slowing it, but since it's idle time processing, reduction of latency to start a new process (and being transparent to foreground processing in general) is much more important than optimized execution. This is also why turning off L1 and L2 caches may be interesting - if one process blocks, you do some idle time processing and it unblocks, the L1 and L2 cache may be polluted by the idle time processing, slowing things down for the foreground process. > Another alternative is to have an idle process rather then try to do > things in the idle loop. This has the advantage of being instantly > interruptable if a 'real' process becomes runnable, but the disadvantage > of having to do a context switch (albeit a relatively cheap one). That would probably be the cleanest solution. Maybe the idprio mechanism could be extended to cover this. -- Lars Eggert Information Sciences Institute http://www.isi.edu/larse/ University of Southern California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 24 12: 1:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 733A537BF4F; Mon, 24 Jul 2000 12:00:55 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id VAA06839; Mon, 24 Jul 2000 21:00:40 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: takawata@shidahara1.planet.sci.kobe-u.ac.jp Cc: jkh@FreeBSD.ORG, hackers@FreeBSD.ORG, committers@FreeBSD.ORG, imp@FreeBSD.ORG, msmith@FreeBSD.ORG, dfr@FreeBSD.ORG, acpi-jp@jp.FreeBSD.ORG Subject: Re: Device major number request for ACPI device. In-reply-to: Your message of "Tue, 25 Jul 2000 00:05:33 +0900." <200007241505.AAA18428@libr.scitec.kobe-u.ac.jp> Date: Mon, 24 Jul 2000 21:00:40 +0200 Message-ID: <6837.964465240@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200007241505.AAA18428@libr.scitec.kobe-u.ac.jp>, takawata@shidahara 1.planet.sci.kobe-u.ac.jp writes: >Hi, I want major number for ACPI device. >I will use the device interface to enable/disable ACPI and access to >switches defined in ACPI. I have allocated major 152 for ACPI. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 24 12:19:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 835E337BC28; Mon, 24 Jul 2000 12:19:12 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id NAA21645; Mon, 24 Jul 2000 13:19:02 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id NAA81885; Mon, 24 Jul 2000 13:18:45 -0600 (MDT) Message-Id: <200007241918.NAA81885@harmony.village.org> To: Poul-Henning Kamp Subject: Re: Device major number request for ACPI device. Cc: takawata@shidahara1.planet.sci.kobe-u.ac.jp, jkh@FreeBSD.ORG, hackers@FreeBSD.ORG, committers@FreeBSD.ORG, msmith@FreeBSD.ORG, dfr@FreeBSD.ORG, acpi-jp@jp.FreeBSD.ORG In-reply-to: Your message of "Mon, 24 Jul 2000 21:00:40 +0200." <6837.964465240@critter.freebsd.dk> References: <6837.964465240@critter.freebsd.dk> Date: Mon, 24 Jul 2000 13:18:45 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <6837.964465240@critter.freebsd.dk> Poul-Henning Kamp writes: : I have allocated major 152 for ACPI. Just a quick note. Projects like this can have any committer allocate the major number. Since watanabe-san is a commiter, I had sent mail to him saying this just before phk's commit. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 24 12:25:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from quack.kfu.com (quack.kfu.com [205.178.90.194]) by hub.freebsd.org (Postfix) with ESMTP id 6A51737B62A; Mon, 24 Jul 2000 12:25:09 -0700 (PDT) (envelope-from nsayer@quack.kfu.com) Received: (from nsayer@localhost) by quack.kfu.com (8.9.3/8.9.3) id MAA01002; Mon, 24 Jul 2000 12:25:09 -0700 (PDT) (envelope-from nsayer) Date: Mon, 24 Jul 2000 12:25:09 -0700 (PDT) From: Nick Sayer Message-Id: <200007241925.MAA01002@quack.kfu.com> To: freebsd-hackers@freebsd.org Subject: Problems with 6-in-4 tunnels in 4.1-RC? Cc: freebsd-stable@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My -stable machine just turned deaf on its gif0 interface. I can see the encapsulated packets coming in and out and they look correct... 12:18:25.138253 205.178.90.194 > 204.123.2.236: 3ffe:1200:301b::1 > 3ffe:1001:1:f001::2: icmp6: echo request (encap) 12:18:25.191209 204.123.2.236 > 205.178.90.194: 3ffe:1001:1:f001::2 > 3ffe:1200:301b::1: icmp6: echo reply (encap) but the replies never make it into gif0, so far as I can see. /etc/rc.conf has: ipv6_enable="YES" ipv6_network_interfaces="lo0 de0" ipv6_prefix_de0="3ffe:1200:301b:0" ipv6_gateway_enable="YES" ipv6_static_routes="default" ipv6_route_default="default -interface gif0" ipv6_router_enable="YES" gif_interfaces="gif0" gifconfig_gif0="205.178.90.194 204.123.2.236" What happened? :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 24 14:56:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 2567937B8C3; Mon, 24 Jul 2000 14:56:36 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id OAA12810; Mon, 24 Jul 2000 14:56:36 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Mon, 24 Jul 2000 14:56:36 -0700 (PDT) From: Kris Kennaway To: Nick Sayer Cc: freebsd-hackers@freebsd.org Subject: Re: Problems with 6-in-4 tunnels in 4.1-RC? In-Reply-To: <200007241925.MAA01002@quack.kfu.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 24 Jul 2000, Nick Sayer wrote: > My -stable machine just turned deaf on its gif0 interface. > I can see the encapsulated packets coming in and out and they > look correct... Hmm. It works fine for me. Can you show me your routing table? Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 24 15:12:28 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mta6.snfc21.pbi.net (mta6.snfc21.pbi.net [206.13.28.240]) by hub.freebsd.org (Postfix) with ESMTP id 3E41237BCF6 for ; Mon, 24 Jul 2000 15:12:24 -0700 (PDT) (envelope-from jazepeda@pacbell.net) Received: from ppp-207-214-149-126.snrf01.pacbell.net ([207.214.149.126]) by mta6.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9) with ESMTP id <0FY800EC42Q9TQ@mta6.snfc21.pbi.net> for hackers@freebsd.org; Mon, 24 Jul 2000 15:06:11 -0700 (PDT) Date: Mon, 24 Jul 2000 15:07:12 -0700 (PDT) From: Alex Zepeda Subject: Re: ELF rtld and environment variables... In-reply-to: <200007241606.JAA03633@vashon.polstra.com> X-Sender: alex@zippy.pacbell.net To: hackers@freebsd.org Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 24 Jul 2000, John Polstra wrote: > No, there isn't. I don't plan to do anything more with the a.out > dynamic linker, as I consider it obsolete at this point. I'd > suggest making a script "run_aout" that looks something like this > (untested): Uck. > BTW, it's generally not a good idea to set either of those environment > variables globally. You should only set them in scripts which run > specific executables that need them to be set. Besides the a.out > problem, they affect programs run under Linux emulation too. Yes, but this is intended to be used for all programs (not an awful idea IMO, questionable implementation, but what other alternatives are there?). It's designed to give the user feedback that an application has been started so one doesn't double click on an icon multiple times. I'm curious, why do a.out/FreeBSD-elf/Linux-elf programs all respond to the same variables? Sure it's perhaps a consistant interface, but wouldn't somthing like LINUX_LD_LIBRARY_PATH and/or AOUT_LD_LIBRARY_PATH make more sense? - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 24 18:23:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id B30D737B7D2 for ; Mon, 24 Jul 2000 18:23:53 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id SAA11608; Mon, 24 Jul 2000 18:23:23 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id SAA04929; Mon, 24 Jul 2000 18:23:22 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Mon, 24 Jul 2000 18:23:22 -0700 (PDT) Message-Id: <200007250123.SAA04929@vashon.polstra.com> To: hackers@freebsd.org Reply-To: hackers@freebsd.org Cc: jazepeda@pacbell.net Subject: Re: ELF rtld and environment variables... In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Alex Zepeda wrote: > > Uck. Glad you liked the idea! :-) > I'm curious, why do a.out/FreeBSD-elf/Linux-elf programs all respond to > the same variables? Sure it's perhaps a consistant interface, but > wouldn't somthing like LINUX_LD_LIBRARY_PATH and/or AOUT_LD_LIBRARY_PATH > make more sense? Well, there is a different reason for each of the dynamic linkers. FreeBSD ELF: It's required by the ELF specification. FreeBSD a.out: Backward compatibility. Linux ELF: Because it's part of Linux and that's just what it does. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 24 22:34:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from beastie.mckusick.com (beastie.mckusick.com [209.31.233.184]) by hub.freebsd.org (Postfix) with ESMTP id 7B73337BA06 for ; Mon, 24 Jul 2000 22:34:41 -0700 (PDT) (envelope-from mckusick@mckusick.com) Received: from beastie.mckusick.com (localhost [127.0.0.1]) by beastie.mckusick.com (8.9.3/8.9.3) with ESMTP id WAA12006; Mon, 24 Jul 2000 22:34:39 -0700 (PDT) (envelope-from mckusick@beastie.mckusick.com) Message-Id: <200007250534.WAA12006@beastie.mckusick.com> To: Sheldon Hearn Subject: Re: Where is the syncer kernel process implemented? Cc: hackers@FreeBSD.ORG In-Reply-To: Your message of "Fri, 14 Jul 2000 14:51:13 +0200." <66769.963579073@axl.ops.uunet.co.za> Date: Mon, 24 Jul 2000 22:34:39 -0700 From: Kirk McKusick Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Sheldon Hearn To: Alfred Perlstein Cc: hackers@FreeBSD.ORG, mckusick@FreeBSD.ORG Subject: Re: Where is the syncer kernel process implemented? In-reply-to: Your message of "Fri, 14 Jul 2000 05:38:58 MST." <20000714053858.L25571@fw.wintelcom.net> Date: Fri, 14 Jul 2000 14:51:13 +0200 Sender: Sheldon Hearn On Fri, 14 Jul 2000 05:38:58 MST, Alfred Perlstein wrote: > /* > * System filesystem synchronizer daemon. > */ > void > sched_sync(void) It seems that the default sync delay, syncer_maxdelay, is no longer controllable via sysctl(8). Are there complex issues restricting the changing of this value in real time, or is it just not something people feel the need to change these days? Ciao, Sheldon. The value of syncer_maxdelay was never settable, as it is used to set the size of the array used to hold the timing events. It was formerly possible to set syncdelay, but that variable was replaced by three variables: time_t filedelay = 30; /* time to delay syncing files */ time_t dirdelay = 29; /* time to delay syncing directories */ time_t metadelay = 28; /* time to delay syncing metadata */ Each of these variables is individually setable. Kirk McKusick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 24 23:39:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.butya.kz (butya-gw.butya.kz [212.154.129.94]) by hub.freebsd.org (Postfix) with ESMTP id 24C7637BA86 for ; Mon, 24 Jul 2000 23:39:13 -0700 (PDT) (envelope-from bp@butya.kz) Received: by relay.butya.kz (Postfix, from userid 1000) id 9132628CF9; Tue, 25 Jul 2000 13:39:05 +0700 (ALMST) Received: from localhost (localhost [127.0.0.1]) by relay.butya.kz (Postfix) with ESMTP id 8551A28CF8 for ; Tue, 25 Jul 2000 13:39:05 +0700 (ALMST) Date: Tue, 25 Jul 2000 13:39:05 +0700 (ALMST) From: Boris Popov To: freebsd-hackers@freebsd.org Subject: NetBIOS name resolver for smbfs Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, At first, I would like to say thanks for everybody who take a time to perform initial testing of smbfs and providing me with feedback. To make this implementation more complete I've added an initial version of NetBIOS name resolver, so the '-I host' flag can be omitted. Please note, that the network with Win9X machines only will require WINS server. An updated version can be downloaded from ftp://ftp.butya.kz/pub/smbfs/smbfs.tar.gz -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 24 23:48: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mta5.snfc21.pbi.net (mta5.snfc21.pbi.net [206.13.28.241]) by hub.freebsd.org (Postfix) with ESMTP id A476D37BAC1 for ; Mon, 24 Jul 2000 23:47:55 -0700 (PDT) (envelope-from jazepeda@pacbell.net) Received: from ppp-207-214-149-234.snrf01.pacbell.net ([207.214.149.234]) by mta5.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9) with ESMTP id <0FY80042UQQ1UG@mta5.snfc21.pbi.net> for hackers@freebsd.org; Mon, 24 Jul 2000 23:44:26 -0700 (PDT) Date: Mon, 24 Jul 2000 23:45:45 -0700 (PDT) From: Alex Zepeda Subject: Re: ELF rtld and environment variables... In-reply-to: <200007250123.SAA04929@vashon.polstra.com> X-Sender: alex@zippy.pacbell.net To: hackers@freebsd.org Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 24 Jul 2000, John Polstra wrote: > Glad you liked the idea! :-) Well imagine if Joe user gets a Linux binary or a.out binary to run. Bam, it doesn't run, and one'd have to check each file, and unset the variables. Or forgo any user-feedback. :( > Well, there is a different reason for each of the dynamic linkers. > > FreeBSD ELF: It's required by the ELF specification. > > FreeBSD a.out: Backward compatibility. > > Linux ELF: Because it's part of Linux and that's just what it does. I can understand the logic for using said variables for FreeBSD ELF stuff, but for the rest of them, I figure we're not actually the native environment. Hmm. Anywho the topic of caching shlib symbols came up in discussion as a possible way speed up loading of programs. Makes me wonder if it would be worth it.. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 25 0:59:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.ops.uunet.co.za (axl.ops.uunet.co.za [196.31.2.163]) by hub.freebsd.org (Postfix) with ESMTP id 2F6A137BAB0 for ; Tue, 25 Jul 2000 00:59:09 -0700 (PDT) (envelope-from sheldonh@axl.ops.uunet.co.za) Received: from sheldonh (helo=axl.ops.uunet.co.za) by axl.ops.uunet.co.za with local-esmtp (Exim 3.15 #1) id 13Gzc9-0000Lt-00; Tue, 25 Jul 2000 09:58:57 +0200 From: Sheldon Hearn To: Kirk McKusick Cc: hackers@FreeBSD.ORG Subject: Re: Where is the syncer kernel process implemented? In-reply-to: Your message of "Mon, 24 Jul 2000 22:34:39 MST." <200007250534.WAA12006@beastie.mckusick.com> Date: Tue, 25 Jul 2000 09:58:57 +0200 Message-ID: <1356.964511937@axl.ops.uunet.co.za> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 24 Jul 2000 22:34:39 MST, Kirk McKusick wrote: > time_t filedelay = 30; /* time to delay syncing files */ > time_t dirdelay = 29; /* time to delay syncing directories */ > time_t metadelay = 28; /* time to delay syncing metadata */ > > Each of these variables is individually setable. These are maximum offsets from the current queue offset (syncer_delayno) at which new vnode entries may be inserted. That means they can be changed arbitrarily without fear of "orphaned" slots, right? Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 25 5:43:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from zippy.osd.bsdi.com (zippy.osd.bsdi.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 7A69937BDBA for ; Tue, 25 Jul 2000 05:43:38 -0700 (PDT) (envelope-from jkh@zippy.osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by zippy.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id FAA07668 for ; Tue, 25 Jul 2000 05:43:40 -0700 (PDT) (envelope-from jkh@zippy.osd.bsdi.com) Date: Tue, 25 Jul 2000 05:43:39 -0700 Message-ID: <7661.964529019.1@localhost> From: "Jordan K. Hubbard" Subject: 4.1-RELEASE will be tagged and done tonite, starting at 18:00 PDT MIME-Version: 1.0 Content-Type: multipart/digest; boundary="----- =_aaaaaaaaaa" Content-Description: Blind Carbon Copy Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ------- =_aaaaaaaaaa Content-Type: message/rfc822 Content-Description: Original Message To: stable@freebsd.org Subject: 4.1-RELEASE will be tagged and done tonite, starting at 18:00 PDT Date: Tue, 25 Jul 2000 05:43:39 -0700 Message-ID: <7661.964529019@localhost> From: "Jordan K. Hubbard" MIME-Version: 1.0 Just a heads-up to say that the last few issues have been dealt with and it looks like we're on target for a July 25th, 18:00 PDT (Pacific Daylight Time) tag and (as soon as that's finished) release operation. I'll be putting the i386 and alpha bits together throughout the night and will be shooting for some FTPable / ISO image bits on ftp.freebsd.org by early morning (the 26th). Thanks for all the hard work people have put into getting many important changes merged into 4.1! We may not have gotten every last minute cosmetic or semi-experimental hack into this release, but then that's not really the objective, either. :-) I'd say 4.1 looks like a good one. - Jordan ------- =_aaaaaaaaaa-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 25 9:21:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 0BF3B37B5CD for ; Tue, 25 Jul 2000 09:21:31 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e6PGLMg11539; Tue, 25 Jul 2000 09:21:22 -0700 (PDT) Date: Tue, 25 Jul 2000 09:21:21 -0700 From: Alfred Perlstein To: Sheldon Hearn Cc: Kirk McKusick , hackers@FreeBSD.ORG Subject: Re: Where is the syncer kernel process implemented? Message-ID: <20000725092121.K13979@fw.wintelcom.net> References: <200007250534.WAA12006@beastie.mckusick.com> <1356.964511937@axl.ops.uunet.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <1356.964511937@axl.ops.uunet.co.za>; from sheldonh@uunet.co.za on Tue, Jul 25, 2000 at 09:58:57AM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Sheldon Hearn [000725 00:59] wrote: > > > On Mon, 24 Jul 2000 22:34:39 MST, Kirk McKusick wrote: > > > time_t filedelay = 30; /* time to delay syncing files */ > > time_t dirdelay = 29; /* time to delay syncing directories */ > > time_t metadelay = 28; /* time to delay syncing metadata */ > > > > Each of these variables is individually setable. > > These are maximum offsets from the current queue offset (syncer_delayno) > at which new vnode entries may be inserted. That means they can > be changed arbitrarily without fear of "orphaned" slots, right? If you mean "they can be changed without fear of loosing vnodes" then the answer is "yes", the problem is that if you bump any of these guys past 30 without fixing the #define SYNCER_MAXDELAY above them they'll still be truncated to SYNCER_MAXDELAY because vn_syncer_add_to_worklist() clips it like so: if (delay > syncer_maxdelay - 2) delay = syncer_maxdelay - 2; (clip to SYNCER_MAXDELAY-2) -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 25 10:11: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id CA5A137B6ED for ; Tue, 25 Jul 2000 10:10:58 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id KAA15521; Tue, 25 Jul 2000 10:10:53 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id KAA07319; Tue, 25 Jul 2000 10:10:52 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Tue, 25 Jul 2000 10:10:52 -0700 (PDT) Message-Id: <200007251710.KAA07319@vashon.polstra.com> To: hackers@freebsd.org Reply-To: hackers@freebsd.org Cc: jazepeda@pacbell.net Subject: Re: ELF rtld and environment variables... In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Alex Zepeda wrote: > On Mon, 24 Jul 2000, John Polstra wrote: > > > FreeBSD ELF: It's required by the ELF specification. > > > > FreeBSD a.out: Backward compatibility. > > > > Linux ELF: Because it's part of Linux and that's just what it does. > > I can understand the logic for using said variables for FreeBSD ELF stuff, > but for the rest of them, I figure we're not actually the native > environment. Hmm. That's why we can't change the current behavior. The Linux RTLD is a 3rd party program. We didn't write it, and we don't maintain it. And I'm not about to break backward compatibility in the a.out RTLD. > Anywho the topic of caching shlib symbols came up in discussion as > a possible way speed up loading of programs. Makes me wonder if it > would be worth it.. The only way to find out would be to take some measurements. But where were you thinking of caching these symbols? You can't do it in the RTLD's address space because the RTLD isn't persistent. You get a new instance of it every time you run a program. And if you want to cache the symbols in a file, well, we already have that -- it's called the shared library's symbol table. I really don't see any potential for gains from this. Besides, have you even established that dynamically linked programs load too slowly? I've certainly never heard any complaints along those lines. Furthermore I would bet that the bulk of the dynamic linking time comes from opening the shared libraries and mmapping them, and there's nothing the RTLD can do about that. John, who spent weeks instrumenting and measuring the a.out RTLD years ago. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 25 10:16:47 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66]) by hub.freebsd.org (Postfix) with ESMTP id 5F2C737B6DD for ; Tue, 25 Jul 2000 10:16:38 -0700 (PDT) (envelope-from nate@yogotech.com) Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.123.131]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id LAA29609; Tue, 25 Jul 2000 11:16:09 -0600 (MDT) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id LAA06040; Tue, 25 Jul 2000 11:16:05 -0600 (MDT) (envelope-from nate) Date: Tue, 25 Jul 2000 11:16:05 -0600 (MDT) Message-Id: <200007251716.LAA06040@nomad.yogotech.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: hackers@FreeBSD.ORG Cc: jazepeda@pacbell.net Subject: Re: ELF rtld and environment variables... In-Reply-To: <200007251710.KAA07319@vashon.polstra.com> References: <200007251710.KAA07319@vashon.polstra.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Besides, have you even established that dynamically linked programs > load too slowly? I've certainly never heard any complaints along > those lines. Furthermore I would bet that the bulk of the dynamic > linking time comes from opening the shared libraries and mmapping > them, and there's nothing the RTLD can do about that. > > John, who spent weeks instrumenting and measuring the a.out RTLD years ago. And optimized it greatly after these weeks, in one of his first projects in FreeBSD. :) :) :) Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 25 10:56:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hq.fsmlabs.com (hq.fsmlabs.com [209.155.42.197]) by hub.freebsd.org (Postfix) with ESMTP id 8CD3F37B7AA for ; Tue, 25 Jul 2000 10:56:09 -0700 (PDT) (envelope-from cort@medea.fsmlabs.com) Received: from medea.fsmlabs.com (medea.fsmlabs.com [209.155.42.137]) by hq.fsmlabs.com (8.9.3/8.9.3) with ESMTP id LAA02576; Tue, 25 Jul 2000 11:55:37 -0600 Received: (from cort@localhost) by medea.fsmlabs.com (8.9.3/8.9.3) id LAA24619; Tue, 25 Jul 2000 11:48:00 -0600 Date: Tue, 25 Jul 2000 11:48:00 -0600 From: cort@fsmlabs.com To: Lars Eggert Cc: Matt Dillon , Alan Cox , hackers@FreeBSD.ORG Subject: Re: clearing pages in the idle loop Message-ID: <20000725114800.M15614@medea.fsmlabs.com> References: <20000719234124.H14543@cs.rice.edu> <39788E48.60F8A59F@isi.edu> <200007211906.MAA19989@earth.backplane.com> <3978A802.E05CC45@isi.edu> <200007221739.KAA31376@earth.backplane.com> <397C8A42.BF52CC4D@isi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1us In-Reply-To: <397C8A42.BF52CC4D@isi.edu>; from larse@ISI.EDU on Mon, Jul 24, 2000 at 11:26:10AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Right, that was the plan with that code. In fact, I saw some improvement in performance when turning the caches off when in the idle task no matter what we were doing in it. It seems that it kept us out of the cache so we didn't evict the working-set of block processes. } The way Cort implemented it in Linux was so that there's a check for new } processes in the loop that clears a page. This is of course slowing it, but } since it's idle time processing, reduction of latency to start a new } process (and being transparent to foreground processing in general) is much } more important than optimized execution. } } This is also why turning off L1 and L2 caches may be interesting - if one } process blocks, you do some idle time processing and it unblocks, the L1 } and L2 cache may be polluted by the idle time processing, slowing things } down for the foreground process. I play with that idea, having a task with the priority set just higher than the idle loop. It let us keep the idle loop unpolluted and allowed it to actually be nothing more than an idle loop. It was nice to be able to dynamically assign priority to PPC hash table clearing, page clearing and any other wacky idea I came up with depending on the load and need of the running system. } > Another alternative is to have an idle process rather then try to do } > things in the idle loop. This has the advantage of being instantly } > interruptable if a 'real' process becomes runnable, but the disadvantage } > of having to do a context switch (albeit a relatively cheap one). } } That would probably be the cleanest solution. Maybe the idprio mechanism } could be extended to cover this. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 25 12:39:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (f194.law7.hotmail.com [216.33.237.194]) by hub.freebsd.org (Postfix) with SMTP id AE4C537B927 for ; Tue, 25 Jul 2000 12:39:17 -0700 (PDT) (envelope-from johnnyteardrop@hotmail.com) Received: (qmail 37722 invoked by uid 0); 25 Jul 2000 19:39:16 -0000 Message-ID: <20000725193916.37721.qmail@hotmail.com> Received: from 209.249.186.215 by www.hotmail.com with HTTP; Tue, 25 Jul 2000 12:39:16 PDT X-Originating-IP: [209.249.186.215] From: "Greg Thompson" To: freebsd-hackers@freebsd.org Subject: odd accept(2) behavior Date: Tue, 25 Jul 2000 15:39:16 EDT Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hackers, i'm seeing some fairly odd behavior from accept(2) when the connecting socket goes away at just the right time. the timing is fairly funky, so i don't know if i can easily whip up a repro for this, but what i'm seeing is: accept returns a positive value (ie: not an error), but sets the addrlen to zero. a subsequent call to getsockname with the new socket returns -1 and sets errno to ECONNRESET. is this the expected behavior? can someone explain? i haven't observed this on any other platforms i've been hacking lately. thanks. -- -greg ________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 25 13:30:13 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mimer.webgiro.com (mimer.webgiro.com [212.209.29.5]) by hub.freebsd.org (Postfix) with ESMTP id 759EB37B896 for ; Tue, 25 Jul 2000 13:30:09 -0700 (PDT) (envelope-from abial@webgiro.com) Received: by mimer.webgiro.com (Postfix, from userid 66) id 6AE622DC0A; Tue, 25 Jul 2000 22:35:17 +0200 (CEST) Received: by mx.webgiro.com (Postfix, from userid 1001) id 7E9727817; Tue, 25 Jul 2000 22:26:53 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mx.webgiro.com (Postfix) with ESMTP id 7937E10E17; Tue, 25 Jul 2000 22:26:53 +0200 (CEST) Date: Tue, 25 Jul 2000 22:26:51 +0200 (CEST) From: Andrzej Bialecki To: Daniel O'Connor Cc: Raymond Wiker , freebsd-hackers@freebsd.org Subject: RE: dlopen() and friends from a statically-linked binary? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 22 Jul 2000, Daniel O'Connor wrote: > > On 20-Jul-00 Raymond Wiker wrote: > > Is it possible, at all, to use dlopen etc from a > > statically-linked executable? My experiments with FreeBSD-4.0 (see > > below) indicate that it's not possible. > > You can't do it from a statically linked binary, however you can create a > dynamic executable with no external unresolved references.. I forget how though > :-/ The same way it's done with the kernel nowadays.. Look into your /sys/compile/WHATEVER/Makefile, and hack.c file there. Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 25 14: 9: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id 7C87837B95C for ; Tue, 25 Jul 2000 14:08:56 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.3/8.9.3) id OAA13311; Tue, 25 Jul 2000 14:08:54 -0700 (PDT) (envelope-from archie) From: Archie Cobbs Message-Id: <200007252108.OAA13311@bubba.whistle.com> Subject: Re: odd accept(2) behavior In-Reply-To: <20000725193916.37721.qmail@hotmail.com> from Greg Thompson at "Jul 25, 2000 03:39:16 pm" To: Greg Thompson Date: Tue, 25 Jul 2000 14:08:54 -0700 (PDT) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Thompson writes: > i'm seeing some fairly odd behavior from accept(2) when the connecting > socket goes away at just the right time. the timing is fairly funky, so i > don't know if i can easily whip up a repro for this, but what i'm seeing is: > > accept returns a positive value (ie: not an error), but sets the addrlen to > zero. a subsequent call to getsockname with the new socket returns -1 and > sets errno to ECONNRESET. Everything sounds normal/expected except the part about addrlen being set to zero. That sounds like a bug. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 25 15:30:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id DD88D37BA0A; Tue, 25 Jul 2000 15:30:26 -0700 (PDT) (envelope-from erik@whistle.com) Received: from whistle.com (erik.whistle.com [207.76.205.71]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id PAA36108; Tue, 25 Jul 2000 15:28:16 -0700 (PDT) Message-ID: <397E147E.7487B761@whistle.com> Date: Tue, 25 Jul 2000 15:28:14 -0700 From: Erik Salander X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: hackers@FreeBSD.ORG Cc: Brian Somers , Junichi Satoh , Ruslan Ermilov , archie@whistle.com Subject: Re: RealSystem module for libalias References: <200006160751.IAA01536@hak.lan.Awfulhak.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here's the latest patch for the aliasing of the RTSP/RTP and PNA (an earlier proprietary protocol from Real.com (Progressive Networks)) protocols. This is the last call for comments, trying to commit this week. ftp://ftp.whistle.com/pub/erik/misc/libalias-rtsp-patch.3 FYI, this is the latest phase of some libalias changes we've been working on. Earlier changes were for FTP enhancements and PPTP aliasing. Those have been committed. Junichi and I worked on this latest change. Let us know of any questions or comments. Thanks. Erik Salander Brian Somers wrote: > > Brian, this is just to let you know that: > > > > 1) I am currently in process of applying *big* PPTP patch to libalias > > so I would really appreciate it if you do not touch libalias before > > I finish with PPTP part. > > Ok, no problem - I'm pretty busy at the moment anyway. > > > 2) Erik Salander is working together with Mr. Junichi > > on $Subject issue (see attached), so you will probably want to contact > > them directly, since I am not particularly interested in these changes. > > But I would appreciate if you send me the patch for review before you > > commit it. > > Absolutely - I planned to anyway. > > Cheers. > -- > Brian > > Don't _EVER_ lose your sense of humour ! > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 25 17: 6:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from slarti.muc.de (slarti.muc.de [193.149.48.10]) by hub.freebsd.org (Postfix) with SMTP id 1EDAB37BCC9 for ; Tue, 25 Jul 2000 17:06:16 -0700 (PDT) (envelope-from jhs@jhs.muc.de) Received: (qmail 23825 invoked from network); 26 Jul 2000 00:14:33 -0000 Received: from jhs.muc.de (HELO park.jhs.no?domain) (193.149.49.84) by slarti.muc.de with SMTP; 26 Jul 2000 00:14:33 -0000 Received: from park.jhs.no_domain (localhost [127.0.0.1]) by park.jhs.no_domain (8.9.3/8.9.3) with ESMTP id SAA63943; Tue, 25 Jul 2000 18:46:57 GMT (envelope-from jhs@park.jhs.no_domain) Message-Id: <200007251846.SAA63943@park.jhs.no_domain> To: John Polstra Cc: hackers@FreeBSD.ORG Subject: Re: ELF rtld and environment variables... From: "Julian Stacey" Organization: Vector Systems Ltd - Unix & Internet consultancy X-Web: http://www.jhs.muc.de http://bim.bsn.com/~jhs/ In-reply-to: Your message of "Mon, 24 Jul 2000 09:06:13 PDT." <200007241606.JAA03633@vashon.polstra.com> Date: Tue, 25 Jul 2000 20:46:57 +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > From: John Polstra > No, there isn't. I don't plan to do anything more with the a.out > dynamic linker, as I consider it obsolete at this point. I'd BTW (last I looked) support of gzipped execs was only available for aout, not for elf, ... one more residual use for aout, (apart from the discussed default netscape) Julian - Julian Stacey http://bim.bsn.com/~jhs/ Anti Software Patent Petition to Euro Parliament: http://petition.eurolinux.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 25 17:30:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-42.dsl.snfc21.pacbell.net [63.202.177.42]) by hub.freebsd.org (Postfix) with ESMTP id 49B9D37BCE0 for ; Tue, 25 Jul 2000 17:30:11 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id RAA33336; Tue, 25 Jul 2000 17:39:31 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200007260039.RAA33336@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Julian Stacey" Cc: John Polstra , hackers@FreeBSD.ORG Subject: Re: ELF rtld and environment variables... In-reply-to: Your message of "Tue, 25 Jul 2000 20:46:57 +0200." <200007251846.SAA63943@park.jhs.no_domain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 25 Jul 2000 17:39:31 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > From: John Polstra > > No, there isn't. I don't plan to do anything more with the a.out > > dynamic linker, as I consider it obsolete at this point. I'd > > BTW (last I looked) support of gzipped execs was only available for aout, not > for elf, ... one more residual use for aout, (apart from the discussed > default netscape) gzipped binaries are actually a terrible idea; they actually *waste* space in most cases. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 26 1:44: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from web119.yahoomail.com (web119.yahoomail.com [205.180.60.120]) by hub.freebsd.org (Postfix) with SMTP id 305CD37B541 for ; Wed, 26 Jul 2000 01:44:02 -0700 (PDT) (envelope-from thallgren@yahoo.com) Received: (qmail 23001 invoked by uid 60001); 26 Jul 2000 08:44:02 -0000 Message-ID: <20000726084402.23000.qmail@web119.yahoomail.com> Received: from [212.75.64.155] by web119.yahoomail.com; Wed, 26 Jul 2000 01:44:01 PDT Date: Wed, 26 Jul 2000 01:44:01 -0700 (PDT) From: =?iso-8859-1?q?Tommy=20Hallgren?= Subject: Benchmark oddities To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! I'm reading http://www-scf.usc.edu/~akhavans/Linux_vs_FreeBSD.pdf and have a couple of questions I hope someone here could answer. 1. Section 4.3 and 4.4 is about syscall overhead context switch time. "Figure 2 indicates that the FreeBSD context switch increases linearly with the number of processes, suggesting that the FreeBSD scheduler must search an O (number of processes) data structure during a context switch. Our results show that Linux responds with extreme speed to system calls, and it scales well as the number of processes increases. Paper [4] reports the reverse of these phenomena, which is puzzling since newer versions of the OS should not perform worse than prior versions in such an important function." (Paper [4] is about Windows NT filesystems, maybe he meant the old Stanford paper?) First, the benchmark does a lot of getpid()'s, I don't have to source of glibc handy, but I've heard that glibc caches the pid, meaning that this benchmark is probably bogus since it doesn't measure syscall time on one of the systems. Is that correct? Second, I've repeatedly read in the various FreeBSD mailing-lists that the complexity of FreeBSD's scheduler is a lot better than O(n). Am I missing something here? 2. In section 4.5("Process creation(Fork, Exec)") he quotes a Linux manpage that claims that FreeBSD copies the entire data section when fork() is called. Sounds like rubbish to me. I thought that all modern OS's used copy-on-write when forking. I'm fairly sure the quote is wrong. The author wants to benchmark out-of-the-box systems, a rather silly thing to do IMHO, and he neglects to turn of SoftUpdates, raise the maximum number of filehandles etc etc. Thanks in advance. Regards, Tommy PS. Please cc me since I'm not on this list. DS. ===== Tommy Hallgren Work: tommy@frontpartner.com Tel: +46 (0)709 - 312 404 __________________________________________________ Do You Yahoo!? Get Yahoo! Mail – Free email you can access from anywhere! http://mail.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 26 3: 9:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-42.dsl.snfc21.pacbell.net [63.202.177.42]) by hub.freebsd.org (Postfix) with ESMTP id 5CC0337B76F for ; Wed, 26 Jul 2000 03:09:07 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id DAA36359 for ; Wed, 26 Jul 2000 03:18:38 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200007261018.DAA36359@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: hackers@freebsd.org Subject: Mylex 160/170/352/2000/3000 driver available Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 26 Jul 2000 03:18:38 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm pleased to finally announce the first public BETA version of a new driver for the current family of Mylex PCI-SCSI RAID adapters. This driver provides support for the following adapters: AcceleRAID 160 AcceleRAID 170 AcceleRAID 352 eXtremeRAID 2000 eXtremeRAID 3000 The driver can be found at http://people.freebsd.org/~msmit/RAID/index.html#mylex Note that this version of the driver provides read/write support but no status monitoring or management. Thanks go to the folks at Mylex for their support and patience, as well as to BSDi for funding development of this driver. Thanks also to Leonard Zubkoff, whose Linux driver allowed me discover and avoid a few critical documentation errors which had blocked me for quite some time. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 26 4:15:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.ctimail3.com (main1.my3mail.com [203.80.96.151]) by hub.freebsd.org (Postfix) with ESMTP id C402637BE74 for ; Wed, 26 Jul 2000 04:14:48 -0700 (PDT) (envelope-from July3@wsi-hk.com) Received: from oemcomputer27 (207user29.ctimail3.com [203.80.207.29]) by mail.ctimail3.com (8.9.3/8.9.3) with SMTP id TAA02302 for ; Wed, 26 Jul 2000 19:15:09 +0800 (HKT) Message-Id: <200007261115.TAA02302@mail.ctimail3.com> From: "Peter Forsythe" To: "freebsd-hackers@freebsd.org" Date: Wed, 26 Jul 2000 19:11:15 +0800 Subject: Workplace English and Summer Specials Reply-To: July3@wsi-hk.com MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit X-Priority: 3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [This email is an update of Hong Kong government's Workplace English Campaign, and of Wall Street Institute English specials for July. If you wish to be removed, or are not in Hong Kong, please click on remove@wsi-hk.com]. The Workplace English Campaign of the Hong Kong government is now in Phase II -- which is significantly more flexible than Phase I, including funding up to $HK4,500. We at Wall Street Institute have assisted over 500 individual applications. Please contact us if you would like to know how you or your colleagues benefit from this program -- 2575 6888. SUMMER SPECIALS: Those enrolling in July are eligible for THREE FREE MONTHS of English learning. Anyone enrolling in July can also take part in a draw to win a TWO WEEK TRIP to Toronto, Sydney or London, including accommodation. Phone us for more details (2575 6888) or fill in the form below and fax or email by return. Looking forward to hearing from you. Peter Forsythe Fax form to 2575 1999 or email to July@wsi-hk.com: ---------------------------------------------------------------- Please send me more information on WEC and Summer Specials: Name _____________________________ Address___________________________ Phone_____________________________ Fax_______________________________ ------------------------------------------------------------------ (For remove, put "remove" in subject line or click on remove@wsi-hk.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 26 8:50:12 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id DCFE937BC67; Wed, 26 Jul 2000 08:50:05 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id LAA77485; Wed, 26 Jul 2000 11:50:03 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Wed, 26 Jul 2000 11:50:03 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: freebsd-hackers@FreeBSD.org Cc: ogud@tislabs.com, marka@nominum.com, markm@FreeBSD.org Subject: kern/19863: Non-blocking IO not supported on /dev/random Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi there, This was brought to my attention by a co-worker, and is a legitimate complaint about our device handling for {/dev/null, /dev/random, /dev/urandom, /dev/zero, ...}. Apparently it is not possible to set the device to support non-blocking file I/O, which seems silly as the semantics of the device should permit it. In order for these devices to be used properly from threaded programs based on a select() loop, non-blocking mode is required. Unfortunately, we didn't give the best answer to the initial bug report: Synopsis: Non-blocking IO not supported on /dev/random Responsible-Changed-From-To: freebsd-bugs->markm Responsible-Changed-By: sheldonh Responsible-Changed-When: Wed Jul 12 01:33:02 PDT 2000 Responsible-Changed-Why: Mark Murray has recently re-implemented the random device in the development branch of FreeBSD. This makes him the closest thing we have to a maintainer, although that may just mean you'll have to wait for the new devices to be merged back onto the stable branch. By the way, are you sure /dev/urandom doesn't do what you want? http://www.freebsd.org/cgi/query-pr.cgi?pr=19863 /dev/urandom also does not allow the setting of non-blocking mode. This is probably something that needs to be fixed; it's a pity we didn't catch this before 4.1-RELEASE. I looked through the code some, and noted that /dev/{useful_virtual_stuff} don't implement ioctl(), specifically, support for async I/O, which apparently is required to enable non-blocking I/O (fo_ioctl()). Note that I believe it is insufficient for us to simply provide non-blocking semantics for the device, we actually have to support the flag also for application compatibility. Apparently /dev/random *does* behave correctly on other platforms (Linux, NetBSD, ...) Given that /dev/random is frequently used by security programs, providing correct and consistent semantics is important. This has been demonstrated both in the old /dev/random in 4.x, as well as the revised 5.x devices. Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services ---------- Forwarded message ---------- Date: Tue, 11 Jul 2000 23:41:08 -0700 (PDT) From: marka@nominum.com To: freebsd-gnats-submit@FreeBSD.org Subject: kern/19863: Non-blocking IO not supported on /dev/random >Number: 19863 >Category: kern >Synopsis: Non-blocking IO not supported on /dev/random >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Jul 11 23:50:03 PDT 2000 >Closed-Date: >Last-Modified: >Originator: Mark Andrews >Release: 4.0-stable >Organization: Nominum >Environment: FreeBSD drugs.dv.isc.org 4.0-STABLE FreeBSD 4.0-STABLE #1: Sat Jul 1 00:10:47 EST 2000 root@drugs.dv.isc.org:/usr/src/sys/compile/DRUGS i386 >Description: It is not possible to set /dev/random into non-blocking mode using fcntl. This make it impossible to use /dev/random in a application that requires IO not to block. >How-To-Repeat: #include #include int main(int argc, char **argv) { int fd; int flags; if ((fd = open("/dev/random", O_RDONLY, 0)) == -1) { perror("open"); exit(1); } if ((flags = fcntl(fd, F_GETFL, 0)) == -1) { perror("fcntl: F_GETFL"); exit(1); } flags |= O_NONBLOCK; if (fcntl(fd, F_SETFL, flags) == -1) { perror("fcntl: F_SETFL"); exit(1); } close(fd); exit(0); } >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 26 9:21:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (f97.law7.hotmail.com [216.33.237.97]) by hub.freebsd.org (Postfix) with SMTP id 0494237BED2 for ; Wed, 26 Jul 2000 09:21:34 -0700 (PDT) (envelope-from johnnyteardrop@hotmail.com) Received: (qmail 17864 invoked by uid 0); 26 Jul 2000 16:21:33 -0000 Message-ID: <20000726162133.17863.qmail@hotmail.com> Received: from 209.249.186.215 by www.hotmail.com with HTTP; Wed, 26 Jul 2000 09:21:33 PDT X-Originating-IP: [209.249.186.215] From: "Greg Thompson" To: freebsd-hackers@freebsd.org Subject: getipnodebyname Date: Wed, 26 Jul 2000 12:21:33 EDT Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hackers, i have a multithreaded app that makes heavy use of sockets. i'm seeing a deadlock that looks like it's coming from getipnodebyname. it's my understanding that this guy is supposed to be threadsafe, but comments like this one in libc/net/getaddrinfo.c make me wonder: * Issues to be discussed: * - Thread safe-ness must be checked. have exhaustive tests been done against it? here are the stacks i'm seeing in two threads when my process locks up: #0 0x28181ebe in _thread_kern_sched () from /usr/lib/libc_r.so.4 #1 0x28182ad2 in _thread_kern_sched_state () from /usr/lib/libc_r.so.4 #2 0x281869fd in _thread_fd_lock_debug () from /usr/lib/libc_r.so.4 #3 0x281b918a in _close () from /usr/lib/libc_r.so.4 #4 0x28189faa in _res_close () from /usr/lib/libc_r.so.4 #5 0x28189ab4 in res_send () from /usr/lib/libc_r.so.4 #6 0x2818cc90 in res_query () from /usr/lib/libc_r.so.4 #7 0x2818d16c in res_querydomain () from /usr/lib/libc_r.so.4 #8 0x2818c529 in freehostent () from /usr/lib/libc_r.so.4 #9 0x2818c808 in freehostent () from /usr/lib/libc_r.so.4 #10 0x2818a8e8 in _thread_sys_poll () from /usr/lib/libc_r.so.4 #11 0x2818aa2a in _getipnodebyname_multi () from /usr/lib/libc_r.so.4 #12 0x2818ab11 in getipnodebyname () from /usr/lib/libc_r.so.4 #0 0x28181ebe in _thread_kern_sched () from /usr/lib/libc_r.so.4 #1 0x28182ad2 in _thread_kern_sched_state () from /usr/lib/libc_r.so.4 #2 0x281a1535 in recvfrom () from /usr/lib/libc_r.so.4 #3 0x28189af7 in res_send () from /usr/lib/libc_r.so.4 #4 0x2818cc90 in res_query () from /usr/lib/libc_r.so.4 #5 0x2818d16c in res_querydomain () from /usr/lib/libc_r.so.4 #6 0x2818c529 in freehostent () from /usr/lib/libc_r.so.4 #7 0x2818c808 in freehostent () from /usr/lib/libc_r.so.4 #8 0x2818a8e8 in _thread_sys_poll () from /usr/lib/libc_r.so.4 #9 0x2818aa2a in _getipnodebyname_multi () from /usr/lib/libc_r.so.4 #10 0x2818ab11 in getipnodebyname () from /usr/lib/libc_r.so.4 if i mutex-protect the call to getipnodebyname, my process does not lock up. i can try to make a small repro case if anyone has doubts about the threadsafeness of this function. thanks. -- -greg ________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 26 9:43:11 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from slarti.muc.de (slarti.muc.de [193.149.48.10]) by hub.freebsd.org (Postfix) with SMTP id 3A1D137BBAE for ; Wed, 26 Jul 2000 09:43:04 -0700 (PDT) (envelope-from jhs@jhs.muc.de) Received: (qmail 19530 invoked from network); 26 Jul 2000 16:51:20 -0000 Received: from jhs.muc.de (HELO park.jhs.no?domain) (193.149.49.84) by slarti.muc.de with SMTP; 26 Jul 2000 16:51:20 -0000 Received: from park.jhs.no_domain (localhost [127.0.0.1]) by park.jhs.no_domain (8.9.3/8.9.3) with ESMTP id NAA70530; Wed, 26 Jul 2000 13:37:40 GMT (envelope-from jhs@park.jhs.no_domain) Message-Id: <200007261337.NAA70530@park.jhs.no_domain> To: Mike Smith Cc: hackers@FreeBSD.ORG Subject: Re: ELF rtld and environment variables... From: "Julian Stacey" Organization: Vector Systems Ltd - Unix & Internet consultancy X-Web: http://www.jhs.muc.de http://bim.bsn.com/~jhs/ In-reply-to: Your message of "Tue, 25 Jul 2000 17:39:31 PDT." <200007260039.RAA33336@mass.osd.bsdi.com> Date: Wed, 26 Jul 2000 15:37:40 +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > From: Mike Smith Mike Smith wrote: > gzipped binaries are actually a terrible idea; they actually *waste* > space in most cases. Suprising, They saved space for a 200M disc in a 486 laptop with 3.[2,3,or4], it was so tight for space I gzipped everything, (entire output of src/ except kernel), to save space to then install X/ or something else big. That laptop has now gone to 4.0, & aout to elf, & a 1.5G disc, so no incentive to do it all again to see how much FreeBSD-4 gzipped aout binary tree might save/waste on a whole tree. BTW I was `strip'ing everything, did not use more than standard optimiser, & didnt compile with -g. Script I used is on http://bim.bsn.com/~jhs/bin/.csh/gzip_bins Julian - Julian Stacey http://bim.bsn.com/~jhs/ Kostenlos: FreeBSD 3200 packages, sources, Netscape, WordPerfect & StarWriter. Anti Software Patent Petition to Euro Parliament: http://petition.eurolinux.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 26 11:59:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 5971D37BEC5 for ; Wed, 26 Jul 2000 11:59:32 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id OAA79977; Wed, 26 Jul 2000 14:59:28 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Wed, 26 Jul 2000 14:59:28 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: =?iso-8859-1?q?Tommy=20Hallgren?= Cc: freebsd-hackers@freebsd.org Subject: Re: Benchmark oddities In-Reply-To: <20000726084402.23000.qmail@web119.yahoomail.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, I tend to agree with your comments on the benchmark, but have observed that when starting a large number of forks from the same parent on 4.0-STABLE, the system sporadically hangs waiting in vm_wait for some processes to exit, despite not having hit max kernel processes permitted, or hitting a per-user bound (user rwatson created 2k processes, and starved login running as root). I assume this is a vm limitation. Also, setting maxusers rediculously high (512, say) seems to result in a panic on 4.0 once you exceed a decent number of processes. Haven't had a chance to track any of this down however. Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 26 12:51:40 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-42.dsl.snfc21.pacbell.net [63.202.177.42]) by hub.freebsd.org (Postfix) with ESMTP id A678B37BE6F for ; Wed, 26 Jul 2000 12:51:34 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id NAA39194; Wed, 26 Jul 2000 13:01:02 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200007262001.NAA39194@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Julian Stacey" Cc: hackers@FreeBSD.ORG Subject: Re: ELF rtld and environment variables... In-reply-to: Your message of "Wed, 26 Jul 2000 15:37:40 +0200." <200007261337.NAA70530@park.jhs.no_domain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 26 Jul 2000 13:01:02 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > From: Mike Smith > Mike Smith wrote: > > gzipped binaries are actually a terrible idea; they actually *waste* > > space in most cases. > > Suprising, They saved space for a 200M disc in a 486 laptop with 3.[2,3,or4], No, that's the one case where they help. But people aren't trying to squeeze whole systems into small disks anymore; they're trying to run cut-down systems in tiny spaces (where the fact that you have to unpack the entire binary into memory hurts), or disk space is so cheap that the speed/swap hit is the only impacting factor. Typically, the loss of the ability to demand-page from a gzipped executable is a worse detracting factor than the space saving makes up for. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 26 12:58:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from unix.worldpath.net (unix.worldpath.net [206.152.180.10]) by hub.freebsd.org (Postfix) with ESMTP id 6734C37B7E5 for ; Wed, 26 Jul 2000 12:58:02 -0700 (PDT) (envelope-from waldroni@lr.net) Received: from camry ([208.133.220.178]) by unix.worldpath.net (8.9.3/8.9.3(WPI)) with SMTP id PAA22670 for ; Wed, 26 Jul 2000 15:57:59 -0400 (EDT) Message-ID: <005301bff73b$bf8a3460$0100000a@waldron.house> Reply-To: "Isaac Waldron" From: "Isaac Waldron" To: Subject: Writing device drivers (ioctl issue) Date: Wed, 26 Jul 2000 15:57:36 -0400 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 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I started working on a port of FreeMWare/plex86 (www.plex86.org) to FreeBSD yesterday, and have run into a small problem. The basic idea is that I need to write a kernel module that implements some ioctls for a new psuedo-device that will eventually reside at /dev/plex86. The issue I'm running into is with the function I'm writing to handle the ioctls for the device. For one of the ioctls, the code needs to get some data from the file descriptor that was passed to the original call to ioctl(2). This is easily accomplished in linux, because the file descriptor is passed as the second argument to the device_ioctl function. Is there an easy way to get at the same data (the file descriptor passed to ioctl(2) by the calling program, in a kernel-style "struct file *", not the standard "struct FILE *") in FreeBSD? Or will it be neccesary to change the ioctl structure slightly and therefore need to change some of the higher level functions in plex? Thanks in advance, Isaac Waldron waldroni at lr dot net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 26 13: 1:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66]) by hub.freebsd.org (Postfix) with ESMTP id 7266B37BE1D; Wed, 26 Jul 2000 13:01:09 -0700 (PDT) (envelope-from nate@yogotech.com) Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.123.131]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id OAA05385; Wed, 26 Jul 2000 14:00:54 -0600 (MDT) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id OAA13499; Wed, 26 Jul 2000 14:00:46 -0600 (MDT) (envelope-from nate) Date: Wed, 26 Jul 2000 14:00:46 -0600 (MDT) Message-Id: <200007262000.OAA13499@nomad.yogotech.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Mike Smith Cc: "Julian Stacey" , hackers@FreeBSD.ORG Subject: Re: ELF rtld and environment variables... In-Reply-To: <200007262001.NAA39194@mass.osd.bsdi.com> References: <200007261337.NAA70530@park.jhs.no_domain> <200007262001.NAA39194@mass.osd.bsdi.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Mike Smith wrote: > > > gzipped binaries are actually a terrible idea; they actually *waste* > > > space in most cases. > > > > Suprising, They saved space for a 200M disc in a 486 laptop with 3.[2,3,or4], > > No, that's the one case where they help. But people aren't trying to > squeeze whole systems into small disks anymore; Really? News to me... > they're trying to run > cut-down systems in tiny spaces (where the fact that you have to unpack > the entire binary into memory hurts), or disk space is so cheap that the > speed/swap hit is the only impacting factor. Methinks you generalize *way* too much, w/out knowing all the facts. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 26 13: 9:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id CA2EB37BE1D; Wed, 26 Jul 2000 13:09:38 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id OAA32869; Wed, 26 Jul 2000 14:09:36 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id OAA31834; Wed, 26 Jul 2000 14:09:34 -0600 (MDT) Message-Id: <200007262009.OAA31834@harmony.village.org> To: Mike Smith Subject: Re: ELF rtld and environment variables... Cc: "Julian Stacey" , hackers@FreeBSD.ORG In-reply-to: Your message of "Wed, 26 Jul 2000 13:01:02 PDT." <200007262001.NAA39194@mass.osd.bsdi.com> References: <200007262001.NAA39194@mass.osd.bsdi.com> Date: Wed, 26 Jul 2000 14:09:33 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200007262001.NAA39194@mass.osd.bsdi.com> Mike Smith writes: : Typically, the loss of the ability to demand-page from a gzipped : executable is a worse detracting factor than the space saving makes up : for. This is one reason that Timing Solutions runs all of its small systems out of uncompressed flash or Disk On Chip. We thought about saving a little money and going to 8MB or 16MB parts rather than 64M parts and decompressing into memory, but some simple exeriments that I did showed that this savings would be offset by needing more RAM to hold the entire decompressed image. Much of the stuff we have on our CF parts is needed only for boot or configuration, so it turns out that only a small part of the binaries need to be in RAM at any given time. The price difference between either the 8MB or 16M and 64M CF part is something like $80. The price for an additional 32MB of ram is about $70-$80, give or take in the 72pin SIMMs that we have on our boards. Given our volumes, it didn't make sense to spend the 50 or so hours needed to make a compressed solution bulletproof, plus the unknown amount of time that a compressed solution causes for updates and patches. Even if we did 100 units, that's only $1000, which, counting overhead, is like 5-10 hours of somebody's time, which is far below the cost it would take to engineer the solution, plus build process additions, upgrade hassles, etc. The .gz files would solve only the upgrade hassle issue, while leaving the other issues in place. Each company has its own cost/benefit analysis for these things. So far none of them have seen enough of a benefit to .gz executables to implement them for elf. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 26 13:12:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 1281337BE1D for ; Wed, 26 Jul 2000 13:12:07 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id OAA32881; Wed, 26 Jul 2000 14:12:05 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id OAA31863; Wed, 26 Jul 2000 14:12:03 -0600 (MDT) Message-Id: <200007262012.OAA31863@harmony.village.org> To: "Isaac Waldron" Subject: Re: Writing device drivers (ioctl issue) Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Wed, 26 Jul 2000 15:57:36 EDT." <005301bff73b$bf8a3460$0100000a@waldron.house> References: <005301bff73b$bf8a3460$0100000a@waldron.house> Date: Wed, 26 Jul 2000 14:12:03 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <005301bff73b$bf8a3460$0100000a@waldron.house> "Isaac Waldron" writes: : The issue I'm running into is with the function I'm writing to handle the : ioctls for the device. For one of the ioctls, the code needs to get some : data from the file descriptor that was passed to the original call to : ioctl(2). This is easily accomplished in linux, because the file descriptor : is passed as the second argument to the device_ioctl function. What data does it need to get from the file descriptor? : Is there an easy way to get at the same data (the file descriptor passed to : ioctl(2) by the calling program, in a kernel-style "struct file *", not the : standard "struct FILE *") in FreeBSD? Or will it be neccesary to change the : ioctl structure slightly and therefore need to change some of the higher : level functions in plex? Since you don't say what data you need, it is hard to answer this question. Generally, however, each device has its state in a per unit or per minor softc structure. This "softc" structure usually contains all the information you'll need to cause the device to do the right thing, or to modify the softc state for the given file descriptor. Keep in mind that you get a dev_t with the ioctl which will tell you exactly which device minor you are dealing with. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 26 15: 1:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ares.cs.Virginia.EDU (ares.cs.Virginia.EDU [128.143.136.41]) by hub.freebsd.org (Postfix) with ESMTP id 813FE37C102 for ; Wed, 26 Jul 2000 15:01:16 -0700 (PDT) (envelope-from sl5b@cs.virginia.edu) Received: from viper.cs.Virginia.EDU (viper.cs.Virginia.EDU [128.143.137.17]) by ares.cs.Virginia.EDU (8.9.2/8.9.2/UVACS-2000040300) with ESMTP id SAA09908 for ; Wed, 26 Jul 2000 18:01:13 -0400 (EDT) Received: from localhost (sl5b@localhost) by viper.cs.Virginia.EDU (8.9.2/8.9.2) with ESMTP id SAA27002 for ; Wed, 26 Jul 2000 18:01:13 -0400 (EDT) X-Authentication-Warning: viper.cs.Virginia.EDU: sl5b owned process doing -bs Date: Wed, 26 Jul 2000 18:01:13 -0400 (EDT) From: Song Li To: freebsd-hackers@FreeBSD.ORG Subject: Fine time recording In-Reply-To: <200007262012.OAA31863@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there any method to record the utime/stime of a process more accurately than one tick(defined in kernel as 1/128 second)? Do I have to write some code by myself? thanks! -Song To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 26 15:48:51 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mailtoaster2.pipeline.ch (mailtoaster2.pipeline.ch [62.48.0.71]) by hub.freebsd.org (Postfix) with ESMTP id C706F37BFE5 for ; Wed, 26 Jul 2000 15:48:41 -0700 (PDT) (envelope-from oppermann@telehouse.ch) Received: (qmail 47108 invoked from network); 26 Jul 2000 22:48:51 -0000 Received: from unknown (HELO telehouse.ch) ([62.48.0.53]) (envelope-sender ) by mailtoaster2.pipeline.ch (qmail-ldap-1.03) with RC4-MD5 encrypted SMTP for ; 26 Jul 2000 22:48:51 -0000 Message-ID: <397F6ABE.6603D6EA@telehouse.ch> Date: Thu, 27 Jul 2000 00:48:30 +0200 From: Andre Oppermann X-Mailer: Mozilla 4.73 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: hackers@freebsd.org Subject: [Fwd: freeBSD4.0/NFS/EMC] Content-Type: multipart/mixed; boundary="------------21DDBE157D2EDE795557DD95" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------21DDBE157D2EDE795557DD95 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I'm forwarding this from the qmail mailing list. Anybody has an idea what might be the problem? Matt? -- Andre --------------21DDBE157D2EDE795557DD95 Content-Type: message/rfc822 Content-Transfer-Encoding: 7bit Content-Disposition: inline Return-Path: Received: from muncher.math.uic.edu ([131.193.178.181]) by ntmail.pipeline.ch (Netscape Messaging Server 3.62) with SMTP id 240 for ; Wed, 26 Jul 2000 21:39:33 +0200 Received: (qmail 26424 invoked by uid 1002); 26 Jul 2000 19:34:53 -0000 Mailing-List: contact qmail-help@list.cr.yp.to; run by ezmlm Precedence: bulk Delivered-To: mailing list qmail@list.cr.yp.to Received: (qmail 16736 invoked from network); 26 Jul 2000 19:34:53 -0000 Received: from mail9.wlv.netzero.net (209.247.163.66) by muncher.math.uic.edu with SMTP; 26 Jul 2000 19:34:53 -0000 Received: (qmail 28965 invoked from network); 26 Jul 2000 19:34:30 -0000 Received: from fw2.wlv.netzero.net (HELO michaelb) (209.247.163.243) by mail9.wlv.netzero.net with SMTP; 26 Jul 2000 19:34:30 -0000 Message-ID: <000101bff738$87f25c60$c1a2640a@michaelb> From: "M.B." To: Subject: freeBSD4.0/NFS/EMC Date: Wed, 26 Jul 2000 12:34:35 -0700 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 4.72.3110.1 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 X-Mozilla-Status2: 00000000 This was so well written by one of our network engineers and covers all the questions I need answers for that I just lifted it and am forwarding to the list for comment/help. I'll just add one additonal error that we see. These pop in and out when lots of mail is coming in (usually in alphabetical order, so in this case, the "b" partition is getting lots of hits on it in a short amount of time) Jul 26 12:23:31 nc4 /kernel: nfs server dm7_1.wlv:/b: is alive again Jul 26 12:23:54 nc4 /kernel: nfs server dm7_1.wlv:/b: not responding Jul 26 12:23:54 nc4 /kernel: nfs server dm7_1.wlv:/b: is alive again Jul 26 12:24:07 nc4 /kernel: nfs server dm7_1.wlv:/b: not responding Jul 26 12:24:08 nc4 /kernel: nfs server dm7_1.wlv:/b: not responding Jul 26 12:24:08 nc4 /kernel: nfs server dm7_1.wlv:/b: is alive again Jul 26 12:24:08 nc4 /kernel: nfs server dm7_1.wlv:/b: is alive again ****following is the text of Keith's questions... I am wondering if anyone is running FreeBSD 4.0-RELEASE in an NFS-heavy environment and is noticing performance issues with NFS, or has any tips on how to tune NFS in the kernel. There are currently 6 identical servers that we are running FreeBSD on, though they were installed at different times so some servers are running FreeBSD 3.2-RELEASE, one FreeBSD 3.3-RELEASE, and one FreeBSD 4.0-RELEASE. The machine that is running FreeBSD 4.0-RELEASE is noticably slower then the other boxes, and thus handles a lesser amount of email, even though they all have the same hardware configuration: Dual PIII 600Mhz, 512mb ram, 9.1gb IBM LVD SCSI system disk, two Intel 100BaseT NICs (it's a server motherboard, so one of them is integrated). I have 5 more servers that are setup with FreeBSD 4.0 that I want to put into place, but need to figure out what could be going on to cause this decrease in performance. These boxes are all running qmail. The machines are NFS mounting the mail spool directories off of an EMC Celerra on a dedicated NIC. The other interface is connected to the outside world where the servers are load balanced behind an Alteon Ace. Sometimes just a 'df' will take 10-15 seconds to run unless given the -n switch so it does not try to get new state information. It's not the backend Celerra since the FreeBSD 3.2 and 3.3 boxes are running fine, and we have a number of Sun servers attached to the Celerra as well, with no problems to report. A message that pops up in the messages file every once and awhile is: Jul 21 14:17:03 host /kernel: got bad cookie vp 0xdcc3d840 bp 0xcd03f6a0 Jul 21 14:17:03 host /kernel: got bad cookie vp 0xdcc3d840 bp 0xcd03f6a0 Jul 21 14:17:05 host /kernel: got bad cookie vp 0xdcc3d840 bp 0xcd040600 Jul 21 14:17:05 host /kernel: got bad cookie vp 0xdcc3d840 bp 0xcd040600 Jul 21 14:17:07 host /kernel: got bad cookie vp 0xdcc3d840 bp 0xcd040890 But, I am not sure what this error message means. I included it because it *might* have something to do with the problem, and wanted to include everything I had hoping that someone might have seen this problem before. My kernel configuration is pretty basic. I enable SMP, disable I386,486,586 support in the kernel, turn maxusers up to 256, disable USB support, and recompile the kernel. Nothing fancy on any of the boxes. It is what someone had configured one of ther boxes, and I just kept it the same across the board. qmail is accepting the mail and writing it to the queue, but it never gets a chance to delivery the email to the NFS-mounted mail spool directories. For instance, we received couple thousand email messages for usernames that started with 'b', and these messages piled up on the FreeBSD 4.0 servers, but were delivered immediatly on all of the other machines. Access to the other partitions mounted off of the same datamover (part of the Celerra, basically an NFS server) was fine. Does anyone have any tips or ideas they can pass on to me? I am lost on what it could be. Thanks, -- Keith McCallion keith@mccallion.com _____NetZero Free Internet Access and Email______ http://www.netzero.net/download/index.html --------------21DDBE157D2EDE795557DD95-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 26 16: 1:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id EA2A037B71A; Wed, 26 Jul 2000 16:01:28 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id QAA91336; Wed, 26 Jul 2000 16:01:28 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Wed, 26 Jul 2000 16:01:28 -0700 (PDT) From: Kris Kennaway To: =?iso-8859-1?q?Tommy=20Hallgren?= Cc: freebsd-hackers@freebsd.org Subject: Re: Benchmark oddities In-Reply-To: <20000726084402.23000.qmail@web119.yahoomail.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 26 Jul 2000, [iso-8859-1] Tommy Hallgren wrote: > I'm reading http://www-scf.usc.edu/~akhavans/Linux_vs_FreeBSD.pdf and have a > couple of questions I hope someone here could answer. I thought this paper was quite poorly written, in general - for example, the author is unable to stop gushing about Linux during the first half of the paper (he talks about how standards-compliant it is, the "exemplary performance" it achieves, etc) but then seems to switch abruptly mid-stream, and comes to the conclusion that neither is better than the other. There are several outright fallacies in his reasoning which invalidate some of the conclusions and testing methodologies (such as the getpid() thing, the claim (allegedly from a Linux manpage, no less!) that FreeBSD copies the entire address space on fork(), the claim that FreeBSD can "run fewer copies of the Apache binary" since the binary size is larger, that it is unable to run on >2 CPUs), etc. Basically, it's so poorly done it's not worth worrying about (until it shows up on slashdot, sigh) Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 26 16:38:47 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from sr14.nsw-remote.bigpond.net.au (sr14.nsw-remote.bigpond.net.au [24.192.3.29]) by hub.freebsd.org (Postfix) with ESMTP id 127DC37B68D for ; Wed, 26 Jul 2000 16:38:44 -0700 (PDT) (envelope-from areilly@nsw.bigpond.net.au) Received: from areilly.bpc-users.org (CPE-144-132-245-92.nsw.bigpond.net.au [144.132.245.92]) by sr14.nsw-remote.bigpond.net.au (Pro-8.9.3/8.9.3) with SMTP id IAA01541 for ; Thu, 27 Jul 2000 08:30:58 +1000 (EST) Received: (qmail 73704 invoked by uid 1000); 26 Jul 2000 22:30:57 -0000 From: "Andrew Reilly" Date: Thu, 27 Jul 2000 08:30:57 +1000 To: Nate Williams Cc: Mike Smith , Julian Stacey , hackers@FreeBSD.ORG Subject: Re: ELF rtld and environment variables... Message-ID: <20000727083057.A73044@gurney.reilly.home> References: <200007261337.NAA70530@park.jhs.no_domain> <200007262001.NAA39194@mass.osd.bsdi.com> <200007262000.OAA13499@nomad.yogotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200007262000.OAA13499@nomad.yogotech.com>; from nate@yogotech.com on Wed, Jul 26, 2000 at 02:00:46PM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jul 26, 2000 at 02:00:46PM -0600, Nate Williams wrote: > > No, that's the one case where they help. But people aren't trying to > > squeeze whole systems into small disks anymore; > > Really? News to me... Well, even if there are/were folk who want tiny disk footprints, and crunching everything isn't going to do the whole job, wouldn't a compressed filesystem be a better way to approach this? At least that way you'd still be able to page from the executable(s), and all of the on-disk data would bennefit too. (I've read serious suggestions in comp.arch that it could be benneficial to compress DRAM, with hardware decompression/ compression on the way in and out of cache...) -- Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 26 19:45:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ans2-pub.dttus.com (ans2-pub.dttus.com [204.151.11.3]) by hub.freebsd.org (Postfix) with ESMTP id 9855237B5B2 for ; Wed, 26 Jul 2000 19:45:42 -0700 (PDT) (envelope-from ckhanh@dttus.com) Received: by ans2-pub.dttus.com id VAA01226 (InterLock SMTP Gateway 3.0 for freebsd-hackers@FreeBSD.org); Wed, 26 Jul 2000 21:45:35 -0500 (CDT) Received: by ans2-pub.dttus.com (Internal Mail Agent-2); Wed, 26 Jul 2000 21:45:35 -0500 (CDT) Received: by ans2-pub.dttus.com (Internal Mail Agent-1); Wed, 26 Jul 2000 21:45:35 -0500 (CDT) Message-Id: From: "Chau, Khanh (US - New York)" To: "'freebsd-hackers@FreeBSD.org'" Subject: Date: Wed, 26 Jul 2000 13:09:55 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01BFF724.52317700" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01BFF724.52317700 Content-Type: text/plain; charset="iso-8859-1" Khanh Chau E-Business Technology & Security Deloitte & Touche LLP Phone: (212) 436 7240 Cell: (718) 986-7683 Email: Ckhanh@dttus.com ------_=_NextPart_001_01BFF724.52317700 Content-Type: text/html; charset="iso-8859-1"

Khanh Chau
E-Business Technology & Security
Deloitte & Touche LLP
Phone: (212) 436 7240
Cell: (718) 986-7683
Email: Ckhanh@dttus.com




------_=_NextPart_001_01BFF724.52317700-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 26 22:15:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from superconductor.rush.net (superconductor.rush.net [208.9.155.8]) by hub.freebsd.org (Postfix) with ESMTP id DE09137C055; Wed, 26 Jul 2000 22:15:40 -0700 (PDT) (envelope-from trish@bsdunix.net) Received: from localhost (trish@localhost) by superconductor.rush.net (8.9.3/8.9.3) with ESMTP id BAA24309; Thu, 27 Jul 2000 01:15:35 -0400 (EDT) Date: Thu, 27 Jul 2000 01:15:35 -0400 (EDT) From: Siobhan Patricia Lynch X-Sender: trish@superconductor.rush.net To: Kris Kennaway Cc: =?iso-8859-1?q?Tommy=20Hallgren?= , freebsd-hackers@FreeBSD.ORG Subject: Re: Benchmark oddities In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG heh, won;t happen if I can help it ;) -Trish __ Trish Lynch FreeBSD - The Power to Serve trish@bsdunix.net Rush Networking trish@rush.net On Wed, 26 Jul 2000, Kris Kennaway wrote: > On Wed, 26 Jul 2000, [iso-8859-1] Tommy Hallgren wrote: > > > I'm reading http://www-scf.usc.edu/~akhavans/Linux_vs_FreeBSD.pdf and have a > > couple of questions I hope someone here could answer. > > I thought this paper was quite poorly written, in general - for example, > the author is unable to stop gushing about Linux during the first half of > the paper (he talks about how standards-compliant it is, the "exemplary > performance" it achieves, etc) but then seems to switch abruptly > mid-stream, and comes to the conclusion that neither is better than the > other. > > There are several outright fallacies in his reasoning which invalidate > some of the conclusions and testing methodologies (such as the getpid() > thing, the claim (allegedly from a Linux manpage, no less!) that FreeBSD > copies the entire address space on fork(), the claim that FreeBSD can "run > fewer copies of the Apache binary" since the binary size is larger, that > it is unable to run on >2 CPUs), etc. > > Basically, it's so poorly done it's not worth worrying about (until it > shows up on slashdot, sigh) > > Kris > > -- > In God we Trust -- all others must submit an X.509 certificate. > -- Charles Forsythe > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 26 22:16:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from nemean.spikeman.net (nemean.spikeman.net [204.137.229.4]) by hub.freebsd.org (Postfix) with ESMTP id 36A0037C02B for ; Wed, 26 Jul 2000 22:16:08 -0700 (PDT) (envelope-from spikeman@nemean.spikeman.net) Received: (from spikeman@localhost) by nemean.spikeman.net (8.9.3/8.9.3) id AAA04409 for freebsd-hackers@FreeBSD.ORG; Thu, 27 Jul 2000 00:16:07 -0500 Date: Thu, 27 Jul 2000 00:16:07 -0500 From: Spikeman To: freebsd-hackers@FreeBSD.ORG Subject: cpu time slicing Message-ID: <20000727001607.A4392@myself.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5us Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does anyone here have any docs about how FreeBSD ( 4.0-RELEASE i'm running ) does its cpu time slicing. - Background on 'issue' I have twin systems one running Linux One Running FreeBSD they both are doing a distributed computing effort, Linux works at one speed forever while FreeBSD after 100 hours doubled the amount it could do ( also doubled the mount linux is doing ) also it seems to be 'testing' the max the system it can do from time to time, as couple times I would check the status it would be very high in how much the client its doing and then slowly come down ( learning ? ) ... Talked to some of the people from the distributed computing effort and its not the client most likely its FreeBSD doing this. I have no problem with it doing this I happen to enjoy it so I thought I would learn more on how bsd does its cpu time slicing.... -- ___ /\ \ phase two of global domination in operation, hide all lions. /::\ \ /:/\:\ \ Comments or Questions email spikeman@myself.com _\:\~\:\ \ /\ \:\ \:\__\ Spikeman spikeman@myself.com \:\ \:\ \/__/ http://www.spikeman.net \:\ \:\__\ Find Me On EFNET /whois Spikeman \:\/:/ / \::/ / Friends are lights in winter; \/__/ The older the friend, the brighter the light. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 27 0:55:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cx587235-a.chnd1.az.home.com (cx587235-a.chnd1.az.home.com [24.11.88.170]) by hub.freebsd.org (Postfix) with ESMTP id 6B32D37C06F for ; Thu, 27 Jul 2000 00:55:29 -0700 (PDT) (envelope-from jjreynold@home.com) Received: (from jjreynold@localhost) by cx587235-a.chnd1.az.home.com (8.9.3/8.9.3) id AAA31337; Thu, 27 Jul 2000 00:55:28 -0700 (MST) (envelope-from jjreynold@home.com) From: John Reynolds MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14719.60144.794393.763015@gargle.gargle.HOWL> Date: Thu, 27 Jul 2000 00:55:28 -0700 (MST) To: hackers@freebsd.org Subject: unable to use disklabel -B from fixit floppy? X-Mailer: VM 6.75 under Emacs 20.7.1 Cc: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello all ... hope this is the right group for this .... Last night I had to re-install win98 on my IDE drive (dual-boot) and it happily clobbered my mbr. No problem. I've had this happen before. I booted up 4.0 from my CDs and chose the "Fixit" option from the CD-ROM. I tried: disklabel -B ad0 and I got this back: disklabel: bad bpack magic number (label is damaged, or pack is unlabeled) huh? So, then I just fell back to method #2 which I've done before in going into the partition editor within sysinstall, editing NOTHING but hitting 'w' to write the current information along with the boot sector. This happily worked. But, why did I get the wierd error above? Previously I had compiled and installed a new 4.1-STABLE world. Is the disklabel command from 4.0 somehow incompatible with device entries or something else in 4.1-STABLE? I also tried downloading the fixit.flp image from 4.1-RC, making that, and using that as the floppy from within sysinstall. Still no dice in using disklabel. Is this error message familiar to anybody? -Jr -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= John Reynolds Chandler Capabilities Engineering, CDS, Intel Corporation jreynold@sedona.ch.intel.com My opinions are mine, not Intel's. Running jjreynold@home.com FreeBSD 4.0-STABLE. FreeBSD: The Power to Serve. http://members.home.com/jjreynold/ Come join us!!! @ http://www.FreeBSD.org/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 27 4:53:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id E34DF37B78B; Thu, 27 Jul 2000 04:53:47 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id EAA90682; Thu, 27 Jul 2000 04:53:47 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Thu, 27 Jul 2000 04:53:46 -0700 (PDT) From: Kris Kennaway To: Julian Stacey Cc: Mike Smith , hackers@FreeBSD.ORG Subject: Re: ELF rtld and environment variables... In-Reply-To: <200007261337.NAA70530@park.jhs.no_domain> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 26 Jul 2000, Julian Stacey wrote: > That laptop has now gone to 4.0, & aout to elf, & a 1.5G disc, so no > incentive to do it all again to see how much FreeBSD-4 gzipped aout > binary tree might save/waste on a whole tree. BTW I was `strip'ing gzexe(1) is your friend :-) Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 27 5:33:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.rila.bg (earth.rila.bg [212.39.75.31]) by hub.freebsd.org (Postfix) with ESMTP id D86D637B92B for ; Thu, 27 Jul 2000 05:33:16 -0700 (PDT) (envelope-from mitko@rila.bg) Received: from earth (mitko@localhost [127.0.0.1]) by earth.rila.bg (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with SMTP id PAA08505 for ; Thu, 27 Jul 2000 15:31:42 +0300 From: Dimitar Peikov Organization: Rila Solutions To: hackers@FreeBSD.ORG Subject: mmap syncs and file extends Date: Thu, 27 Jul 2000 15:22:01 +0300 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <00072715314205.05330@earth> Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, hackers, I've try to use mmap() and resize the mapping. msync() syncronizes only t= he memory that was mmapped with mmap(). How can I extend the main file? Memo= ry is filled correctly, but I must write extended data to file by hand. In my examples 'x.txt' was 11 bytes (some text); Where I'm wrong? ---------- #include #include #include #include #include =20 int main() { char *ptr; int fd, size=3D20; =20 fd =3D open("x.txt", O_RDWR | O_CREAT); ptr =3D mmap(0, 15, PROT_READ | PROT_WRITE, MAP_SHARED, fd, 0); ptr[0] =3D 'D'; ptr[6] =3D 'D'; ptr =3D mremap(ptr, 10, 20, 1); close(fd); ptr[10] =3D 'Y'; ptr[12] =3D 'X'; printf("1%C\n", ptr[12]); msync(ptr, size, MS_SYNC); munmap(ptr, size); } ---------- --=20 Dimitar Peikov Programmer "We Build e-Business" =20 RILA Solutions =20 27 Building, Acad.G.Bonchev Str. =20 1113 Sofia, Bulgaria =20 home: (+359 2) 595495 phone: (+359 2) 9797320=20 phone: (+359 2) 9797300=20 fax: (+359 2) 9733355 =20 http://www.rila.com=20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 27 8: 8:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from teapot28.domain6.bigpond.com (teapot28.domain6.bigpond.com [139.134.5.197]) by hub.freebsd.org (Postfix) with SMTP id EF3C137BA8D for ; Thu, 27 Jul 2000 08:08:45 -0700 (PDT) (envelope-from tpnelson@echidna.stu.cowan.edu.au) Received: from localhost (localhost [127.0.0.1]) by teapot28.domain6.bigpond.com (NTMail 3.02.13) with ESMTP id ha454877 for ; Fri, 28 Jul 2000 01:10:31 +1000 Received: from WEBH-T-003-p-145-158.tmns.net.au ([139.134.145.158]) by mail6.bigpond.com (Claudes-Well-Rounded-MailRouter V2.9 11/276193); 28 Jul 2000 01:10:30 Message-ID: <398050BA.E7C7F4A0@echidna.stu.cowan.edu.au> Date: Thu, 27 Jul 2000 23:09:46 +0800 From: Trent Nelson X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Dimitar Peikov Cc: hackers@FreeBSD.ORG Subject: Re: mmap syncs and file extends References: <00072715314205.05330@earth> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dimitar Peikov wrote: > > Hi, hackers, > > I've try to use mmap() and resize the mapping. msync() syncronizes > only the memory that was mmapped with mmap(). How can I extend the > main file? Memory is filled correctly, but I must write extended data > to file by hand. You need to extend the main file by calling ftruncate() as you can't map memory past the file's current EOF. I got an excellent response from Matt Dillon on a question of a similar nature a few months ago. It might be in your interest to check the hackers mail archive a little deeper. > Dimitar Peikov Regards, Trent. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 27 8:44:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from animaths.com (AMontsouris-101-2-95.abo.wanadoo.fr [193.251.54.95]) by hub.freebsd.org (Postfix) with SMTP id 9361937B8A6 for ; Thu, 27 Jul 2000 08:44:33 -0700 (PDT) (envelope-from nicolas.leonard@animaths.com) Received: (qmail 5891 invoked by uid 31); 26 Jul 2000 07:40:15 -0000 Received: from nicolas.leonard@animaths.com by ns.masa.com with scan4virus-0.53 (uvscan: v4.0.70/v4085. . Clean. Processed in 0.236951 secs); 26/07/2000 09:40:15 Received: from nld.masa.com (HELO nld) (172.16.2.15) by ns.masa.com with SMTP; 26 Jul 2000 07:40:15 -0000 Message-ID: <011b01bff6d4$778dbae0$0f0210ac@masa.com> From: =?Windows-1252?Q?Nicolas_L=E9onard?= To: Subject: kevent()/kqueue() in a multithreaded environment Date: Wed, 26 Jul 2000 09:38:18 +0200 Organization: =?Windows-1252?Q?Math=E9matiques_Appliqu=E9es_SA?= MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello I'm trying to use the new kqueue()/kevent() syscalls in the last snapshot of FreeBSD 5.0. It works perfectly, except when I'm trying to use it in a multi- threaded program. The call of kevent() by my network thread blocks the other thread. I look in the libc_r sources and I found that this syscall isn't already wrapped. Does anybody know if there is a patch or another tips to make it work ? Thanks Leon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 27 9:36:59 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 4DC7C37BC1F for ; Thu, 27 Jul 2000 09:36:56 -0700 (PDT) (envelope-from jhb@pike.osd.bsdi.com) Received: (from jhb@localhost) by pike.osd.bsdi.com (8.9.3/8.9.3) id JAA76849; Thu, 27 Jul 2000 09:36:37 -0700 (PDT) (envelope-from jhb) From: John Baldwin Message-Id: <200007271636.JAA76849@pike.osd.bsdi.com> Subject: Re: unable to use disklabel -B from fixit floppy? In-Reply-To: <14719.60144.794393.763015@gargle.gargle.HOWL> from John Reynolds at "Jul 27, 2000 00:55:28 am" To: John Reynolds Date: Thu, 27 Jul 2000 09:36:37 -0700 (PDT) Cc: hackers@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Reynolds wrote: > > Hello all ... hope this is the right group for this .... Umm, well. First off, disklabel -B doesn't fix your MBR. fdisk does that, or boot0cfg if you are using boot0 to dual-boot. However, can you type disklabel ad0 now and get useful information? Or disklabel ad0sX (where X is the slice number for your FreeBSD slice)? > So, then I just fell back to method #2 which I've done before in going into the > partition editor within sysinstall, editing NOTHING but hitting 'w' to write > the current information along with the boot sector. This happily worked. Yes, this touches the MBR. The disklabel command serves the same purpose as the label editor in sysinstall. IOW, you use disklabel to lay out partitions (a-h) within a FreeBSD slice. > But, why did I get the wierd error above? Previously I had compiled and > installed a new 4.1-STABLE world. Is the disklabel command from 4.0 somehow > incompatible with device entries or something else in 4.1-STABLE? See if disklabel ad0 works now. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 27 11: 4:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from web214.mail.yahoo.com (web214.mail.yahoo.com [128.11.68.114]) by hub.freebsd.org (Postfix) with SMTP id 8B82337BDCA for ; Thu, 27 Jul 2000 11:04:35 -0700 (PDT) (envelope-from nasko_b@yahoo.com) Received: (qmail 27780 invoked by uid 60001); 27 Jul 2000 18:04:35 -0000 Message-ID: <20000727180435.27779.qmail@web214.mail.yahoo.com> Received: from [212.50.18.3] by web214.mail.yahoo.com; Thu, 27 Jul 2000 11:04:35 PDT Date: Thu, 27 Jul 2000 11:04:35 -0700 (PDT) From: Nasko Bachvaroff Subject: pcm sound driver works with CMI8330 To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a temporal solution on running CMI8330 sundcard under FreeBSD 4.0-RELEASE. Everybody having troubles with this soundcard, send me email and i'll send em the patch. I'm working in the moment on making the solution completely working and I'll release it soon. Atanas Bachvaroff, BGR, nasko_b@yahoo.com __________________________________________________ Do You Yahoo!? Kick off your party with Yahoo! Invites. http://invites.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 27 11:28:51 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from slarti.muc.de (slarti.muc.de [193.149.48.10]) by hub.freebsd.org (Postfix) with SMTP id D5C4C37B798 for ; Thu, 27 Jul 2000 11:28:46 -0700 (PDT) (envelope-from jhs@jhs.muc.de) Received: (qmail 11392 invoked from network); 27 Jul 2000 18:37:07 -0000 Received: from jhs.muc.de (HELO park.jhs.no?domain) (193.149.49.84) by slarti.muc.de with SMTP; 27 Jul 2000 18:37:07 -0000 Received: from park.jhs.no_domain (localhost [127.0.0.1]) by park.jhs.no_domain (8.9.3/8.9.3) with ESMTP id MAA02788 for ; Thu, 27 Jul 2000 12:47:03 GMT (envelope-from jhs@park.jhs.no_domain) Message-Id: <200007271247.MAA02788@park.jhs.no_domain> To: hackers@FreeBSD.ORG Subject: Re: ELF rtld and environment variables... From: "Julian Stacey" Organization: Vector Systems Ltd - Unix & Internet consultancy X-Web: http://www.jhs.muc.de http://bim.bsn.com/~jhs/ In-reply-to: Your message of "Thu, 27 Jul 2000 08:30:57 +1000." <20000727083057.A73044@gurney.reilly.home> Date: Thu, 27 Jul 2000 14:47:03 +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Andrew Reilly" wrote: > Well, even if there are/were folk who want tiny disk footprints, > and crunching everything isn't going to do the whole job, wouldn't > a compressed filesystem be a better way to approach this? At least > that way you'd still be able to page from the executable(s), and > all of the on-disk data would bennefit too. I would have used a compressing file system if it had existed, just as today I'd use an encrypting file system on my new laptop, but such file system don't exist on FreeBSD unfortunately. Nice ideas to add to a web page of project ideas for students & other contributors. When I was a student, friends were keen to find project ideas more inspiring than those on lists drawn up by the lecturers. Julian - Julian Stacey http://bim.bsn.com/~jhs/ Munich Unix Consultant. Free BSD Unix with 3200 packages & sources. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 27 11:45:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cx587235-a.chnd1.az.home.com (cx587235-a.chnd1.az.home.com [24.11.88.170]) by hub.freebsd.org (Postfix) with ESMTP id D559537BBCE; Thu, 27 Jul 2000 11:45:11 -0700 (PDT) (envelope-from jjreynold@home.com) Received: from whale.home-net (whale [192.168.1.2]) by cx587235-a.chnd1.az.home.com (8.9.3/8.9.3) with ESMTP id LAA09117; Thu, 27 Jul 2000 11:45:11 -0700 (MST) (envelope-from jjreynold@home.com) Received: (from jjreynold@localhost) by whale.home-net (8.9.3/8.9.3) id LAA44493; Thu, 27 Jul 2000 11:45:11 -0700 (MST) (envelope-from jjreynold@home.com) From: John Reynolds MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14720.33591.77038.377961@whale.home-net> Date: Thu, 27 Jul 2000 11:45:11 -0700 (MST) To: hackers@freebsd.org Cc: doc@freebsd.org Subject: Re: unable to use disklabel -B from fixit floppy? In-Reply-To: <200007271636.JAA76849@pike.osd.bsdi.com> References: <14719.60144.794393.763015@gargle.gargle.HOWL> <200007271636.JAA76849@pike.osd.bsdi.com> X-Mailer: VM 6.75 under Emacs 20.7.1 Cc: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ copying -doc because I've got a doc patch for the FAQ ... perhaps :) ] [ On Thursday, July 27, John Baldwin wrote: ] > > Umm, well. First off, disklabel -B doesn't fix your MBR. fdisk does that, > or boot0cfg if you are using boot0 to dual-boot. However, can you type Hmmm. Must have just been bit-rot in my brain from WAY back. Maybe it was the 3.x to 4.x transition where I remember seeing ``do disklabel -B'' ... can't remember. OK, now I know boot0cfg so I'll remember that. Thanks very much! > disklabel ad0 now and get useful information? Or disklabel ad0sX (where X > is the slice number for your FreeBSD slice)? oh yes, no problems. > Yes, this touches the MBR. The disklabel command serves the same purpose as > the label editor in sysinstall. IOW, you use disklabel to lay out partitions > (a-h) within a FreeBSD slice. > > See if disklabel ad0 works now. Absolutely. Since this is a way to recover the MBR in addition to what was already in the FAQ, I hacked up some changes to that FAQ entry. Attached is a diff--be gentle, this is my very first time attempting to hack SGML :) ... (I will go ahead and just send-pr this as well ....) --- book.sgml.orig Thu Jul 27 11:08:53 2000 +++ book.sgml Thu Jul 27 11:38:03 2000 @@ -1306,22 +1306,22 @@ -Can Windows 95 co-exist with FreeBSD? +Can Windows 95/98 co-exist with FreeBSD? -Install Windows 95 first, after that FreeBSD. FreeBSD's boot -manager will then manage to boot Win95 and FreeBSD. If you -install Windows 95 second, it will boorishly overwrite your +Install Windows 95/98 first, after that FreeBSD. FreeBSD's boot +manager will then manage to boot Win95/98 and FreeBSD. If you +install Windows 95/98 second, it will boorishly overwrite your boot manager without even asking. If that happens, see the next section. - Windows 95 killed my boot manager! How do I get it back? + Windows 95/98 killed my boot manager! How do I get it back? You can reinstall the boot manager FreeBSD comes with in one of -two ways: +three ways: @@ -1351,6 +1351,24 @@ prompt, be sure to select "Boot Manager." This will re-write the boot manager to disk. Now quit out of the installation menu and reboot off the hard disk as normal. + + + +Boot the FreeBSD boot floppy (or CD-ROM) and choose the +Fixit menu item. Select either the Fixit floppy or +CD-ROM #2 (the live file system option) as appropriate +and enter the fixit shell. Then execute the following command: + + +Fixit# boot0cfg -B bootdevice + + +substituting bootdevice for your real boot device such +as ad0 (first IDE disk), ad4 (first IDE disk on auxiliary controller), da0 +(first SCSI disk), etc. + + + -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= John Reynolds Chandler Capabilities Engineering, CDS, Intel Corporation jreynold@sedona.ch.intel.com My opinions are mine, not Intel's. Running jjreynold@home.com FreeBSD 4.0-STABLE. FreeBSD: The Power to Serve. http://members.home.com/jjreynold/ Come join us!!! @ http://www.FreeBSD.org/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 27 13:13:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id BC3A737BD63; Thu, 27 Jul 2000 13:13:15 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id QAA10252; Thu, 27 Jul 2000 16:13:08 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Thu, 27 Jul 2000 16:13:08 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Isaac Waldron Cc: freebsd-hackers@freebsd.org, freebsd-arch@freebsd.org Subject: Re: Writing device drivers (ioctl issue) In-Reply-To: <005301bff73b$bf8a3460$0100000a@waldron.house> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 26 Jul 2000, Isaac Waldron wrote: > I started working on a port of FreeMWare/plex86 (www.plex86.org) to FreeBSD > yesterday, and have run into a small problem. The basic idea is that I need > to write a kernel module that implements some ioctls for a new psuedo-device > that will eventually reside at /dev/plex86. > > The issue I'm running into is with the function I'm writing to handle the > ioctls for the device. For one of the ioctls, the code needs to get some > data from the file descriptor that was passed to the original call to > ioctl(2). This is easily accomplished in linux, because the file descriptor > is passed as the second argument to the device_ioctl function. > > Is there an easy way to get at the same data (the file descriptor passed to > ioctl(2) by the calling program, in a kernel-style "struct file *", not the > standard "struct FILE *") in FreeBSD? Or will it be neccesary to change the > ioctl structure slightly and therefore need to change some of the higher > level functions in plex? I ran into this same problem when modifying the vmmon VMWare driver for FreeBSD to support mulitple emulator instances. FreeBSD's VFS does not have a concept of stateful file access: there are open's and close's, but the VOP_READ/WRITE operations are not associated with sessions. This influences the way in which drivers are implemented for BSD (and platforms like it.) For example, rather than having one /dev/bpf with multiple "open" instances, we have /dev/bpf{0,1,...}, and a process needing a session will sequentially attempt to open devices until it finds one that doesn't return EBUSY. The driver, in this case, limits the number of open references to 1. There are a number of possible solutions to this problem, including the Linux solution solution of passing the file descriptor down the VFS stack so that VFS layers can attach attach information to the file descriptor providing session information. In this manner, VOP_READ/WRITE can determine which session is active, and behave appropriately. I dislike this solution: right now, file descriptors are a property of the process and ABI, and the VFS is unaware of them. Having a stacked file system suggests that the single hook in the file descriptor is insufficient to maintain per-layer information associated with a session, also. It also makes a mess of access to files from within the kernel, where file descriptors are not used. My preferred solution, and I actually hacked around with a kernel a bit to do this, is to make the VFS provide (optional) stateful vnode sessions. vop_open() would gain an additional call-by-reference argument, probably a void**. When NULL, the caller would be requesting a stateless vnode open, and all would be as today. When non-NULL, this would allow the vnode provider to return a cookie/rock/void pointer to state information for the session. Other VOP's would similarly accept back this cookie, allowing the VOP provider to inspect it (if non-NULL) and behave appropriately with state. vop_close() could be used to release the cookie. This would provide the ability for file systems and callers to optionally make use of state, without violating the seperation of file descriptors/open file records and the VFS. It would also allow stacking to occur, as each vnode private data layer/layered cookie struct could do appropriate layer transformations to get the right cookie for the next layer down. I.e., there would be a sensical semantic for stacked file systems to provide stateful access. My changes are incomplete as I was working on it on the plane, and comments on the idea would be welcome. One thing this would allow is for us to not heavily replicate device nodes in /dev for multi-instance virtual devices. The BPF example is a useful one here: while the kernel currently supports dynamically allocated BPF devices, /dev has to have BPF entries manually added. The same goes for tunnel devices, et al. While a real devfs would fix this, the semantic is also useful for drivers ported from Linux (and other platforms with stateful vnode access) that expect to be able to open /dev/vmmon, and get a new unique session. For /dev/vmnet, it means the driver can detect multiple sessions on the same device, and act appropriately. In vmnet, each vmnet device acts like an ethernet bridge for the sessions open on it, so you can bind different VMWare sessions to different virtual network segments, potentially more than one VMWare session to each network segment. Or, you can binary-modify VMWare each run time to open a different /dev/{whatever}, or ge the developer to use a /dev/whatever{0,1,2,3...} model, for which there is much precedent in Linux (BPF, ttys, etc). Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 27 14: 8:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.122.47]) by hub.freebsd.org (Postfix) with ESMTP id 7797537C116 for ; Thu, 27 Jul 2000 14:08:46 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.10.1/8.10.1) with ESMTP id e6RL8hS69786; Thu, 27 Jul 2000 14:08:43 -0700 (PDT) Date: Thu, 27 Jul 2000 14:08:43 -0700 (PDT) From: Doug White To: =?Windows-1252?Q?Nicolas_L=E9onard?= Cc: hackers@FreeBSD.ORG Subject: Re: kevent()/kqueue() in a multithreaded environment In-Reply-To: <011b01bff6d4$778dbae0$0f0210ac@masa.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 26 Jul 2000, [Windows-1252] Nicolas Léonard wrote: > I'm trying to use the new kqueue()/kevent() syscalls in the last > snapshot of FreeBSD 5.0. > It works perfectly, except when I'm trying to use it in a multi- > threaded program. > The call of kevent() by my network thread blocks the other thread. > > I look in the libc_r sources and I found that this syscall isn't > already wrapped. > > Does anybody know if there is a patch or another tips to make it > work ? You normally wouldn't mix kqueue and threads; you'd use kqueue to *implement* threads. :-) AFAIK kqueue hasn't been made threadsafe, you'll have to bug jlemon@freebsd.org about it. Patches gladly accepted :) Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 27 14:35:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from peony.ezo.net (peony.ezo.net [206.102.130.11]) by hub.freebsd.org (Postfix) with ESMTP id 6670A37B523 for ; Thu, 27 Jul 2000 14:35:07 -0700 (PDT) (envelope-from jflowers@peony.ezo.net) Received: from localhost (jflowers@localhost) by peony.ezo.net (8.11.0.Beta3/8.11.0.Beta3) with ESMTP id e6RLaOg78197 for ; Thu, 27 Jul 2000 17:36:24 -0400 (EDT) Date: Thu, 27 Jul 2000 17:36:23 -0400 (EDT) From: Jim Flowers To: freebsd-hackers@freebsd.org Subject: fbsd 4.0Release Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We have been using fbsd 4.0-RELEASE on a number of router applications (IPV4). Recently we have switched to new hardware and now we get fatal faults periodically. Typically these run with a minimum kernal using ipfw and natd and not much more. 32 MB memory. Does this indicate that my new hardware is probably not going to work with fbsd 4.0? Anything I can do to find out message on fatal fault --------------------------- Fatal Trap 12: Page Fault While In Kernel Mode Fault Virtual Address =0x8 Fault Code =Supervisor Read, Page Not Present Instruction Pointer =0x8:;0xc018c370 Stack Pointer =0x10:0xxc470ee3c Frame Pointer =0x10:0xc470ee44 Code Segment =Base 0x0, Limit 0xfffff,Type 0x1b Processor Eflags =Interrupt Enabled,Resume,IOPL=0 Current Process =171 (Ping) Interrupt Mask = Trap Number =12 Panic:Page Fault dmesg ---------------- natd-cr# dmesg Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-RELEASE #1: Thu Jul 27 21:06:34 CST 2000 root@natd-cr.ezo.net:/usr/src/sys/compile/LOCAL Timecounter "i8254" frequency 1193182 Hz CPU: Pentium/P55C (233.40-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x543 Stepping = 3 Features=0x8001bf real memory = 31457280 (30720K bytes) avail memory = 27467776 (26824K bytes) Preloaded elf kernel "kernel" at 0xc0318000. Intel Pentium detected, installing workaround for F00F bug md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 atapci0: port 0xffa0-0xffaf,0x374-0x377,0x170-0x177,0x3f4-0x3f7,0x1f0-0x1f7 irq 0 at device 0.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 isab0: at device 1.0 on pci0 isa0: on isab0 pci0: (vendor=0x1039, dev=0x0009) at 1.1 pcib2: at device 2.0 on pci0 pci1: on pcib2 pci1: at 0.0 rl0: port 0xde00-0xdeff mem 0xefffbf00-0xefffbfff irq 10 at device 8.0 on pci0 rl0: Ethernet address: 00:48:54:82:13:d2 miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl1: port 0xdc00-0xdcff mem 0xefffbe00-0xefffbeff irq 9 at device 11.0 on pci0 rl1: Ethernet address: 00:40:ca:1d:ff:30 miibus1: on rl1 rlphy1: on miibus1 rlphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pcib1: on motherboard pci2: on pcib1 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold ppi0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port plip0: on ppbus0 IP packet filtering initialized, divert enabled, rule-based forwarding enabled, default to accept, logging limited to 100 packets/entry by default ad0: 4126MB [8944/15/63] at ata0-master using UDMA33 Mounting root from ufs:/dev/ad0s1a Jim Flowers #4 ranked ISP on C|NET #1 in Ohio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 27 14:45: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [207.154.226.10]) by hub.freebsd.org (Postfix) with ESMTP id 4D2D937C0FD for ; Thu, 27 Jul 2000 14:44:57 -0700 (PDT) (envelope-from paul@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1000) id 805372B228; Thu, 27 Jul 2000 16:44:46 -0500 (CDT) Date: Thu, 27 Jul 2000 14:44:46 -0700 From: Paul Saab To: Jim Flowers Cc: freebsd-hackers@freebsd.org Subject: Re: fbsd 4.0Release Message-ID: <20000727144446.A71534@elvis.mu.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from jflowers@peony.ezo.net on Thu, Jul 27, 2000 at 05:36:23PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There are known panics in the network stack in 4.0-RELEASE. You should really upgrade to 4.1-RELEASE. paul Jim Flowers (jflowers@peony.ezo.net) wrote: > We have been using fbsd 4.0-RELEASE on a number of router applications > (IPV4). Recently we have switched to new hardware and now we get fatal > faults periodically. > > Typically these run with a minimum kernal using ipfw and natd and not much > more. 32 MB memory. > > Does this indicate that my new hardware is probably not going to work with > fbsd 4.0? > > Anything I can do to find out > > message on fatal fault --------------------------- > > Fatal Trap 12: Page Fault While In Kernel Mode > Fault Virtual Address =0x8 > Fault Code =Supervisor Read, Page Not Present > Instruction Pointer =0x8:;0xc018c370 > Stack Pointer =0x10:0xxc470ee3c > Frame Pointer =0x10:0xc470ee44 > Code Segment =Base 0x0, Limit 0xfffff,Type 0x1b > Processor Eflags =Interrupt Enabled,Resume,IOPL=0 > Current Process =171 (Ping) > Interrupt Mask = > Trap Number =12 > Panic:Page Fault > > dmesg ---------------- > > natd-cr# dmesg > Copyright (c) 1992-2000 The FreeBSD Project. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > FreeBSD 4.0-RELEASE #1: Thu Jul 27 21:06:34 CST 2000 > root@natd-cr.ezo.net:/usr/src/sys/compile/LOCAL > Timecounter "i8254" frequency 1193182 Hz > CPU: Pentium/P55C (233.40-MHz 586-class CPU) > Origin = "GenuineIntel" Id = 0x543 Stepping = 3 > Features=0x8001bf > real memory = 31457280 (30720K bytes) > avail memory = 27467776 (26824K bytes) > Preloaded elf kernel "kernel" at 0xc0318000. > Intel Pentium detected, installing workaround for F00F bug > md0: Malloc disk > npx0: on motherboard > npx0: INT 16 interface > pcib0: on motherboard > pci0: on pcib0 > atapci0: port > 0xffa0-0xffaf,0x374-0x377,0x170-0x177,0x3f4-0x3f7,0x1f0-0x1f7 irq 0 at > device 0.1 on pci0 > ata0: at 0x1f0 irq 14 on atapci0 > isab0: at device 1.0 on pci0 > isa0: on isab0 > pci0: (vendor=0x1039, dev=0x0009) at 1.1 > pcib2: at device 2.0 on pci0 > pci1: on pcib2 > pci1: at 0.0 > rl0: port 0xde00-0xdeff mem > 0xefffbf00-0xefffbfff irq 10 at device 8.0 on pci0 > rl0: Ethernet address: 00:48:54:82:13:d2 > miibus0: on rl0 > rlphy0: on miibus0 > rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > rl1: port 0xdc00-0xdcff mem > 0xefffbe00-0xefffbeff irq 9 at device 11.0 on pci0 > rl1: Ethernet address: 00:40:ca:1d:ff:30 > miibus1: on rl1 > rlphy1: on miibus1 > rlphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > pcib1: on motherboard > pci2: on pcib1 > fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 > fdc0: FIFO enabled, 8 bytes threshold > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > atkbdc0: at port 0x60-0x6f on isa0 > atkbd0: irq 1 on atkbdc0 > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > sc0: on isa0 > sc0: VGA <16 virtual consoles, flags=0x200> > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 16550A > sio1 at port 0x2f8-0x2ff irq 3 on isa0 > sio1: type 16550A > ppc0: at port 0x378-0x37f irq 7 on isa0 > ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode > ppc0: FIFO with 16/16/16 bytes threshold > ppi0: on ppbus0 > lpt0: on ppbus0 > lpt0: Interrupt-driven port > plip0: on ppbus0 > IP packet filtering initialized, divert enabled, rule-based forwarding > enabled, default to accept, logging limited to 100 packets/entry by > default > ad0: 4126MB [8944/15/63] at ata0-master using UDMA33 > Mounting root from ufs:/dev/ad0s1a > > Jim Flowers > #4 ranked ISP on C|NET #1 in Ohio > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Paul Saab Technical Yahoo paul@mu.org - ps@yahoo-inc.com - ps@freebsd.org Do You .. uhh .. Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 27 14:45:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from piranha.amis.net (piranha.amis.net [212.18.32.3]) by hub.freebsd.org (Postfix) with ESMTP id CC80637C0E6 for ; Thu, 27 Jul 2000 14:45:40 -0700 (PDT) (envelope-from blaz@amis.net) Received: from titanic.medinet.si (titanic.medinet.si [212.18.32.66]) by piranha.amis.net (Postfix) with ESMTP id 502145D37; Thu, 27 Jul 2000 23:45:38 +0200 (CEST) Date: Thu, 27 Jul 2000 23:45:38 +0200 (CEST) From: Blaz Zupan X-Sender: blaz@titanic.medinet.si To: Jim Flowers Cc: freebsd-hackers@freebsd.org Subject: Re: fbsd 4.0Release In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Does this indicate that my new hardware is probably not going to work with > fbsd 4.0? [snip] > rl0: port 0xde00-0xdeff mem [snip] I notice that you use a RealTek card in your router. First of all, there is a bug in the RealTek driver in 4.0 that crashes the system (more info on that in PR kern/17582), this is probably what you are seeing. You should either upgrade the driver or upgrade the whole system to 4.0. Second, reconsider your choice of network card. I quote Bill Paul's comment in the rl driver sources: * The RealTek 8139 PCI NIC redefines the meaning of 'low end.' This is * probably the worst PCI ethernet controller ever made, with the possible * exception of the FEAST chip made by SMC. The 8139 supports bus-master * DMA, but it has a terrible interface that nullifies any performance * gains that bus-master DMA usually offers. ... * It's impossible given this rotten design to really achieve decent * performance at 100Mbps, unless you happen to have a 400Mhz PII or * some equally overmuscled CPU to drive it. I would think twice before using such a card in router.... Blaz Zupan, Medinet d.o.o, Linhartova 21, 2000 Maribor, Slovenia E-mail: blaz@amis.net, Tel: +386-2-320-6320, Fax: +386-2-320-6325 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 27 14:55:12 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 2A9B837C0EA for ; Thu, 27 Jul 2000 14:55:09 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id RAA03681; Thu, 27 Jul 2000 17:54:47 -0400 (EDT) Date: Thu, 27 Jul 2000 17:54:47 -0400 (EDT) From: Daniel Eischen To: Doug White Cc: =?Windows-1252?Q?Nicolas_L=E9onard?= , hackers@FreeBSD.ORG Subject: Re: kevent()/kqueue() in a multithreaded environment In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 27 Jul 2000, Doug White wrote: > On Wed, 26 Jul 2000, [Windows-1252] Nicolas L=E9onard wrote: >=20 > > I'm trying to use the new kqueue()/kevent() syscalls in the last=20 > > snapshot of FreeBSD 5.0. > > It works perfectly, except when I'm trying to use it in a multi- > > threaded program. > > The call of kevent() by my network thread blocks the other thread. > >=20 > > I look in the libc_r sources and I found that this syscall isn't=20 > > already wrapped. > >=20 > > Does anybody know if there is a patch or another tips to make it=20 > > work ? >=20 > You normally wouldn't mix kqueue and threads; you'd use kqueue to > *implement* threads. :-) Right. This is what we did for poll() -- wrapped it and used it to implement our libc_r threads. We could probably change libc_r's internal use of poll() to kqueue(), but I'm not sure we want to be beating a dead horse when a better threading solution is on the horizon. --=20 Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 27 15: 0:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 0044B37C0EA for ; Thu, 27 Jul 2000 15:00:32 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e6RM0Uk04650; Thu, 27 Jul 2000 15:00:30 -0700 (PDT) Date: Thu, 27 Jul 2000 15:00:30 -0700 From: Alfred Perlstein To: Jim Flowers Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: fbsd 4.0Release Message-ID: <20000727150029.F17222@fw.wintelcom.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: ; from jflowers@peony.ezo.net on Thu, Jul 27, 2000 at 05:36:23PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Jim Flowers [000727 14:35] wrote: > We have been using fbsd 4.0-RELEASE on a number of router applications > (IPV4). Recently we have switched to new hardware and now we get fatal > faults periodically. > > Typically these run with a minimum kernal using ipfw and natd and not much > more. 32 MB memory. > > Does this indicate that my new hardware is probably not going to work with > fbsd 4.0? > > Anything I can do to find out Yes, please see: http://www.freebsd.org/handbook/kerneldebug.html You shouldn't use Realtek, the cards are junk afaik, get an intel card or 3com. You should also look at increasing ram and/or maxusers or NMBCLUSTERS. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 27 15: 5:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id E35F037B8BF for ; Thu, 27 Jul 2000 15:05:37 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.7/nospam) with UUCP id AAA03758 for hackers@FreeBSD.ORG; Fri, 28 Jul 2000 00:05:34 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id A7DAE8894; Fri, 28 Jul 2000 00:01:08 +0200 (CEST) Date: Fri, 28 Jul 2000 00:01:08 +0200 From: Ollivier Robert To: hackers@FreeBSD.ORG Subject: Re: ELF rtld and environment variables... Message-ID: <20000728000108.A44138@keltia.freenix.fr> Mail-Followup-To: hackers@FreeBSD.ORG References: <20000727083057.A73044@gurney.reilly.home> <200007271247.MAA02788@park.jhs.no_domain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200007271247.MAA02788@park.jhs.no_domain>; from jhs@jhs.muc.de on Thu, Jul 27, 2000 at 02:47:03PM +0200 X-Operating-System: FreeBSD 5.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Julian Stacey: > just as today I'd use an encrypting file system on my new laptop, > but such file system don't exist on FreeBSD unfortunately. Ahem. Why did I sent an update for security/cfs to green a few months ago? :-) -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 5.0-CURRENT #80: Sun Jun 4 22:44:19 CEST 2000 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 27 16:24:46 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 39BA137C162 for ; Thu, 27 Jul 2000 16:24:40 -0700 (PDT) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with SMTP id TAA04240 for ; Thu, 27 Jul 2000 19:23:53 -0400 (EDT) Message-Id: <200007272323.TAA04240@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Thu, 27 Jul 2000 19:37:48 -0400 To: hackers@freebsd.org From: Dennis Subject: PTP ethernets Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is it possible to have only one address on an ethernet network? the only way that I can get it to work is with: ifconfig fxp0 200.1.1.1 netmask 255.255.255.255 route add fxp0 200.1.1.2 -interface fxp0 arp -s 200.1.1.2 ether-address Is there a way to get such a setup to work dynamically with ARPs? DB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 27 16:43:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from tinker.com (troll.tinker.com [216.91.221.226]) by hub.freebsd.org (Postfix) with ESMTP id BDC3237C16C for ; Thu, 27 Jul 2000 16:43:46 -0700 (PDT) (envelope-from kim@tinker.com) Received: by localhost (8.8.5/8.8.5) Received: by mail.tinker.com via smap (V2.0) id xma022726; Thu Jul 27 18:41:14 2000 Received: by localhost (8.8.8/8.8.8) id SAA05245; Thu, 27 Jul 2000 18:36:16 -0500 (CDT) Message-ID: <3980CA26.3978DCB8@tinker.com> Date: Thu, 27 Jul 2000 18:47:50 -0500 From: Kim Shrier Organization: Shrier and Deihl X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.2-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Dennis Cc: hackers@FreeBSD.ORG Subject: Re: PTP ethernets References: <200007272323.TAA04240@etinc.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If I understand your question correctly, all you need to do to set up a ptp ethernet link is: ifconfig fxp0 inet 200.1.1.1 200.1.1.2 Dennis wrote: > > Is it possible to have only one address on an ethernet network? the only > way that I can get it to work is with: > > ifconfig fxp0 200.1.1.1 netmask 255.255.255.255 > route add fxp0 200.1.1.2 -interface fxp0 > arp -s 200.1.1.2 ether-address > > Is there a way to get such a setup to work dynamically with ARPs? > > DB > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Kim Shrier - principal, Shrier and Deihl - mailto:kim@tinker.com Remote Unix Network Admin, Security, Internet Software Development Tinker Internet Services - Superior FreeBSD-based Web Hosting http://www.tinker.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 27 17:21: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 0DE1A37C17A for ; Thu, 27 Jul 2000 17:20:58 -0700 (PDT) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with SMTP id UAA04422; Thu, 27 Jul 2000 20:20:09 -0400 (EDT) Message-Id: <200007280020.UAA04422@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Thu, 27 Jul 2000 20:34:04 -0400 To: Kim Shrier From: Dennis Subject: Re: PTP ethernets Cc: hackers@FreeBSD.ORG In-Reply-To: <3980CA26.3978DCB8@tinker.com> References: <200007272323.TAA04240@etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 06:47 PM 7/27/00 -0500, Kim Shrier wrote: >If I understand your question correctly, all you need to do to set up >a ptp ethernet link is: > >ifconfig fxp0 inet 200.1.1.1 200.1.1.2 It *seems* like that should work, but it doesnt. When ping from one machine to another, the receiver doesnt respond and ip stats show "upsupported protocol" counter increasing accordingly. On the lan monitor the packet looks ok, so i dont quite understand why it doesnt work. dennis > > >Dennis wrote: >> >> Is it possible to have only one address on an ethernet network? the only >> way that I can get it to work is with: >> >> ifconfig fxp0 200.1.1.1 netmask 255.255.255.255 >> route add fxp0 200.1.1.2 -interface fxp0 >> arp -s 200.1.1.2 ether-address >> >> Is there a way to get such a setup to work dynamically with ARPs? >> >> DB >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-hackers" in the body of the message > >-- > Kim Shrier - principal, Shrier and Deihl - mailto:kim@tinker.com >Remote Unix Network Admin, Security, Internet Software Development > Tinker Internet Services - Superior FreeBSD-based Web Hosting > http://www.tinker.com/ > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 27 17:58: 1 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from peony.ezo.net (peony.ezo.net [206.102.130.11]) by hub.freebsd.org (Postfix) with ESMTP id 4174537B5CA for ; Thu, 27 Jul 2000 17:57:54 -0700 (PDT) (envelope-from jflowers@peony.ezo.net) Received: from localhost (jflowers@localhost) by peony.ezo.net (8.11.0.Beta3/8.11.0.Beta3) with ESMTP id e6S0xA478941; Thu, 27 Jul 2000 20:59:11 -0400 (EDT) Date: Thu, 27 Jul 2000 20:59:10 -0400 (EDT) From: Jim Flowers To: Paul Saab Cc: freebsd-hackers@freebsd.org Subject: Re: fbsd 4.0Release / 4.1-RC ? In-Reply-To: <20000727144446.A71534@elvis.mu.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I noticed in cvsuping RELENG_4 day before yesterday it came back as 4.1-RC. Does that also address the network stack panics? Jim Flowers #4 ranked ISP on C|NET #1 in Ohio On Thu, 27 Jul 2000, Paul Saab wrote: > There are known panics in the network stack in 4.0-RELEASE. You should > really upgrade to 4.1-RELEASE. > > paul > > Jim Flowers (jflowers@peony.ezo.net) wrote: > > We have been using fbsd 4.0-RELEASE on a number of router applications > > (IPV4). Recently we have switched to new hardware and now we get fatal > > faults periodically. > > > > Typically these run with a minimum kernal using ipfw and natd and not much > > more. 32 MB memory. > > > > Does this indicate that my new hardware is probably not going to work with > > fbsd 4.0? > > > > Anything I can do to find out > > > > message on fatal fault --------------------------- > > > > Fatal Trap 12: Page Fault While In Kernel Mode > > Fault Virtual Address =0x8 > > Fault Code =Supervisor Read, Page Not Present > > Instruction Pointer =0x8:;0xc018c370 > > Stack Pointer =0x10:0xxc470ee3c > > Frame Pointer =0x10:0xc470ee44 > > Code Segment =Base 0x0, Limit 0xfffff,Type 0x1b > > Processor Eflags =Interrupt Enabled,Resume,IOPL=0 > > Current Process =171 (Ping) > > Interrupt Mask = > > Trap Number =12 > > Panic:Page Fault To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 27 19:36:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [207.154.226.10]) by hub.freebsd.org (Postfix) with ESMTP id DF3CD37C193 for ; Thu, 27 Jul 2000 19:36:10 -0700 (PDT) (envelope-from paul@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1000) id B4C5A2B249; Thu, 27 Jul 2000 21:36:05 -0500 (CDT) Date: Thu, 27 Jul 2000 19:36:05 -0700 From: Paul Saab To: Jim Flowers Cc: freebsd-hackers@freebsd.org Subject: Re: fbsd 4.0Release / 4.1-RC ? Message-ID: <20000727193605.A75570@elvis.mu.org> References: <20000727144446.A71534@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from jflowers@peony.ezo.net on Thu, Jul 27, 2000 at 08:59:10PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes.. the problems were fixed a few months ago. paul Jim Flowers (jflowers@peony.ezo.net) wrote: > > I noticed in cvsuping RELENG_4 day before yesterday it came back as > 4.1-RC. Does that also address the network stack panics? > > Jim Flowers > #4 ranked ISP on C|NET #1 in Ohio > > On Thu, 27 Jul 2000, Paul Saab wrote: > > > There are known panics in the network stack in 4.0-RELEASE. You should > > really upgrade to 4.1-RELEASE. > > > > paul > > > > Jim Flowers (jflowers@peony.ezo.net) wrote: > > > We have been using fbsd 4.0-RELEASE on a number of router applications > > > (IPV4). Recently we have switched to new hardware and now we get fatal > > > faults periodically. > > > > > > Typically these run with a minimum kernal using ipfw and natd and not much > > > more. 32 MB memory. > > > > > > Does this indicate that my new hardware is probably not going to work with > > > fbsd 4.0? > > > > > > Anything I can do to find out > > > > > > message on fatal fault --------------------------- > > > > > > Fatal Trap 12: Page Fault While In Kernel Mode > > > Fault Virtual Address =0x8 > > > Fault Code =Supervisor Read, Page Not Present > > > Instruction Pointer =0x8:;0xc018c370 > > > Stack Pointer =0x10:0xxc470ee3c > > > Frame Pointer =0x10:0xc470ee44 > > > Code Segment =Base 0x0, Limit 0xfffff,Type 0x1b > > > Processor Eflags =Interrupt Enabled,Resume,IOPL=0 > > > Current Process =171 (Ping) > > > Interrupt Mask = > > > Trap Number =12 > > > Panic:Page Fault > -- Paul Saab Technical Yahoo paul@mu.org - ps@yahoo-inc.com - ps@freebsd.org Do You .. uhh .. Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 27 19:56:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp9.xs4all.nl (smtp9.xs4all.nl [194.109.127.135]) by hub.freebsd.org (Postfix) with ESMTP id 77D5F37B709 for ; Thu, 27 Jul 2000 19:56:28 -0700 (PDT) (envelope-from whs@xs4all.nl) Received: from localhost (dc2-modem867.dial.xs4all.nl [194.109.131.99]) by smtp9.xs4all.nl (8.9.3/8.9.3) with SMTP id EAA27450 for ; Fri, 28 Jul 2000 04:56:26 +0200 (CEST) Message-Id: <200007280256.EAA27450@smtp9.xs4all.nl> Date: Fri, 28 Jul 2000 02:28:53 +0000 From: "W.H.Scholten" <"whs"@xs4all.nl> X-Mailer: Mozilla 3.04 (X11; I; FreeBSD 3.3-RELEASE i386) MIME-Version: 1.0 To: hackers@freebsd.org Subject: Re: uncool MO disk problems References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG L.S. Update on previous mail a while back. I tried the latest sym driver from the CVS tree (into fbsd 3.3) but little has changed (haven't checked what happens with 640MB 2048 b/s disks yet): > 4. Formatting ufs on fbsd: > newfs hangs (unkillable). This now works. > 3. ufs disk formatted on obsd: > I cannot use da0a but mounting da0 (with -t ufs) works. > After I change the disklabel's '16 partitions:' to '8 partitions:' I can > mount da0a (and read/write) but unmounting fails (umount -> unkillable > process). No change (also goes for a disk formatted under fbsd). Here's what happens after I mount the disk, and have written something to it, then try to unmount: ----------------------------------------------------------------------- ps axl for the umount process shows: cdwait D+ When I now halt the machine: after a short while: syncing disks... done then after about 3 minutes I get into DDB: page fault while in kernel mode kernel: type 12 trap, code=0 stopped at ffs_sync+0x1f movl 0xc(%esi),%esi a vm/vfs problem? Second situation: mounting a write protected disk (RW, but the OS should change that itself to a read only mount if the disk is write protected, which it does recognize at mount time). ------------------------------------------------------------------------ unmounting failed, at reboot the machine tried it some more, gave up said: giving up: rebooting which it did; unfortunately, it didn't unmount the file systems which could be unmounted so started checking the ffs partitions next time I booted fbsd. As apart from Gerard's response there were no reactions of anyone with similar problems nor of people using MO drives without problems, can I assume everyone using MO drives nuked fbsd and uses something else now? Or does anyone use MO drives with 4.0 or 4.1 without the problems I mentioned (in this and my previous mail) ? Btw, I compiled the kernel with DDB now so if there's any use for it I can give the trace information etc. Wouter PS. CC responses to my mail address please. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 27 21:54:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from idet.rsn.hk-r.se (idet.rsn.hk-r.se [194.47.142.179]) by hub.freebsd.org (Postfix) with ESMTP id E674637B9C5 for ; Thu, 27 Jul 2000 21:53:55 -0700 (PDT) (envelope-from bjorn@tornqvist.net) Received: from tornqvist.net ([194.52.130.37]) by idet.rsn.hk-r.se (8.9.3/8.9.3) with ESMTP id GAA97046 for ; Fri, 28 Jul 2000 06:50:26 +0200 (CEST) (envelope-from bjorn@tornqvist.net) Message-ID: <398111DA.443B41F9@tornqvist.net> Date: Fri, 28 Jul 2000 06:53:46 +0200 From: Bjorn Tornqvist Organization: West Entertainment Solutions & Technologies AB X-Mailer: Mozilla 4.72 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: BSD,Posix,Linux Threading - Are they really useable? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Howdy all, I must have missed something very importand w.r.t threads under FreeBSD, here's what I've come up with during the last week: PosixThreads are userland threads - if one thread blocks on i/o the whole process is blocked. Which makes PosixThreads rather useless. FreeBSD Kernel-threads (dunno what they are called actually) can't be used natively!? (Searched the archives and found an explanation that the only way to access normal kernel SMP-thread functionality is to use LinuxThreads) LinuxThreads: While they are kernel-threads, if one thread receives an uncought signal, all threads are killed (as they should be), but the resulting coredump is useless since it only captures the state of the last-killed-thread (or process or whatever you want to call it. LinuxThreads seems like just a big hack...). How do I use normal kernel-threads that will allow all nonblocked threads in a process to work concurrently, *and* will generate useful coredumps? There must be a way - I've just haven't found any documentation on the subject. And yes, I must use threads - fork()ing will only give me the same trouble as LinuxThreads (a process sharing memory with another won't give a corefile). Please help me with this one. //Bjorn Tornqvist, West Entertainment Solutions & Technologies AB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 27 22:41:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mta5.rcsntx.swbell.net (mta5.rcsntx.swbell.net [151.164.30.29]) by hub.freebsd.org (Postfix) with ESMTP id E42C737B50D for ; Thu, 27 Jul 2000 22:41:32 -0700 (PDT) (envelope-from chris@holly.calldei.com) Received: from holly.calldei.com ([208.191.149.190]) by mta5.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9) with ESMTP id <0FYE0024Y7SCSZ@mta5.rcsntx.swbell.net> for freebsd-hackers@FreeBSD.ORG; Fri, 28 Jul 2000 00:41:00 -0500 (CDT) Received: (from chris@localhost) by holly.calldei.com (8.9.3/8.9.3) id AAA41058; Fri, 28 Jul 2000 00:39:14 -0500 (CDT envelope-from chris) Date: Fri, 28 Jul 2000 00:39:14 -0500 From: Chris Costello Subject: Re: BSD,Posix,Linux Threading - Are they really useable? In-reply-to: <398111DA.443B41F9@tornqvist.net> To: Bjorn Tornqvist Cc: freebsd-hackers@FreeBSD.ORG Reply-To: chris@calldei.com Message-id: <20000728003913.K37935@holly.calldei.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i References: <398111DA.443B41F9@tornqvist.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, July 28, 2000, Bjorn Tornqvist wrote: > PosixThreads are userland threads - if one thread blocks on i/o the > whole process is blocked. Which makes PosixThreads rather useless. That is incorrect. FreeBSD's userland pthread implementation does not block the whole process on I/O. POSIX does not specify this behavior either. > FreeBSD Kernel-threads (dunno what they are called actually) can't be > used natively!? (Searched the archives and found an explanation that the > only way to access normal kernel SMP-thread functionality is to use > LinuxThreads) FreeBSD's kernel threads are for separate threads of execution in the kernel and aren't the same thing as threads for a user process. > LinuxThreads: While they are kernel-threads, if one thread receives an > uncought signal, all threads are killed (as they should be), but the > resulting coredump is useless since it only captures the state of the > last-killed-thread (or process or whatever you want to call it. > LinuxThreads seems like just a big hack...). LinuxThreads on FreeBSD cannot be kernel threads because that would require modifications to our scheduler which simply have not been made. -- |Chris Costello |Save energy: Drive a smaller shell. `------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 27 23: 2:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from piranha.amis.net (piranha.amis.net [212.18.32.3]) by hub.freebsd.org (Postfix) with ESMTP id DB34E37B763 for ; Thu, 27 Jul 2000 23:02:14 -0700 (PDT) (envelope-from blaz@amis.net) Received: from titanic.medinet.si (titanic.medinet.si [212.18.32.66]) by piranha.amis.net (Postfix) with ESMTP id AEC615D19; Fri, 28 Jul 2000 08:02:12 +0200 (CEST) Date: Fri, 28 Jul 2000 08:02:12 +0200 (CEST) From: Blaz Zupan X-Sender: blaz@titanic.medinet.si To: Jim Flowers Cc: freebsd-hackers@freebsd.org Subject: Re: fbsd 4.0Release In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > bug in the RealTek driver in 4.0 that crashes the system (more info on that in > PR kern/17582), this is probably what you are seeing. You should either > upgrade the driver or upgrade the whole system to 4.0. ^^^^ Oops, that should of course read 4.1. Blaz Zupan, Medinet d.o.o, Linhartova 21, 2000 Maribor, Slovenia E-mail: blaz@amis.net, Tel: +386-2-320-6320, Fax: +386-2-320-6325 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 28 0:50:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from kbgroup.co.nz (gateway.kbgroup.co.nz [203.96.151.81]) by hub.freebsd.org (Postfix) with ESMTP id C467937B562 for ; Fri, 28 Jul 2000 00:50:19 -0700 (PDT) (envelope-from david.preece@niceshotbill.com) Received: from kb_exchange.kbgroup.co.nz ([202.202.203.10]) by gateway.kbgroup.co.nz with ESMTP id <115202>; Fri, 28 Jul 2000 20:10:30 +1200 Received: by internet.kbgroup.co.nz with Internet Mail Service (5.5.2650.21) id ; Fri, 28 Jul 2000 20:00:02 +1200 Message-ID: <67B808B0DD93D211ABEE0000B498356B36176C@internet.kbgroup.co.nz> From: "David Preece (Nice Shot Bill)" To: freebsd-hackers@freebsd.org Subject: Re:Neil Clayton, Sending personal mail to this list, Sorry. MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Date: Fri, 28 Jul 2000 20:10:24 +1200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Idiot. Never forward an email about how terrible Realtek are to a linux freak, they'll completely fail to reply properly. Some people just should not be allowed computers, they may hurt themselves. Dave :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 28 2:19: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from grunt.vl.net.ua (grunt.vl.net.ua [194.44.80.198]) by hub.freebsd.org (Postfix) with ESMTP id 9015B37B746 for ; Fri, 28 Jul 2000 02:18:50 -0700 (PDT) (envelope-from news@grunt.vl.net.ua) Received: from news by grunt.vl.net.ua with local (Exim 3.12 #2) id 13I6I4-000Hk8-00 for freebsd-hackers@freebsd.org; Fri, 28 Jul 2000 12:18:48 +0300 To: freebsd-hackers@freebsd.org Subject: Majordomo results Date: 28 Jul 2000 12:18:41 +0300 Message-ID: <20000728091832.6724F37B93F@hub.freebsd.org> X-Trace: uran.kharkiv.net 964775928 66634 127.0.0.1 (28 Jul 2000 09:18:48 GMT) X-Complaints-To: usenet@news.kharkiv.net NNTP-Posting-Date: 28 Jul 2000 09:18:48 GMT X-Received: from hub.freebsd.org (hub.FreeBSD.ORG [204.216.27.18]) X-Received: by hub.freebsd.org (Postfix, from userid 538) X-To: freebsd-hackers-m@kharkiv.net X-Reply-To: Majordomo@FreeBSD.ORG X-Via: News-To-Mail v1.0 From: Majordomo@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -- >>>> subscribe freebsd-hackers **** Your request to Majordomo@FreeBSD.ORG: **** **** subscribe freebsd-hackers freebsd-hackers-m@kharkiv.net **** **** must be authenticated. To accomplish this, another request must be **** sent in with an authorization key, which has been sent to: **** freebsd-hackers-m@kharkiv.net **** **** If the message is not received, there is generally a problem with **** the address. Before reporting this as a problem, please note the **** following: **** **** You only need to give an address to the subscribe command if you want **** to receive list mail at a different address from where you sent the **** command. Otherwise you can simply omit it. **** **** If you do give an address to the subscribe command, it must be a legal **** address. It should not consist solely of your name. The address must **** point to a machine that is reachable from the list server. **** **** If you have any questions about the policy of the list owner, please **** contact "freebsd-hackers-approval@FreeBSD.ORG". **** **** Thanks! **** **** Majordomo@FreeBSD.ORG >>>> --- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 28 2:19: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from grunt.vl.net.ua (grunt.vl.net.ua [194.44.80.198]) by hub.freebsd.org (Postfix) with ESMTP id F302737B570 for ; Fri, 28 Jul 2000 02:18:50 -0700 (PDT) (envelope-from news@grunt.vl.net.ua) Received: from news by grunt.vl.net.ua with local (Exim 3.12 #2) id 13I6I4-000HkD-00 for freebsd-hackers@freebsd.org; Fri, 28 Jul 2000 12:18:48 +0300 To: freebsd-hackers@freebsd.org Subject: Confirmation for subscribe freebsd-hackers Date: 28 Jul 2000 12:18:40 +0300 Message-ID: <20000728091832.5F58837B91D@hub.freebsd.org> X-Trace: uran.kharkiv.net 964775928 66628 127.0.0.1 (28 Jul 2000 09:18:48 GMT) X-Complaints-To: usenet@news.kharkiv.net NNTP-Posting-Date: 28 Jul 2000 09:18:48 GMT X-Received: from hub.freebsd.org (hub.FreeBSD.ORG [204.216.27.18]) X-Received: by hub.freebsd.org (Postfix, from userid 538) X-To: freebsd-hackers-m@kharkiv.net X-Reply-To: Majordomo@FreeBSD.ORG X-Via: News-To-Mail v1.0 From: Majordomo@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -- Please be sure to read the charters before subscribing or sending mail to any FreeBSD mailing list for an explanation of which topics are relevant for a given list and what types of postings are and are not allowed. They may be found at: http://www.freebsd.org/handbook/eresources.html#ERESOURCES-MAIL Someone (possibly you) has requested that your email address be added to or deleted from the mailing list "freebsd-hackers@FreeBSD.ORG". If you really want this action to be taken, please send the following commands (exactly as shown) back to "Majordomo@FreeBSD.ORG": auth 824d0397 subscribe freebsd-hackers freebsd-hackers-m@kharkiv.net If you do not want this action to be taken, simply ignore this message and the request will be disregarded. If your mailer will not allow you to send the entire command as a single line, you may split it using backslashes, like so: auth 824d0397 subscribe freebsd-hackers \ freebsd-hackers-m@kharkiv.net If you have any questions about the policy of the list owner, please contact "freebsd-hackers-approval@FreeBSD.ORG". Thanks! Majordomo@FreeBSD.ORG --- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 28 3: 7:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from grunt.vl.net.ua (grunt.vl.net.ua [194.44.80.198]) by hub.freebsd.org (Postfix) with ESMTP id 7DAD637C1A9 for ; Fri, 28 Jul 2000 03:07:04 -0700 (PDT) (envelope-from news@grunt.vl.net.ua) Received: from news by grunt.vl.net.ua with local (Exim 3.12 #2) id 13I72k-000IEZ-00 for freebsd-hackers@freebsd.org; Fri, 28 Jul 2000 13:07:02 +0300 To: freebsd-hackers@freebsd.org Subject: Welcome to freebsd-hackers Date: 28 Jul 2000 13:06:56 +0300 Message-ID: <20000728093118.EC2C637C1D5@hub.freebsd.org> X-Trace: uran.kharkiv.net 964778822 69150 127.0.0.1 (28 Jul 2000 10:07:02 GMT) X-Complaints-To: usenet@news.kharkiv.net NNTP-Posting-Date: 28 Jul 2000 10:07:02 GMT X-Received: from hub.freebsd.org (hub.FreeBSD.ORG [204.216.27.18]) X-Received: by hub.freebsd.org (Postfix, from userid 538) X-To: freebsd-hackers-m@kharkiv.net X-Reply-To: Majordomo@FreeBSD.ORG X-Via: News-To-Mail v1.0 From: Majordomo@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -- Welcome to the freebsd-hackers mailing list! Please save this message for future reference. Thank you. If you ever want to remove yourself from this mailing list, you can send mail to with the following command in the body of your email message: unsubscribe freebsd-hackers or from another account, besides freebsd-hackers-m@kharkiv.net: unsubscribe freebsd-hackers freebsd-hackers-m@kharkiv.net If you ever need to get in contact with the owner of the list, (if you have trouble unsubscribing, or have questions about the list itself) send email to . This is the general rule for most mailing lists when you need to contact a human. Here's the general information for the list you've subscribed to, in case you don't already have it: FREEBSD-HACKERS Technical discussions This is a forum for technical discussions related to FreeBSD. This is the primary technical mailing list. It is for individuals actively working on FreeBSD, to bring up problems or discuss alternative solutions. Individuals interested in following the technical discussion are also welcome. --- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 28 3: 7:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from grunt.vl.net.ua (grunt.vl.net.ua [194.44.80.198]) by hub.freebsd.org (Postfix) with ESMTP id DD82B37C1AD for ; Fri, 28 Jul 2000 03:07:06 -0700 (PDT) (envelope-from news@grunt.vl.net.ua) Received: from news by grunt.vl.net.ua with local (Exim 3.12 #2) id 13I72m-000IEe-00 for freebsd-hackers@freebsd.org; Fri, 28 Jul 2000 13:07:04 +0300 To: freebsd-hackers@freebsd.org Subject: Majordomo results Date: 28 Jul 2000 13:06:58 +0300 Message-ID: <20000728093118.F3DF837C1FF@hub.freebsd.org> X-Trace: uran.kharkiv.net 964778824 69163 127.0.0.1 (28 Jul 2000 10:07:04 GMT) X-Complaints-To: usenet@news.kharkiv.net NNTP-Posting-Date: 28 Jul 2000 10:07:04 GMT X-Received: from hub.freebsd.org (hub.FreeBSD.ORG [204.216.27.18]) X-Received: by hub.freebsd.org (Postfix, from userid 538) X-To: freebsd-hackers-m@kharkiv.net X-Reply-To: Majordomo@FreeBSD.ORG X-Via: News-To-Mail v1.0 From: Majordomo@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -- >>>> auth 824d0397 subscribe freebsd-hackers Succeeded. >>>> --- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 28 4:19:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from c2bapps1.btconnect.com (c2bapps1.btconnect.com [193.113.209.21]) by hub.freebsd.org (Postfix) with SMTP id 934A237BF25 for ; Fri, 28 Jul 2000 04:19:31 -0700 (PDT) (envelope-from rapid@pro-rally.com) Received: from richards (actually host 62-6-209-107.btconnect.com) by c2bapps1 with SMTP (XT-PP); Fri, 28 Jul 2000 12:19:08 +0100 Message-ID: <003201bff886$2c55f480$6bd1063e@richards> From: Richard Stoodley To: hackers Subject: CRACK - Dreamweaver Date: Fri, 28 Jul 2000 12:22:52 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_002F_01BFF88E.8D388800" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.1 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_002F_01BFF88E.8D388800 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi Can you tell me where I can get Crack for Dreamweaver 3 ?/ Thanks rapid@pro-rally.com ------=_NextPart_000_002F_01BFF88E.8D388800 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi Can you tell me where I can get = Crack for=20 Dreamweaver 3 ?/
 
Thanks
 
rapid@pro-rally.com
 
------=_NextPart_000_002F_01BFF88E.8D388800-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 28 4:26:46 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id EF1D837C05D; Fri, 28 Jul 2000 04:26:44 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id EAA71055; Fri, 28 Jul 2000 04:26:44 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Fri, 28 Jul 2000 04:26:44 -0700 (PDT) From: Kris Kennaway To: Richard Stoodley Cc: hackers Subject: Re: CRACK - Dreamweaver In-Reply-To: <003201bff886$2c55f480$6bd1063e@richards> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 28 Jul 2000, Richard Stoodley wrote: > Hi Can you tell me where I can get Crack for Dreamweaver 3 ?/ Go to http://2130706433/crackz/index.html for all of your 0-day cracks. The site is busy though, you might have to keep retrying for a while before you get in. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 28 4:34: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hermes.research.kpn.com (hermes.research.kpn.com [139.63.192.8]) by hub.freebsd.org (Postfix) with ESMTP id 3937E37B551 for ; Fri, 28 Jul 2000 04:33:59 -0700 (PDT) (envelope-from K.J.Koster@kpn.com) Received: from l04.research.kpn.com (l04.research.kpn.com [139.63.192.204]) by research.kpn.com (PMDF V5.2-31 #42699) with ESMTP id <01JSAW88TCPW0004VD@research.kpn.com> for hackers@FreeBSD.ORG; Fri, 28 Jul 2000 13:33:50 +0200 Received: by l04.research.kpn.com with Internet Mail Service (5.5.2650.21) id ; Fri, 28 Jul 2000 13:33:50 +0100 Content-return: allowed Date: Fri, 28 Jul 2000 13:33:49 +0100 From: "Koster, K.J." Subject: RE: CRACK - Dreamweaver To: 'Richard Stoodley' Cc: hackers Message-id: <59063B5B4D98D311BC0D0001FA7E4522026D7723@l04.research.kpn.com> MIME-version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Richard, > > Can you tell me where I can get Crack for Dreamweaver 3 ?/ > http://www.macromedia.com/software/dreamweaver/buy/ They'll even send you a pretty box and some books. Kees Jan PS. I think you're confusing the terms "cracker" and "hacker". ================================================= TV is the worst of both worlds. It's not as good at words as radio is because the pictures are a distraction which demand attention, and it's not as good as cinema because the pictures are not nearly as good. Douglas Adams To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 28 7:29:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fling.sanbi.ac.za (fling.sanbi.ac.za [196.38.142.119]) by hub.freebsd.org (Postfix) with ESMTP id 3B19037C226 for ; Fri, 28 Jul 2000 07:29:01 -0700 (PDT) (envelope-from pvh@egenetics.com) Received: from pvh (helo=localhost) by fling.sanbi.ac.za with local-esmtp (Exim 3.13 #4) id 13IB8E-000PvS-00 for hackers@freebsd.org; Fri, 28 Jul 2000 16:28:58 +0200 Date: Fri, 28 Jul 2000 16:28:58 +0200 (SAST) From: Peter van Heusden X-Sender: pvh@fling.sanbi.ac.za To: hackers@freebsd.org Subject: Documentation for pcm/voxware sound drivers? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there complete documentation for pcm / voxware sound drivers anywhere? I'd like to play around with sound on my 4-STABLE box (soundcard is a SB Live), but there documentation in the man pages, and on Luigi Rizzo's page, doesn't completely cover the ioctls and uses of the various sound devices. Thanks for any answers. Peter -- Peter van Heusden pvh@egenetics.com Electric Genetics To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 28 8: 4:55 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hda.hda.com (host65.hda.com [63.104.68.65]) by hub.freebsd.org (Postfix) with ESMTP id 4AA9937C1D8 for ; Fri, 28 Jul 2000 08:04:52 -0700 (PDT) (envelope-from dufault@hda.hda.com) Received: (from dufault@localhost) by hda.hda.com (8.9.3/8.9.3) id LAA27583 for hackers@freebsd.org; Fri, 28 Jul 2000 11:07:09 -0400 (EDT) (envelope-from dufault) From: Peter Dufault Message-Id: <200007281507.LAA27583@hda.hda.com> Subject: core dumps when mmap'd to large sparse files To: hackers@freebsd.org Date: Fri, 28 Jul 2000 11:07:04 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a program where I mmap a huge sparse file. If I fault and generate a core dump it proceeds to do something until the disk is full, but the disk is then left not full and a perfectly good core dump of a reasonable size is left. Can anyone explain? This is with 4.0. Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Fail-Safe systems, Agency approval To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 28 8:21:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bongo.rbc.ru (bongo.rbc.ru [212.111.65.120]) by hub.freebsd.org (Postfix) with ESMTP id ED7C937C2A5 for ; Fri, 28 Jul 2000 08:21:20 -0700 (PDT) (envelope-from koma@rbc.ru) Received: from bingo.rbc.ru (bingo.rbc.ru [212.111.65.28]) by bongo.rbc.ru (Postfix) with ESMTP id D4E2714F98 for ; Fri, 28 Jul 2000 19:21:16 +0400 (MSD) Received: from stone.rbc.ru (stone.rbc.ru [195.218.168.68]) by bingo.rbc.ru (8.9.3/8.9.3) with ESMTP id TAA72399; Fri, 28 Jul 2000 19:21:10 +0400 (MSD) (envelope-from koma@rbc.ru) Date: Fri, 28 Jul 2000 19:21:10 +0400 (MSD) From: Maxim Konovalov To: freebsd-hackers@freebsd.org Cc: koma@rbc.ru Subject: vinum striping quiestion Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I've got a question about vinum. There are two scsi disks with vinum stripe. Here is a vinum config: drive a device /dev/da2s1e drive b device /dev/da3s1e volume vinum0 plex name vinum0.p0 org striped 1024s vol vinum0 sd name vinum0.p0.s0 drive a plex vinum0.p0 len 34791424s driveoffset 265s plexoffset 0s sd name vinum0.p0.s1 drive b plex vinum0.p0 len 34791424s driveoffset 265s plexoffset 1024s # uname -sr FreeBSD 4.1-STABLE There are not any other fs on these disks. The problem is - when I run iozone (iozone 4096 /logs/io0.tmp) I get a very strange result: # iostat -d da1 da3 10 da1 da3 KB/t tps MB/s KB/t tps MB/s 0.00 0 0.00 0.00 0 0.00 4.50 107 0.47 0.00 0 0.00 4.51 98 0.43 0.00 0 0.00 4.50 116 0.51 0.00 0 0.00 4.49 117 0.52 0.00 0 0.00 4.50 111 0.49 0.00 0 0.00 .... You see, there is not activity on da3. Are there any explanations? Thanks, maxim - -- Maxim Konovalov, mailto: koma@rbc.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 28 8:38:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66]) by hub.freebsd.org (Postfix) with ESMTP id 4F6AA37C2E6 for ; Fri, 28 Jul 2000 08:38:18 -0700 (PDT) (envelope-from nate@yogotech.com) Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.123.131]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id JAA14227; Fri, 28 Jul 2000 09:38:09 -0600 (MDT) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id JAA22915; Fri, 28 Jul 2000 09:38:03 -0600 (MDT) (envelope-from nate) Date: Fri, 28 Jul 2000 09:38:03 -0600 (MDT) Message-Id: <200007281538.JAA22915@nomad.yogotech.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: chris@calldei.com Cc: Bjorn Tornqvist , freebsd-hackers@FreeBSD.ORG Subject: Re: BSD,Posix,Linux Threading - Are they really useable? In-Reply-To: <20000728003913.K37935@holly.calldei.com> References: <398111DA.443B41F9@tornqvist.net> <20000728003913.K37935@holly.calldei.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > PosixThreads are userland threads - if one thread blocks on i/o the > > whole process is blocked. Which makes PosixThreads rather useless. > > That is incorrect. FreeBSD's userland pthread implementation > does not block the whole process on I/O. POSIX does not specify > this behavior either. Actually, sometimes it does (for example when reading from an I/O device where select can't be used succesfully). > > FreeBSD Kernel-threads (dunno what they are called actually) can't be > > used natively!? (Searched the archives and found an explanation that the > > only way to access normal kernel SMP-thread functionality is to use > > LinuxThreads) > > FreeBSD's kernel threads are for separate threads of execution > in the kernel and aren't the same thing as threads for a user > process. You're missing the point. He's asking for 'kernel threads' so that multiple independant thread of execution for a given 'userland process' can be running simulataneously (virtually on a UP, and realistically on a MP). Currently, FreeBSD doesn't have any such thing, although there are a number of design documentations on how it would be done, if it were to be done. The recent work that Matt Dillon and Greg Lehey have been doing is intended to make this more possible. > > LinuxThreads: While they are kernel-threads, if one thread receives an > > uncought signal, all threads are killed (as they should be), but the > > resulting coredump is useless since it only captures the state of the > > last-killed-thread (or process or whatever you want to call it. > > LinuxThreads seems like just a big hack...). > > LinuxThreads on FreeBSD cannot be kernel threads because that > would require modifications to our scheduler which simply have > not been made. Not quite. LinuxThreads on FreeBSD *ARE* kernel threads, but they aren't part of the regular kernel because they aren't adequate, and they have the wrong license model to be used by default. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 28 10:53:51 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id 22E8137B7E5 for ; Fri, 28 Jul 2000 10:53:40 -0700 (PDT) (envelope-from ben@scientia.demon.co.uk) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=exim) by scientia.demon.co.uk with esmtp (Exim 3.15 #1) id 13IEGq-000BVb-00; Fri, 28 Jul 2000 18:50:04 +0100 Received: (from ben) by strontium.scientia.demon.co.uk (Exim 3.15 #1) id 13IEGq-000OTl-00; Fri, 28 Jul 2000 18:50:04 +0100 Date: Fri, 28 Jul 2000 18:50:03 +0100 From: Ben Smithurst To: Richard Stoodley Cc: hackers Subject: Re: CRACK - Dreamweaver Message-ID: <20000728185003.U59315@strontium.scientia.demon.co.uk> References: <003201bff886$2c55f480$6bd1063e@richards> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <003201bff886$2c55f480$6bd1063e@richards> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Richard Stoodley wrote: > Can you tell me where I can get Crack Try -- Ben Smithurst / ben@FreeBSD.org / PGP: 0x99392F7D FreeBSD Documentation Project / To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 28 12: 0:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from majordomo2.umd.edu (majordomo2.umd.edu [128.8.10.7]) by hub.freebsd.org (Postfix) with ESMTP id 3FA4837BC81 for ; Fri, 28 Jul 2000 12:00:03 -0700 (PDT) (envelope-from culverk@wam.umd.edu) Received: from rac7.wam.umd.edu (root@rac7.wam.umd.edu [128.8.10.147]) by majordomo2.umd.edu (8.9.3/8.9.3) with ESMTP id OAA14627; Fri, 28 Jul 2000 14:59:48 -0400 (EDT) Received: from rac7.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac7.wam.umd.edu (8.9.3/8.9.3) with SMTP id OAA26772; Fri, 28 Jul 2000 14:59:58 -0400 (EDT) Received: from localhost (culverk@localhost) by rac7.wam.umd.edu (8.9.3/8.9.3) with ESMTP id OAA26768; Fri, 28 Jul 2000 14:59:58 -0400 (EDT) X-Authentication-Warning: rac7.wam.umd.edu: culverk owned process doing -bs Date: Fri, 28 Jul 2000 14:59:58 -0400 (EDT) From: Kenneth Wayne Culver To: Bjorn Tornqvist Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: BSD,Posix,Linux Threading - Are they really useable? In-Reply-To: <398111DA.443B41F9@tornqvist.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Currently as far as I know, there isn't really a way to do this, although much work is being done in -CURRENT to fix this. ================================================================= | Kenneth Culver | FreeBSD: The best NT upgrade | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= On Fri, 28 Jul 2000, Bjorn Tornqvist wrote: > Howdy all, > > I must have missed something very importand w.r.t threads under FreeBSD, > here's what I've come up with during the last week: > > PosixThreads are userland threads - if one thread blocks on i/o the > whole process is blocked. Which makes PosixThreads rather useless. > > FreeBSD Kernel-threads (dunno what they are called actually) can't be > used natively!? (Searched the archives and found an explanation that the > only way to access normal kernel SMP-thread functionality is to use > LinuxThreads) > > LinuxThreads: While they are kernel-threads, if one thread receives an > uncought signal, all threads are killed (as they should be), but the > resulting coredump is useless since it only captures the state of the > last-killed-thread (or process or whatever you want to call it. > LinuxThreads seems like just a big hack...). > > How do I use normal kernel-threads that will allow all nonblocked > threads in a process to work concurrently, *and* will generate useful > coredumps? > > There must be a way - I've just haven't found any documentation on the > subject. And yes, I must use threads - fork()ing will only give me the > same trouble as LinuxThreads (a process sharing memory with another > won't give a corefile). > > Please help me with this one. > > //Bjorn Tornqvist, West Entertainment Solutions & Technologies AB > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 28 12:16:18 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mta5.rcsntx.swbell.net (mta5.rcsntx.swbell.net [151.164.30.29]) by hub.freebsd.org (Postfix) with ESMTP id DC72637BC18 for ; Fri, 28 Jul 2000 12:16:12 -0700 (PDT) (envelope-from chris@holly.calldei.com) Received: from holly.calldei.com ([208.191.149.190]) by mta5.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9) with ESMTP id <0FYF00L9E9A0LQ@mta5.rcsntx.swbell.net> for freebsd-hackers@FreeBSD.ORG; Fri, 28 Jul 2000 14:10:49 -0500 (CDT) Received: (from chris@localhost) by holly.calldei.com (8.9.3/8.9.3) id OAA42362; Fri, 28 Jul 2000 14:08:55 -0500 (CDT envelope-from chris) Date: Fri, 28 Jul 2000 14:08:54 -0500 From: Chris Costello Subject: Re: BSD,Posix,Linux Threading - Are they really useable? In-reply-to: <200007281538.JAA22915@nomad.yogotech.com> To: Nate Williams Cc: Bjorn Tornqvist , freebsd-hackers@FreeBSD.ORG Reply-To: chris@calldei.com Message-id: <20000728140854.L37935@holly.calldei.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i References: <398111DA.443B41F9@tornqvist.net> <20000728003913.K37935@holly.calldei.com> <200007281538.JAA22915@nomad.yogotech.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, July 28, 2000, Nate Williams wrote: > > That is incorrect. FreeBSD's userland pthread implementation > > does not block the whole process on I/O. POSIX does not specify > > this behavior either. > Actually, sometimes it does (for example when reading from an I/O device > where select can't be used succesfully). Hmm. That's true. And that's where uthreads has its main problems as I understand it. > > > FreeBSD Kernel-threads (dunno what they are called actually) can't be > > > used natively!? (Searched the archives and found an explanation that the > > > only way to access normal kernel SMP-thread functionality is to use > > > LinuxThreads) > > FreeBSD's kernel threads are for separate threads of execution > > in the kernel and aren't the same thing as threads for a user > > process. > You're missing the point. He's asking for 'kernel threads' so that > multiple independant thread of execution for a given 'userland process' > can be running simulataneously (virtually on a UP, and realistically on > a MP). I thought he had seen the term 'kernel threads' in the context of FreeBSD before, likely in the context of kthread_create() in the kernel. -- |Chris Costello |May the force be... your umbrella! - Plucky Duck `------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 28 12:46: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id 1BD8B37BCE3 for ; Fri, 28 Jul 2000 12:46:06 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.3/8.9.3) id MAA26198; Fri, 28 Jul 2000 12:45:56 -0700 (PDT) (envelope-from archie) From: Archie Cobbs Message-Id: <200007281945.MAA26198@bubba.whistle.com> Subject: Re: kevent()/kqueue() in a multithreaded environment In-Reply-To: from Doug White at "Jul 27, 2000 02:08:43 pm" To: Doug White Date: Fri, 28 Jul 2000 12:45:56 -0700 (PDT) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug White writes: > You normally wouldn't mix kqueue and threads; you'd use kqueue to > *implement* threads. :-) > > AFAIK kqueue hasn't been made threadsafe, you'll have to bug > jlemon@freebsd.org about it. Patches gladly accepted :) I may be just being stupid but I don't understand that last sentence. I thought kqueue() and kevent() were system calls... how can they not be thread safe? -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 28 13:14:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 633CA37B5F8 for ; Fri, 28 Jul 2000 13:14:17 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id QAA09241; Fri, 28 Jul 2000 16:13:58 -0400 (EDT) Date: Fri, 28 Jul 2000 16:13:58 -0400 (EDT) From: Daniel Eischen To: Archie Cobbs Cc: Doug White , hackers@FreeBSD.ORG Subject: Re: kevent()/kqueue() in a multithreaded environment In-Reply-To: <200007281945.MAA26198@bubba.whistle.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 28 Jul 2000, Archie Cobbs wrote: > Doug White writes: > > You normally wouldn't mix kqueue and threads; you'd use kqueue to > > *implement* threads. :-) > > > > AFAIK kqueue hasn't been made threadsafe, you'll have to bug > > jlemon@freebsd.org about it. Patches gladly accepted :) > > I may be just being stupid but I don't understand that last sentence. > > I thought kqueue() and kevent() were system calls... how can they > not be thread safe? They really mean "wrapped by the threads library" so that kqueue doesn't block other threads from running. -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 28 13:24:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mta4.rcsntx.swbell.net (mta4.rcsntx.swbell.net [151.164.30.28]) by hub.freebsd.org (Postfix) with ESMTP id E784A37BC74 for ; Fri, 28 Jul 2000 13:24:17 -0700 (PDT) (envelope-from chris@holly.calldei.com) Received: from holly.calldei.com ([208.191.149.190]) by mta4.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9) with ESMTP id <0FYF00JN0BY3U0@mta4.rcsntx.swbell.net> for hackers@FreeBSD.ORG; Fri, 28 Jul 2000 15:08:28 -0500 (CDT) Received: (from chris@localhost) by holly.calldei.com (8.9.3/8.9.3) id PAA42531; Fri, 28 Jul 2000 15:05:53 -0500 (CDT envelope-from chris) Date: Fri, 28 Jul 2000 15:05:53 -0500 From: Chris Costello Subject: Re: kevent()/kqueue() in a multithreaded environment In-reply-to: <200007281945.MAA26198@bubba.whistle.com> To: Archie Cobbs Cc: Doug White , hackers@FreeBSD.ORG Reply-To: chris@calldei.com Message-id: <20000728150552.N37935@holly.calldei.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i References: <200007281945.MAA26198@bubba.whistle.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, July 28, 2000, Archie Cobbs wrote: > Doug White writes: > > AFAIK kqueue hasn't been made threadsafe, you'll have to bug > > jlemon@freebsd.org about it. Patches gladly accepted :) > > I may be just being stupid but I don't understand that last sentence. > > I thought kqueue() and kevent() were system calls... how can they > not be thread safe? Consider a kqueue() with a timeout--the calling process does not get woken up until the timeout is completed. Look at src/lib/libc_r/uthread/uthread_poll.c for something similar to how a threaded kevent() could be implemented. I don't think kqueue() would block. -- |Chris Costello |If a group of N persons implements a COBOL compiler, there will be N-1 |passes. Someone in the group has to be the manager. -- T. Cheatham `---------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 28 14: 4:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from nec.com (mail1.nec.com [143.101.112.2]) by hub.freebsd.org (Postfix) with ESMTP id 7CA1237BDB0; Fri, 28 Jul 2000 14:04:41 -0700 (PDT) (envelope-from jfu@asl.dl.nec.com) Received: from aslws01.asl.dl.nec.com (aslws01.asl.dl.nec.com [143.101.2.1]) by nec.com (8.9.3/8.9.3) with ESMTP id QAA19464; Fri, 28 Jul 2000 16:04:39 -0500 (CDT) Received: by aslws01.asl.dl.nec.com (8.7.3/YDL1.9.1-940729.15) id QAA21921(aslws01.asl.dl.nec.com); Fri, 28 Jul 2000 16:04:38 -0500 (CDT) Received: by aslws111.asl.dl.nec.com (8.7.3/YDL1.9.1-940729.15) id QAA23144(aslws111.asl.dl.nec.com); Fri, 28 Jul 2000 16:04:37 -0500 (CDT) Message-ID: <3981F565.C6B12FCD@asl.dl.nec.com> Date: Fri, 28 Jul 2000 16:04:37 -0500 From: Jeffrey Fu Organization: ASL X-Mailer: Mozilla 4.7 [en] (X11; U; SunOS 5.5.1 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org, freebsd-questions@freebsd.org Subject: tar Content-Type: text/plain; charset=big5 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I want to download the FreeBSD 2.2.2 for IPV6 Mobility development. Because of the firewall, I can only access the Freebsd site by a SUN Solaris machine. I use CVSup to download the FreeBSD2.2.2 from cvsup7.freebsd.com to the Solaris machine. After the download, it create a src directory(The size is about 180MB) in the solaris machine. Then, I did a "tar cvf src.tar src" to compress it and ftp it to a PC running FreeBSD3.3. I checked the size of the src.tar files and they are the same in Solaris and the FreeBSD machines. After I uncompress it("tar xvf src.tar"), the directory has only 150MB. Why is the uncompress directory different in size in Solaris and FreeBSD? Another question is, after I get the src directory, what should I do to change the FreeBSD 3.3 to 2.2.2? Should I copy the src(the download one for 2.2.2) to /usr/src of the FreeBSD 3.3 machine, then do "make world" and then rebuild the kernel? Do I need to do "cvs" before make world? What path should I set the $CVSROOT? Thanks for answering my question. Jeffrey Fu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 28 14:46:53 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bluerose.windmoon.nu (c255152-a.plstn1.sfba.home.com [24.176.132.48]) by hub.freebsd.org (Postfix) with ESMTP id 1E87637B6E5 for ; Fri, 28 Jul 2000 14:46:49 -0700 (PDT) (envelope-from fengyue@bluerose.windmoon.nu) Received: from localhost (fengyue@localhost) by bluerose.windmoon.nu (8.10.2/Windmoon/8.10.2) with ESMTP id e6SM0dS14798 for ; Fri, 28 Jul 2000 15:00:40 -0700 (PDT) Date: Fri, 28 Jul 2000 15:00:39 -0700 (PDT) From: FengYue To: freebsd-hackers@FreeBSD.ORG Subject: a quick one In-Reply-To: <3981F565.C6B12FCD@asl.dl.nec.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi there, a quick one. Is getpeername() considered expensive? Would it be much better if I cache the result myself instead of calling it everytime on the connected socket(returned from accept) to find out which IP it connects to? Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 28 14:51:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id E2F2037BC1A for ; Fri, 28 Jul 2000 14:51:13 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.3/8.9.3) id OAA27665; Fri, 28 Jul 2000 14:51:00 -0700 (PDT) (envelope-from archie) From: Archie Cobbs Message-Id: <200007282151.OAA27665@bubba.whistle.com> Subject: Re: a quick one In-Reply-To: from FengYue at "Jul 28, 2000 03:00:39 pm" To: FengYue Date: Fri, 28 Jul 2000 14:51:00 -0700 (PDT) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FengYue writes: > Hi there, a quick one. Is getpeername() considered expensive? > Would it be much better if I cache the result myself instead of > calling it everytime on the connected socket(returned from accept) to > find out which IP it connects to? It's not particularly expensive compared to other system calls.. but if you find system calls in general expensive, then it would certainly count as one :-) I'd say it's unlikely that this kind of optimization would be worth the trouble for a 'normal' application. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 28 15:59:36 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rdc1.ct.home.com (ha1.rdc1.ct.home.com [24.2.0.66]) by hub.freebsd.org (Postfix) with ESMTP id 118FD37B674 for ; Fri, 28 Jul 2000 15:59:33 -0700 (PDT) (envelope-from tsikora@home.com) Received: from home.com ([24.2.168.186]) by mail.rdc1.ct.home.com (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20000728225931.VJPY9101.mail.rdc1.ct.home.com@home.com> for ; Fri, 28 Jul 2000 15:59:31 -0700 Message-ID: <39821108.CD43006A@home.com> Date: Fri, 28 Jul 2000 19:02:32 -0400 From: Ted Sikora Organization: Jtl Development Group X-Mailer: Mozilla 4.73 [en] (X11; I; FreeBSD 4.1-STABLE i386) X-Accept-Language: en-US, en MIME-Version: 1.0 To: "freebsd-hackers@FreeBSD.ORG" Subject: /tmp on a ramdisk? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A while ago several people suggested using /tmp on a ramdisk along with softupdates. Right now I am running several production servers with 4.1-STABLE with softupdates. I'm really happy with the performance. What benefits would I realize using /tmp on a ramdisk? Regards, -- Ted Sikora Jtl Development Group tsikora@powerusersbbs.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 28 16: 7:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from incandescent.firedrake.org (incandescent.firedrake.org [195.157.96.1]) by hub.freebsd.org (Postfix) with ESMTP id A147537BA39 for ; Fri, 28 Jul 2000 16:07:15 -0700 (PDT) (envelope-from float@incandescent.firedrake.org) Received: from float by incandescent.firedrake.org with local (Exim 2.05 #1 (Debian)) id 13IJDd-0000eG-00; Sat, 29 Jul 2000 00:07:05 +0100 Date: Sat, 29 Jul 2000 00:07:05 +0100 From: void To: hackers@freebsd.org Subject: some "md" (memory disk) questions Message-ID: <20000729000705.A2486@firedrake.org> Mime-Version: 1.0 Content-Type: message/rfc822 Content-Disposition: inline User-Agent: Mutt/1.2i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I sent this to -questions and received no answer, perhaps the kind denizens of -hackers can help me. 1) Might I want to replace my MFS /tmp with an md-based one? 2) I looked at LINT and GENERIC, I read section 10.6.2 of the Handbook, and I looked for an md man page in vain. Where could I find additional documentation for md? I'm particularly interested in finding out what it's good for. -- Ben 220 go.ahead.make.my.day ESMTP Postfix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 28 17:23:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dt052n3e.san.rr.com (dt052n3e.san.rr.com [204.210.33.62]) by hub.freebsd.org (Postfix) with ESMTP id A8F1637C2E0 for ; Fri, 28 Jul 2000 17:23:29 -0700 (PDT) (envelope-from DougB@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt052n3e.san.rr.com (8.9.3/8.9.3) with ESMTP id RAA12156; Fri, 28 Jul 2000 17:23:27 -0700 (PDT) (envelope-from DougB@gorean.org) Message-ID: <398223FF.17B737A7@gorean.org> Date: Fri, 28 Jul 2000 17:23:27 -0700 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Ted Sikora Cc: "freebsd-hackers@FreeBSD.ORG" Subject: Re: /tmp on a ramdisk? References: <39821108.CD43006A@home.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ted Sikora wrote: > > A while ago several people suggested using /tmp on a ramdisk along with > softupdates. Right now I am running several production servers with > 4.1-STABLE with softupdates. I'm really happy with the performance. What > benefits would I realize using /tmp on a ramdisk? CW on this is varied, but the current trend is that /tmp on a md is just a waste of ram, since (basically) everything in /tmp is in ram twice. Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 28 17:43: 6 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id D6BAC37B5C3 for ; Fri, 28 Jul 2000 17:42:55 -0700 (PDT) (envelope-from grog@wantadilla.lemis.com) Received: (from grog@localhost) by wantadilla.lemis.com (8.9.3/8.9.3) id KAA14319; Sat, 29 Jul 2000 10:12:40 +0930 (CST) (envelope-from grog) Date: Sat, 29 Jul 2000 10:12:40 +0930 From: Greg Lehey To: Maxim Konovalov Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: vinum striping quiestion Message-ID: <20000729101239.B92724@wantadilla.lemis.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: ; from koma@rbc.ru on Fri, Jul 28, 2000 at 07:21:10PM +0400 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, 28 July 2000 at 19:21:10 +0400, Maxim Konovalov wrote: > > Hello, > > I've got a question about vinum. There are two scsi disks with vinum > stripe. Here is a vinum config: > > drive a device /dev/da2s1e > drive b device /dev/da3s1e > volume vinum0 > plex name vinum0.p0 org striped 1024s vol vinum0 > sd name vinum0.p0.s0 drive a plex vinum0.p0 > len 34791424s driveoffset 265s plexoffset 0s > sd name vinum0.p0.s1 drive b plex vinum0.p0 > len 34791424s driveoffset 265s plexoffset 1024s Please show the output of 'vinum list'. > # uname -sr > FreeBSD 4.1-STABLE > > There are not any other fs on these disks. The problem is - when I run > iozone (iozone 4096 /logs/io0.tmp) I get a very strange result: > > # iostat -d da1 da3 10 > da1 da3 > KB/t tps MB/s KB/t tps MB/s > 0.00 0 0.00 0.00 0 0.00 > 4.50 107 0.47 0.00 0 0.00 > 4.51 98 0.43 0.00 0 0.00 > 4.50 116 0.51 0.00 0 0.00 > 4.49 117 0.52 0.00 0 0.00 > 4.50 111 0.49 0.00 0 0.00 > .... > > You see, there is not activity on da3. Are there any explanations? I think this says more about iozone than it does about Vinum. Try running rawio instead and see what happens. Note also that a stripe size which is a power of two is not a good idea. It can give rise to the kind of behaviour you report: since cylinder groups are usually 32 MB in size, this arrangement will put all the super blocks on the same subdisk. Use an odd number, say 283 kB, instead. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 28 17:52:51 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from unix.worldpath.net (unix.worldpath.net [206.152.180.10]) by hub.freebsd.org (Postfix) with ESMTP id 15FA737B5C3 for ; Fri, 28 Jul 2000 17:52:47 -0700 (PDT) (envelope-from waldroni@lr.net) Received: from camry ([208.133.220.153]) by unix.worldpath.net (8.9.3/8.9.3(WPI)) with SMTP id UAA11225 for ; Fri, 28 Jul 2000 20:52:44 -0400 (EDT) Message-ID: <000701bff8f7$422e3bc0$0100000a@waldron.house> Reply-To: "Isaac Waldron" From: "Isaac Waldron" To: Subject: Best way to lock malloc'd memory in kernel Date: Fri, 28 Jul 2000 20:52:22 -0400 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 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm writing a device driver for plex86 (the FreeMWare virtual machine software), and have a buffer that needs to be non-pageable. It was malloc'd with the malloc(size, type, flags) kernel malloc function. What's the best way to make this memory unpageable? Thanks in advance, Isaac Waldron waldroni at lr dot net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 28 18:19:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from midget.dons.net.au (daniel.lnk.telstra.net [139.130.137.70]) by hub.freebsd.org (Postfix) with ESMTP id 0A5A837C22F for ; Fri, 28 Jul 2000 18:19:10 -0700 (PDT) (envelope-from darius@guppy.dons.net.au) Received: from guppy.dons.net.au (guppy.dons.net.au [203.31.81.9]) by midget.dons.net.au (8.9.3/8.9.1) with ESMTP id KAA50401; Sat, 29 Jul 2000 10:49:06 +0930 (CST) (envelope-from darius@guppy.dons.net.au) Received: (from darius@localhost) by guppy.dons.net.au (8.9.3/8.9.3) id KAA02516; Sat, 29 Jul 2000 10:49:04 +0930 (CST) (envelope-from darius) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <000701bff8f7$422e3bc0$0100000a@waldron.house> Date: Sat, 29 Jul 2000 10:49:04 +0930 (CST) From: "Daniel O'Connor" To: Isaac Waldron Subject: RE: Best way to lock malloc'd memory in kernel Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 29-Jul-00 Isaac Waldron wrote: > I'm writing a device driver for plex86 (the FreeMWare virtual machine > software), and have a buffer that needs to be non-pageable. It was malloc'd > with the malloc(size, type, flags) kernel malloc function. What's the best > way to make this memory unpageable? No kernel memory is pageable so it doesn't matter :) --- 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 28 18:31: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from unix.worldpath.net (unix.worldpath.net [206.152.180.10]) by hub.freebsd.org (Postfix) with ESMTP id E8D6737B670 for ; Fri, 28 Jul 2000 18:31:00 -0700 (PDT) (envelope-from waldroni@lr.net) Received: from camry ([208.133.220.153]) by unix.worldpath.net (8.9.3/8.9.3(WPI)) with SMTP id VAA24140 for ; Fri, 28 Jul 2000 21:30:58 -0400 (EDT) Message-ID: <006301bff8fc$98795a00$0100000a@waldron.house> Reply-To: "Isaac Waldron" From: "Isaac Waldron" To: References: Subject: Re: Best way to lock malloc'd memory in kernel Date: Fri, 28 Jul 2000 21:30:35 -0400 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 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I'm writing a device driver for plex86 (the FreeMWare virtual machine > > software), and have a buffer that needs to be non-pageable. It was malloc'd > > with the malloc(size, type, flags) kernel malloc function. What's the best > > way to make this memory unpageable? > > No kernel memory is pageable so it doesn't matter :) > Thanks! I didn't realize that, I suppose I should have RTFM'ed a bit more before asking, but I just kind of assumed (we all know what that does) that memory malloc'd in kernel mode was pageable. I guess I should ask whether that holds true for kernel modules as well, because that's what I'm actually writing. Thanks again, Isaac Waldron waldroni at lr dot net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 28 18:53: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from midget.dons.net.au (daniel.lnk.telstra.net [139.130.137.70]) by hub.freebsd.org (Postfix) with ESMTP id 3CFDC37BB28 for ; Fri, 28 Jul 2000 18:52:41 -0700 (PDT) (envelope-from darius@guppy.dons.net.au) Received: from guppy.dons.net.au (guppy.dons.net.au [203.31.81.9]) by midget.dons.net.au (8.9.3/8.9.1) with ESMTP id LAA50611; Sat, 29 Jul 2000 11:22:16 +0930 (CST) (envelope-from darius@guppy.dons.net.au) Received: (from darius@localhost) by guppy.dons.net.au (8.9.3/8.9.3) id LAA03793; Sat, 29 Jul 2000 11:22:06 +0930 (CST) (envelope-from darius) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <006301bff8fc$98795a00$0100000a@waldron.house> Date: Sat, 29 Jul 2000 11:22:06 +0930 (CST) From: "Daniel O'Connor" To: Isaac Waldron Subject: Re: Best way to lock malloc'd memory in kernel Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 29-Jul-00 Isaac Waldron wrote: > Thanks! I didn't realize that, I suppose I should have RTFM'ed a bit more > before asking, but I just kind of assumed (we all know what that does) that > memory malloc'd in kernel mode was pageable. I guess I should ask whether Yes, well it would be nice to have some kernel memory pageable but.. > that holds true for kernel modules as well, because that's what I'm actually > writing. Yes, writing a module is no different than writing for static kernel code. --- 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 28 19:22:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 933F437BB75 for ; Fri, 28 Jul 2000 19:22:12 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e6T2MAS17433; Fri, 28 Jul 2000 19:22:10 -0700 (PDT) Date: Fri, 28 Jul 2000 19:22:10 -0700 From: Alfred Perlstein To: Isaac Waldron Cc: hackers@FreeBSD.ORG Subject: Re: Best way to lock malloc'd memory in kernel Message-ID: <20000728192210.M17222@fw.wintelcom.net> References: <006301bff8fc$98795a00$0100000a@waldron.house> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <006301bff8fc$98795a00$0100000a@waldron.house>; from waldroni@lr.net on Fri, Jul 28, 2000 at 09:30:35PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Isaac Waldron [000728 18:31] wrote: > > > > I'm writing a device driver for plex86 (the FreeMWare virtual machine > > > software), and have a buffer that needs to be non-pageable. It was > malloc'd > > > with the malloc(size, type, flags) kernel malloc function. What's the > best > > > way to make this memory unpageable? > > > > No kernel memory is pageable so it doesn't matter :) > > > > Thanks! I didn't realize that, I suppose I should have RTFM'ed a bit more > before asking, but I just kind of assumed (we all know what that does) that > memory malloc'd in kernel mode was pageable. I guess I should ask whether > that holds true for kernel modules as well, because that's what I'm actually > writing. Just a note that you may have to use 'contigmalloc' if you need the memory to be physically contiguous. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 28 21:42:46 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66]) by hub.freebsd.org (Postfix) with ESMTP id 3644D37B81B for ; Fri, 28 Jul 2000 21:42:39 -0700 (PDT) (envelope-from nate@yogotech.com) Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.123.131]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id WAA16757; Fri, 28 Jul 2000 22:42:35 -0600 (MDT) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id WAA25461; Fri, 28 Jul 2000 22:42:27 -0600 (MDT) (envelope-from nate) Date: Fri, 28 Jul 2000 22:42:27 -0600 (MDT) Message-Id: <200007290442.WAA25461@nomad.yogotech.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Archie Cobbs Cc: Doug White , hackers@FreeBSD.ORG Subject: Re: kevent()/kqueue() in a multithreaded environment In-Reply-To: <200007281945.MAA26198@bubba.whistle.com> References: <200007281945.MAA26198@bubba.whistle.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > You normally wouldn't mix kqueue and threads; you'd use kqueue to > > *implement* threads. :-) > > > > AFAIK kqueue hasn't been made threadsafe, you'll have to bug > > jlemon@freebsd.org about it. Patches gladly accepted :) > > I may be just being stupid but I don't understand that last sentence. > > I thought kqueue() and kevent() were system calls... how can they > not be thread safe? I think there is a mis-communication here. They are thread 'safe', but if called, they block out all other 'threads' from running, so using kqueue doesn't allow for multiple threads to run 'concurrently'. In other words, a wrapper needs to be written so it can work in a 'threaded' environment effeciently. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 29 3:52: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mta01-svc.ntlworld.com (mta01-svc.ntlworld.com [62.253.162.41]) by hub.freebsd.org (Postfix) with ESMTP id 96A2B37B5B3 for ; Sat, 29 Jul 2000 03:51:59 -0700 (PDT) (envelope-from mark@ukug.uk.freebsd.org) Received: from parish.my.domain ([62.253.84.67]) by mta01-svc.ntlworld.com (InterMail vM.4.01.02.27 201-229-119-110) with ESMTP id <20000729105157.BJGS26680.mta01-svc.ntlworld.com@parish.my.domain> for ; Sat, 29 Jul 2000 11:51:57 +0100 Received: (from mark@localhost) by parish.my.domain (8.9.3/8.9.3) id LAA00972 for hackers@freebsd.org; Sat, 29 Jul 2000 11:51:54 +0100 (BST) (envelope-from mark) Date: Sat, 29 Jul 2000 11:51:53 +0100 From: Mark Ovens To: hackers@freebsd.org Subject: ANSI compliance, gcc(1) and FreeBSD Message-ID: <20000729115153.C236@parish> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2i Organization: Total lack of Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Apologies if this is the wrong list for this question but it seems the best place to get a *definitive* answer. In the ANSI Standard (K&R 2e, A7.14 & A7.15) it states that, in the case of the ``&&'' operator, the right operand is evaluated only if the left operand evaluates to non-zero, and, for ``||'', the right operand is evaluated only if the left operand evaluates to zero. My questions are: does gcc(1) honour this, and is it permitted to rely on this behaviour in FreeBSD (base system)?, e.g., would the following be acceptable if we wanted to guarantee that foobar was set to BAR *only* if FOO was unset or NULL? char *foobar; if ((foobar = getenv("FOO")) != NULL || (foobar = getenv("BAR")) != NULL) I couldn't find the answer in style(9). Please Cc: me as I'm not subscribed to -hackers. TIA -- If I buy a copy of WinDelete, and it doesn't delete Windows, am I entitled to my money back? ________________________________________________________________ 51.44°N FreeBSD - The Power To Serve http://www.freebsd.org 2.057°W My Webpage http://ukug.uk.freebsd.org/~mark mailto:marko@freebsd.org http://www.radan.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 29 3:55: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 83C1337B79F; Sat, 29 Jul 2000 03:54:58 -0700 (PDT) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 29 Jul 2000 11:54:57 +0100 (BST) Date: Sat, 29 Jul 2000 11:54:56 +0100 From: David Malone To: Mark Ovens Cc: hackers@freebsd.org Subject: Re: ANSI compliance, gcc(1) and FreeBSD Message-ID: <20000729115456.A65276@walton.maths.tcd.ie> References: <20000729115153.C236@parish> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.2i In-Reply-To: <20000729115153.C236@parish>; from marko@freebsd.org on Sat, Jul 29, 2000 at 11:51:53AM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jul 29, 2000 at 11:51:53AM +0100, Mark Ovens wrote: > In the ANSI Standard (K&R 2e, A7.14 & A7.15) it states that, in the > case of the ``&&'' operator, the right operand is evaluated only if > the left operand evaluates to non-zero, and, for ``||'', the right > operand is evaluated only if the left operand evaluates to zero. > > My questions are: does gcc(1) honour this, and is it permitted to rely > on this behaviour in FreeBSD (base system)? Lots of C code would break if this wasn't honoured. Gcc deals with it just fine. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 29 8:59:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from echidna.stu.cowan.edu.au (echidna.stu.cowan.edu.au [139.230.33.5]) by hub.freebsd.org (Postfix) with ESMTP id 0503937B967 for ; Sat, 29 Jul 2000 08:58:37 -0700 (PDT) (envelope-from tpnelson@echidna.stu.cowan.edu.au) Received: from echidna.stu.cowan.edu.au ([139.230.242.70]) by echidna.stu.cowan.edu.au (8.9.1/8.9.1) with ESMTP id XAA12342108; Sat, 29 Jul 2000 23:58:02 +0800 (WST) Message-ID: <3982FF55.2AD5356E@echidna.stu.cowan.edu.au> Date: Sat, 29 Jul 2000 23:59:17 +0800 From: Trent Nelson X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: behanna@zbzoom.net Cc: hackers@FreeBSD.org Subject: Linux NVIDIA drivers vs. default XFree86 drivers (WAS: RE: Video card support) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Moving to hackers@, where most discussions regarding the NVIDIA drivers seem to take place lately. Chris BeHanna wrote: > I don't remember if it was this list on which I saw this > discussion, or if it was hackers. Anyway, I looked at xfree86.org > today, and noticed that there is accelerated support for ATI Mach64 > and for NVIDIA TNT2 and GeForce256 boards, as well as many others. > > Is there some reason why this isn't "good enough," or do we > really need actual drivers for these boards to get at their > extra-nifty features (e.g., hardware backface culling, fog, bump maps, > etc.)? The NVIDIA drivers for XFree86 are the result of a collaborative effort between NVIDIA, SGI and VA Linux. Concentration, as far as I know, has been focused on OpenGL development in the new DRI environment XFree86 4.0 provides. You could speculate that with fairly high calibre companies partaking in such an effort - where there's obviously a fair amount of financial investment - their drivers are going to perform better than those provided with XFree86. For those interested, it is the code of the accelerated OpenGL driver/libraries that NVIDIA are distributing as Linux binaries (i.e. closed-source). The only source that *is* provided is for the cards' kernel device driver. I remember reading somewhere on NVIDIA's site that the only reason they're providing *this* code is because Linux's kernel module loading mechanism prevents the introduction of foreign pre-compiled binary objects as system device drivers. So, effectively, a kernel device driver has to be compiled on the system natively before it can be used (?). It was something along those lines, anyway. Someone should tell NVIDIA there's a lot more to "Open Source" than just writing closed-source drivers for Linux. On a more technical note, given an accurate port of the kernel device driver (which would be trivial at best), is there any reason these Linux OpenGL drivers & associated libraries can't just be branded as 'Linux' object types and handled as-per-normal by linux.ko? After all, it's the kernel driver's responsibility to manage all the Operating System's specific hardware resource management etc. I'm doubting it's that easy, though. > Chris BeHanna > Software Engineer (at yourfit.com) Regards, Trent. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 29 10:16:55 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.bezeqint.net (mail-a.bezeqint.net [192.115.106.23]) by hub.freebsd.org (Postfix) with ESMTP id 4EDE437B57C for ; Sat, 29 Jul 2000 10:16:51 -0700 (PDT) (envelope-from nimrodm@bezeqint.net) Received: from bsd.net.il ([212.179.172.131]) by mail.bezeqint.net (Sun Internet Mail Server sims.3.5.2000.03.23.18.03.p10) with ESMTP id <0FYG00F6CYLQMA@mail.bezeqint.net> for hackers@FreeBSD.ORG; Sat, 29 Jul 2000 20:15:27 +0300 (IDT) Received: (from nimrodm@localhost) by bsd.net.il (8.9.3/8.9.3) id UAA00800 for hackers@FreeBSD.ORG; Sat, 29 Jul 2000 20:08:15 +0300 (IDT envelope-from nimrodm) Date: Sat, 29 Jul 2000 20:08:15 +0300 From: Nimrod Mesika Subject: Re: Linux NVIDIA drivers vs. default XFree86 drivers (WAS: RE: Video card support) In-reply-to: <3982FF55.2AD5356E@echidna.stu.cowan.edu.au>; from tpnelson@echidna.stu.cowan.edu.au on Sat, Jul 29, 2000 at 11:59:17PM +0800 To: hackers@FreeBSD.ORG Reply-To: nimrodm@email.com Message-id: <20000729200815.A772@localhost.bsd.net.il> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline Mail-Followup-To: Nimrod Mesika , hackers@FreeBSD.ORG User-Agent: Mutt/1.2i References: <3982FF55.2AD5356E@echidna.stu.cowan.edu.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jul 29, 2000 at 11:59:17PM +0800, Trent Nelson wrote: > On a more technical note, given an accurate port of the kernel > device driver (which would be trivial at best), is there any > reason these Linux OpenGL drivers & associated libraries can't > just be branded as 'Linux' object types and handled as-per-normal > by linux.ko? After all, it's the kernel driver's responsibility to > manage all the Operating System's specific hardware resource > management etc. I thought the whole point of XFree4 new driver mechanism was that it was OS-neutral. It should be possible to run the same binary driver on all x86 platforms running XFree4 *without* recompiling. I don't know how this driver interacts with the kernel module, though. I'm not sure I even understand why a kernel module is needed in this case. -- Nimrod. http://www.geocities.com/rodd_27 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 29 10:27:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id 3F36637B728 for ; Sat, 29 Jul 2000 10:27:43 -0700 (PDT) (envelope-from rooneg@rpi.edu) Received: from cortez.sss.rpi.edu (rooneg@cortez.sss.rpi.edu [128.113.113.33]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id NAA400526; Sat, 29 Jul 2000 13:27:41 -0400 Received: from localhost (rooneg@localhost) by cortez.sss.rpi.edu (8.8.5/8.8.6) with SMTP id NAA135046; Sat, 29 Jul 2000 13:28:00 -0400 X-Authentication-Warning: cortez.sss.rpi.edu: rooneg owned process doing -bs Date: Sat, 29 Jul 2000 13:28:00 -0400 (EDT) From: Garrett Rooney X-Sender: rooneg@cortez.sss.rpi.edu To: nimrodm@email.com Cc: hackers@FreeBSD.ORG Subject: Re: Linux NVIDIA drivers vs. default XFree86 drivers (WAS: RE: Video card support) In-Reply-To: <20000729200815.A772@localhost.bsd.net.il> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 29 Jul 2000, Nimrod Mesika wrote: > I thought the whole point of XFree4 new driver mechanism was that > it was OS-neutral. It should be possible to run the same binary > driver on all x86 platforms running XFree4 *without* recompiling. > > I don't know how this driver interacts with the kernel module, > though. I'm not sure I even understand why a kernel module is > needed in this case. i believe it requires hooks into the kernel to make use of AGP, which is necessary for high performance 3d rendering. -garrett x----------------------------------------------------------------------x | rooneg@rpi.edu garrett rooney | | http://www.rpi.edu/~rooneg unix geek | |----------------------------------------------------------------------| | unrequited love is neat because it lasts so much longer - w. t. c. | x----------------------------------------------------------------------x To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 29 12:47:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from netplex.com.au (adsl-63-207-30-186.dsl.snfc21.pacbell.net [63.207.30.186]) by hub.freebsd.org (Postfix) with ESMTP id 375A337B595 for ; Sat, 29 Jul 2000 12:47:55 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (peter@localhost [127.0.0.1]) by netplex.com.au (8.9.3/8.9.3) with ESMTP id MAA57344; Sat, 29 Jul 2000 12:47:29 -0700 (PDT) (envelope-from peter@netplex.com.au) Message-Id: <200007291947.MAA57344@netplex.com.au> X-Mailer: exmh version 2.1.1 10/15/1999 To: Garrett Rooney Cc: nimrodm@email.com, hackers@FreeBSD.ORG Subject: Re: Linux NVIDIA drivers vs. default XFree86 drivers (WAS: RE: Video card support) In-Reply-To: Date: Sat, 29 Jul 2000 12:47:29 -0700 From: Peter Wemm Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Garrett Rooney wrote: > On Sat, 29 Jul 2000, Nimrod Mesika wrote: > > > I thought the whole point of XFree4 new driver mechanism was that > > it was OS-neutral. It should be possible to run the same binary > > driver on all x86 platforms running XFree4 *without* recompiling. > > > > I don't know how this driver interacts with the kernel module, > > though. I'm not sure I even understand why a kernel module is > > needed in this case. > > i believe it requires hooks into the kernel to make use of AGP, which is > necessary for high performance 3d rendering. More to the point, they want to use their high performance proprietary internal cross platform driver that they also use on Windows etc. They provide the OS interface glue to enable interfacing with the kernel. The driver then completely takes over the card management in kernel context - busmaster DMA, command fifo managenent, card memory management, the lot. A userland XFree driver cannot use DMA as it cannot know what the virtual-> physical address mappings are. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 29 15:49:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freya.unik.no (freya.unik.no [193.156.96.215]) by hub.freebsd.org (Postfix) with ESMTP id BC83437B7E7 for ; Sat, 29 Jul 2000 15:49:07 -0700 (PDT) (envelope-from andreasd@unik.no) Received: from odin.unik.no (odin.unik.no [193.156.96.7]) by freya.unik.no (8.9.3/8.9.3) with ESMTP id AAA25615 for ; Sun, 30 Jul 2000 00:48:52 +0200 (MEST) Received: (from andreasd@localhost) by odin.unik.no (8.9.3/8.9.3) id AAA26095; Sun, 30 Jul 2000 00:48:52 +0200 (MET DST) To: hackers@freebsd.org Subject: Re: Funky scheduler stuff under heavy I/O. References: From: andreasd@unik.no (Andreas Dobloug; UiO; H98) Date: 30 Jul 2000 00:48:52 +0200 In-Reply-To: Message-ID: Lines: 9 X-Mailer: Gnus v5.5/Emacs 20.2 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Charles Randall | Could it be a boundary condition when the PCI bus gets saturated? When this happens there's at least 5000-6500 interrupts/sec on the SCSI-controller (reported by systat). How many cycles do each interrupt use? (ahc-driver+SMP) -- Andreas Dobloug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 29 19:27:51 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from maxim.gba.oz.au (gba.tmx.com.au [203.9.155.249]) by hub.freebsd.org (Postfix) with SMTP id 3ED6F37B875 for ; Sat, 29 Jul 2000 19:27:45 -0700 (PDT) (envelope-from gjb@acm.org) Received: (qmail 24134 invoked by uid 1001); 30 Jul 2000 12:25:59 +1000 X-Posted-By: GBA-Post 2.02.01 12-Dec-1999 X-PGP-Fingerprint: 5A91 6942 8CEA 9DAB B95B C249 1CE1 493B 2B5A CE30 Message-Id: Date: Sun, 30 Jul 2000 12:25:59 +1000 From: Greg Black To: Mark Ovens Cc: hackers@FreeBSD.ORG Subject: Re: ANSI compliance, gcc(1) and FreeBSD References: <20000729115153.C236@parish> In-reply-to: <20000729115153.C236@parish> of Sat, 29 Jul 2000 11:51:53 +0100 Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Apologies if this is the wrong list for this question but it seems the > best place to get a *definitive* answer. The best place to get a definitive answer about C is in the Standard. The best place to get a definitive answer about gcc is in the source. > In the ANSI Standard (K&R 2e, A7.14 & A7.15) As a point of fact, K&R-2, while largely correct, is not itself the Standard. > it states that, in the > case of the ``&&'' operator, the right operand is evaluated only if > the left operand evaluates to non-zero, and, for ``||'', the right > operand is evaluated only if the left operand evaluates to zero. This has been mandated ever since the days of the original language definition (K&R-1, 1978) and is absolutely required of anything that purports to be a C compiler -- and yes, gcc is conformant in this respect. > would the following > be acceptable if we wanted to guarantee that foobar was set to BAR > *only* if FOO was unset or NULL? > > if ((foobar = getenv("FOO")) != NULL || (foobar = getenv("BAR")) != NULL) The second getenv() will only be called if the first one returns NULL. Of course, if the second getenv() also returns NULL, then foobar will be set to NULL and the statement part of the "if" will not be executed. -- Greg Black -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 29 21: 2: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from acl.lanl.gov (acl.lanl.gov [128.165.147.1]) by hub.freebsd.org (Postfix) with ESMTP id 6E07E37B689 for ; Sat, 29 Jul 2000 21:02:00 -0700 (PDT) (envelope-from rminnich@lanl.gov) Received: from mini.acl.lanl.gov (root@mini.acl.lanl.gov [128.165.147.34]) by acl.lanl.gov (8.8.8/8.8.5) with ESMTP id WAA7080167 for ; Sat, 29 Jul 2000 22:01:58 -0600 (MDT) Received: from localhost (rminnich@localhost) by mini.acl.lanl.gov (8.9.3/8.8.8) with ESMTP id WAA05805 for ; Sat, 29 Jul 2000 22:01:58 -0600 X-Authentication-Warning: mini.acl.lanl.gov: rminnich owned process doing -bs Date: Sat, 29 Jul 2000 22:01:58 -0600 (MDT) From: Ronald G Minnich X-Sender: rminnich@mini.acl.lanl.gov To: hackers@FreeBSD.ORG Subject: Re: Linux NVIDIA drivers vs. default XFree86 drivers (WAS: RE: Video card support) In-Reply-To: <3982FF55.2AD5356E@echidna.stu.cowan.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG actually you're not even getting kernel driver source for linux. What you're getting is an ugly binary blob that looks like the guts of an NT driver, plus enough source stuff to let the kernel hook to the binary blob. It's not pretty. And, as you might expect, it's a little prone to failure. ron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 29 22: 8:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from echidna.stu.cowan.edu.au (echidna.stu.cowan.edu.au [139.230.33.5]) by hub.freebsd.org (Postfix) with ESMTP id A622B37B908 for ; Sat, 29 Jul 2000 22:08:36 -0700 (PDT) (envelope-from tpnelson@echidna.stu.cowan.edu.au) Received: from echidna.stu.cowan.edu.au (s212n167.rev.ecu.edu.au [139.230.212.167]) by echidna.stu.cowan.edu.au (8.9.1/8.9.1) with ESMTP id NAA12941629; Sun, 30 Jul 2000 13:05:24 +0800 (WST) Message-ID: <3983B7E1.B89C35CF@echidna.stu.cowan.edu.au> Date: Sun, 30 Jul 2000 13:06:41 +0800 From: Trent Nelson X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Peter Wemm Cc: Garrett Rooney , nimrodm@email.com, hackers@FreeBSD.ORG Subject: Re: Linux NVIDIA drivers vs. default XFree86 drivers (WAS: RE: Video card support) References: <200007291947.MAA57344@netplex.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Wemm wrote: > They provide the OS interface glue to enable interfacing with the > kernel. The driver then completely takes over the card management > in kernel context - busmaster DMA, command fifo managenent, card > memory management, the lot. So, given a working FreeBSD-specific kernel device driver - can the Linux OpenGL driver/libraries provided be handled via linux.ko? > Cheers, > -Peter Regards, Trent. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 29 22:34:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id 4DC7837B958 for ; Sat, 29 Jul 2000 22:34:45 -0700 (PDT) (envelope-from rooneg@rpi.edu) Received: from cortez.sss.rpi.edu (rooneg@cortez.sss.rpi.edu [128.113.113.33]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id BAA89452; Sun, 30 Jul 2000 01:34:43 -0400 Received: from localhost (rooneg@localhost) by cortez.sss.rpi.edu (8.8.5/8.8.6) with SMTP id BAA106264; Sun, 30 Jul 2000 01:35:02 -0400 X-Authentication-Warning: cortez.sss.rpi.edu: rooneg owned process doing -bs Date: Sun, 30 Jul 2000 01:35:02 -0400 (EDT) From: Garrett Rooney X-Sender: rooneg@cortez.sss.rpi.edu To: Trent Nelson Cc: Peter Wemm , nimrodm@email.com, hackers@FreeBSD.ORG Subject: Re: Linux NVIDIA drivers vs. default XFree86 drivers (WAS: RE: Video card support) In-Reply-To: <3983B7E1.B89C35CF@echidna.stu.cowan.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 30 Jul 2000, Trent Nelson wrote: > So, given a working FreeBSD-specific kernel device driver - can the > Linux OpenGL driver/libraries provided be handled via linux.ko? i believe the general answer is a definative maybe. but honestly, do you really care enough to try? it seems like an awful lot of trouble just to use a dead end binary only driver that will doom you to an eternity of working around bugs since you can't fix them. if you want real 3d on FreeBSD go buy a 3dfx card or something else that actually has real open drivers. it's a hundred bucks for a VooDoo3. that's less than the programmer time to make the NVidia drivers work is worth, and you can actually be sure you'll have some kind of success, where the NVidia stuff is really up in the air. -garrett x----------------------------------------------------------------------x | rooneg@rpi.edu garrett rooney | | http://www.rpi.edu/~rooneg unix geek | |----------------------------------------------------------------------| | unrequited love is neat because it lasts so much longer - w. t. c. | x----------------------------------------------------------------------x To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 29 22:47:11 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from anarchy.io.com (anarchy.io.com [199.170.88.101]) by hub.freebsd.org (Postfix) with ESMTP id 6C77537B9D8 for ; Sat, 29 Jul 2000 22:47:06 -0700 (PDT) (envelope-from eighner@io.com) Received: from dumpster.io.com.io.com (aus-as3-173.io.com [208.2.106.173]) by anarchy.io.com (8.9.3/8.9.3) with SMTP id AAA13986 for ; Sun, 30 Jul 2000 00:47:04 -0500 To: freebsd-hackers@FreeBSD.org Subject: Can ordinary users run libvgl applications? From: Lars Eighner Date: 30 Jul 2000 00:53:34 -0500 Message-ID: <86k8e4go4g.fsf@dumpster.io.com> Lines: 5 X-Mailer: Gnus v5.6.45/XEmacs 21.1 - "Capitol Reef" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Can ordinary users run libvgl applications? If so, how? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 29 23:29: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from echidna.stu.cowan.edu.au (echidna.stu.cowan.edu.au [139.230.33.5]) by hub.freebsd.org (Postfix) with ESMTP id 52AC837B5B9 for ; Sat, 29 Jul 2000 23:27:39 -0700 (PDT) (envelope-from tpnelson@echidna.stu.cowan.edu.au) Received: from echidna.stu.cowan.edu.au (s212n167.rev.ecu.edu.au [139.230.212.167]) by echidna.stu.cowan.edu.au (8.9.1/8.9.1) with ESMTP id OAA13308218; Sun, 30 Jul 2000 14:27:06 +0800 (WST) Message-ID: <3983CB07.9436BB0C@echidna.stu.cowan.edu.au> Date: Sun, 30 Jul 2000 14:28:23 +0800 From: Trent Nelson X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Garrett Rooney Cc: Peter Wemm , nimrodm@email.com, hackers@FreeBSD.ORG Subject: Re: Linux NVIDIA drivers vs. default XFree86 drivers (WAS: RE: Video card support) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Garrett Rooney wrote: > > On Sun, 30 Jul 2000, Trent Nelson wrote: > > > So, given a working FreeBSD-specific kernel device driver - can the > > Linux OpenGL driver/libraries provided be handled via linux.ko? > > i believe the general answer is a definative maybe. but honestly, do you > really care enough to try? 'Maybe' is good enough for me. > that's less than the > programmer time to make the NVidia drivers work is worth, and you can > actually be sure you'll have some kind of success, where the NVidia stuff > is really up in the air. NVIDIA's stand on Open Source can only get better. Unless they're *really* stupid. > -garrett Trent. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message