From owner-freebsd-fs Sun Mar 1 02:31:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA23794 for freebsd-fs-outgoing; Sun, 1 Mar 1998 02:31:01 -0800 (PST) (envelope-from owner-freebsd-fs@FreeBSD.ORG) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA23782 for ; Sun, 1 Mar 1998 02:30:58 -0800 (PST) (envelope-from michaelh@cet.co.jp) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.8/CET-v2.2) with SMTP id KAA17232; Sun, 1 Mar 1998 10:29:47 GMT Date: Sun, 1 Mar 1998 19:29:47 +0900 (JST) From: Michael Hancock To: Bruce Evans cc: eivind@yes.no, jlemon@americantv.com, fs@FreeBSD.ORG Subject: Re: syncer / SMP question In-Reply-To: <199802281349.AAA03879@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 1 Mar 1998, Bruce Evans wrote: > >This is about half the code of the previous version, and to me it is > >much clearer than before. > > It seems to make one case simpler. How would you handle a return from > inside the loop, like the one in getfsstat()? Requiring a single exit > point is not an option :-). goto out; Regards, Mike Hancock To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Sun Mar 1 02:57:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA25438 for freebsd-fs-outgoing; Sun, 1 Mar 1998 02:57:05 -0800 (PST) (envelope-from owner-freebsd-fs@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA25432 for ; Sun, 1 Mar 1998 02:57:02 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id VAA09758; Sun, 1 Mar 1998 21:54:22 +1100 Date: Sun, 1 Mar 1998 21:54:22 +1100 From: Bruce Evans Message-Id: <199803011054.VAA09758@godzilla.zeta.org.au> To: bde@zeta.org.au, michaelh@cet.co.jp Subject: Re: syncer / SMP question Cc: eivind@yes.no, fs@FreeBSD.ORG, jlemon@americantv.com Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >> >This is about half the code of the previous version, and to me it is >> >much clearer than before. >> >> It seems to make one case simpler. How would you handle a return from >> inside the loop, like the one in getfsstat()? Requiring a single exit >> point is not an option :-). > >goto out; Not an option :-), and leaves mp locked (which you can't know about since its locking is hidden in the loop macros). In general, you would need macros for all sorts of abnormal loop exits. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Sun Mar 1 03:17:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA29258 for freebsd-fs-outgoing; Sun, 1 Mar 1998 03:17:43 -0800 (PST) (envelope-from owner-freebsd-fs@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA29253 for ; Sun, 1 Mar 1998 03:17:40 -0800 (PST) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id EAA23212; Sun, 1 Mar 1998 04:17:35 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp04.primenet.com, id smtpd023205; Sun Mar 1 04:17:31 1998 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id EAA29852; Sun, 1 Mar 1998 04:17:26 -0700 (MST) From: Terry Lambert Message-Id: <199803011117.EAA29852@usr09.primenet.com> Subject: Re: syncer / SMP question To: bde@zeta.org.au (Bruce Evans) Date: Sun, 1 Mar 1998 11:17:26 +0000 (GMT) Cc: bde@zeta.org.au, michaelh@cet.co.jp, eivind@yes.no, fs@FreeBSD.ORG, jlemon@americantv.com In-Reply-To: <199803011054.VAA09758@godzilla.zeta.org.au> from "Bruce Evans" at Mar 1, 98 09:54:22 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Not an option :-), and leaves mp locked (which you can't know about since > its locking is hidden in the loop macros). In general, you would need > macros for all sorts of abnormal loop exits. Like NFS. And then you might end up with hard to track bugs. Like NFS. Single-entry/single-exit is good. But don't write Homeric epics in header files to achieve it. 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Sun Mar 1 17:59:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA16456 for freebsd-fs-outgoing; Sun, 1 Mar 1998 17:59:38 -0800 (PST) (envelope-from owner-freebsd-fs@FreeBSD.ORG) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA16448 for ; Sun, 1 Mar 1998 17:59:33 -0800 (PST) (envelope-from michaelh@cet.co.jp) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.8/CET-v2.2) with SMTP id BAA22584; Mon, 2 Mar 1998 01:58:20 GMT Date: Mon, 2 Mar 1998 10:58:20 +0900 (JST) From: Michael Hancock To: Terry Lambert cc: Bruce Evans , eivind@yes.no, fs@FreeBSD.ORG, jlemon@americantv.com Subject: Re: syncer / SMP question In-Reply-To: <199803011117.EAA29852@usr09.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 1 Mar 1998, Terry Lambert wrote: > > Not an option :-), and leaves mp locked (which you can't know about since > > its locking is hidden in the loop macros). In general, you would need > > macros for all sorts of abnormal loop exits. > > Like NFS. And then you might end up with hard to track bugs. > Like NFS. > > Single-entry/single-exit is good. But don't write Homeric epics in > header files to achieve it. 8-). When we start the pushdown in the the fs systems and do about 6 to 9 months of debugging without getting anywhere, maybe we should consider looking at a new locking model. ;-). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Mon Mar 2 11:06:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA24444 for freebsd-fs-outgoing; Mon, 2 Mar 1998 11:06:53 -0800 (PST) (envelope-from owner-freebsd-fs@FreeBSD.ORG) Received: from gate.iterated.com (gate.iterated.com [206.30.188.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA24429; Mon, 2 Mar 1998 11:06:43 -0800 (PST) (envelope-from CSagar@exchange.iterated.com) Received: from [198.242.115.150] by gate.iterated.com for id OAA03908; Mon Mar 2 14:06:38 1998 Received: by exchange.iterated.com with Internet Mail Service (5.5.1664.3) id ; Mon, 2 Mar 1998 14:06:37 -0500 Message-ID: Subject: help with CD-ROM setup Date: Mon, 2 Mar 1998 14:06:36 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1664.3) Content-Type: text/plain; charset="iso-8859-1" To: "'freebsd-fs@freebsd.org'" , "'freebsd-admin@freebsd.org'" From: Chris Sagar Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am trying to build another FreeBSD machine, and I am having difficulty getting the CD-ROM to work. Here are the specifics: Sound-blaster 16/SCSI with CDROM attached. SB16 is at irq 12 and dma 340. During bootup, the probe sees the SB16 as aic0 at 340 and 12. Next line is waiting for scsi devices to settle, then it finds the CD drive. It reports the cd as cd0(aic0:1:0) CD-ROM can not get size. No CD is in at this time. I have also had it report a size when a CD was in the drive. I have made and remade the /dev/cd0 files. When I try to mount an ISO-9660 format CD, I get the following error- Cd0(aic0:1:0) timeout This error repeats over and over. I can not CTRL-Z or CTRL-C out of the mount command. I have opened another login session and tried to kill the mount command, but with no success. Any help please... Secondly, related to the CD issue, I need to be able to play audio files and such thru the SB16. I have found X and command line CD players, but nothing for playing wav files or similar. Is anyone aware of anything and what kind of configuration issues are likely to come up??? Thanks to all in advance. Chris Sagar Csagar@iterated.com ( yes, the stuck in systemV admin). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Tue Mar 3 08:09:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA02805 for freebsd-fs-outgoing; Tue, 3 Mar 1998 08:09:37 -0800 (PST) (envelope-from owner-freebsd-fs@FreeBSD.ORG) Received: from gate.iterated.com (gate.iterated.com [206.30.188.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA02790 for ; Tue, 3 Mar 1998 08:09:29 -0800 (PST) (envelope-from CSagar@exchange.iterated.com) Received: from [198.242.115.150] by gate.iterated.com for id LAA20814; Tue Mar 3 11:09:28 1998 Received: by exchange.iterated.com with Internet Mail Service (5.5.1664.3) id ; Tue, 3 Mar 1998 11:09:28 -0500 Message-ID: Subject: help with CDROM setup Date: Tue, 3 Mar 1998 11:09:26 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1664.3) Content-Type: text/plain To: "'freebsd-fs@freebsd.org'" From: Chris Sagar Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Please accept apologies if you have already seen this. I sent it yesterday, but got back a weird notice about freebsd-admin. I am trying to setup CDROM and sound card for Freebsd. I have a Soundblaster 16 SCSI with CD attached. It is found during the probe (aic0) and it sees the CD attached to the card. However, when I try to mount a CD (ISO9660 format), I get timeout errors. I have changed the CD, I have added a disk with terminator to the chain (all internal) to see if it is a termination problem, but no success. I have rebuilt my kernal with support for snd controller and sb devices, but with no luck. I also need to get the sound card portion working. I have not spent any time yet on it. Any insight into what might be involved with that would be appreciated. All help is greatly appreciated. Chris Sagar Csagar@iterated.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Thu Mar 5 09:05:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA09680 for freebsd-fs-outgoing; Thu, 5 Mar 1998 09:05:19 -0800 (PST) (envelope-from owner-freebsd-fs@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA09642 for ; Thu, 5 Mar 1998 09:05:14 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id RAA20669 for ; Thu, 5 Mar 1998 17:05:12 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id SAA02276; Thu, 5 Mar 1998 18:05:12 +0100 (MET) Message-ID: <19980305180512.15607@follo.net> Date: Thu, 5 Mar 1998 18:05:12 +0100 From: Eivind Eklund To: fs@FreeBSD.ORG Subject: [bouyer@antioche.lip6.fr: bi-endian ffs available] Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Should we adopt this? ----- Forwarded message from Manuel Bouyer ----- Message-ID: <19980304173610.09180@antioche.lip6.fr> Date: Wed, 4 Mar 1998 17:36:10 +0100 From: Manuel Bouyer To: tech-kern@NetBSD.ORG Subject: bi-endian ffs available Hi, I've made big progress in getting ffs read both big and little endian file systems. A preliminary (but working :) version is available at ftp.netbsd.org:/pub/incoming/bouyer/ffs_endian.diff.gz. Features are: kernel can mount read/write both big and little endian ffs. The selection is made on the superblock magic order at mount time. fsck_ffs can work on both endian, and will convert from one to another if the '-s' flag is given. However, the filesystem will be unrecoverable if fsck is stopped before the end of the convertion for some reason. I really don't know how to be safer here. Once fsck starts rewrinting the fielsystem metadatas, there is no way to know where it stopped. Other filsystem utilities (badsect, clri, dump, fsdb, fsirand, newfs, tunefs, dumpfs, quotacheck - let me know if I missed some !) will work on both byte order. newfs will be able create both byte order ffs (not done yet, but will be soon). Quotacheck will be able to work on any byte order, but the quota file will always be used in host byte order - if you move a disk with user quotas, you will have to rerun quotacheck on it. If peoples feels it's a too strong limitation, I can have a look at this too. My understanding of things are that such situations should be exceptional. I can't see the use of quotas on removable medias. On the kernel side, I added a 'int um_flags' to struct ufsmount. For now it can only take one value - UFS_NEEDSWAP. This flags is checked at various place in the kernel when reading/writing metadatas. As inodes and the superblocks have a in-memory copy, they are converted in whole at read/write time (exept the blocks addresses in the inode). The blocks adresses (in inode or indirect blocks), cylinder groups and the directory infos are converted at use time, as the in-memory copy is the disk buffer itself. Things could maybe be improved here by adding a cylinder group cache, as does linux, but this needs further studies. I plan to commit this next friday, unless I get negative comments sine then. -- Manuel Bouyer, LIP6, Universite Paris VI. Manuel.Bouyer@lip6.fr -- ----- End forwarded message ----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Thu Mar 5 09:58:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA18677 for freebsd-fs-outgoing; Thu, 5 Mar 1998 09:58:55 -0800 (PST) (envelope-from owner-freebsd-fs@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA18671 for ; Thu, 5 Mar 1998 09:58:51 -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.8.8/8.8.8) with SMTP id KAA23744; Thu, 5 Mar 1998 10:58:42 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id KAA19486; Thu, 5 Mar 1998 10:58:40 -0700 Date: Thu, 5 Mar 1998 10:58:40 -0700 Message-Id: <199803051758.KAA19486@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Eivind Eklund Cc: fs@FreeBSD.ORG Subject: Re: [bouyer@antioche.lip6.fr: bi-endian ffs available] In-Reply-To: <19980305180512.15607@follo.net> References: <19980305180512.15607@follo.net> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Should we adopt this? > From: Manuel Bouyer ... > I've made big progress in getting ffs read both big and little endian > file systems. A preliminary (but working :) version is available > at ftp.netbsd.org:/pub/incoming/bouyer/ffs_endian.diff.gz. Not if performance matters to you, which it does to me. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Thu Mar 5 10:01:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA18852 for freebsd-fs-outgoing; Thu, 5 Mar 1998 10:01:25 -0800 (PST) (envelope-from owner-freebsd-fs@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA18846 for ; Thu, 5 Mar 1998 10:01:22 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id SAA21368; Thu, 5 Mar 1998 18:01:19 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id TAA02508; Thu, 5 Mar 1998 19:01:19 +0100 (MET) Message-ID: <19980305190118.29623@follo.net> Date: Thu, 5 Mar 1998 19:01:18 +0100 From: Eivind Eklund To: Nate Williams , Eivind Eklund Cc: fs@FreeBSD.ORG Subject: Re: [bouyer@antioche.lip6.fr: bi-endian ffs available] References: <19980305180512.15607@follo.net> <199803051758.KAA19486@mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199803051758.KAA19486@mt.sri.com>; from Nate Williams on Thu, Mar 05, 1998 at 10:58:40AM -0700 Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Mar 05, 1998 at 10:58:40AM -0700, Nate Williams wrote: > > Should we adopt this? > > > From: Manuel Bouyer > ... > > I've made big progress in getting ffs read both big and little endian > > file systems. A preliminary (but working :) version is available > > at ftp.netbsd.org:/pub/incoming/bouyer/ffs_endian.diff.gz. > > Not if performance matters to you, which it does to me. I seem to remember about .5 percent performance loss being mentioned in later messages. Not too terrible - it would at least be worthwhile to make it a kernel option. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Thu Mar 5 10:06:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA19781 for freebsd-fs-outgoing; Thu, 5 Mar 1998 10:06:27 -0800 (PST) (envelope-from owner-freebsd-fs@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA19775 for ; Thu, 5 Mar 1998 10:06:24 -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.8.8/8.8.8) with SMTP id LAA23813; Thu, 5 Mar 1998 11:06:18 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id LAA19568; Thu, 5 Mar 1998 11:06:16 -0700 Date: Thu, 5 Mar 1998 11:06:16 -0700 Message-Id: <199803051806.LAA19568@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Eivind Eklund Cc: Nate Williams , fs@FreeBSD.ORG Subject: Re: [bouyer@antioche.lip6.fr: bi-endian ffs available] In-Reply-To: <19980305190118.29623@follo.net> References: <19980305180512.15607@follo.net> <199803051758.KAA19486@mt.sri.com> <19980305190118.29623@follo.net> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [ FS for big/little endian switch ] > > Not if performance matters to you, which it does to me. > > I seem to remember about .5 percent performance loss being mentioned in > later messages. I have a *REALLY* hard time believing that number, because for every read/write you potentially do byte-swapping. Earlier attempts at such a thing at I believe Univ. of Utah were on the order of 10-15% if I remember right. (Which I might not be.) Also, it requires you to redo all your FS's in order to take advantage of it, which therefore makes it of little use to 99% of the poeple, and it could potentially 'kill' someone if they add it to their kernel. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Thu Mar 5 10:23:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA23315 for freebsd-fs-outgoing; Thu, 5 Mar 1998 10:23:01 -0800 (PST) (envelope-from owner-freebsd-fs@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA23302 for ; Thu, 5 Mar 1998 10:22:58 -0800 (PST) (envelope-from tlambert@usr06.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id LAA01324; Thu, 5 Mar 1998 11:22:58 -0700 (MST) Received: from usr06.primenet.com(206.165.6.206) via SMTP by smtp01.primenet.com, id smtpd001202; Thu Mar 5 11:22:46 1998 Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id LAA25980; Thu, 5 Mar 1998 11:22:43 -0700 (MST) From: Terry Lambert Message-Id: <199803051822.LAA25980@usr06.primenet.com> Subject: Re: [bouyer@antioche.lip6.fr: bi-endian ffs available] To: nate@mt.sri.com (Nate Williams) Date: Thu, 5 Mar 1998 18:22:43 +0000 (GMT) Cc: eivind@yes.no, nate@mt.sri.com, fs@FreeBSD.ORG In-Reply-To: <199803051806.LAA19568@mt.sri.com> from "Nate Williams" at Mar 5, 98 11:06:16 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > [ FS for big/little endian switch ] > > > > Not if performance matters to you, which it does to me. > > > > I seem to remember about .5 percent performance loss being mentioned in > > later messages. > > I have a *REALLY* hard time believing that number, because for every > read/write you potentially do byte-swapping. Earlier attempts at such a > thing at I believe Univ. of Utah were on the order of 10-15% if I > remember right. (Which I might not be.) I have a hard time believing that number as well. It would be very tempting (to me) to seperate this out as a layer in an "FS type" based on the swapped magic number. The buffer data would be swapped before the upper level (non-swapped) FS code saw it. This would mean the performance penalty was only paid in the swapped media case, and *no* penalty was paid in the default (normal) case. > Also, it requires you to redo all your FS's in order to take advantage > of it, which therefore makes it of little use to 99% of the poeple, and > it could potentially 'kill' someone if they add it to their kernel. I didn't see where this was necessary. The "fsck -s" is, of course, too dangerous, being unrecoverable without a failure. One potential fix for this would be to take part of the reserved area in fs_sparecon; probably this would be 8 full bytes. 8-(. The progress in conversion would be logged to this area. If the log was 0, then the conversion is complete. Otherwise, it could be resumed. Conversion could be done one-behind, since it only applies to metadata ordering; that is, allocate an additional object of the type and bubble-swap through the conversion. This would result in a crash during conversion being completely recoverable. Anyway... I don't think conversion is a good idea, in any case. If you are going to transport media around, then you want to leave it in the native ordering, whatever that is. If you are going to convert data from one machine to another, you would greatly benefit by rebuilding the FS from a backup, instead. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Thu Mar 5 10:42:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA26220 for freebsd-fs-outgoing; Thu, 5 Mar 1998 10:42:38 -0800 (PST) (envelope-from owner-freebsd-fs@FreeBSD.ORG) Received: from saturn.fast-ag.de (saturn.aladdin.de [194.123.19.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA26212 for ; Thu, 5 Mar 1998 10:42:31 -0800 (PST) (envelope-from cpg@aladdin.de) Received: by saturn.fast-ag.de(Lotus SMTP MTA v1.06 (346.4 3-18-1997)) id 412565BE.0067B0E5 ; Thu, 5 Mar 1998 19:52:34 +0100 X-Lotus-FromDomain: AKS From: "Christian Groessler" To: nate@mt.sri.com cc: fs@FreeBSD.ORG Message-ID: <412565BE.0065BED5.00@saturn.fast-ag.de> Date: Thu, 5 Mar 1998 19:33:56 +0100 Subject: Re: [bouyer@antioche.lip6.fr: bi-endian ffs available] Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 3/5/98 7:06:16 PM Nate Williams wrote: > >[ FS for big/little endian switch ] > >> > Not if performance matters to you, which it does to me. >> >> I seem to remember about .5 percent performance loss being mentioned in >> later messages. > >I have a *REALLY* hard time believing that number, because for every read/write you potentially do byte-swapping. Earlier attempts at such a >thing at I believe Univ. of Utah were on the order of 10-15% if I >remember right. (Which I might not be.) This 10-15% are the case when swapping occurs, I think? It's plain stupid to use the wrong byte order for your host harddisk: then you deserve that performance loss :-) And for removable media, interoperability matters more than speed. imo. regards, chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Thu Mar 5 12:45:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA17466 for freebsd-fs-outgoing; Thu, 5 Mar 1998 12:45:40 -0800 (PST) (envelope-from owner-freebsd-fs@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA17441 for ; Thu, 5 Mar 1998 12:45:11 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id VAA00428; Thu, 5 Mar 1998 21:39:57 +0100 (CET) To: Nate Williams cc: Eivind Eklund , fs@FreeBSD.ORG Subject: Re: [bouyer@antioche.lip6.fr: bi-endian ffs available] In-reply-to: Your message of "Thu, 05 Mar 1998 10:58:40 MST." <199803051758.KAA19486@mt.sri.com> Date: Thu, 05 Mar 1998 21:39:57 +0100 Message-ID: <426.889130397@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <199803051758.KAA19486@mt.sri.com>, Nate Williams writes: >> Should we adopt this? > >> From: Manuel Bouyer >... >> I've made big progress in getting ffs read both big and little endian >> file systems. A preliminary (but working :) version is available >> at ftp.netbsd.org:/pub/incoming/bouyer/ffs_endian.diff.gz. > >Not if performance matters to you, which it does to me. Well, we can make it "OEFFS" for "Omni-Endian-FFS", I can see the point of having it. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "Drink MONO-tonic, it goes down but it will NEVER come back up!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Thu Mar 5 14:15:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA28708 for freebsd-fs-outgoing; Thu, 5 Mar 1998 14:15:55 -0800 (PST) (envelope-from owner-freebsd-fs@FreeBSD.ORG) Received: from sasami.jurai.net (winter@sasami.jurai.net [207.31.78.80]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA28703 for ; Thu, 5 Mar 1998 14:15:53 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id RAA25069; Thu, 5 Mar 1998 17:14:25 -0500 (EST) Date: Thu, 5 Mar 1998 17:14:24 -0500 (EST) From: "Matthew N. Dodd" To: Eivind Eklund cc: fs@FreeBSD.ORG Subject: Re: [bouyer@antioche.lip6.fr: bi-endian ffs available] In-Reply-To: <19980305180512.15607@follo.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 5 Mar 1998, Eivind Eklund wrote: > Should we adopt this? Yes -PLEASE- > ----- Forwarded message from Manuel Bouyer ----- > Message-ID: <19980304173610.09180@antioche.lip6.fr> > Date: Wed, 4 Mar 1998 17:36:10 +0100 > From: Manuel Bouyer > To: tech-kern@NetBSD.ORG > Subject: bi-endian ffs available > > > Hi, > I've made big progress in getting ffs read both big and little endian > file systems. A preliminary (but working :) version is available > at ftp.netbsd.org:/pub/incoming/bouyer/ffs_endian.diff.gz. > > Features are: > kernel can mount read/write both big and little endian ffs. The selection > is made on the superblock magic order at mount time. > > fsck_ffs can work on both endian, and will convert from one to another > if the '-s' flag is given. However, the filesystem will be unrecoverable if > fsck is stopped before the end of the convertion for some reason. > I really don't know how to be safer here. Once fsck starts rewrinting the > fielsystem metadatas, there is no way to know where it stopped. > > Other filsystem utilities (badsect, clri, dump, fsdb, fsirand, newfs, tunefs, > dumpfs, quotacheck - let me know if I missed some !) will work on both > byte order. newfs will be able create both byte order ffs (not done yet, > but will be soon). > Quotacheck will be able to work on any byte order, but the quota file will > always be used in host byte order - if you move a disk with user quotas, > you will have to rerun quotacheck on it. If peoples feels it's a too strong > limitation, I can have a look at this too. My understanding of things are > that such situations should be exceptional. I can't see the use of quotas > on removable medias. > > On the kernel side, I added a 'int um_flags' to struct ufsmount. > For now it can only take one value - UFS_NEEDSWAP. This flags is checked > at various place in the kernel when reading/writing metadatas. > As inodes and the superblocks have a in-memory copy, they are converted > in whole at read/write time (exept the blocks addresses in the inode). > The blocks adresses (in inode or indirect blocks), cylinder groups and the > directory infos are converted at use time, as the in-memory copy is > the disk buffer itself. Things could maybe be improved here by adding a > cylinder group cache, as does linux, but this needs further studies. > > I plan to commit this next friday, unless I get negative comments sine then. > > -- > Manuel Bouyer, LIP6, Universite Paris VI. Manuel.Bouyer@lip6.fr > -- > ----- End forwarded message ----- > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-fs" in the body of the message > /* Matthew N. Dodd | A memory retaining a love you had for life winter@jurai.net | As cruel as it seems nothing ever seems to http://www.jurai.net/~winter | go right - FLA M 3.1:53 */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Thu Mar 5 14:31:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA00973 for freebsd-fs-outgoing; Thu, 5 Mar 1998 14:31:32 -0800 (PST) (envelope-from owner-freebsd-fs@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA00964 for ; Thu, 5 Mar 1998 14:31:28 -0800 (PST) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id OAA17356; Thu, 5 Mar 1998 14:28:13 -0800 (PST) Message-Id: <199803052228.OAA17356@implode.root.com> To: Eivind Eklund cc: Nate Williams , fs@FreeBSD.ORG Subject: Re: [bouyer@antioche.lip6.fr: bi-endian ffs available] In-reply-to: Your message of "Thu, 05 Mar 1998 19:01:18 +0100." <19980305190118.29623@follo.net> From: David Greenman Reply-To: dg@root.com Date: Thu, 05 Mar 1998 14:28:13 -0800 Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >On Thu, Mar 05, 1998 at 10:58:40AM -0700, Nate Williams wrote: >> > Should we adopt this? >> >> > From: Manuel Bouyer >> ... >> > I've made big progress in getting ffs read both big and little endian >> > file systems. A preliminary (but working :) version is available >> > at ftp.netbsd.org:/pub/incoming/bouyer/ffs_endian.diff.gz. >> >> Not if performance matters to you, which it does to me. > >I seem to remember about .5 percent performance loss being mentioned in >later messages. Not too terrible - it would at least be worthwhile to make >it a kernel option. I'd rather not obfuscate the code. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Thu Mar 5 20:32:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA22640 for freebsd-fs-outgoing; Thu, 5 Mar 1998 20:32:18 -0800 (PST) (envelope-from owner-freebsd-fs@FreeBSD.ORG) Received: from bachue.usc.unal.edu.co ([168.176.3.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA22635 for ; Thu, 5 Mar 1998 20:32:15 -0800 (PST) (envelope-from giffunip@asme.org) Received: from giffuni.usc.unal.edu.co ([168.176.3.33]) by bachue.usc.unal.edu.co (Netscape Messaging Server 3.0) with SMTP id AAA22647 for ; Thu, 5 Mar 1998 23:35:27 +0500 Message-ID: <34FF7C52.2781E494@asme.org> Date: Thu, 05 Mar 1998 23:32:18 -0500 From: "Pedro F. Giffuni" Organization: U. Nacional de Colombia X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: freebsd-fs@FreeBSD.ORG Subject: Portable Parallel Filesystem (PPFS) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I posted something about this long ago, but now that we have SMP, and that there seems to be a growing interest in the filesystem area, I thought someone might find useful the old pointer (It's in Yahoo :-): http://www-pablo.cs.uiuc.edu/Projects/PPFS/ppfs.html It requires PVM or MPICH, and both seem to work under FreeBSD. cheers, Pedro. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message