There were two issues. First there were numerous buffer dependancies
that required a synchronous write to 'open' the cluster before the rest
of the buffers could be flushed. It got messy really fast.
The second issue was that I found it really hard to predict the key range
for a new cluster to get a reasonable fill ratio before HAMMER would have
Hmm. I think the answer is no, historical access must be turned on
(especially now with the FIFO mechanic). There's no random bitmap free
any more so 'nohistory' won't work anyway in the initial release.
In otherwords, if your disk fills up the only way to clear space is to
cycle the fifo. That will ultimately be improved by a future backing
store behind the fifo (the blockmap idea I talked about before), and/or
out of band data references, allowing some immediate gratification for
e.g. large files.
Personally speaking I think the blockmap idea may be the best way to go.
It would be theoretically possible to immediately reuse a block that
becomes completely free by unmapping it from the fifo (creating a 'hole'
in the fifo) and freeing it for reuse. One would thus not have to cycle
the fifo to reach the block in order to reuse it.
-Matt
Matthew Dillon
<dillon@backplane.com>I might be wrong (and have misunderstood your reply) but I think he asked whether it would be possible to disallow a user to access the historical data (even if it is present on the disk). As I have not studied the code I might be wrong, but should it not be quite easy to create some switch which determines whether a @@0x<timestamp> will be treated as a normal filename or the name or not? -- Erik Wikström
No. That would be, as you say, trivial :) Aggelos
Now combine that with 64bit block idents and you have a "quasi infinte FIFO" :) cheers simon -- Serve - BSD +++ RENT this banner advert +++ ASCII Ribbon /"\ Work - Mac +++ space for low €€€ NOW!1 +++ Campaign \ / Party Enjoy Relax | http://dragonflybsd.org Against HTML \ Dude 2c 2 the max ! http://golden-apple.biz Mail + News / \
| Torsten Kaiser | Re: 2.6.23-mm1 |
| debian developer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Davide Libenzi | [patch 7/8] fdmap v2 - implement sys_socket2 |
| Luca Tettamanti | [BUG] Oops with KVM-27 |
git: | |
| Rene Herman | "git pull . <branch>" versus "git merge <branch>" |
| Wink Saville | Resolving conflicts |
| Matthieu Moy | git push to a non-bare repository |
| Johannes Schindelin | Re: [ANNOUNCE] GIT 1.5.4 |
| Pieter Verberne | pkg_add keeps giving errors |
| Matthew Dempsky | Re: Real men don't attack straw men |
| GVG GVG | ssh_exchange_identification: Connection closed by remote host |
| Ivo Chutkin | problem installing some packages on 4.2 |
| David Miller | TCP event tracking via netlink... |
| Rafael J. Wysocki | Re: [bug?] tg3: Failed to load firmware "tigon/tg3_tso.bin" |
| Jon Smirl | e1000 tcp checksum incorrect, x86 64b |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
