From: geoff@collyer.net
To: 9fans@cse.psu.edu
Subject: Re: [9fans] truncation via wstat on ken's fs
Date: Mon, 18 Oct 2004 01:38:54 -0700 [thread overview]
Message-ID: <c4a4e42cd6bdbe380b7a7fafb6c2ac6e@collyer.net> (raw)
In-Reply-To: <2d26e403df2c03ed8e41e93d4bc64b2d@terzarima.net>
As I recall, it didn't help enough on Unix; a busy system got its free
list scrambled pretty quickly, which was one of Berkeley's arguments
for bitmap allocation.
I'm inclined to free blocks in forward order for wstat truncation,
which ought to be far less common than truncation of existing files
via create, thus minimising any inefficiency.
next prev parent reply other threads:[~2004-10-18 8:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-17 11:05 geoff
2004-10-17 11:18 ` Brantley Coile
2004-10-17 17:01 ` Russ Cox
2004-10-18 0:43 ` geoff
2004-10-18 8:03 ` Charles Forsyth
2004-10-18 8:24 ` geoff
2004-10-18 8:36 ` Charles Forsyth
2004-10-18 8:38 ` geoff [this message]
2004-10-17 17:35 ` boyd, rounin
2004-10-17 13:19 Aharon Robbins
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=c4a4e42cd6bdbe380b7a7fafb6c2ac6e@collyer.net \
--to=geoff@collyer.net \
--cc=9fans@cse.psu.edu \
/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).