Received: (from majordomo@localhost)
	by oss.sgi.com (8.11.2/8.11.3) id g0UNmOc27688
	for linux-xfs-outgoing; Wed, 30 Jan 2002 15:48:24 -0800
Received: from pizda.ninka.net (IDENT:root@pizda.ninka.net [216.101.162.242])
	by oss.sgi.com (8.11.2/8.11.3) with SMTP id g0UNmLd27666
	for <linux-xfs@oss.sgi.com>; Wed, 30 Jan 2002 15:48:21 -0800
Received: from localhost (IDENT:davem@localhost.localdomain [127.0.0.1])
	by pizda.ninka.net (8.9.3/8.9.3) with ESMTP id OAA16792;
	Wed, 30 Jan 2002 14:46:47 -0800
Date: Wed, 30 Jan 2002 14:46:47 -0800 (PST)
Message-Id: <20020130.144647.21928212.davem@redhat.com>
To: a.gruenbacher@computer.org
CC: linux-xfs@oss.sgi.com
Subject: extended attributes interface
From: "David S. Miller" <davem@redhat.com>
X-Mailer: Mew version 2.1 on Emacs 21.1 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-linux-xfs@oss.sgi.com
Precedence: bulk
Status: O
Content-Length: 636
Lines: 15


All the values that go through these syscalls seem to be
opaque and filesystem specific.  Therefore can I ask the filesystems
that use these things use fixed sized types such as "u32" "u16" et al.
instead of things such as "long" or "int"?

The reason I ask is, unless strict sized types are used it is going
to be a real pain in the ass to translate the types passed to these
system calls in mixed 32-bit/64-bit environments.  This is thus going
to be a mess on sparc64, ppc64, mips64, ia64, and probably others I
have forgotten :-)

If strict sized types are used for the attributes, then no
translations will need to occur at all.