From: "David B. Ritch" <dritch@hpti.com>
To: NFS mailing list <nfs@lists.sourceforge.net>
Subject: NFS_All on alpha
Date: 03 Sep 2002 17:03:11 -0400 [thread overview]
Message-ID: <1031086991.5196.53.camel@twitch> (raw)
I applied the nfs_all patch from
http://www.fys.uio.no/~trondmy/src/2.4.19/ to a linux-2.4.19 kernel, and
ran into trouble compiling.
In particular, the linux-2.4.19-02-fix_kmap2.dif patch defines a
conflicting type for xdr_shift_buf's second argument. In
linux-2.4.19/include/linux/sunrpc/xdr.h, it is defined to be of type
unsigned int, and in linux-2.4.19/net/sunrpc/xdr.c, it is defined to be
of type size_t.
Size_t is defined to be __kernel_size_t in /usr/include/linux/types.h,
which is defined to be unsigned long in /usr/include/asm/posix_types.h.
On an IA32 architecture, unsigned long and unsigned int are the same, so
this is not a big deal. However, on an alpha, a long is 64 bits,
whereas an int is only 32 bits.
Should xdr_shift_buf take an int or a long? Are there any other known
problems for a 64-bit architecture in the nfs_all patches?
Thank you,
dbr
--
David B. Ritch
High Performance Technologies, Inc.
-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2002-09-03 21:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-03 21:03 David B. Ritch [this message]
2002-09-03 22:59 ` NFS_All on alpha Trond Myklebust
2002-09-04 15:47 ` David B. Ritch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1031086991.5196.53.camel@twitch \
--to=dritch@hpti.com \
--cc=nfs@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.