On Mon, Jul 6, 2009 at 2:20 PM, Donato Capitella<d.capitella@xxxxxx> wrote:
> Ok, this is what I want to do.
>
> I'm developing a patch to ext3; this patch uses a queue of structures
> representing tasks to be performed and a separated kernel thread that
> reads the structures from the queue as they become available and
> performs the required task on the filesystem.
>
> So, if the system crashes when there are still things to do in the
> queue, those tasks won't be accomplished. That's why I want to keep this
> queue in a reserved inode so that I can restart the tasks in case of
> system crash.
>
> Now, what am I trying to develop? Basically this function:
>
> write_to_log(my_struct *task) {
> 1. get reserved inode
> 2. append the struct pointed to by task to the reserved inode
> }
>
> I tried to be clear, my English doesn't help I guess :P.
>
> Thanks again for your time,
> Donato :D
If your goal is to get it in mainstream you probably need to be thinking ext4.
Ext3 is basically in maintenance mode now I believe, so new features
are not likely to be accepted.
Greg
--
Greg Freemyer
Head of EDD Tape Extraction and Processing team
Litigation Triage Solutions Specialist
http://www.linkedin.com/in/gregfreemyer
Preservation and Forensic processing of Exchange Repositories White Paper -
<http://www.norcrossgroup.com/forms/whitepapers/tng_whitepaper_fpe.html>
The Norcross Group
The Intersection of Evidence & Technology
http://www.norcrossgroup.com
--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx
Please read the FAQ at http://kernelnewbies.org/FAQ
