ocfs2-devel.oss.oracle.com archive mirror
 help / color / mirror / Atom feed
From: Joel Becker <Joel.Becker@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 2/2] Ocfs2: Add a new code 'OCFS2_INFO_FREEFRAG' for o2info ioctl.
Date: Mon, 6 Dec 2010 16:46:28 -0800	[thread overview]
Message-ID: <20101207004628.GK16687@mail.oracle.com> (raw)
In-Reply-To: <4CD25B2A.7040909@oracle.com>

On Thu, Nov 04, 2010 at 03:05:14PM +0800, tristan wrote:
> #1 chunk   #2 chunk   #3 chunk    #4 chunk
> 1100       0010       0000        1100
> 
>  From above case, we found 3 real free chunks, they are:
> 
> 1st free_chunk_size = 4
> 
> 2nd free_chunk_size = 5
> 
> 3rd free_chunk_size = 2
> 
> Therefore, real_free_chunks = 3
> 
> While for the 'user-specified-chunksize' logic, we have 4 
> chunks(chunksize = 4), and only
> one(#3 chunk) was free.
> 
> Does it make sense?

	Yes.

Joel

-- 

 print STDOUT q
 Just another Perl hacker,
 unless $spring
	- Larry Wall

Joel Becker
Senior Development Manager
Oracle
E-mail: joel.becker at oracle.com
Phone: (650) 506-8127

  reply	other threads:[~2010-12-07  0:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-03 11:02 [Ocfs2-devel] [PATCH 1/2] Ocfs2: Add a new code 'OCFS2_INFO_FREEINODE' for o2info ioctl Tristan Ye
2010-11-03 11:02 ` [Ocfs2-devel] [PATCH 2/2] Ocfs2: Add a new code 'OCFS2_INFO_FREEFRAG' " Tristan Ye
2010-11-04  1:29   ` Joel Becker
2010-11-04  2:56     ` tristan
2010-11-04  4:47       ` tristan
2010-11-04  6:32       ` Joel Becker
2010-11-04  7:05         ` tristan
2010-12-07  0:46           ` Joel Becker [this message]
2010-11-04  1:18 ` [Ocfs2-devel] [PATCH 1/2] Ocfs2: Add a new code 'OCFS2_INFO_FREEINODE' " Joel Becker
2010-11-04  2:27   ` tristan
2010-11-04  6:28     ` Joel Becker
2010-11-04  8:10       ` tristan
2010-11-04 21:24         ` Joel Becker

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=20101207004628.GK16687@mail.oracle.com \
    --to=joel.becker@oracle.com \
    --cc=ocfs2-devel@oss.oracle.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;
as well as URLs for NNTP newsgroup(s).