9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] long filenames in cwfs
Date: Mon, 24 Jun 2013 09:03:18 -0400	[thread overview]
Message-ID: <7d1c080e58d9aaf4d40fff29ec1bc1e0@lyons.quanstro.net> (raw)
In-Reply-To: <CAJSxfmKg-7NnBy=MKnaZTW7uTE6eV026H+jq7per_voEvuGD=g@mail.gmail.com>

On Sun Jun 23 18:01:11 EDT 2013, skip.tavakkolian@gmail.com wrote:

> with 8K names, using base64, one could encode 6111 bytes of data in the
> name. i just did a quick inventory[*] of my $home; 74% of my files have
> less than 6112 bytes of data.

i was proposing a pointer, which could be nil.
i would put the pointer where the file name should
be—perhaps by setting the first 8 bytes to non-unicode
magic and the next 8 bytes to a pointer to the
direct name block.

so why not change nothing.  the first 8180 bytes go
in the first direct block anyway.

btw, i have far fewer large files than you, but still 25%
of the ones bigger than 6112 bytes are smaller than
8180

 ; du -a .>[2=]|awk '$1>8180 {s++}END{print s/NR}'
0.00325015
; du -a .>[2=]|awk '$1>6112 {s++}END{print s/NR}'
0.00416286

- erik



  reply	other threads:[~2013-06-24 13:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-23  1:48 arisawa
2013-06-23  7:45 ` cinap_lenrek
2013-06-23 13:36   ` arisawa
2013-06-23 14:08     ` erik quanstrom
2013-06-23 21:59       ` Skip Tavakkolian
2013-06-24 13:03         ` erik quanstrom [this message]
2013-06-24 10:57       ` arisawa
2013-06-24 11:21         ` hiro
2013-06-24 12:43           ` arisawa
2013-06-23  2:11 Erik Quanstrom
2013-06-23  6:19 ` arisawa

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=7d1c080e58d9aaf4d40fff29ec1bc1e0@lyons.quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@9fans.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).