public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rohit Sharma" <imreckless@gmail.com>
To: "Peter Teoh" <htmldeveloper@gmail.com>
Cc: "Jan Kara" <jack@suse.cz>,
	Kernelnewbies <kernelnewbies@nl.linux.org>,
	ext4 <linux-ext4@vger.kernel.org>
Subject: Re: block allocation for ext2_mkdir
Date: Sat, 20 Dec 2008 00:19:54 +0530	[thread overview]
Message-ID: <2d08ef090812191049p1da42e74jc9cce8f076a56ab7@mail.gmail.com> (raw)
In-Reply-To: <804dabb00812190729r74d9f131kdd5c86d56320dc20@mail.gmail.com>

Is there a difference between how ext2 allocates block between
inode's indirect blocks and data blocks.


On Fri, Dec 19, 2008 at 8:59 PM, Peter Teoh <htmldeveloper@gmail.com> wrote:
> On Fri, Dec 19, 2008 at 7:18 PM, Rohit Sharma <imreckless@gmail.com> wrote:
>> On Fri, Dec 19, 2008 at 3:05 PM, Peter Teoh <htmldeveloper@gmail.com> wrote:
>>> On Fri, Dec 19, 2008 at 3:42 PM, Rohit Sharma <imreckless@gmail.com> wrote:
>>>> 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?
>>>>
>>>
>>> I think this can be done.   Or is done in the kernel source in several
>>> ways (indirectly).
>>>
>>> 1.   ext2_find_goal()-->this will look for the best new block.   when
>>> searching, it will try to find the block to be allocated to follow the
>>> one last allocated in the file, so as to maintain storage contiguity.
>>>
>>> 2.   looking into fs/ext2/balloc.c: ext2_try_to_allocate(), there is a
>>> argument called group_goal, whose purpose is to specify the goal block
>>> group, and the algorithm will start searching from the group specified
>>> (look for "start=grp_goal").   Of course, if search is in vain it will
>>> proceed to other block group, which u don't want ....so may be can
>>> customize from here.
>>>
>>> Not sure if I am right?
>>>
>> When we create new file, do we use reservation window to allocate blocks
>> or we use reservation window every time we need a new data blocks
>> for file.
>>
>>
>
> http://lwn.net/Articles/81357/ ===> from here, we deduced that it
> should be done at every new block request level, and not at the file
> level.   This is because when file level request is initiated, the
> first thing is see if any existing block can be reused or not, before
> allocating new block (which then comes with reservation features - to
> ensure contiguity of datablocks).
>
>
> --
> Regards,
> Peter Teoh
>
> Ernest Hemingway - "Never mistake motion for action."
>

  reply	other threads:[~2008-12-19 18:49 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
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 [this message]
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=2d08ef090812191049p1da42e74jc9cce8f076a56ab7@mail.gmail.com \
    --to=imreckless@gmail.com \
    --cc=htmldeveloper@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