All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Greg Banks <gnb@melbourne.sgi.com>
Cc: Timothy Shimmin <tes@sgi.com>,
	Richard Scobie <richard@sauce.co.nz>,
	xfs@oss.sgi.com
Subject: Re: Filestreams (and 64bit inodes)
Date: Thu, 12 Jun 2008 22:06:04 -0500	[thread overview]
Message-ID: <4851E41C.6050108@sandeen.net> (raw)
In-Reply-To: <4851CD32.7080106@melbourne.sgi.com>

Greg Banks wrote:
> Eric Sandeen wrote:

> Cool, thanks for the data Eric.
> 
>>  but it ain't pretty.
>>
>> I installed all fedora packages under a directory and ran greg's tool over:
>>
>> /sbin /usr/sbin /bin /usr/bin /usr/kerberos/bin/ /usr/kerberos/sbin/
>>
>> Aggregate results:
>>
>>    4070 29.1% are scripts (shell, perl, whatever)
>>    6598 47.2% don't use any stat() family calls at all
>>    1829 13.1% use 32-bit stat() family interfaces only
>>    1312  9.4% use 64-bit stat64() family interfaces only
>>     180  1.3% use both 32-bit and 64-bit stat() family interfaces
>>   
> Ouch.  That's over two thousand executables to patch, rebuild, and ship.
>> list of packages, sorted by the semi-lame "number of files in package
>> which call a 32-bit stat variant" metric:
>>
>> http://sandeen.fedorapeople.org/stat32-ers

And about 900 packages...

>> I'm going to see if I can't leverage Fedora to clean some of this up.
>>
>> -Eric
>>   
> Good luck with that.

Heh :)  At first I was just going to correlate with st_ino users to cut
it down, but then I learned that glibc will actually give you an
EOVERFLOW if, say st_ino overflows, even if you were only going to check
st_mode.  :(  So pretty much everything needs fixing.

(FWIW I gathered statfs/statvfs calls, too...)

-Eric

  reply	other threads:[~2008-06-13  3:05 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-07 23:11 Filestreams Richard Scobie
2008-06-09  3:31 ` Filestreams Eric Sandeen
2008-06-10  1:49   ` Filestreams Timothy Shimmin
2008-06-10  2:14     ` Filestreams Richard Scobie
2008-06-10 23:09     ` Filestreams (and 64bit inodes) Richard Scobie
2008-06-11  1:39       ` Timothy Shimmin
2008-06-11  2:47         ` Richard Scobie
2008-06-11  3:23         ` Eric Sandeen
2008-06-12 13:52           ` Eric Sandeen
2008-06-13  1:28             ` Greg Banks
2008-06-13  3:06               ` Eric Sandeen [this message]
2008-06-13  3:24                 ` Greg Banks
2008-06-13  3:20               ` Mark Goodwin
2008-06-13  3:40                 ` Greg Banks
2008-06-13  3:46                   ` Eric Sandeen
2008-06-13  3:57                     ` Greg Banks
2008-06-13  5:35                   ` Greg Banks
2008-06-13 13:28                     ` Eric Sandeen
2008-06-13  3:45                 ` Eric Sandeen

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=4851E41C.6050108@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=gnb@melbourne.sgi.com \
    --cc=richard@sauce.co.nz \
    --cc=tes@sgi.com \
    --cc=xfs@oss.sgi.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 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.