public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@muc.de>
To: Peter Chubb <peter@chubb.wattle.id.au>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
	Andi Kleen <ak@muc.de>,
	linux-kernel@vger.kernel.org
Subject: Re: statfs64 missing
Date: Thu, 17 Oct 2002 02:01:11 +0200	[thread overview]
Message-ID: <20021017000111.GA25054@averell> (raw)
In-Reply-To: <15789.64263.606518.921166@wombat.chubb.wattle.id.au>

On Thu, Oct 17, 2002 at 01:49:27AM +0200, Peter Chubb wrote:
>    2.  Change the in-kernel definition of struct statfs to use 64-bit
>        types, (if CONFIG_LBD) and convert at syscall time depending on
>        whether statfs or statfs64 is called (or even, allow glibc to
>        do it, but that's an externally-visible interface change)
> 
> Which is cleaner?  Personally I dislike multiplying interfaces for no
> good reason, so I lean to (2) --- keep the in-kernel paths 64-bit
> clean.

I prefer (2) too.

Regarding the new fields Trond proposed: there is the issue of 64bit
architectures. They already use 64bit block counts, so in theory they 
don't need a statfs64(). But if we wanted to add new fields patterned
after Solaris 64bit would need the new system call too.

So it boils down to if the new fields are important enough to justify
the pain they cause on 64bit.

(I ran into a similar issue with my nanosecond stat patchkit - 
alpha stat is 64bit clean, but doesn't have the padding for ns fields
added used in later ports)

-Andi

  parent reply	other threads:[~2002-10-16 23:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-16 14:06 statfs64 missing Andi Kleen
2002-10-16 14:16 ` Trond Myklebust
     [not found]   ` <15789.64263.606518.921166@wombat.chubb.wattle.id.au>
2002-10-17  0:01     ` Andi Kleen [this message]
2002-10-17 19:41       ` Benjamin LaHaise
2002-10-18  0:19         ` [PATCH] statfs64 no longer missing Peter Chubb
2002-10-18  0:26           ` Benjamin LaHaise
2002-10-18  2:31           ` Andi Kleen
2002-10-18  3:27             ` Peter Chubb
2002-10-18  6:17           ` Andreas Dilger
2002-10-18  6:31             ` Andi Kleen
2002-10-18  6:41               ` David S. Miller
  -- strict thread matches above, loose matches on Subject: below --
2002-10-17 20:28 statfs64 missing Steven French
2002-10-17 21:55 ` Andreas Dilger
2002-10-17 21:27 Petr Vandrovec

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=20021017000111.GA25054@averell \
    --to=ak@muc.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter@chubb.wattle.id.au \
    --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