public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Rich Johnston <rjohnston@sgi.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Mark Tinguely <tinguely@sgi.com>, xfs@oss.sgi.com
Subject: Re: [PATCH] xfs: reserve fields in inode for parent ptr and alloc policy
Date: Wed, 10 Apr 2013 14:39:32 -0500	[thread overview]
Message-ID: <5165BFF4.8020601@sgi.com> (raw)
In-Reply-To: <5165B5CB.2070203@sandeen.net>

On 04/10/2013 01:56 PM, Eric Sandeen wrote:
> On 4/10/13 1:24 PM, Mark Tinguely wrote:
>> Reserve fields in new inode layout for parent pointer and
>> allocation policy.
>> 		----
>> The inode will hold the parent information for the first
>> link to a file. Information for the other links will be
>> held in extended attribute entries.
>>
>> The "di_parino" is the inode of the parent directory. The
>> directory information for this entry is located the parent
>> directory with "di_paroff" offset.
>>
>> The di_parino/di_paroff concept code is running.
>> 		----
>> The "di_allocpolicy" will be used to remember the allocation
>> policy associated with this inode.
>
> can you say more about this allocation policy?
>
> -Eric

No its super secret information. ;)

Its on my plate Eric, because Mark was making a change for parent ptrs, 
I asked him to request space for allocation policies also.

I don't have all the details yet but here is a very high level concept.

Identify allocation groups by names (or numbers -- preferably using names
in user-visible areas), allowing many different areas. Placing the 
allocation
policy outside of user programs is necessary for this to be successful.

  Current thoughts on proposed a layered allocation policies:

     Policy for the entire filesystem
     Policy attached to a directory (whose policy would be inherited by 
subdirectories when subdirectories are created)
     Policy for a single file

The policy would define:

    where to place file data
    where to place metadata for the files.
    a prefered allocation group for placing file data (for directories).

--Rich

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2013-04-10 19:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-10 18:24 [PATCH] xfs: reserve fields in inode for parent ptr and alloc policy Mark Tinguely
2013-04-10 18:56 ` Eric Sandeen
2013-04-10 19:39   ` Rich Johnston [this message]
2013-04-10 20:31     ` Mark Tinguely
2013-04-10 20:40       ` Eric Sandeen
2013-04-11  3:28       ` Dave Chinner
2013-04-11  3:00 ` Dave Chinner
2013-04-11 13:54   ` Mark Tinguely
2013-04-12  0:24     ` Dave Chinner

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=5165BFF4.8020601@sgi.com \
    --to=rjohnston@sgi.com \
    --cc=sandeen@sandeen.net \
    --cc=tinguely@sgi.com \
    --cc=xfs@oss.sgi.com \
    /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