From: "Takashi Sato" <sho@bsd.tnes.nec.co.jp>
To: "Dave Kleikamp" <shaggy@austin.ibm.com>
Cc: "'Andreas Dilger'" <adilger@clusterfs.com>,
<linux-kernel@vger.kernel.org>, <linux-fsdevel@vger.kernel.org>,
"Trond Myklebust" <trond.myklebust@fys.uio.no>
Subject: Re: stat64 for over 2TB file returned invalid st_blocks
Date: Thu, 8 Dec 2005 20:38:54 +0900 [thread overview]
Message-ID: <02ab01c5fbeb$faf7d740$4168010a@bsd.tnes.nec.co.jp> (raw)
In-Reply-To: <1133973247.8907.33.camel@kleikamp.austin.ibm.com>
Hi,
> On Wed, 2005-12-07 at 10:34 -0500, Trond Myklebust wrote:
>> If you really want a variable size type here, then the right thing to do
>> is to define a __kernel_blkcnt_t or some such thing, and hide the
>> configuration knob for it somewhere in the arch-specific Kconfigs.
>
> Takashi's patch does improve on what currently exists. Maybe someone
> can create a separate patch to replace sector_t with blkcnt_t where it
> makes sense.
I prefer sector_t for i_blocks rather than newly defined blkcnt_t.
The reasons are:
- Both i_blocks and common sector_t are for on-disk 512-byte unit.
In this point of view, they have the same character.
- If we created the type blkcnt_t newly, the patch would have to
touch a lot of files as follows, like sector_t does.
block/Kconfig, asm-i386/types.h, asm-x86_64/types.h,
asm-ppc/types.h, asm-s390/types.h, asm-sh/types.h,
asm-h8300/types.h, asm-mips/types.h
It will be simple if we use sector_t for i_blocks.
Also, I cannot imagine the situation that > 2TB files are used over
network with CONFIG_LBD disabled kernel. Is there such a thing
realistically?
-- Takashi Sato
next prev parent reply other threads:[~2005-12-08 11:39 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-06 12:42 Takashi Sato
2005-12-06 14:30 ` Dave Kleikamp
2005-12-06 14:48 ` Trond Myklebust
2005-12-06 14:51 ` Dave Kleikamp
2005-12-06 21:24 ` Andreas Dilger
2005-12-07 0:59 ` Trond Myklebust
2005-12-07 10:57 ` Takashi Sato
2005-12-07 13:52 ` Trond Myklebust
2005-12-07 15:01 ` Dave Kleikamp
2005-12-07 15:34 ` Trond Myklebust
2005-12-07 16:34 ` Dave Kleikamp
2005-12-07 18:55 ` Trond Myklebust
2005-12-08 11:38 ` Takashi Sato [this message]
2005-12-08 14:27 ` Trond Myklebust
2005-12-08 14:50 ` Anton Altaparmakov
2005-12-08 15:03 ` Trond Myklebust
2005-12-10 11:22 ` Takashi Sato
[not found] <5eVqw-2ug-61@gated-at.bofh.it>
2005-12-03 2:19 ` Bodo Eggert
-- strict thread matches above, loose matches on Subject: below --
2005-12-01 12:00 Takashi Sato
2005-12-01 12:39 ` Jörn Engel
2005-12-01 12:52 ` Jörn Engel
2005-12-01 13:52 ` Avi Kivity
2005-12-01 14:32 ` Dave Kleikamp
2005-12-02 13:18 ` Takashi Sato
2005-12-02 14:11 ` Dave Kleikamp
2005-12-02 18:58 ` Andreas Dilger
2005-12-03 13:00 ` Takashi Sato
2005-12-05 8:11 ` Andreas Dilger
2005-12-05 12:35 ` Takashi Sato
2005-12-05 13:34 ` Trond Myklebust
2005-12-01 14:53 ` Al Viro
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='02ab01c5fbeb$faf7d740$4168010a@bsd.tnes.nec.co.jp' \
--to=sho@bsd.tnes.nec.co.jp \
--cc=adilger@clusterfs.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shaggy@austin.ibm.com \
--cc=trond.myklebust@fys.uio.no \
/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®