From: "Alexander V. Lukyanov" <lav@yars.free.net>
To: linux-kernel@vger.kernel.org
Cc: sparc-list@redhat.com
Subject: nfs_fsinfo->bsize size (2.4.2)
Date: Tue, 10 Apr 2001 14:47:46 +0400 [thread overview]
Message-ID: <20010410144746.A23745@swing.yars.free.net> (raw)
Hello!
Some time ago I had an undefined symbol in kernel compilation (__mul64) It
was sparc architecture, cross compilation on solaris/sparc. I have found
that 64-bit multiplication is in nfs2xdr.c, nfs_xdr_statfsres function. The
multiplication is by nfs_fsinfo->bsize.
For some reason nfs_fsinfo->bsize is declared as __u64. I don't see how
block size can be greater that 2G. What is the reason behind such type
for block size?
I did the following change and nfs still works fine. I've also rearranged
structure fields for alignment reasons.
--- include/linux/nfs_xdr.h.1 Fri Apr 6 17:57:25 2001
+++ include/linux/nfs_xdr.h Fri Apr 6 17:59:14 2001
@@ -47,8 +47,8 @@
__u32 wtpref; /* pref. write transfer size */
__u32 wtmult; /* writes should be multiple of this */
__u32 dtpref; /* pref. readdir transfer size */
+ __u32 bsize; /* block size */
__u64 maxfilesize;
- __u64 bsize; /* block size */
__u64 tbytes; /* total size in bytes */
__u64 fbytes; /* # of free bytes */
__u64 abytes; /* # of bytes available to user */
--
Alexander. | http://www.yars.free.net/~lav/
reply other threads:[~2001-04-10 10:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20010410144746.A23745@swing.yars.free.net \
--to=lav@yars.free.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sparc-list@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®