From: vineetagarwal <checkout.vineet@gmail.com>
To: linux-ext4@vger.kernel.org
Subject: Re: Block allocation
Date: Mon, 29 Sep 2008 05:01:38 -0700 (PDT) [thread overview]
Message-ID: <19722589.post@talk.nabble.com> (raw)
In-Reply-To: <20080927215059.GA5025@mit.edu>
thank you for replying .
well iam working on a project where i need to allocate few blockgroups for
manipulation of data.
yeah i can write the code but i was actually thinking that could i somehow
manipulate the code at top level of allocation , so that not much changes
Theodore Ts'o wrote:
>
> On Sat, Sep 27, 2008 at 08:07:06AM -0700, vineetagarwal wrote:
>>
>> I want to allocate few blocks from a blockgroup in ext2 within a range of
>> offset specified by user. Is it possible of doing so if yes then can
>> someone
>> please explain.As i know balloc.c and ialloc.c are responsible for it and
>> they work on entire file system can i somehow manipulate it for ceratin
>> ranges.
>>
>> For Ex
>> let say i provide a range 100 - 3000. Can i allocate few blocks within
>> this
>> range .
>
> While the filesystem mounted (and accessed through the kernel) or
> unmounted (and accessed via libext2fs)? Anything is possible. if you
> are willing to write some code....
>
> Why do you need to do this, and is this for some class or problem set?
>
> - Ted
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
--
View this message in context: http://www.nabble.com/Block-allocation-tp19703506p19722589.html
Sent from the linux-ext4 mailing list archive at Nabble.com.
next prev parent reply other threads:[~2008-09-29 12:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-27 15:07 Block allocation vineetagarwal
2008-09-27 21:50 ` Theodore Tso
2008-09-29 12:01 ` vineetagarwal [this message]
2008-09-29 12:05 ` vineetagarwal
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=19722589.post@talk.nabble.com \
--to=checkout.vineet@gmail.com \
--cc=linux-ext4@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.