:What about overlapping regions?
:
:
:
:
:the OLD won't have a delete_tid != 0. Or will hammer split up the
:extent into smaller pieces when the new one comes in?
:
:cheers
: simon
Overlapping regions do not exist. The closest you get is an adjacency
where the d
Matthew Dillon wrote:
:I think it is not as easy, because we want the current state to be the
:reference, and have the usage of the snapshots show what would be free'd
:when the snapshot was removed. So old, unmodfied data has to be charged
:to the current usage and not to the snapshot that fi
:I think it is not as easy, because we want the current state to be the
:reference, and have the usage of the snapshots show what would be free'd
:when the snapshot was removed. So old, unmodfied data has to be charged
:to the current usage and not to the snapshot that first contained it.
:
:c
Thomas Nikolajsen wrote:
Thomas, its definitely possible to do both those things.
Pruning on a per-file basis can be done by carefully specifying the
key range in the ioctl call to just cover the desired object id (inode
number).
Determining how much space the snapshots use can
> Thomas, its definitely possible to do both those things.
> Pruning on a per-file basis can be done by carefully specifying the
> key range in the ioctl call to just cover the desired object id (inode
> number).
>
> Determining how much space the snapshots use can be accomplished
On Fri, Aug 28, 2009 at 12:52:30AM +0200, Simon 'corecode' Schubert wrote:
> Francois Tigeot wrote:
> >As far as I know, mm_malloc.h is part of gcc-4.1. Is there any reason it
> >is not
> >installed in a DragonFly-2.3.2 system ?
>
> I have a patch for this, will commit in the morning.
That's gre
