Re: RFH: zfs-fuse
On Mon, Feb 02, 2009 at 07:52:03PM +0100, Mike Hommey wrote: Could someone still give me current policy regarding sparc64 code (see below for a reminder of the original question) Mike Hommey wrote: > Hi, > > I'm currently giving a try to zfs-fuse (ITP #419746) and it has support > for sparc64. My understanding of the debian port is that it is mostly a > 32 bits port, with a 64 bits kernel. The zfs-fuse build scripts only > deal with sparc64 as returned by uname -m, but builds as 32-bits > application with the current toolchain. Also, it builds with > -mcpu=ultrasparc, which I'm unsure is allowed for the debian sparc port > (as well as expecting uname -m to always return sparc64), but the code > does use ultrasparc specific opcodes, most notably "cas". It is my understanding (the porters will correct me if I'm wrong) that lenny will no longer support SPARC v8 (support for v7 was removed long ago) because the 32-bit SPARC kernel is no longer supported upstream. Since v9 systems are UltraSPARC, this shouldn't be a problem. This also has the pleasant side-effects that multiplication and division (and other UltraSPARC instructions) are now assumed to be available for all sparc machines. However, I suggest you use -mcpu=v9. -mcpu=ultrasparc chooses v9 instructions, but then optimizes the code for UltraSPARC I/II/IIi; this may not be optimal for newer UltraSPARC machines, such as III, IV, T1, and T2. -- brian m. carlson / brian with sandals: Houston, Texas, US +1 713 440 7475 | http://crustytoothpaste.ath.cx/~bmc | My opinion only troff on top of XML: http://crustytoothpaste.ath.cx/~bmc/code/thwack OpenPGP: RSA v4 4096b 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187 signature.asc Description: Digital signature
Re: RFH: zfs-fuse
On Mon, Dec 29, 2008 at 03:58:23AM +0800, Paolo Scarabelli wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hi Mike... > > There you go, I hope it can be of some help. > > Paolo. > > > sun:/tmp# uname -a > Linux sun 2.6.26-1-sparc64 #1 Mon Dec 15 17:04:34 UTC 2008 sparc64 GNU/Linux > sun:/tmp# dd of=foo bs=1024 count=0 seek=50 > 0+0 records in > 0+0 records out > 0 bytes (0 B) copied, 7.4265e-05 s, 0.0 kB/s > sun:/tmp# zpool create foo $(pwd)/foo > sun:/tmp# zfs create foo/bar > sun:/tmp# touch /foo/bar/baz > sun:/tmp# ls -l /foo/bar/baz > - -rw-r--r-- 1 root root 0 2008-12-29 03:49 /foo/bar/baz > sun:/tmp# zpool destroy foo > sun:/tmp# rm foo Thanks for the feedback (I'm late, I know ;) ) Could someone still give me current policy regarding sparc64 code (see below for a reminder of the original question) Cheers Mike > Mike Hommey wrote: > > Hi, > > > > I'm currently giving a try to zfs-fuse (ITP #419746) and it has support > > for sparc64. My understanding of the debian port is that it is mostly a > > 32 bits port, with a 64 bits kernel. The zfs-fuse build scripts only > > deal with sparc64 as returned by uname -m, but builds as 32-bits > > application with the current toolchain. Also, it builds with > > -mcpu=ultrasparc, which I'm unsure is allowed for the debian sparc port > > (as well as expecting uname -m to always return sparc64), but the code > > does use ultrasparc specific opcodes, most notably "cas". > > > > For those interested in the code, they can lookup > > src/lib/libsolcompat/sparc64/atomic.S which contains most sparc specific > > assembly in http://prdownload.berlios.de/zfs-fuse/zfs-fuse-0.5.0.tar.bz2 > > > > I'm not sure the resulting package works properly either (as I'm unable > > to test it on porter machines), so if someone could check out > > http://people.debian.org/~glandium/zfs-fuse_0.5.0-1_sparc.deb > > and see if the following sequence of commands work (as root): > > dd of=foo bs=1024 count=0 seek=50 > > zpool create foo $(pwd)/foo > > zfs create foo/bar > > touch /foo/bar/baz > > ls /foo/bar/baz > > > > You can cleanup with: > > zpool destroy foo > > rm foo > > > > before removing the package. > > > > Thanks for your help. > > > > Mike > > > > > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.9 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iEYEARECAAYFAklX2l8ACgkQqAaEpZvj+VOZhQCfTBe8qJMgph47cdcC1qlktDsQ > oi8AoJgf9S8oErI+pi2QUnJ+xMmYUo02 > =Yjxm > -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFH: zfs-fuse
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Mike... There you go, I hope it can be of some help. Paolo. sun:/tmp# uname -a Linux sun 2.6.26-1-sparc64 #1 Mon Dec 15 17:04:34 UTC 2008 sparc64 GNU/Linux sun:/tmp# dd of=foo bs=1024 count=0 seek=50 0+0 records in 0+0 records out 0 bytes (0 B) copied, 7.4265e-05 s, 0.0 kB/s sun:/tmp# zpool create foo $(pwd)/foo sun:/tmp# zfs create foo/bar sun:/tmp# touch /foo/bar/baz sun:/tmp# ls -l /foo/bar/baz - -rw-r--r-- 1 root root 0 2008-12-29 03:49 /foo/bar/baz sun:/tmp# zpool destroy foo sun:/tmp# rm foo Mike Hommey wrote: > Hi, > > I'm currently giving a try to zfs-fuse (ITP #419746) and it has support > for sparc64. My understanding of the debian port is that it is mostly a > 32 bits port, with a 64 bits kernel. The zfs-fuse build scripts only > deal with sparc64 as returned by uname -m, but builds as 32-bits > application with the current toolchain. Also, it builds with > -mcpu=ultrasparc, which I'm unsure is allowed for the debian sparc port > (as well as expecting uname -m to always return sparc64), but the code > does use ultrasparc specific opcodes, most notably "cas". > > For those interested in the code, they can lookup > src/lib/libsolcompat/sparc64/atomic.S which contains most sparc specific > assembly in http://prdownload.berlios.de/zfs-fuse/zfs-fuse-0.5.0.tar.bz2 > > I'm not sure the resulting package works properly either (as I'm unable > to test it on porter machines), so if someone could check out > http://people.debian.org/~glandium/zfs-fuse_0.5.0-1_sparc.deb > and see if the following sequence of commands work (as root): > dd of=foo bs=1024 count=0 seek=50 > zpool create foo $(pwd)/foo > zfs create foo/bar > touch /foo/bar/baz > ls /foo/bar/baz > > You can cleanup with: > zpool destroy foo > rm foo > > before removing the package. > > Thanks for your help. > > Mike > > -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAklX2l8ACgkQqAaEpZvj+VOZhQCfTBe8qJMgph47cdcC1qlktDsQ oi8AoJgf9S8oErI+pi2QUnJ+xMmYUo02 =Yjxm -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
