From owner-freebsd-emulation Mon Jan 3 1:46:34 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 946C315462; Mon, 3 Jan 2000 01:46:20 -0800 (PST) (envelope-from marcel@scc.nl) Received: from [212.238.132.94] (helo=scones.sup.scc.nl) by post.mail.nl.demon.net with esmtp (Exim 2.02 #1) id 12544A-0002ic-00; Mon, 3 Jan 2000 09:46:18 +0000 Received: from scc.nl (scones.sup.scc.nl [192.168.2.4]) by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id KAA08139; Mon, 3 Jan 2000 10:46:14 +0100 (CET) (envelope-from marcel@scc.nl) Message-ID: <38706FE6.2D995C0C@scc.nl> Date: Mon, 03 Jan 2000 10:46:14 +0100 From: Marcel Moolenaar Organization: SCC vof X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5 i386) X-Accept-Language: en MIME-Version: 1.0 To: Doug White Cc: current@freebsd.org, emulation@freebsd.org Subject: Re: SUBMIT: compat.linux.pathmunge References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [This thread started on -hackers, went private and now pops up in -emulation through -current. You may want to look in -hackers to see the original posting by Doug White] Doug White wrote: > > I'm bringing this back up to -current to kick around some more. We may > want to move it to -emulators. I added -emulation so that current can be removed on the reply. > > Hmmm.. What we want is a way to tell the Linuxulator on a process/binary > > level whether we want /compat/linux overlaying or not. Indeed, backup > > clients will pick up /compat/linux as an ordinary directory without > > overlaying and that is exactly what we want. In most cases we do want > > the overlaying. > > Having process/binary granularity would be more useful, but is hard to > implement in an inobrusive way, as we're discovering below. :) Binary > granulatirty could be an issue for shells. I don't think it's that hard to do. It basicly needs a bit in struc proc, a test in linux_emul_find and a way to set the bit. It's generic enough to be used by other emulators as well. We just need to figure out what good ways there are to set the bit. Alternatively, we don't have it apply to all file access. We could have the 'no overlaying' property apply to opening directories only so that a directory scan will yield the native directories only. > > > If you could tag dynamic loader open()s you could have a selective > > > translator for just that, but when it's hunting for /etc/host.conf, which > > > one do you give it? Is it a call from resolv+ looking for it's > > > configuration, or a backup client putting it on tape? > > > > What about brandelf? When a static ELF binary is branded as `Linux', we > > have overlaying; when it's branded as 'LinuxBSD' (or what's in a name) > > it's a Linux binary that don't want/need overlaying. Dynamic ELF > > binaries are more tricky, but can make to work by setting > > LD_LIBRARY_PATH in a wrapper. > > Yuck. brandelf is an agreed-on standard (or is supposed to be) and it > wouldn't be appropriate to abuse it. Are any other OS's branding ELF binaries? > I'd be more apt to run the target > app in a wrapper that makes a 'shut off translation for this pid' type > syscall then execve()s the app. Kinda like nohup. What about inheritence? Setting `the bit' for a process is one thing, but what about it's children? I think we should implement the 'no overlaying' property as a static property and not a dynamic one. Having it a static property means that we need to tag it to a binary. -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Mon Jan 3 8:48:38 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from metzelkueche.tabu.uni-bonn.de (metzelkueche.tabu.uni-bonn.de [131.220.159.242]) by hub.freebsd.org (Postfix) with ESMTP id B92971516C for ; Mon, 3 Jan 2000 08:48:34 -0800 (PST) (envelope-from armin@metzelkueche.tabu.uni-bonn.de) Received: from localhost (localhost [127.0.0.1]) by metzelkueche.tabu.uni-bonn.de (8.9.3/8.9.3) with ESMTP id RAA06092 for ; Mon, 3 Jan 2000 17:48:23 +0100 Date: Mon, 3 Jan 2000 17:48:23 +0100 (MET) From: Armin Ollig X-Sender: armin@metzelkueche.tabu.uni-bonn.de To: freebsd-emulation@freebsd.org Subject: vmware again... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, i am running vladimir's vmware port on -current as described on http://www.mindspring.com/~vsilyaev/vmware/ Thanks a lot for this nice port :-) However my problem is when running NT 4.0 SP4 on vmware the virtual machine does freeze for about 7 seconds in intervals of about 30secs. My setup is this: - virtual ide disk (on dedicated scsi disk da1) - 64mb ram - virt cdrom drive (maps to my scsi drive) - floppy disk - host networking (works well) - mouse When i monitor the freebsd system with vmstat it shows me that when the virtual machine freezes disk access to da0 (my freebsd disk (the virtual disk for vmware is on da1)) is heavy also page-out activity is heave too: procs memory page disks faults cpu r b w avm fre flt re pi po fr sr da0 da1 in sy cs us sy id 0 3 0 139436 4924 61 1 1 12 26 93 0 0 285 2000 228 9 57 34 1 3 0 139524 4904 83 0 0 0 0 0 0 1 301 2256 442 7 23 69 0 7 0 139524 4896 31 0 0 274 1 0 106 4 456 1568 311 6 12 82 0 7 0 139524 4892 5 0 0 0 0 0 148 0 418 332 42 1 2 97 0 3 0 139772 4888 91 0 0 0 0 0 37 0 387 1865 336 7 22 71 1 3 0 139772 4876 82 0 0 0 0 0 0 0 310 1824 451 5 23 72 0 3 0 139772 4876 75 0 0 0 0 0 0 0 275 1808 491 3 23 74 1 3 0 136988 4876 82 0 0 0 0 0 0 1 298 1700 425 5 21 73 0 3 0 136168 4876 46 0 0 0 0 0 0 0 298 1430 373 2 21 77 0 6 0 130956 4884 34 0 0 274 1 0 35 0 266 1027 309 3 19 78 0 6 0 131756 4884 1 0 0 10 0 0 153 0 429 790 243 1 2 97 1 3 0 135696 4884 32 0 0 0 0 0 111 0 389 980 224 5 8 87 1 3 0 135696 4880 73 0 0 0 0 0 0 0 280 1969 365 5 22 73 1 3 0 134896 4880 43 0 0 0 0 0 0 0 283 1534 416 2 21 76 0 3 0 134896 4880 2 0 0 0 0 0 0 0 229 1167 295 1 20 79 1 3 0 134008 4880 1 0 0 0 0 0 0 0 255 1339 322 2 22 77 0 8 0 137316 4552 22 0 0 121 21 0 111 0 341 347 60 3 5 92 This output shows that during the freezes (3 times) the page-out activity and disk activity on da0 are heavy. WindowsNT "task manager" does not show anything during the freezes. However when i run the cpu-eating screen saver ("3D OpenGL") the virtual machine does *not* freeze at all. The screensaver runns smooth and vmstat does not report any heave disk or page-out activity: procs memory page disks faults cpu r b w avm fre flt re pi po fr sr da0 da1 in sy cs us sy id 1 3 0 124680 7484 2 0 0 0 0 0 0 0 236 893 231 1 99 0 1 3 0 124680 7484 1 0 0 0 0 0 0 0 229 801 217 2 98 0 1 3 0 102072 7480 1 0 0 0 0 0 0 0 229 790 205 2 98 0 1 3 0 101272 7480 1 0 0 0 0 0 0 0 230 804 218 3 97 0 1 3 0 101272 7480 2 0 0 1 0 0 1 0 237 900 240 2 98 0 1 3 0 102892 7480 1 0 0 0 0 0 0 0 229 803 215 2 98 0 1 3 0 102892 7480 1 0 0 0 0 0 0 0 229 789 204 2 98 0 1 3 0 102892 7480 1 0 0 0 0 0 0 0 229 790 214 1 99 0 1 3 0 102892 7480 1 0 0 0 0 0 0 0 234 864 226 2 98 0 2 3 0 101272 7480 1 0 0 0 0 0 0 0 234 889 242 2 98 0 1 3 0 123884 7480 2 0 0 1 0 0 1 0 237 907 238 1 99 0 1 3 0 124684 7480 1 0 0 0 0 0 0 0 258 1453 391 4 96 0 1 3 0 124684 7480 1 0 0 0 0 0 0 0 244 1029 267 3 97 0 1 3 0 124684 7480 1 0 0 0 0 0 0 0 242 1051 289 2 98 0 1 3 0 102072 7480 4 0 0 0 0 0 0 0 244 1009 270 2 98 0 1 3 0 101276 7476 1 0 0 0 0 0 0 0 244 1070 298 3 97 0 1 3 0 101276 7476 2 0 0 3 0 0 3 0 239 830 224 2 96 2 1 3 0 131380 7472 2 0 0 0 0 0 0 1 232 1782 260 4 96 0 2 3 0 131380 7464 1 0 0 0 0 0 0 1 233 971 189 16 84 0 1 3 0 131380 7456 1 0 0 0 0 0 0 0 229 585 105 25 75 0 1 3 0 129652 7456 1 0 0 0 0 0 0 2 284 752 124 32 68 0 all fine in screen-saver mode :-) Does anyone experienced this too ? And what about win95/98 ? Do they freeze too for some seconds ? best regards, --Armin -- "To save energy the light at the end of the tunnel will temporarily be switched off." PS: my system is a p2@300mhz, 128mb ram, scsi disk+cdrom. i did this test with and without swap space. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Mon Jan 3 10:51: 5 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from gvr.gvr.org (gvr.gvr.org [194.151.74.97]) by hub.freebsd.org (Postfix) with ESMTP id 8F8581508A; Mon, 3 Jan 2000 10:51:02 -0800 (PST) (envelope-from guido@gvr.org) Received: by gvr.gvr.org (Postfix, from userid 657) id D7399A84F; Mon, 3 Jan 2000 19:51:00 +0100 (CET) Date: Mon, 3 Jan 2000 19:51:00 +0100 From: Guido van Rooij To: Peter Wemm Cc: Hidetoshi Shimokawa , vsilyaev@mindspring.com, dillon@freebsd.org, freebsd-emulation@FreeBSD.ORG, dbutter@wireless.net Subject: Re: VMware: Questions... Message-ID: <20000103195100.A44079@gvr.gvr.org> References: <19991231010245.C630E1CA0@overcee.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <19991231010245.C630E1CA0@overcee.netplex.com.au>; from Peter Wemm on Fri, Dec 31, 1999 at 09:02:45AM +0800 Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Dec 31, 1999 at 09:02:45AM +0800, Peter Wemm wrote: > > a directory entry in the file system. This could even be done for the general > > mmap call (provided a regular file of course). But it might be a very > > specific situation because one usually would not used a file backed > > mmap in FreeBSD, yet use an anonymous mmap. > > I had a go, it turned out to be quite easy (so far). I haven't finished > verifying that it's doing everything exactly as expected yet though. I am now using the following patch. I had a printf in the if clause to see if other processes would use the code, but vmware seems the only one. In fact I have been thinking about an fcntl() for files to b able to specify the nosync option. This would be handy in mkstemp(). However Bruceb thinks it would not result in much improvement. -Guido --- vm_mmap.c.orig Sun Dec 12 04:19:29 1999 +++ vm_mmap.c Fri Dec 24 10:08:37 1999 @@ -1024,6 +1024,14 @@ return (error); objsize = round_page(vat.va_size); type = OBJT_VNODE; + /* + * if it is a regular file without any references + * we do not need to sync it. + */ + if (vp->v_type == VREG && vat.va_nlink == 0) { + flags |= MAP_NOSYNC; + } } } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Mon Jan 3 10:53: 4 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id EE60014A04 for ; Mon, 3 Jan 2000 10:53:01 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id C5DEC1CA0; Tue, 4 Jan 2000 02:52:59 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Armin Ollig Cc: freebsd-emulation@freebsd.org Subject: Re: vmware again... In-Reply-To: Message from Armin Ollig of "Mon, 03 Jan 2000 17:48:23 +0100." Date: Tue, 04 Jan 2000 02:52:59 +0800 From: Peter Wemm Message-Id: <20000103185259.C5DEC1CA0@overcee.netplex.com.au> Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Armin Ollig wrote: > Hi, > > i am running vladimir's vmware port on -current as described on > http://www.mindspring.com/~vsilyaev/vmware/ > > Thanks a lot for this nice port :-) > > However my problem is when running NT 4.0 SP4 on vmware the virtual > machine does freeze for about 7 seconds in intervals of about 30secs. This is the syncer process doing a msync() of the mmap'ed virtual memory file every 30 seconds. I have a trivial patch that should fix this properly, but I haven't been in a position to reboot my box that has vmware on it to test it. (background: vmware mmap's /var/tmp/somefile and then unlinks it. My tweak is to stop msyncing files that have been unlinked as the data does not need to be saved in a reboot. Pending dirty data is already discarded when a file is closed if it is unlinked already.) Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Mon Jan 3 11: 1:19 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id A0A181541A; Mon, 3 Jan 2000 11:01:09 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA07286; Mon, 3 Jan 2000 11:00:55 -0800 (PST) (envelope-from dillon) Date: Mon, 3 Jan 2000 11:00:55 -0800 (PST) From: Matthew Dillon Message-Id: <200001031900.LAA07286@apollo.backplane.com> To: Guido van Rooij Cc: Peter Wemm , Hidetoshi Shimokawa , vsilyaev@mindspring.com, dillon@FreeBSD.ORG, freebsd-emulation@FreeBSD.ORG, dbutter@wireless.net Subject: Re: VMware: Questions... References: <19991231010245.C630E1CA0@overcee.netplex.com.au> <20000103195100.A44079@gvr.gvr.org> Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org : :I am now using the following patch. I had a printf in the if clause :to see if other processes would use the code, but vmware seems the only one. : :In fact I have been thinking about an fcntl() for files to b able :to specify the nosync option. This would be handy in mkstemp(). :However Bruceb thinks it would not result in much improvement. : :-Guido : :--- vm_mmap.c.orig Sun Dec 12 04:19:29 1999 :+++ vm_mmap.c Fri Dec 24 10:08:37 1999 :@@ -1024,6 +1024,14 @@ : return (error); : objsize = round_page(vat.va_size); : type = OBJT_VNODE; :+ /* :+ * if it is a regular file without any references :+ * we do not need to sync it. :+ */ :+ if (vp->v_type == VREG && vat.va_nlink == 0) { :+ flags |= MAP_NOSYNC; :+ } : } : } Simple and to the point. The patch looks fine, I would go ahead and commit it! re: NOSYNC on write() for tmp files via fctl - no, there wouldn't be much of an improvement. Softupdates takes care of it pretty well and if you aren't running softupdates on the partition you still have the create/delete overhead to contend with which in most cases will be worse then for write() due to being semi-synchronous (without softupdates) rather then asynchronous (with softupdates). Also, it's possible to 'over-use' the feature and force the machine into doing unnecessary paging. I did a big set of experiments while working on the write clustering code and found that attempting to leave filesystem writes entirely up to the VM system resulted in fairly bad performance. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Mon Jan 3 11:29:21 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 0B8D415151; Mon, 3 Jan 2000 11:29:06 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id AEF531CA0; Tue, 4 Jan 2000 03:29:03 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Guido van Rooij Cc: Hidetoshi Shimokawa , vsilyaev@mindspring.com, dillon@freebsd.org, freebsd-emulation@FreeBSD.ORG, dbutter@wireless.net Subject: Re: VMware: Questions... In-Reply-To: Message from Guido van Rooij of "Mon, 03 Jan 2000 19:51:00 +0100." <20000103195100.A44079@gvr.gvr.org> Date: Tue, 04 Jan 2000 03:29:03 +0800 From: Peter Wemm Message-Id: <20000103192903.AEF531CA0@overcee.netplex.com.au> Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Guido van Rooij wrote: > On Fri, Dec 31, 1999 at 09:02:45AM +0800, Peter Wemm wrote: > > > a directory entry in the file system. This could even be done for the gen eral > > > mmap call (provided a regular file of course). But it might be a very > > > specific situation because one usually would not used a file backed > > > mmap in FreeBSD, yet use an anonymous mmap. > > > > I had a go, it turned out to be quite easy (so far). I haven't finished > > verifying that it's doing everything exactly as expected yet though. > > I am now using the following patch. I had a printf in the if clause > to see if other processes would use the code, but vmware seems the only one. > > In fact I have been thinking about an fcntl() for files to b able > to specify the nosync option. This would be handy in mkstemp(). > However Bruceb thinks it would not result in much improvement. > > -Guido > > --- vm_mmap.c.orig Sun Dec 12 04:19:29 1999 > +++ vm_mmap.c Fri Dec 24 10:08:37 1999 > @@ -1024,6 +1024,14 @@ > return (error); > objsize = round_page(vat.va_size); > type = OBJT_VNODE; > + /* > + * if it is a regular file without any references > + * we do not need to sync it. > + */ > + if (vp->v_type == VREG && vat.va_nlink == 0) { > + flags |= MAP_NOSYNC; > + } > } > } Heh, yours is simpler than mine. I was attempting a more generic solution that marked a vnode as unlinked in the filesystems and the syncer then took special care to avoid msyncing them. Mine would have caught the case where a file was mmaped first then unlinked and kept open. If the syncer could do anything special with unlinked plain files, it would then have the information to deal with them too. (It doesn't, so that part is academic). FFS already discards dirty blocks on last close if the file is already unlinked. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Mon Jan 3 11:51:49 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from gvr.gvr.org (gvr.gvr.org [194.151.74.97]) by hub.freebsd.org (Postfix) with ESMTP id A8AFB14EA2; Mon, 3 Jan 2000 11:51:45 -0800 (PST) (envelope-from guido@gvr.org) Received: by gvr.gvr.org (Postfix, from userid 657) id E6C73A84F; Mon, 3 Jan 2000 20:51:43 +0100 (CET) Date: Mon, 3 Jan 2000 20:51:43 +0100 From: Guido van Rooij To: Peter Wemm Cc: Hidetoshi Shimokawa , vsilyaev@mindspring.com, dillon@freebsd.org, freebsd-emulation@FreeBSD.ORG, dbutter@wireless.net Subject: Re: VMware: Questions... Message-ID: <20000103205143.A44784@gvr.gvr.org> References: <20000103192903.AEF531CA0@overcee.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <20000103192903.AEF531CA0@overcee.netplex.com.au>; from Peter Wemm on Tue, Jan 04, 2000 at 03:29:03AM +0800 Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Jan 04, 2000 at 03:29:03AM +0800, Peter Wemm wrote: > > Heh, yours is simpler than mine. I was attempting a more generic solution > that marked a vnode as unlinked in the filesystems and the syncer then took > special care to avoid msyncing them. Mine would have caught the case where > a file was mmaped first then unlinked and kept open. If the syncer could Which is better then mine. > do anything special with unlinked plain files, it would then have the > information to deal with them too. (It doesn't, so that part is academic). > FFS already discards dirty blocks on last close if the file is already > unlinked. > I just committed my patch. If you think yours is better, feel free to back mine out. -Guido To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Mon Jan 3 12: 0: 6 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id E677F14D34; Mon, 3 Jan 2000 11:59:59 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA08461; Mon, 3 Jan 2000 11:59:54 -0800 (PST) (envelope-from dillon) Date: Mon, 3 Jan 2000 11:59:54 -0800 (PST) From: Matthew Dillon Message-Id: <200001031959.LAA08461@apollo.backplane.com> To: Guido van Rooij Cc: Peter Wemm , Hidetoshi Shimokawa , vsilyaev@mindspring.com, dillon@FreeBSD.ORG, freebsd-emulation@FreeBSD.ORG, dbutter@wireless.net Subject: Re: VMware: Questions... References: <20000103192903.AEF531CA0@overcee.netplex.com.au> <20000103205143.A44784@gvr.gvr.org> Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org :> that marked a vnode as unlinked in the filesystems and the syncer then took :> special care to avoid msyncing them. Mine would have caught the case where :> a file was mmaped first then unlinked and kept open. If the syncer could : :Which is better then mine. :... Well, yes and no. I'd rather not get *too* fancy because, if this catches on, programs will start using the new flag anyway and we will be left with a lot of cruft in the kernel source that nobody uses any more. :I just committed my patch. If you think yours is better, feel free to back mine :out. : :-Guido -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Mon Jan 3 12:12:34 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 4B1F615166; Mon, 3 Jan 2000 12:12:30 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 06AAF1CA0; Tue, 4 Jan 2000 04:12:27 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Guido van Rooij Cc: Hidetoshi Shimokawa , vsilyaev@mindspring.com, dillon@freebsd.org, freebsd-emulation@FreeBSD.ORG, dbutter@wireless.net Subject: Re: VMware: Questions... In-Reply-To: Message from Guido van Rooij of "Mon, 03 Jan 2000 20:51:43 +0100." <20000103205143.A44784@gvr.gvr.org> Date: Tue, 04 Jan 2000 04:12:27 +0800 From: Peter Wemm Message-Id: <20000103201227.06AAF1CA0@overcee.netplex.com.au> Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Guido van Rooij wrote: > On Tue, Jan 04, 2000 at 03:29:03AM +0800, Peter Wemm wrote: > > > > Heh, yours is simpler than mine. I was attempting a more generic solution > > that marked a vnode as unlinked in the filesystems and the syncer then took > > special care to avoid msyncing them. Mine would have caught the case where > > a file was mmaped first then unlinked and kept open. If the syncer could > > Which is better then mine. But has the same overall effect - ie: stops vmware's temp file being msync'ed. The rest of the stuff is academic unless it actually does something. > > do anything special with unlinked plain files, it would then have the > > information to deal with them too. (It doesn't, so that part is academic). > > FFS already discards dirty blocks on last close if the file is already > > unlinked. > > > > I just committed my patch. If you think yours is better, feel free to back mi ne > out. No, it's not worth it. Yours is tested, mine isn't. :-) Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Mon Jan 3 12:22:30 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 283F9150FB; Mon, 3 Jan 2000 12:22:27 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id CD4A51CCE; Tue, 4 Jan 2000 04:22:21 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Matthew Dillon Cc: Guido van Rooij , Hidetoshi Shimokawa , vsilyaev@mindspring.com, dillon@FreeBSD.ORG, freebsd-emulation@FreeBSD.ORG, dbutter@wireless.net Subject: Re: VMware: Questions... In-Reply-To: Message from Matthew Dillon of "Mon, 03 Jan 2000 11:59:54 PST." <200001031959.LAA08461@apollo.backplane.com> Date: Tue, 04 Jan 2000 04:22:21 +0800 From: Peter Wemm Message-Id: <20000103202221.CD4A51CCE@overcee.netplex.com.au> Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew Dillon wrote: > :> that marked a vnode as unlinked in the filesystems and the syncer then too k > :> special care to avoid msyncing them. Mine would have caught the case wher e > :> a file was mmaped first then unlinked and kept open. If the syncer could > : > :Which is better then mine. > :... > > Well, yes and no. I'd rather not get *too* fancy because, if this > catches on, programs will start using the new flag anyway and we will > be left with a lot of cruft in the kernel source that nobody uses any > more. I tend to agree. I went looking for hammers that I knew about - ie: catching the last-unlink events. Having said that, I do like the "after the event" option though... ie: rm'ing an in-use mmap'ed file stops it being msynced by syncer. It's quite simple to do and doesn't add much at all. However, it's not worth doing it this way when it has a footprint all the way down into the filesystems when there's a much easier way of fixing the problem at hand (vmware). Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Mon Jan 3 16:53:55 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from io.dreamscape.com (io.dreamscape.com [206.64.128.6]) by hub.freebsd.org (Postfix) with ESMTP id E40341520A for ; Mon, 3 Jan 2000 16:53:46 -0800 (PST) (envelope-from krentel@dreamscape.com) Received: from dreamscape.com ([209.217.204.97]) by io.dreamscape.com (8.9.3/8.8.4) with ESMTP id TAA11223 for ; Mon, 3 Jan 2000 19:53:33 -0500 (EST) X-Dreamscape-Track-A: [209.217.204.97] X-Dreamscape-Track-B: Mon, 3 Jan 2000 19:53:33 -0500 (EST) Received: (from krentel@localhost) by dreamscape.com (8.9.3/8.9.3) id TAA03343 for freebsd-emulation@FreeBSD.ORG; Mon, 3 Jan 2000 19:53:44 -0500 (EST) (envelope-from krentel) Date: Mon, 3 Jan 2000 19:53:44 -0500 (EST) From: "Mark W. Krentel" Message-Id: <200001040053.TAA03343@dreamscape.com> To: freebsd-emulation@FreeBSD.ORG Subject: running linux binaries from ext2fs partition Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Last month, I reported a problem when running linux binaries directly from an ext2fs partition. I've done several more tests to narrow down the problem, and I can now produce a kernel dump (see below). Here's what it takes to produce the bug: (1) a Red Hat linux binary, (2) one from linux's /bin (one that uses /lib instead of /usr/lib), (3) run from an ext2fs partition, (4) in stable. By contrast, I can run Red Hat binaries from /usr/bin or /usr/X11R6/bin. I can run SuSE 6.3 binaries from /bin. (Does SuSE keep separate /lib and /usr/lib like Red Hat?) And I can run Red Hat /bin binaries by copying them to a UFS partition. But running Red Hat's /bin/ls from its ext2fs partition produces an immediate panic. As for stable vs. current, well, I don't run current, so I don't know. It's not a new problem. I'm currently running 3.4-Release, the linux_base-6.0 port with Red Hat 6.0 installed on a spare disk. But I saw the same problem with Red Hat 5.2 and the linux_base-5.2 port. And it's not something like bad sectors on the disk. I've installed Red Hat on two disks, and it panics on both. I've seen a few different panic messages: vfs_busy: unexpected lock failure ext2fs_statfs - magic number spoiled lockmgr: pid 409, not exclusive lock holder 848 unlocking So, perhaps the in-core version of the ext2fs partition is getting corrupted which then causes the panic (I mount the ext2fs partition read-only). I'd really like to track this down, but I don't know enough about the internals of linux emulation or ext2fs. But I can run experiments if some developer suggests what to try. Here's a sample kernel dump. This is in 3.4-Release with the linux_base-6.0 port. The kernel is 3.4 GENERIC plus EXT2FS and IPFIREWALL and minus a bunch of devices I don't have. I mounted Red Hat's / on /mnt (read-only), then as user, I cd'd to /mnt/bin, ran "./ls -l" and I got this panic: % gdb -k GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd". (kgdb) symbol /usr/src/sys/compile/RHTEST/kernel.debug Reading symbols from /usr/src/sys/compile/RHTEST/kernel.debug...done. (kgdb) exec-file /var/crash/kernel.3 (kgdb) core-file /var/crash/vmcore.3 IdlePTD 2506752 initial pcb at 200f18 panicstr: vfs_busy: unexpected lock failure panic messages: --- panic: lockmgr: pid 409, not exclusive lock holder 848 unlocking syncing disks... panic: vfs_busy: unexpected lock failure dumping to dev 401, offset 196608 dump 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 --- #0 boot (howto=260) at ../../kern/kern_shutdown.c:285 285 dumppcb.pcb_cr3 = rcr3(); (kgdb) bt #0 boot (howto=260) at ../../kern/kern_shutdown.c:285 #1 0xc0141f7c in at_shutdown ( function=0xc01dd20b <__set_sysctl__kern_sym_sysctl___kern_maxvnodes+19>, arg=0xc45b9cac, queue=-1072265566) at ../../kern/kern_shutdown.c:446 #2 0xc01653e5 in vfs_busy (mp=0xc08d5400, flags=16, interlkp=0xc021809c, p=0xc0217024) at ../../kern/vfs_subr.c:201 #3 0xc01686a2 in sync (p=0xc0217024, uap=0x0) at ../../kern/vfs_syscalls.c:541 #4 0xc0141b3d in boot (howto=256) at ../../kern/kern_shutdown.c:203 #5 0xc0141f7c in at_shutdown ( function=0xc01da868 <__set_sysuninit_set_sym_M_KTRACE_uninit_sys_uninit+208>, arg=0x199, queue=-1071798190) at ../../kern/kern_shutdown.c:446 #6 0xc013dd2b in lockmgr (lkp=0xc08f9a00, flags=6, interlkp=0xc45c48b0, p=0xc455c5a0) at ../../kern/kern_lock.c:373 #7 0xc0163d43 in vop_stdunlock (ap=0xc45b9dbc) at ../../kern/vfs_default.c:232 #8 0xc019a0bd in ufs_vnoperate (ap=0xc45b9dbc) at ../../ufs/ufs/ufs_vnops.c:2300 #9 0xc08aa7d6 in ?? () #10 0xc01c0043 in syscall (frame={tf_es = 39, tf_ds = 39, tf_edi = 3, tf_esi = -1077946520, tf_ebp = -1077945612, tf_isp = -1000628252, tf_ebx = 3, tf_edx = 849, tf_ecx = -1077946520, tf_eax = 141, tf_trapno = 12, tf_err = 2, tf_eip = 672096315, tf_cs = 31, tf_eflags = 642, tf_esp = -1077946524, tf_ss = 39}) at ../../i386/i386/trap.c:1100 #11 0xc01b64fc in Xint0x80_syscall () #12 0x280f5cc7 in ?? () #13 0x804a6d5 in ?? () #14 0x8049594 in ?? () #15 0x28081cb3 in ?? () (kgdb) up 6 #6 0xc013dd2b in lockmgr (lkp=0xc08f9a00, flags=6, interlkp=0xc45c48b0, p=0xc455c5a0) at ../../kern/kern_lock.c:373 373 panic("lockmgr: pid %d, not %s %d unlocking", (kgdb) info lo lkp = (struct lock *) 0xc01da868 flags = 0 p = (struct proc *) 0x0 error = 0 pid = 409 extflags = 256 (kgdb) up #7 0xc0163d43 in vop_stdunlock (ap=0xc45b9dbc) at ../../kern/vfs_default.c:232 232 return (lockmgr(l, ap->a_flags | LK_RELEASE, &ap->a_vp->v_interlock, (kgdb) info lo ap = (struct vop_unlock_args *) 0x0 l = (struct lock *) 0x0 (kgdb) up #8 0xc019a0bd in ufs_vnoperate (ap=0xc45b9dbc) at ../../ufs/ufs/ufs_vnops.c:2300 2300 return (VOCALL(ufs_vnodeop_p, ap->a_desc->vdesc_offset, ap)); (kgdb) info lo ap = (struct vop_generic_args *) 0x0 (kgdb) up #9 0xc08aa7d6 in ?? () (kgdb) up #10 0xc01c0043 in syscall (frame={tf_es = 39, tf_ds = 39, tf_edi = 3, tf_esi = -1077946520, tf_ebp = -1077945612, tf_isp = -1000628252, tf_ebx = 3, tf_edx = 849, tf_ecx = -1077946520, tf_eax = 141, tf_trapno = 12, tf_err = 2, tf_eip = 672096315, tf_cs = 31, tf_eflags = 642, tf_esp = -1077946524, tf_ss = 39}) at ../../i386/i386/trap.c:1100 1100 error = (*callp->sy_call)(p, args); (kgdb) info lo params = 0x0 callp = (struct sysent *) 0xc45c4840 p = (struct proc *) 0xc455c5a0 sticks = 0 error = 3 args = {3, -1077946520, 849, -1077946520, 3, 134578740, 0, 0} code = 141 (kgdb) up #11 0xc01b64fc in Xint0x80_syscall () (kgdb) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Mon Jan 3 18:34:40 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from assurance.rstcorp.com (rstrorp2.daf.concentric.net [216.112.242.2]) by hub.freebsd.org (Postfix) with ESMTP id D710615348 for ; Mon, 3 Jan 2000 18:34:28 -0800 (PST) (envelope-from vshah@rstcorp.com) Received: (from uucp@localhost) by assurance.rstcorp.com (8.9.3/8.9.3) id VAA26585 for ; Mon, 3 Jan 2000 21:36:00 -0500 Received: from proxy.rstcorp.com(216.112.242.5) by assurance.rstcorp.com via smap (V2.0) id xma026539; Tue, 4 Jan 00 02:35:09 GMT Received: from jabberwock.rstcorp.com (jabberwock.rstcorp.com [192.168.2.98]) by sandbox.rstcorp.com (8.9.3/8.9.3) with ESMTP id VAA19379 for ; Mon, 3 Jan 2000 21:32:38 -0500 (EST) Received: by jabberwock.rstcorp.com (Postfix, from userid 93) id 7F98E5AC9; Mon, 3 Jan 2000 21:33:34 -0500 (EST) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="dNFmJMHCPB" Content-Transfer-Encoding: 7bit Message-ID: <14449.23550.377927.676189@jabberwock.rstcorp.com> Date: Mon, 3 Jan 2000 21:33:34 -0500 (EST) From: "Viren R.Shah" To: freebsd-emulation@freebsd.org Subject: SVR4 emulation problem.. X-Mailer: VM 6.72 under 19.16 "Lille" XEmacs Lucid Reply-To: "Viren R.Shah" X-Face: )~y+U*K:yzjz{q<5lzpI_SVef'U.])9g[C9`1N@]u3,MHY7f*l7C)[_NjM4y4K8$uIUh|\u (K&&HS6,M!61&GMTk'mqmB/Qg]]X}"?TzsFl]"2v!bl8']dma.:^IY^a[lbOI>U:b<~FyK3q-p{HmZ mn~g.`~BE!5{2D:}Yi+\_KkWe?XaHj9$ko1k8iKLYv5*_2c8"G=?Up[}hn+7RNM(bzBZ_wWk6!Pf&B ?3Tcm7M7B~W%K/I0aX3]*=jP?aM]H6HBPT`oLk+0n^_;N\2\%|Rhy;p}34Q.jEsM\qtnxcm;ag%Nq Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --dNFmJMHCPB Content-Type: text/plain; charset=us-ascii Content-Description: message body text Content-Transfer-Encoding: 7bit I was trying to load the svr4 module in order to try and run a solaris x86 binary, and it failed to load with an "Exec format error" message. I looked in /var/log/messages and found: Jan 3 17:53:35 jabberwock /kernel: link_elf: symbol zfree undefined I have the following options enabled in my kernel config: options KTRACE #ktrace(1) syscall trace support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores pseudo-device streams This is from a -current system from about 4am EST Jan 2, '00 I used to have the svr4 emulator running a few months ago (before it got put into -current). Any idea what I'm missing? Here's my kernel config : --dNFmJMHCPB Content-Type: application/octet-stream Content-Description: kernel config Content-Disposition: attachment; filename="FIVE" Content-Transfer-Encoding: base64 CiMKIyBHRU5FUklDIC0tIEdlbmVyaWMgbWFjaGluZSB3aXRoIFdEL0FIeC9OQ1IvQlR4IGZh bWlseSBkaXNrcwojCiMgRm9yIG1vcmUgaW5mb3JtYXRpb24gb24gdGhpcyBmaWxlLCBwbGVh c2UgcmVhZCB0aGUgaGFuZGJvb2sgc2VjdGlvbiBvbgojIEtlcm5lbCBDb25maWd1cmF0aW9u IEZpbGVzOgojCiMgICAgaHR0cDovL3d3dy5mcmVlYnNkLm9yZy9oYW5kYm9vay9rZXJuZWxj b25maWctY29uZmlnLmh0bWwKIwojIFRoZSBoYW5kYm9vayBpcyBhbHNvIGF2YWlsYWJsZSBs b2NhbGx5IGluIC91c3Ivc2hhcmUvZG9jL2hhbmRib29rCiMgaWYgeW91J3ZlIGluc3RhbGxl ZCB0aGUgZG9jIGRpc3RyaWJ1dGlvbiwgb3RoZXJ3aXNlIGFsd2F5cyBzZWUgdGhlCiMgRnJl ZUJTRCBXb3JsZCBXaWRlIFdlYiBzZXJ2ZXIgKGh0dHA6Ly93d3cuRnJlZUJTRC5PUkcvKSBm b3IgdGhlCiMgbGF0ZXN0IGluZm9ybWF0aW9uLgojCiMgQW4gZXhoYXVzdGl2ZSBsaXN0IG9m IG9wdGlvbnMgYW5kIG1vcmUgZGV0YWlsZWQgZXhwbGFuYXRpb25zIG9mIHRoZQojIGRldmlj ZSBsaW5lcyBpcyBhbHNvIHByZXNlbnQgaW4gdGhlIC4vTElOVCBjb25maWd1cmF0aW9uIGZp bGUuIElmIHlvdSBhcmUKIyBpbiBkb3VidCBhcyB0byB0aGUgcHVycG9zZSBvciBuZWNlc3Np dHkgb2YgYSBsaW5lLCBjaGVjayBmaXJzdCBpbiBMSU5ULgojCiMgJEZyZWVCU0Q6IHNyYy9z eXMvaTM4Ni9jb25mL0dFTkVSSUMsdiAxLjIxMyAxOTk5LzEyLzEwIDEwOjQ0OjQ1IHBoayBF eHAgJAoKbWFjaGluZQkJaTM4NgpjcHUJCUk1ODZfQ1BVCmNwdQkJSTY4Nl9DUFUKaWRlbnQJ CUZJVkUKbWF4dXNlcnMJNjQKCgojbWFrZW9wdGlvbnMJREVCVUc9LWcJCSNCdWlsZCBrZXJu ZWwgd2l0aCBnZGIoMSkgZGVidWcgc3ltYm9scwoKb3B0aW9ucyAJSU5FVAkJCSNJbnRlck5F VHdvcmtpbmcKb3B0aW9ucyAJRkZTCQkJI0JlcmtlbGV5IEZhc3QgRmlsZXN5c3RlbQpvcHRp b25zIAlGRlNfUk9PVAkJI0ZGUyB1c2FibGUgYXMgcm9vdCBkZXZpY2UgW2tlZXAgdGhpcyFd Cm9wdGlvbnMgCUNPTVBBVF80MwkJI0NvbXBhdGlibGUgd2l0aCBCU0QgNC4zIFtLRUVQIFRI SVMhXQpvcHRpb25zIAlTQ1NJX0RFTEFZPTgwMDAJCSNCZSBwZXNzaW1pc3RpYyBhYm91dCBK b2UgU0NTSSBkZXZpY2UKb3B0aW9ucyAJVUNPTlNPTEUJCSNBbGxvdyB1c2VycyB0byBncmFi IHRoZSBjb25zb2xlCm9wdGlvbnMgCVVTRVJDT05GSUcJCSNib290IC1jIGVkaXRvcgpvcHRp b25zIAlLVFJBQ0UJCQkja3RyYWNlKDEpIHN5c2NhbGwgdHJhY2Ugc3VwcG9ydApvcHRpb25z IAlTWVNWU0hNCQkJI1NZU1Ytc3R5bGUgc2hhcmVkIG1lbW9yeQpvcHRpb25zIAlTWVNWTVNH CQkJI1NZU1Ytc3R5bGUgbWVzc2FnZSBxdWV1ZXMKb3B0aW9ucyAJU1lTVlNFTQkJCSNTWVNW LXN0eWxlIHNlbWFwaG9yZXMKb3B0aW9ucwkJTkZTCgpjb250cm9sbGVyCWlzYTAKY29udHJv bGxlcglwY2kwCgojIEZsb3BweSBkcml2ZXMKY29udHJvbGxlcglmZGMwCWF0IGlzYT8gcG9y dCBJT19GRDEgaXJxIDYgZHJxIDIKZGV2aWNlCQlmZDAJYXQgZmRjMCBkcml2ZSAwCmRldmlj ZQkJZmQxCWF0IGZkYzAgZHJpdmUgMQoKIyBBVEEgYW5kIEFUQVBJIGRldmljZXMKY29udHJv bGxlcglhdGEwCWF0IGlzYT8gcG9ydCBJT19XRDEgaXJxIDE0CmNvbnRyb2xsZXIJYXRhMQlh dCBpc2E/IHBvcnQgSU9fV0QyIGlycSAxNQpjb250cm9sbGVyCWF0YTIKZGV2aWNlCQlhdGFk aXNrMAkjIEFUQSBkaXNrIGRyaXZlcwpkZXZpY2UJCWF0YXBpY2QwCSMgQVRBUEkgQ0RST00g ZHJpdmVzCm9wdGlvbnMgCUFUQV9TVEFUSUNfSUQJCSNTdGF0aWMgZGV2aWNlIG51bWJlcmlu ZwpvcHRpb25zIAlBVEFfRU5BQkxFX0FUQVBJX0RNQQkjRW5hYmxlIERNQSBvbiBBVEFQSSBk ZXZpY2VzCgpjb250cm9sbGVyCWFoYzAJCSMgQUhBMjk0MCBhbmQgb25ib2FyZCBBSUM3eHh4 IGRldmljZXMKCgojIFNDU0kgcGVyaXBoZXJhbHMKIyBPbmx5IG9uZSBvZiBlYWNoIG9mIHRo ZXNlIGlzIG5lZWRlZCwgdGhleSBhcmUgZHluYW1pY2FsbHkgYWxsb2NhdGVkLgpjb250cm9s bGVyCXNjYnVzMAkJIyBTQ1NJIGJ1cyAocmVxdWlyZWQpCmRldmljZQkJZGEwCQkjIERpcmVj dCBBY2Nlc3MgKGRpc2tzKQpkZXZpY2UJCXBhc3MwCQkjIFBhc3N0aHJvdWdoIGRldmljZSAo ZGlyZWN0IFNDU0kgYWNjZXNzKQoKCiMgYXRrYmRjMCBjb250cm9scyBib3RoIHRoZSBrZXli b2FyZCBhbmQgdGhlIFBTLzIgbW91c2UKY29udHJvbGxlcglhdGtiZGMwCWF0IGlzYT8gcG9y dCBJT19LQkQKZGV2aWNlCQlhdGtiZDAJYXQgYXRrYmRjPyBpcnEgMQpkZXZpY2UJCXBzbTAJ YXQgYXRrYmRjPyBpcnEgMTIKCmRldmljZQkJdmdhMAlhdCBpc2E/IHBvcnQgPyBjb25mbGlj dHMKCiMgc3BsYXNoIHNjcmVlbi9zY3JlZW4gc2F2ZXIKI3BzZXVkby1kZXZpY2UJc3BsYXNo CgojIHN5c2NvbnMgaXMgdGhlIGRlZmF1bHQgY29uc29sZSBkcml2ZXIsIHJlc2VtYmxpbmcg YW4gU0NPIGNvbnNvbGUKZGV2aWNlCQlzYzAJYXQgaXNhPwoKCiMgRmxvYXRpbmcgcG9pbnQg c3VwcG9ydCAtIGRvIG5vdCBkaXNhYmxlLgpkZXZpY2UJCW5weDAJYXQgbmV4dXM/IHBvcnQg SU9fTlBYIGlycSAxMwoKCiMgU2VyaWFsIChDT00pIHBvcnRzCmRldmljZQkJc2lvMAlhdCBp c2E/IHBvcnQgSU9fQ09NMSBmbGFncyAweDEwIGlycSA0CmRldmljZQkJc2lvMQlhdCBpc2E/ IHBvcnQgSU9fQ09NMiBpcnEgMwoKIyBQc2V1ZG8gZGV2aWNlcyAtIHRoZSBudW1iZXIgaW5k aWNhdGVzIGhvdyBtYW55IHVuaXRzIHRvIGFsbG9jYXRlZC4KcHNldWRvLWRldmljZQlsb29w CQkjIE5ldHdvcmsgbG9vcGJhY2sKcHNldWRvLWRldmljZQlldGhlcgkJIyBFdGhlcm5ldCBz dXBwb3J0CnBzZXVkby1kZXZpY2UJcHR5CQkjIFBzZXVkby10dHlzICh0ZWxuZXQgZXRjKQoK IyBUaGUgYGJwZicgcHNldWRvLWRldmljZSBlbmFibGVzIHRoZSBCZXJrZWxleSBQYWNrZXQg RmlsdGVyLgojIEJlIGF3YXJlIG9mIHRoZSBhZG1pbmlzdHJhdGl2ZSBjb25zZXF1ZW5jZXMg b2YgZW5hYmxpbmcgdGhpcyEKcHNldWRvLWRldmljZQlicGYJCSNCZXJrZWxleSBwYWNrZXQg ZmlsdGVyCgpvcHRpb25zIFNPRlRVUERBVEVTCgojb3B0aW9ucwkJUE5QQklPUwojZGV2aWNl CQlwY20wCgpjb250cm9sbGVyCW1paWJ1czAJCSMgTUlJIGJ1cyBzdXBwb3J0CmRldmljZQkJ eGwwCQkjIDNDb20gM2M5MHggKGBgQm9vbWVyYW5nJycsIGBgQ3ljbG9uZScnKQoKb3B0aW9u cwkJRERCCgpvcHRpb25zIAlJUEZJUkVXQUxMCQkjZmlyZXdhbGwKb3B0aW9ucyAJSVBGSVJF V0FMTF9WRVJCT1NFCSNwcmludCBpbmZvcm1hdGlvbiBhYm91dAoJCQkJCSMgZHJvcHBlZCBw YWNrZXRzCm9wdGlvbnMgCUlQRklSRVdBTExfVkVSQk9TRV9MSU1JVD0xMDAJI2xpbWl0IHZl cmJvc2l0eQpvcHRpb25zIAlJUEZJUkVXQUxMX0RFRkFVTFRfVE9fQUNDRVBUCSNhbGxvdyBl dmVyeXRoaW5nIGJ5IGRlZmF1bHQKb3B0aW9ucyAJSVBESVZFUlQJCSNkaXZlcnQgc29ja2V0 cwoKcHNldWRvLWRldmljZSAJc3RyZWFtcwojb3B0aW9ucwkJQ09NUEFUX1NWUjQ= --dNFmJMHCPB Content-Type: text/plain; charset=us-ascii Content-Description: message body and .signature Content-Transfer-Encoding: 7bit Thanks Viren -- Viren R. Shah, {viren @ rstcorp . com} "SCSI *is* God's bus and it's hardly an old-fashioned (or academic) attitude to think so, it's simply an informed attitude." -- Jordan Hubbard --dNFmJMHCPB-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Mon Jan 3 20:15:29 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from smtp10.atl.mindspring.net (smtp10.atl.mindspring.net [207.69.200.246]) by hub.freebsd.org (Postfix) with ESMTP id A029C14DDD for ; Mon, 3 Jan 2000 20:15:26 -0800 (PST) (envelope-from vsilyaev@mindspring.com) Received: from mindspring.com (user-2ivearb.dialup.mindspring.com [165.247.43.107]) by smtp10.atl.mindspring.net (8.9.3/8.8.5) with ESMTP id XAA20867; Mon, 3 Jan 2000 23:15:23 -0500 (EST) Received: (from vsilyaev@localhost) by mindspring.com (8.9.3/8.9.3) id XAA00383; Mon, 3 Jan 2000 23:15:21 -0500 (EST) (envelope-from vsilyaev) Date: Mon, 3 Jan 2000 23:15:21 -0500 From: "Vladimir N. Silyaev" To: Armin Ollig Cc: freebsd-emulation@freebsd.org Subject: Re: vmware again... Message-ID: <20000103231521.A297@jupiter.delta.ny.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > However my problem is when running NT 4.0 SP4 on vmware the virtual > machine does freeze for about 7 seconds in intervals of about 30secs. Try to apply the patch from the next message: http://www.geocrawler.com/archives/3/157/1999/12/0/3014014 -- Vladimir Silyaev To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Tue Jan 4 1:57:32 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from gvr.gvr.org (gvr.gvr.org [194.151.74.97]) by hub.freebsd.org (Postfix) with ESMTP id 47D42150C5 for ; Tue, 4 Jan 2000 01:57:30 -0800 (PST) (envelope-from guido@gvr.org) Received: by gvr.gvr.org (Postfix, from userid 657) id D1DEDA84F; Tue, 4 Jan 2000 10:57:28 +0100 (CET) Date: Tue, 4 Jan 2000 10:57:28 +0100 From: Guido van Rooij To: "Vladimir N. Silyaev" Cc: Armin Ollig , freebsd-emulation@freebsd.org Subject: Re: vmware again... Message-ID: <20000104105728.A47144@gvr.gvr.org> References: <20000103231521.A297@jupiter.delta.ny.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <20000103231521.A297@jupiter.delta.ny.us>; from Vladimir N. Silyaev on Mon, Jan 03, 2000 at 11:15:21PM -0500 Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Jan 03, 2000 at 11:15:21PM -0500, Vladimir N. Silyaev wrote: > > > However my problem is when running NT 4.0 SP4 on vmware the virtual > > machine does freeze for about 7 seconds in intervals of about 30secs. > Try to apply the patch from the next message: > http://www.geocrawler.com/archives/3/157/1999/12/0/3014014 I just committed another one that does not have the drawbacks of the above patch. See: http://www.FreeBSD.org/cgi/cvsweb.cgi/src/sys/vm/vm_mmap.c.diff?r1=1.105&r2=1.106 -Guido To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Tue Jan 4 3:18:26 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from metzelkueche.tabu.uni-bonn.de (metzelkueche.tabu.uni-bonn.de [131.220.159.242]) by hub.freebsd.org (Postfix) with ESMTP id 12AA514FFD for ; Tue, 4 Jan 2000 03:18:15 -0800 (PST) (envelope-from armin@metzelkueche.tabu.uni-bonn.de) Received: from localhost (localhost [127.0.0.1]) by metzelkueche.tabu.uni-bonn.de (8.9.3/8.9.3) with ESMTP id MAA16612; Tue, 4 Jan 2000 12:17:53 +0100 Date: Tue, 4 Jan 2000 12:17:53 +0100 (MET) From: Armin Ollig X-Sender: armin@metzelkueche.tabu.uni-bonn.de To: Guido van Rooij Cc: "Vladimir N. Silyaev" , Armin Ollig , freebsd-emulation@freebsd.org Subject: Re: vmware again... In-Reply-To: <20000104105728.A47144@gvr.gvr.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Guido, i applied your patch, everything works like a charm now. Thanks a lot. --Armin -- "To save energy the light at the end of the tunnel will temporarily be switched off." On Tue, 4 Jan 2000, Guido van Rooij wrote: > On Mon, Jan 03, 2000 at 11:15:21PM -0500, Vladimir N. Silyaev wrote: > > > > > However my problem is when running NT 4.0 SP4 on vmware the virtual > > > machine does freeze for about 7 seconds in intervals of about 30secs. > > Try to apply the patch from the next message: > > http://www.geocrawler.com/archives/3/157/1999/12/0/3014014 > > I just committed another one that does not have the drawbacks of the above > patch. See: > http://www.FreeBSD.org/cgi/cvsweb.cgi/src/sys/vm/vm_mmap.c.diff?r1=1.105&r2=1.106 > > -Guido > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Tue Jan 4 4:15: 1 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from gw-nl4.philips.com (gw-nl4.philips.com [192.68.44.36]) by hub.freebsd.org (Postfix) with ESMTP id 94C6414FFD for ; Tue, 4 Jan 2000 04:14:58 -0800 (PST) (envelope-from Guido.vanRooij@nl.origin-it.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl4.philips.com with ESMTP id NAA15719 for ; Tue, 4 Jan 2000 13:14:56 +0100 (MET) (envelope-from Guido.vanRooij@nl.origin-it.com) Received: from smtprelay-eur1.philips.com(130.139.36.3) by gw-nl4.philips.com via mwrap (4.0a) id xma015717; Tue, 4 Jan 00 13:14:57 +0100 Received: from dibbs1.eur.cis.philips.com (dibbs1.eur.cis.philips.com [130.139.33.66]) by smtprelay-nl1.philips.com (8.9.3/8.8.5-1.2.2m-19990317) with ESMTP id NAA25339 for ; Tue, 4 Jan 2000 13:14:56 +0100 (MET) Received: from eniac.mpn.cp.philips.com (eniac.mpn.cp.philips.com [130.139.64.192]) by dibbs1.eur.cis.philips.com (8.9.3/8.9.3) with ESMTP id NAA22043 for ; Tue, 4 Jan 2000 13:14:56 +0100 (MET) (envelope-from Guido.vanRooij@nl.origin-it.com) Received: by eniac.mpn.cp.philips.com (VMailer, from userid 4887) id EEDB97865; Tue, 4 Jan 2000 13:14:55 +0100 (CET) Date: Tue, 4 Jan 2000 13:14:55 +0100 To: freebsd-emulation@freebsd.org Subject: NT on vmware: timing problems Message-ID: <20000104131455.A75184@eniac.mpn.cp.philips.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i From: Guido.vanRooij@nl.origin-it.com (Guido van Rooij) Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org When you run NT in a VMWare box, time gopes very slowly on the NT platform. Apparently this is not due to lack of /dev/rtc because VMware states (when it discovers that /dev/rtc is absent) that there will only be timing problems on Windows 95. The problem is that an NT second takes about 3 wall clock seconds. Does someone know what the cause of the timing problem is and how to fix it? -Guido To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Tue Jan 4 11:32:27 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from relay.securify.com (relay.securify.com [207.5.63.61]) by hub.freebsd.org (Postfix) with SMTP id 3585B14CCA for ; Tue, 4 Jan 2000 11:32:25 -0800 (PST) (envelope-from bob@securify.com) Received: by relay.securify.com; id LAA14186; Tue, 4 Jan 2000 11:31:57 -0800 Received: from unknown(10.5.63.6) by relay.securify.com via smap (V5.5) id xma014181; Tue, 4 Jan 00 11:31:10 -0800 Received: from securify.com (vg-145.securify.com [10.5.63.145]) by dude.securify.com (8.8.7/8.8.7) with ESMTP id LAA16628; Tue, 4 Jan 2000 11:31:09 -0800 Message-ID: <38724B62.522B5F79@securify.com> Date: Tue, 04 Jan 2000 11:34:58 -0800 From: Bob Shaw Organization: Kroll-O'Gara X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: emulation@freebsd.org, bob@securify.com Subject: linux_base-6.1: Are Linux threads supported? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'd like to install Blackdown JDK 1.2.2 RC3 on FreeBSD 3.4 with linux_base-6.1. I know there are some Blackdown problems with native threads, but I have not been able to determine whether there are any FreeBSD-specific problems that will remain once Blackdown gets their release fixed. Will native threads at the JDK level map to native threads at the FreeBSD 3.4 level? (If so, is there any idea how performance will compare to native Linux?) We're intending to run a servlet engine, so native threads seems like a necessity. Having the servlet engine block when a single thread blocks sounds bad. Thanks for any help or pointers. -- Bob Shaw bob@securify.com (650) 213-4600 x4102 The Kroll-O'Gara Company PGP Key: ldap://certserver.pgp.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Tue Jan 4 11:47:13 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id 66D4C14D6E for ; Tue, 4 Jan 2000 11:47:10 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.9.3/8.9.3) with SMTP id MAA13393; Tue, 4 Jan 2000 12:47:09 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id MAA14347; Tue, 4 Jan 2000 12:47:08 -0700 Date: Tue, 4 Jan 2000 12:47:08 -0700 Message-Id: <200001041947.MAA14347@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Bob Shaw Cc: emulation@FreeBSD.ORG Subject: Re: linux_base-6.1: Are Linux threads supported? In-Reply-To: <38724B62.522B5F79@securify.com> References: <38724B62.522B5F79@securify.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@mt.sri.com (Nate Williams) Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I'd like to install Blackdown JDK 1.2.2 RC3 on FreeBSD 3.4 > with linux_base-6.1. I know there are some Blackdown problems with > native threads, but I have not been able to determine whether there > are any FreeBSD-specific problems that will remain once Blackdown > gets their release fixed. Will native threads at the JDK level map to > native threads at the FreeBSD 3.4 level? (If so, is there any idea how > performance will compare to native Linux?) FreeBSD has no native 'kernel threads', so it won't help out. However, the Linux JIT is a *big* improvement. > We're intending to run a servlet engine, so native threads seems like > a necessity. Having the servlet engine block when a single thread > blocks sounds bad. See above. Using green-threads is probably more effecient for you on FreeBSD. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Tue Jan 4 13:28:20 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id 35DBF14EDF for ; Tue, 4 Jan 2000 13:28:17 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.3/8.9.3) with ESMTP id NAA25824; Tue, 4 Jan 2000 13:27:58 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <200001042127.NAA25824@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: nate@mt.sri.com (Nate Williams) Cc: Bob Shaw , emulation@FreeBSD.ORG Subject: Re: linux_base-6.1: Are Linux threads supported? In-reply-to: Your message of "Tue, 04 Jan 2000 12:47:08 MST." <200001041947.MAA14347@mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 04 Jan 2000 13:27:58 -0800 From: Amancio Hasty Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > I'd like to install Blackdown JDK 1.2.2 RC3 on FreeBSD 3.4 > > with linux_base-6.1. I know there are some Blackdown problems with > > native threads, but I have not been able to determine whether there > > are any FreeBSD-specific problems that will remain once Blackdown > > gets their release fixed. Will native threads at the JDK level map to > > native threads at the FreeBSD 3.4 level? (If so, is there any idea how > > performance will compare to native Linux?) > > FreeBSD has no native 'kernel threads', so it won't help out. However, > the Linux JIT is a *big* improvement. I could have sworn to have used linux kernel threads in FreeBSD 8) -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Tue Jan 4 13:35:59 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id 9E8B314CF6 for ; Tue, 4 Jan 2000 13:35:56 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.9.3/8.9.3) with SMTP id OAA14461; Tue, 4 Jan 2000 14:35:51 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id OAA15019; Tue, 4 Jan 2000 14:35:50 -0700 Date: Tue, 4 Jan 2000 14:35:50 -0700 Message-Id: <200001042135.OAA15019@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Amancio Hasty Cc: nate@mt.sri.com (Nate Williams), Bob Shaw , emulation@FreeBSD.ORG Subject: Re: linux_base-6.1: Are Linux threads supported? In-Reply-To: <200001042127.NAA25824@rah.star-gate.com> References: <200001041947.MAA14347@mt.sri.com> <200001042127.NAA25824@rah.star-gate.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@mt.sri.com (Nate Williams) Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > I'd like to install Blackdown JDK 1.2.2 RC3 on FreeBSD 3.4 > > > with linux_base-6.1. I know there are some Blackdown problems with > > > native threads, but I have not been able to determine whether there > > > are any FreeBSD-specific problems that will remain once Blackdown > > > gets their release fixed. Will native threads at the JDK level map to > > > native threads at the FreeBSD 3.4 level? (If so, is there any idea how > > > performance will compare to native Linux?) > > > > FreeBSD has no native 'kernel threads', so it won't help out. However, > > the Linux JIT is a *big* improvement. > > I could have sworn to have used linux kernel threads in FreeBSD 8) Linux kernel threads are not native kernel threads. They are not part of the standard distribution, they have an incompatible license, and do not scale very well on most Java applications. However, for *certain* applications they do work, but these are limited to mostly CPU-bound applications that do light I/O. Applications that have lots of I/O threads will not work well with the Linux-threads stuff. (While applications run with the green-threads version tends to work *very* well, almost as well as C code.) Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Tue Jan 4 13:44:20 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from luna.lyris.net (luna.shelby.com [207.90.155.6]) by hub.freebsd.org (Postfix) with ESMTP id AD77414ED5 for ; Tue, 4 Jan 2000 13:44:18 -0800 (PST) (envelope-from kip@lyris.com) Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4) id NAA22932; Tue, 4 Jan 2000 13:43:50 -0800 (PST) Received: from (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Tue, 04 Jan 2000 13:43:50 -0800 Date: Tue, 4 Jan 2000 13:43:50 -0800 (PST) From: Kip Macy To: Nate Williams Cc: emulation@FreeBSD.ORG Subject: Re: linux_base-6.1: Are Linux threads supported? In-Reply-To: <200001042135.OAA15019@mt.sri.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SMTP-HELO: luna.lyris.com X-SMTP-MAIL-FROM: kip@lyris.com X-SMTP-RCPT-TO: nate@mt.sri.com,emulation@FreeBSD.ORG X-SMTP-PEER-INFO: luna.shelby.com [207.90.155.6] Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Linux kernel threads are not native kernel threads. They are not part > of the standard distribution, they have an incompatible license, and do > not scale very well on most Java applications. However, for *certain* > applications they do work, but these are limited to mostly CPU-bound > applications that do light I/O. Applications that have lots of I/O > threads will not work well with the Linux-threads stuff. (While > applications run with the green-threads version tends to work *very* > well, almost as well as C code.) > A friend of mine at Berkeley did some benchmarking of some native threads vs. green threads jave code on Linux and found that the native threads implementation at times ran 100x more slowly. At least on Linux, kernel threads are very heavy weight. This is, at least in part due to the way they handle scheduling and synchronization. -Kip To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Tue Jan 4 13:45:50 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id EC40214CF6 for ; Tue, 4 Jan 2000 13:45:48 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.3/8.9.3) with ESMTP id NAA26137; Tue, 4 Jan 2000 13:45:29 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <200001042145.NAA26137@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: nate@mt.sri.com (Nate Williams) Cc: Bob Shaw , emulation@FreeBSD.ORG Subject: Re: linux_base-6.1: Are Linux threads supported? In-reply-to: Your message of "Tue, 04 Jan 2000 14:35:50 MST." <200001042135.OAA15019@mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 04 Jan 2000 13:45:29 -0800 From: Amancio Hasty Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > > I'd like to install Blackdown JDK 1.2.2 RC3 on FreeBSD 3.4 > > > > with linux_base-6.1. I know there are some Blackdown problems with > > > > native threads, but I have not been able to determine whether there > > > > are any FreeBSD-specific problems that will remain once Blackdown > > > > gets their release fixed. Will native threads at the JDK level map to > > > > native threads at the FreeBSD 3.4 level? (If so, is there any idea how > > > > performance will compare to native Linux?) > > > > > > FreeBSD has no native 'kernel threads', so it won't help out. However, > > > the Linux JIT is a *big* improvement. > > > > I could have sworn to have used linux kernel threads in FreeBSD 8) > > Linux kernel threads are not native kernel threads. They are not part > of the standard distribution, they have an incompatible license, and do > not scale very well on most Java applications. However, for *certain* Dumb question: Are the Linux kernel threads on FreeBSD comparable to Linux kernel threads running on Linux? That is do the kernel threaded apps run with the same architectural flaws both on Linux and FreeBSD? -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Tue Jan 4 14:23:48 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from test.tar.com (test.tar.com [204.95.187.4]) by hub.freebsd.org (Postfix) with ESMTP id 8DC8A14DD4 for ; Tue, 4 Jan 2000 14:23:42 -0800 (PST) (envelope-from dick@test.tar.com) Received: (from dick@localhost) by test.tar.com (8.9.3/8.9.3) id QAA29153; Tue, 4 Jan 2000 16:23:25 -0600 (CST) (envelope-from dick) Date: Tue, 4 Jan 2000 16:23:25 -0600 From: "Richard Seaman, Jr." To: Nate Williams Cc: Amancio Hasty , Bob Shaw , emulation@FreeBSD.ORG Subject: Re: linux_base-6.1: Are Linux threads supported? Message-ID: <20000104162325.C15887@tar.com> References: <200001041947.MAA14347@mt.sri.com> <200001042127.NAA25824@rah.star-gate.com> <200001042135.OAA15019@mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001042135.OAA15019@mt.sri.com>; from nate@mt.sri.com on Tue, Jan 04, 2000 at 02:35:50PM -0700 Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Jan 04, 2000 at 02:35:50PM -0700, Nate Williams wrote: > > > > I'd like to install Blackdown JDK 1.2.2 RC3 on FreeBSD 3.4 > > > > with linux_base-6.1. I know there are some Blackdown problems with > > > > native threads, but I have not been able to determine whether there > > > > are any FreeBSD-specific problems that will remain once Blackdown > > > > gets their release fixed. Will native threads at the JDK level map to > > > > native threads at the FreeBSD 3.4 level? (If so, is there any idea how > > > > performance will compare to native Linux?) > > > > > > FreeBSD has no native 'kernel threads', so it won't help out. However, > > > the Linux JIT is a *big* improvement. > > > > I could have sworn to have used linux kernel threads in FreeBSD 8) > > Linux kernel threads are not native kernel threads. They are not part > of the standard distribution, they have an incompatible license, and do > not scale very well on most Java applications. However, for *certain* > applications they do work, but these are limited to mostly CPU-bound > applications that do light I/O. Applications that have lots of I/O > threads will not work well with the Linux-threads stuff. (While > applications run with the green-threads version tends to work *very* > well, almost as well as C code.) I'm confused by all this. For more than a year the FreeBSD linuxulator has had a functioning "clone()" syscall. AFAIK it works fine with the libpthread that ships with recent versions of linux, as long as its used with a compatible version of linux glibc. If you want SMP threads in the linuxulator, you need to be running FreeBSD-current. If you're UP, then AFAIK any version of 3.X since about last April or May is ok. I don't understand why I/O threads would not work well with linuxthreads. Programs like squid work very well with linuxthreads, and AFAIK will outperform squid compiled with FreeBSD "user" threads. "kernel threads" should improve I/O concurrency when there is I/O that blocks in the kernel. Each linuxthreads context switch involves a syscall. If you have a threads implemenation that can do some context switches without making a syscall (should be very doable, but FreeBSD user threads isn't there at this point), then those context switches should be *much* faster than linuxthreads, because a syscall is so expensive. I have to assume that the "green-threads" you are referring to are different than FreeBSD user threads. If they're that much faster that linuxthreads (which are very competitive with FreeBSD user threads at the moment), and if they can handle "concurrent I/O" like kernel threads, then I would assume that Jason Evans and the threads discussion that has been going on in the -arch mailing list ought to look very closely at this implementation. It sure sounds much better than anything FreeBSD has now. -- Richard Seaman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 262-367-5450 Chenequa WI 53058 fax: 262-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Tue Jan 4 15:52:35 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id 9A18914A28 for ; Tue, 4 Jan 2000 15:52:32 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.9.3/8.9.3) with SMTP id QAA15749; Tue, 4 Jan 2000 16:52:29 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id QAA15718; Tue, 4 Jan 2000 16:52:28 -0700 Date: Tue, 4 Jan 2000 16:52:28 -0700 Message-Id: <200001042352.QAA15718@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Amancio Hasty Cc: nate@mt.sri.com (Nate Williams), Bob Shaw , emulation@FreeBSD.ORG Subject: Re: linux_base-6.1: Are Linux threads supported? In-Reply-To: <200001042145.NAA26137@rah.star-gate.com> References: <200001042135.OAA15019@mt.sri.com> <200001042145.NAA26137@rah.star-gate.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@mt.sri.com (Nate Williams) Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > > > I'd like to install Blackdown JDK 1.2.2 RC3 on FreeBSD 3.4 > > > > > with linux_base-6.1. I know there are some Blackdown problems with > > > > > native threads, but I have not been able to determine whether there > > > > > are any FreeBSD-specific problems that will remain once Blackdown > > > > > gets their release fixed. Will native threads at the JDK level map to > > > > > native threads at the FreeBSD 3.4 level? (If so, is there any idea how > > > > > performance will compare to native Linux?) > > > > > > > > FreeBSD has no native 'kernel threads', so it won't help out. However, > > > > the Linux JIT is a *big* improvement. > > > > > > I could have sworn to have used linux kernel threads in FreeBSD 8) > > > > Linux kernel threads are not native kernel threads. They are not part > > of the standard distribution, they have an incompatible license, and do > > not scale very well on most Java applications. However, for *certain* > > Dumb question: Are the Linux kernel threads on FreeBSD comparable to > Linux kernel threads running on Linux? That is do the kernel threaded apps > run with the same architectural flaws both on Linux and FreeBSD? I believe so. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Tue Jan 4 16: 3:52 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id 7C3B414D5E for ; Tue, 4 Jan 2000 16:03:41 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.9.3/8.9.3) with SMTP id RAA15851; Tue, 4 Jan 2000 17:03:34 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id RAA15774; Tue, 4 Jan 2000 17:03:33 -0700 Date: Tue, 4 Jan 2000 17:03:33 -0700 Message-Id: <200001050003.RAA15774@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Richard Seaman, Jr." Cc: Nate Williams , Amancio Hasty , Bob Shaw , emulation@FreeBSD.ORG Subject: Re: linux_base-6.1: Are Linux threads supported? In-Reply-To: <20000104162325.C15887@tar.com> References: <200001041947.MAA14347@mt.sri.com> <200001042127.NAA25824@rah.star-gate.com> <200001042135.OAA15019@mt.sri.com> <20000104162325.C15887@tar.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@mt.sri.com (Nate Williams) Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Linux kernel threads are not native kernel threads. They are not part > > of the standard distribution, they have an incompatible license, and do > > not scale very well on most Java applications. However, for *certain* > > applications they do work, but these are limited to mostly CPU-bound > > applications that do light I/O. Applications that have lots of I/O > > threads will not work well with the Linux-threads stuff. (While > > applications run with the green-threads version tends to work *very* > > well, almost as well as C code.) > > I'm confused by all this. No need to be confused. :) > For more than a year the FreeBSD linuxulator has had a functioning > "clone()" syscall. AFAIK it works fine with the libpthread that ships > with recent versions of linux, as long as its used with a compatible > version of linux glibc. So far so good. Again, this isn't 'native' though, as I pointed out in an earlier email. > If you want SMP threads in the linuxulator, you need to be running > FreeBSD-current. If you're UP, then AFAIK any version of 3.X since > about last April or May is ok. Right, this gives you the 1:1 user/kernel thread mapping. > I don't understand why I/O threads would not work well with > linuxthreads. They work fine, but tend to be too heavy when the number of active I/O threads gets large. Too many threads are spawned off, taking up too many resources and the system tends to bog down heavily. On my system, I had roughly 2000 running threads, with about 50-100 of them active at any one point. About 2/3 of them were involved in I/O of some kind, and as such would become 'kernel threads' in the kernel thread implementation. Using the green-thread implementation of the Java VM, context switches were very fast, and the use of select inside the green-thread libraries caused the application to rarely block inside the kernel. (Although, at times it did block, especially when writing to disk.) > Programs like squid work very well with linuxthreads, and AFAIK will > outperform squid compiled with FreeBSD "user" threads. "kernel > threads" should improve This is sometimes the case, but not always. In my case, the number of threads and their weight caused the program to behave very *poorly*, because it took so many more resources. The 'userland thread' implementation (using select behind the scenes) performed much better than the 'kernel thread' version. > I/O concurrency when there is I/O that blocks in the kernel. In my case, most of the time the I/O didn't block in the kernel because select was used. Keeping things 'lightweight' made it much easier to do context switching, and the number of resources used was much less. So, I state again the existing 'non-native' kernel thread implementation is not always a win. It depends on your application. > Each linuxthreads context switch involves a syscall. If you have a threads > implemenation that can do some context switches without making a syscall > (should be very doable, but FreeBSD user threads isn't there at this point), > then those context switches should be *much* faster than linuxthreads, > because a syscall is so expensive. I have to assume that the "green-threads" > you are referring to are different than FreeBSD user threads. They are similar to the user-land threads code that exist in FreeBSD, but are tuned specifically to the JVM. They are in fact part of the JDK implementation. However, like the existing userland threads code, they block inside of the kernel, since they have no concept of 'kernel threads'. Finally, they are not 'publically' available, so we couldn't use them even if we wanted to. The other choice in the JDK is to use 'native' kernel threads, but the existing 'kernel threads' in FreeBSD has some negative side-effects which you just spoke about. So, in summary, the Linux JDK that uses native threads is not necessarily a win because of it's use of native threads. As a matter of fact, it may be a loss, due to the architectural side-effects of the existing linux threads implementation. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Tue Jan 4 21:28:27 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 4AA2214BB8 for ; Tue, 4 Jan 2000 21:28:16 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id AEA871CC6; Wed, 5 Jan 2000 13:28:12 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: nate@mt.sri.com (Nate Williams) Cc: Amancio Hasty , Bob Shaw , emulation@FreeBSD.ORG Subject: Re: linux_base-6.1: Are Linux threads supported? In-Reply-To: Message from Nate Williams of "Tue, 04 Jan 2000 14:35:50 MST." <200001042135.OAA15019@mt.sri.com> Date: Wed, 05 Jan 2000 13:28:12 +0800 From: Peter Wemm Message-Id: <20000105052812.AEA871CC6@overcee.netplex.com.au> Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Nate Williams wrote: > > > > I'd like to install Blackdown JDK 1.2.2 RC3 on FreeBSD 3.4 > > > > with linux_base-6.1. I know there are some Blackdown problems with > > > > native threads, but I have not been able to determine whether there > > > > are any FreeBSD-specific problems that will remain once Blackdown > > > > gets their release fixed. Will native threads at the JDK level map to > > > > native threads at the FreeBSD 3.4 level? (If so, is there any idea how > > > > performance will compare to native Linux?) > > > > > > FreeBSD has no native 'kernel threads', so it won't help out. However, > > > the Linux JIT is a *big* improvement. > > > > I could have sworn to have used linux kernel threads in FreeBSD 8) > > Linux kernel threads are not native kernel threads. They are not part > of the standard distribution, they have an incompatible license, and do > not scale very well on most Java applications. However, for *certain* > applications they do work, but these are limited to mostly CPU-bound > applications that do light I/O. Applications that have lots of I/O > threads will not work well with the Linux-threads stuff. (While > applications run with the green-threads version tends to work *very* > well, almost as well as C code.) Also, beware, rfork(2), linux's emulated clone(2) etc are only supported under single processor mode in 3.x kernels. If you want to use linuxthreads under SMP, you will have to use 4.x. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Thu Jan 6 2:37:37 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from elch.de.uu.net (elch.de.uu.net [192.76.144.55]) by hub.freebsd.org (Postfix) with ESMTP id 4384715464 for ; Thu, 6 Jan 2000 02:37:34 -0800 (PST) (envelope-from michaelc@tmbbwmc.bbn.hp.com) Received: from pc-micha.mc.hp.com (pec-45-1.tnt3.s2.uunet.de [149.225.45.1]) by elch.de.uu.net (5.5.5/5.5.5) with ESMTP id LAA00004 for ; Thu, 6 Jan 2000 11:35:22 +0100 (MET) Received: from localhost (michaelc@localhost) by pc-micha.mc.hp.com (8.9.3/8.9.3) with ESMTP id LAA23007 for ; Thu, 6 Jan 2000 11:36:56 +0100 (MET) (envelope-from michaelc@pc-micha.mc.hp.com) Date: Thu, 6 Jan 2000 11:36:56 +0100 (MET) From: Michael Class Reply-To: Michael Class To: freebsd-emulation@freebsd.org Subject: vmware and SMP Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, I got vmware running on a 4.0-current system (UP). Thanks a lot! This is just plain fun. I read (and tried) that it does not work on a SMP- System (i am getting messages about wrong IRQs ...) Has anybody already looked closer of what would to be done to make that work? Thank you Michael ------------------------------------------------------------------------- michael class, viktor-renner str. 39, 72074 tuebingen, frg E-Mail: michael_class@gmx.net Phone: +49 7031 14-3707 (work) +49 7071 81950 (private) ------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Thu Jan 6 8:25:35 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from patrick.whetstonelogic.com (patrick.whetstonelogic.com [205.252.46.171]) by hub.freebsd.org (Postfix) with ESMTP id 8BD8014BC4 for ; Thu, 6 Jan 2000 08:25:28 -0800 (PST) (envelope-from patrick@patrick.whetstonelogic.com) Received: (from patrick@localhost) by patrick.whetstonelogic.com (8.9.3/8.9.3) id LAA38334; Thu, 6 Jan 2000 11:23:37 -0500 (EST) (envelope-from patrick) Message-Id: <200001061623.LAA38334@patrick.whetstonelogic.com> Date: Thu, 6 Jan 2000 11:23:37 -0500 (EST) From: patrick@whetstonelogic.com Subject: Re: vmware and SMP To: michael_class@gmx.net Cc: michaelc@tmbbwmc.bbn.hp.com, freebsd-emulation@FreeBSD.ORG In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 6 Jan, Michael Class wrote: > Hello, > > I got vmware running on a 4.0-current system (UP). Thanks a lot! This > is just plain fun. I read (and tried) that it does not work on a SMP- > System (i am getting messages about wrong IRQs ...) > > Has anybody already looked closer of what would to be done to make that > work? Yes. Work is being done on this now. :) Patrick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Thu Jan 6 16:48:56 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (Postfix) with ESMTP id 329241567D; Thu, 6 Jan 2000 16:48:41 -0800 (PST) (envelope-from van.woerkom@netcologne.de) Received: from oranje.my.domain (dial-ra-nc3-47.netcologne.de [195.14.251.47]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id BAA06966; Fri, 7 Jan 2000 01:44:22 +0100 (MET) Received: (from marc@localhost) by oranje.my.domain (8.9.3/8.9.3) id BAA07413; Fri, 7 Jan 2000 01:42:59 +0100 (CET) (envelope-from van.woerkom@netcologne.de) Date: Fri, 7 Jan 2000 01:42:59 +0100 (CET) Message-Id: <200001070042.BAA07413@oranje.my.domain> X-Authentication-Warning: oranje.my.domain: marc set sender to van.woerkom@netcologne.de using -f From: Marc van Woerkom To: freebsd-multimedia@freebsd.org, freebsd-emulation@freebsd.org Cc: se@freebsd.org Subject: Win32 Netscape and Real Audio Player run under Wine on -CURRENT Reply-To: van.woerkom@netcologne.de Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org See subject. This came unexpected. http://www.freebsd.org/~3d/screenshots/chameleon.jpg http://www.freebsd.org/~3d/screenshots/chameleon2.jpg Heck, it looks and sounds better even than the Linux version! Mozilla seems to have slight problems with frames. Threading is a bit clumsy at times. Listening to BBC Worldservice, Marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Thu Jan 6 18:39: 5 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from blaubaer.kn-bremen.de (blaubaer.kn-bremen.de [195.37.179.254]) by hub.freebsd.org (Postfix) with ESMTP id 716BB1586D for ; Thu, 6 Jan 2000 18:38:50 -0800 (PST) (envelope-from nox@saturn.kn-bremen.de) Received: from saturn.kn-bremen.de (uucp@localhost) by blaubaer.kn-bremen.de (8.9.1/8.9.1) with UUCP id DAA15556; Fri, 7 Jan 2000 03:30:56 +0100 Received: (from nox@localhost) by saturn.kn-bremen.de (8.9.3/8.8.5) id DAA07190; Fri, 7 Jan 2000 03:08:30 +0100 (CET) Date: Fri, 7 Jan 2000 03:08:30 +0100 (CET) From: Juergen Lock Message-Id: <200001070208.DAA07190@saturn.kn-bremen.de> To: marcel@scc.nl Subject: Re: Seagate Backup Exec for Linux? X-Newsgroups: local.list.freebsd.emulation In-Reply-To: <383FB4CF.CA6F6E79@scc.nl> References: <4.2.2.19991126162208.00cd4880@imap.tassie.net.au>, <14398.57642.861319.487652@jabberwock.rstcorp.com> Organization: home Cc: FreeBSD-emulation@FreeBSD.ORG Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <383FB4CF.CA6F6E79@scc.nl> you write: >"Viren R.Shah" wrote: >> >> Well, I just looked thru my log file, and saw: >> >> Nov 22 13:58:14 jabberwock last message repeated 51 times >> Nov 22 13:58:15 jabberwock /kernel: linux: syscall ustat is obsoleted >> or not implemented (pid=35198) >> >> Does anyone know whether the emulation of ustat was removed form the >> linux compatibility code? > >It has not been removed. We now simply emit a diagnostic message so that >people can find out why their Linux binary doesn't work. > >I'll try to implement it ASAP. Remember that it will live in -current >for a couple of days before it will be merged to -stable. Well, we just updated our -stable and tried this program in the subject again, and it still didn't see any directories. here's a snippet from linux_kdump... (EXPOSE and immotest are directories and they don't show up at all in Backup Exec.) ... 643 agent.be CALL linux_newstat(0x8082288,0xbfbfd770) 643 agent.be NAMI "/compat/linux/smb/src/disk0/export" 643 agent.be NAMI "/smb/src/disk0/export" 643 agent.be RET linux_newstat 0 643 agent.be CALL linux_open(0x8082288,0x800,0x8082288) 643 agent.be NAMI "/compat/linux/smb/src/disk0/export" 643 agent.be NAMI "/smb/src/disk0/export" 643 agent.be RET linux_open 9 643 agent.be CALL linux_fcntl(0x9,0x2,0x1) 643 agent.be RET linux_fcntl 0 643 agent.be CALL linux_lseek(0x9,0,0x1) 643 agent.be RET linux_lseek 0 643 agent.be CALL linux_getdents(0x9,0xbfbfb924,0x1eb9) 643 agent.be RET linux_getdents 220/0xdc 643 agent.be CALL close(0x9) 643 agent.be RET close 0 643 agent.be CALL linux_newlstat(0xbfbfd628,0xbfbfd56c) 643 agent.be NAMI "/compat/linux/smb/src/disk0/export/EXPOSE" 643 agent.be NAMI "/smb/src/disk0/export/EXPOSE" 643 agent.be RET linux_newlstat 0 643 agent.be CALL linux_ustat(0x40c,0xbfbfd63c) 643 agent.be RET linux_ustat 0 643 agent.be CALL linux_newstat(0x8082288,0xbfbfd770) 643 agent.be NAMI "/compat/linux/smb/src/disk0/export" 643 agent.be NAMI "/smb/src/disk0/export" 643 agent.be RET linux_newstat 0 643 agent.be CALL linux_open(0x8082288,0x800,0x8082288) 643 agent.be NAMI "/compat/linux/smb/src/disk0/export" 643 agent.be NAMI "/smb/src/disk0/export" 643 agent.be RET linux_open 9 643 agent.be CALL linux_fcntl(0x9,0x2,0x1) 643 agent.be RET linux_fcntl 0 643 agent.be CALL linux_lseek(0x9,0,0x1) 643 agent.be RET linux_lseek 0 643 agent.be CALL linux_getdents(0x9,0xbfbfb924,0x1eb9) 643 agent.be RET linux_getdents 220/0xdc 643 agent.be CALL close(0x9) 643 agent.be RET close 0 643 agent.be CALL linux_newlstat(0xbfbfd628,0xbfbfd56c) 643 agent.be NAMI "/compat/linux/smb/src/disk0/export/immotest" 643 agent.be NAMI "/smb/src/disk0/export/immotest" 643 agent.be RET linux_newlstat 0 643 agent.be CALL linux_ustat(0x40c,0xbfbfd63c) 643 agent.be RET linux_ustat 0 643 agent.be CALL linux_newstat(0x8082288,0xbfbfd770) 643 agent.be NAMI "/compat/linux/smb/src/disk0/export" 643 agent.be NAMI "/smb/src/disk0/export" 643 agent.be RET linux_newstat 0 643 agent.be CALL linux_open(0x8082288,0x800,0x8082288) 643 agent.be NAMI "/compat/linux/smb/src/disk0/export" 643 agent.be NAMI "/smb/src/disk0/export" 643 agent.be RET linux_open 9 643 agent.be CALL linux_fcntl(0x9,0x2,0x1) 643 agent.be RET linux_fcntl 0 643 agent.be CALL linux_lseek(0x9,0,0x1) 643 agent.be RET linux_lseek 0 643 agent.be CALL linux_getdents(0x9,0xbfbfb924,0x1eb9) 643 agent.be RET linux_getdents 220/0xdc 643 agent.be CALL close(0x9) 643 agent.be RET close 0 I'm willing to help debug this and test patches... (Btw i just noticed there's an agent.linux and also an agent.linux_old in the tarball and one links libc5 and the other links libc6. so for we have only tried one. And we would really like this working because of linux' problems with the async mounted filesystems... and i know BSD better too. :) Oh and there are also isc and sco binaries in the tarball, would those maybe have more chances? And is the old linux version that worked on 3.2(?) maybe still available somewhere? Regards, -- Juergen Lock (remove dot foo from address to reply) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Fri Jan 7 2:13:26 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id C9F7B15042 for ; Fri, 7 Jan 2000 02:13:13 -0800 (PST) (envelope-from marcel@scc.nl) Received: from [212.238.132.94] (helo=scones.sup.scc.nl) by post.mail.nl.demon.net with esmtp (Exim 2.02 #1) id 126WOO-0007Sn-00; Fri, 7 Jan 2000 10:13:12 +0000 Received: from scc.nl (scones.sup.scc.nl [192.168.2.4]) by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id LAA52135; Fri, 7 Jan 2000 11:13:09 +0100 (CET) (envelope-from marcel@scc.nl) Message-ID: <3875BC35.F0D47500@scc.nl> Date: Fri, 07 Jan 2000 11:13:09 +0100 From: Marcel Moolenaar Organization: SCC vof X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5 i386) X-Accept-Language: en MIME-Version: 1.0 To: Juergen Lock Cc: FreeBSD-emulation@FreeBSD.ORG Subject: Re: Seagate Backup Exec for Linux? References: <4.2.2.19991126162208.00cd4880@imap.tassie.net.au>, <14398.57642.861319.487652@jabberwock.rstcorp.com> <200001070208.DAA07190@saturn.kn-bremen.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Juergen Lock wrote: > > Well, we just updated our -stable and tried this program in the > subject again, and it still didn't see any directories. here's > a snippet from linux_kdump... (EXPOSE and immotest are directories > and they don't show up at all in Backup Exec.) > [ktrace snipped] I can't see anything trivially wrong... > I'm willing to help debug this and test patches... (Btw i just > noticed there's an agent.linux and also an agent.linux_old in the > tarball and one links libc5 and the other links libc6. so for we > have only tried one. Which one? How does the other do? > Oh and there are also isc and sco binaries in the tarball, would > those maybe have more chances? > And is the old linux version that worked on 3.2(?) maybe still > available somewhere? I wouldn't know (both questions :-) -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Fri Jan 7 10:22:57 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from blaubaer.kn-bremen.de (blaubaer.kn-bremen.de [195.37.179.254]) by hub.freebsd.org (Postfix) with ESMTP id DCD8614C37 for ; Fri, 7 Jan 2000 10:22:52 -0800 (PST) (envelope-from nox@saturn.kn-bremen.de) Received: from saturn.kn-bremen.de (uucp@localhost) by blaubaer.kn-bremen.de (8.9.1/8.9.1) with UUCP id TAA03375; Fri, 7 Jan 2000 19:18:51 +0100 Received: (from nox@localhost) by saturn.kn-bremen.de (8.9.3/8.8.5) id TAA48449; Fri, 7 Jan 2000 19:09:00 +0100 (CET) Date: Fri, 7 Jan 2000 19:09:00 +0100 (CET) From: Juergen Lock Message-Id: <200001071809.TAA48449@saturn.kn-bremen.de> To: marcel@scc.nl Subject: Re: Seagate Backup Exec for Linux? X-Newsgroups: local.list.freebsd.emulation In-Reply-To: <3875BC35.F0D47500@scc.nl> References: <4.2.2.19991126162208.00cd4880@imap.tassie.net.au>, <14398.57642.861319.487652@jabberwock.rstcorp.com> <200001070208.DAA07190@saturn.kn-bremen.de> Organization: home Cc: FreeBSD-emulation@FreeBSD.ORG Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <3875BC35.F0D47500@scc.nl> you write: >Juergen Lock wrote: >> >> Well, we just updated our -stable and tried this program in the >> subject again, and it still didn't see any directories. here's >> a snippet from linux_kdump... (EXPOSE and immotest are directories >> and they don't show up at all in Backup Exec.) >> >[ktrace snipped] > >I can't see anything trivially wrong... > Hmmm... >> I'm willing to help debug this and test patches... (Btw i just >> noticed there's an agent.linux and also an agent.linux_old in the >> tarball and one links libc5 and the other links libc6. so for we >> have only tried one. > >Which one? The libc6 one. >How does the other do? Just tried: same problem. > >> Oh and there are also isc and sco binaries in the tarball, would >> those maybe have more chances? >> And is the old linux version that worked on 3.2(?) maybe still >> available somewhere? > >I wouldn't know (both questions :-) Well and this is getting even stranger: nfs-mounted this same filesystem (/smb/src/disk0) from a linux box and gave its export/ (which is also exported via samba as you probably already guessed) to the agent.be running there: exact same result, files show up but no directories! So this must be some property of ufs that also shows up over nfs that it doesn't like, and there's probably nothing wrong at all with the linux emulation... Oh: int linux_ustat(p, uap) ... /* * XXX - Don't return an error if we can't find a vnode for the * device. Our dev_t is 32-bits whereas Linux only has a 16-bits * dev_t. The dev_t that is used now may as well be a truncated * dev_t returned from previous syscalls. Just return a bzeroed * ustat in that case. */ 16-bit dev_t, oh dear :( I just re-mounted it on /dev/da1e (instead of the `real' device with the slice), and now it sees the directories! Soo... its included in today's backup run now and we'll see if any other problems show up. Regards, -- Juergen Lock (remove dot foo from address to reply) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Sat Jan 8 14:12:10 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from postfix2.free.fr (postfix2.free.fr [212.27.32.74]) by hub.freebsd.org (Postfix) with ESMTP id C1B6115111; Sat, 8 Jan 2000 14:12:05 -0800 (PST) (envelope-from nsouch@free.fr) Received: from free.fr (paris11-nas1-41-94.dial.proxad.net [212.27.41.94]) by postfix2.free.fr (Postfix) with ESMTP id 21B9D7421E; Sat, 8 Jan 2000 23:12:00 +0100 (MET) Received: (from nsouch@localhost) by free.fr (8.9.3/8.9.3) id AAA02139; Sun, 9 Jan 2000 00:19:06 +0100 (CET) (envelope-from nsouch) Message-ID: <20000109001906.49031@breizh.free.fr> Date: Sun, 9 Jan 2000 00:19:06 +0100 From: Nicolas Souchu To: van.woerkom@netcologne.de Cc: freebsd-multimedia@freebsd.org, freebsd-emulation@freebsd.org, se@freebsd.org Subject: Re: Win32 Netscape and Real Audio Player run under Wine on -CURRENT References: <200001070042.BAA07413@oranje.my.domain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <200001070042.BAA07413@oranje.my.domain>; from Marc van Woerkom on Fri, Jan 07, 2000 at 01:42:59AM +0100 X-Operating-System: FreeBSD breizh 4.0-CURRENT FreeBSD 4.0-CURRENT Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Jan 07, 2000 at 01:42:59AM +0100, Marc van Woerkom wrote: > >See subject. This came unexpected. > > http://www.freebsd.org/~3d/screenshots/chameleon.jpg > http://www.freebsd.org/~3d/screenshots/chameleon2.jpg > > >Heck, it looks and sounds better even than the Linux version! !!! I'm very impressed. 1) I thought the wine project has been died for a long time 2) I never thought this would ever succeed 3) You guys of the -multimedia list and other human interface hackers are doing very good things for the FreeBSD community We can thank you for most of FreeBSD youthfulness But, Linux is very attractive to common people with all these projects: StarOffice, Wine and many things that make it Windows-like with the unix power and stability. What makes FreeBSD attractive to such people today? Not the server/rock-stable/clean-devel/... arguments. Isn't it? And neither what some of you make really heavy and good work for: 'MAINTAIN ON FREEBSD WHAT RUNS ON LINUX' Of course, the challenge is neither the widest distribution nor being every body's OS. And I'm enough proud of working with an alternative OS ;) One of the best ones moreover. Then, What would make really sense in choosing FreeBSD versus other OSes? Nothing I think for people we do not want necesseraly as FreeBSD users. So, All what you're doing is mostly for us! FreeBSD lovers. Thanks again, but this is certainly not the opinion of everybody here. Nicholas -- nsouch@free.fr / nsouch@freebsd.org FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message