From: "Rohit Sharma" <imreckless@gmail.com>
To: "Jan Kara" <jack@suse.cz>
Cc: Kernelnewbies <kernelnewbies@nl.linux.org>,
ext4 <linux-ext4@vger.kernel.org>
Subject: Re: block allocation for ext2_mkdir
Date: Fri, 19 Dec 2008 13:12:32 +0530 [thread overview]
Message-ID: <2d08ef090812182342p1a210adcgd70d8a5cf3bf828c@mail.gmail.com> (raw)
In-Reply-To: <20081218223928.GA20092@atrey.karlin.mff.cuni.cz>
On Fri, Dec 19, 2008 at 4:09 AM, Jan Kara <jack@suse.cz> wrote:
>> On Fri, Dec 19, 2008 at 12:12 AM, Rohit Sharma <imreckless@gmail.com> wrote:
>> > How does ext2 allocate blocks for directory.
>> >
>> > ext2_mkdir calls ext2_make_empty
>> >
>> > ext2_make_empty calls __ext2_write_begin
>> >
>> > __ ext2_write_begin calls block_write_begin
>> >
>> > my query is that how does this function allocates blocks for directories. ??
>> >
>>
>> Does ext2 uses ext2_get_block to allocate blocks for both files and
>> directories. ??
> Yes, exactly. Ext2 (unlike ext3 or ext4) treats directories the same
> ways as ordinary files and thus ext2_get_block is used for block
> allocation.
>
Can i modify this function to restrict allocation of blocks
to a particular block group ?
Like i want that my abc.txt file should be in block group 5 suppose, then
what should i do?
> Honza
>
> --
> Jan Kara <jack@suse.cz>
> SuSE CR Labs
>
next prev parent reply other threads:[~2008-12-19 7:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-18 18:42 block allocation for ext2_mkdir Rohit Sharma
2008-12-18 19:52 ` Rohit Sharma
2008-12-18 22:39 ` Jan Kara
2008-12-19 7:42 ` Rohit Sharma [this message]
2008-12-19 9:21 ` Sandeep K Sinha
2008-12-19 9:35 ` Peter Teoh
2008-12-19 11:18 ` Rohit Sharma
2008-12-19 15:29 ` Peter Teoh
2008-12-19 18:49 ` Rohit Sharma
2008-12-19 19:01 ` Rohit Sharma
2008-12-19 20:24 ` Sandeep K Sinha
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=2d08ef090812182342p1a210adcgd70d8a5cf3bf828c@mail.gmail.com \
--to=imreckless@gmail.com \
--cc=jack@suse.cz \
--cc=kernelnewbies@nl.linux.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox