[1110] in arla-drinkers
Re: Arla 0.26/27pre4 vs. Linux 2.2.10 on SparcUltra 5
daemon@ATHENA.MIT.EDU (Magnus Ahltorp)
Fri Aug 27 21:15:56 1999
From owner-arla-drinkers@stacken.kth.se Sat Aug 28 01:15:55 1999
Return-Path: <owner-arla-drinkers@stacken.kth.se>
Delivered-To: arla-drinkers-mtg@bloom-picayune.mit.edu
Received: (qmail 19308 invoked from network); 28 Aug 1999 01:15:54 -0000
Received: from unknown (HELO sundance.stacken.kth.se) (130.237.234.41)
by bloom-picayune.mit.edu with SMTP; 28 Aug 1999 01:15:54 -0000
Received: (from majordom@localhost)
by sundance.stacken.kth.se (8.8.8/8.8.8) id DAA11302
for arla-drinkers-list; Sat, 28 Aug 1999 03:07:11 +0200 (MET DST)
Received: from turbot.pdc.kth.se (turbot.pdc.kth.se [130.237.221.42])
by sundance.stacken.kth.se (8.8.8/8.8.8) with ESMTP id DAA11298
for <arla-drinkers@stacken.kth.se>; Sat, 28 Aug 1999 03:07:07 +0200 (MET DST)
Received: (from d95-mah@localhost)
by turbot.pdc.kth.se (8.8.7/8.8.7) id DAA12999;
Sat, 28 Aug 1999 03:06:53 +0200 (MET DST)
To: Tobias Grundmann <grundman@Informatik.Uni-Tuebingen.De>
Cc: arla-drinkers@stacken.kth.se
Subject: Re: Arla 0.26/27pre4 vs. Linux 2.2.10 on SparcUltra 5
References: <199908271120.NAA23372@peanuts.informatik.uni-tuebingen.de>
From: Magnus Ahltorp <map@stacken.kth.se>
Content-Type: text/plain; charset="iso-8859-1"
Content-Language: en
Date: 28 Aug 1999 03:06:53 +0200
In-Reply-To: Tobias Grundmann's message of "Fri, 27 Aug 1999 13:22:09 +0200"
Message-ID: <ixdn1vck91u.fsf@turbot.pdc.kth.se>
Lines: 19
X-Mailer: Gnus v5.6.45/Emacs 19.34
Sender: owner-arla-drinkers@stacken.kth.se
Precedence: bulk
> after digging around a bit in the arla sources I think one of the
> problems with this 32/64 bit issue is CACHEHANDLESIZE in xfs_message.h
> which is to small. xfs_message.h is included in both the kernel module
> and arlad stuff. Compiling one with 64 bit and the other one with 32
> bit while this file_handle thing in xfs/linux/xfs_syscalls.c has a
> plain unsigned int in it... then a memcpy in xfs_fh_to_dentry...
>
> Well I wonder if its worth to investigate this further and do
> eventually some real work on it. Will there be an update soon?
I have written the code, but it contains some bugs, and I will commit
it as soon as it more or less bug free. I don't want to commit code
that breaks everything.
The problem is that I haven't had the time to work on the sparc64
things, since we are having our two weeks of newcomer's reception here
at KTH. Hopefully, I will look at it any day now.
/Magnus
