Dump Utility cache efficiency analysis
Nirmal Thacker
thacker.nirmal at gmail.com
Wed Jun 24 17:59:10 UTC 2009
Thanks for all the replies and suggestions
I ll begin by running, benchmarking, understanding dump for myself and take
up Matt's suggestions above to understand the unified caching implementation
in more detail
-n
On Wed, Jun 24, 2009 at 3:58 AM, Peter Jeremy
<peterjeremy at optushome.com.au>wrote:
> On 2009-Jun-23 15:52:04 -0400, Nirmal Thacker <thacker.nirmal at gmail.com>
> wrote:
> >I would first like to understand the opinions of anyone who has looked at
> >this problem or think this would be a worthwhile project to start off
> with.
>
> I'm aware of the following references:
> http://www.mavetju.org/mail/view_message.php?list=freebsd-hackers&id=375676
>
> http://www.mavetju.org/mail/view_thread.php?list=freebsd-stable&id=1335519&thread=yes
>
> >1. Installing a stable FreeBSD build
> >2. Check out a version of the Build suitable for the project
>
> Any changes will need to apply to FreeBSD -current, though they may be
> back-ported once tested. This means that you will need a -current
> system at some point. 8-current is reasonably stable at this point and
> would be my suggestion.
>
> >3. Pointers to begin studying the current implementation in the code-tree
> >structure (would I expect it to lie in the fs/ directory?). I tried to
> find
> >it in the FreeBSD cross reference (http://fxr.watson.org/)
>
> The code is in src/sbin/dump. It references various system header
> files in order to understand the UFS on-disk format.
>
> >Lastly- does this project require the know-how's of device drivers? If so,
> I
> >would have to work harder.
>
> No. Dump is completely userland.
>
> --
> Peter Jeremy
>
More information about the freebsd-hackers
mailing list