linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: Chao Yu <chao2.yu@samsung.com>
To: 'Kinglong Mee' <kinglongmee@gmail.com>
Cc: 'Jaegeuk Kim' <jaegeuk@kernel.org>,
	linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH] mkfs.f2fs: support large sector size
Date: Sat, 31 Jan 2015 16:50:17 +0800	[thread overview]
Message-ID: <008a01d03d33$18052080$480f6180$@samsung.com> (raw)
In-Reply-To: <CAB6yy36s8rSCv11_RMVLc1_MX351DZLvcQyW_sAr35+__z7WQw@mail.gmail.com>

Hi Kinglong,

> -----Original Message-----
> From: Kinglong Mee [mailto:kinglongmee@gmail.com]
> Sent: Friday, January 30, 2015 8:04 PM
> To: Chao Yu
> Cc: Jaegeuk Kim; Changman Lee; linux-f2fs-devel@lists.sourceforge.net
> Subject: Re: [f2fs-dev] [PATCH] mkfs.f2fs: support large sector size
> 
> On Fri, Jan 30, 2015 at 3:49 PM, Chao Yu <chao2.yu@samsung.com> wrote:
> > Since f2fs support large sector size in commit 55cf9cb63f0e "f2fs: support large
> > sector size", block device with sector size of 512/1024/2048/4096 bytes can be
> > supported.
> >
> > But mkfs.f2fs still use default sector size: 512 bytes as sector size, let's fix
> > this issue in this patch.
> >
> > Signed-off-by: Chao Yu <chao2.yu@samsung.com>
> > ---
> >  lib/libf2fs.c            | 2 +-
> >  mkfs/f2fs_format.c       | 6 +++---
> >  mkfs/f2fs_format_utils.c | 2 +-
> >  3 files changed, 5 insertions(+), 5 deletions(-)
> >
> > diff --git a/lib/libf2fs.c b/lib/libf2fs.c
> > index 8123528..9b9578b 100644
> > --- a/lib/libf2fs.c
> > +++ b/lib/libf2fs.c
> > @@ -504,7 +504,7 @@ int f2fs_get_device_info(struct f2fs_configuration *c)
> >         MSG(0, "Info: total sectors = %"PRIu64" (in 512bytes)\n",
> 
> Should using c->sector_size instead 512bytes here ?

Right, I will fix this.

> 
> >                                         c->total_sectors);
> >         if (c->total_sectors <
> > -                       (F2FS_MIN_VOLUME_SIZE / DEFAULT_SECTOR_SIZE)) {
> > +                       (F2FS_MIN_VOLUME_SIZE / c->sector_size)) {
> >                 MSG(0, "Error: Min volume size supported is %d\n",
> >                                 F2FS_MIN_VOLUME_SIZE);
> >                 return -1;
> > diff --git a/mkfs/f2fs_format.c b/mkfs/f2fs_format.c
> > index a8d2db6..861fe2f 100644
> > --- a/mkfs/f2fs_format.c
> > +++ b/mkfs/f2fs_format.c
> > @@ -198,10 +198,10 @@ static int f2fs_prepare_super_block(void)
> >         set_sb(block_count, config.total_sectors >> log_sectors_per_block);
> >
> >         zone_align_start_offset =
> > -               (config.start_sector * DEFAULT_SECTOR_SIZE +
> > +               (config.start_sector * config.sector_size +
> >                 2 * F2FS_BLKSIZE + zone_size_bytes - 1) /
> >                 zone_size_bytes * zone_size_bytes -
> > -               config.start_sector * DEFAULT_SECTOR_SIZE;
> > +               config.start_sector * config.sector_size;
> >
> >         if (config.start_sector % DEFAULT_SECTORS_PER_BLOCK) {
> 
> and,
> DEFAULT_SECTORS_PER_BLOCK should be instead by config.sectors_per_blk
> at the same patch ?

That's right, will fix.

Thank you for the review. :)

Regards,

> 
> thanks,
> Kinglong Mee


------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/

      reply	other threads:[~2015-01-31  8:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-30  7:49 [PATCH] mkfs.f2fs: support large sector size Chao Yu
2015-01-30 12:04 ` Kinglong Mee
2015-01-31  8:50   ` Chao Yu [this message]

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='008a01d03d33$18052080$480f6180$@samsung.com' \
    --to=chao2.yu@samsung.com \
    --cc=jaegeuk@kernel.org \
    --cc=kinglongmee@gmail.com \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    /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).