All of lore.kernel.org
 help / color / mirror / Atom feed
From: Damien Le Moal <damien.lemoal@wdc.com>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: Reinecke <hare@suse.de>,
	Hannes, Shaun Tancheff <shaun@tancheff.com>,
	linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH 0/7] f2fs-tools: zoned block device support
Date: Tue, 1 Nov 2016 17:25:54 +0900	[thread overview]
Message-ID: <d948f7b5-a37b-52f2-6ca9-5f0c750f71d3@wdc.com> (raw)
In-Reply-To: <20161101034618.GA30731@jaegeuk>


Jaegeuk,

On 11/1/16 12:46, Jaegeuk Kim wrote:
> I've resolved some conflicts in the patches, and finally integrated them on
> top of our dev branch.
> Could you take a look at them from the below url?
> 
> http://git.kernel.org/cgit/linux/kernel/git/jaegeuk/f2fs-tools.git/log/?h=dev

Checked and tested. This all looks good, no problems detected.
Thank you !

Please let me know how the kernel side integration goes. I can rebase on
the dev branch if needed. I used the f2fs code in Jens for-4.10/block
tree. That code was identical to f2fs tree master branch, apart from the
gc bug fix patch that I added.

Best regards.

> 
> Thanks,
> 
> On Fri, Oct 28, 2016 at 04:56:56PM +0900, Damien Le Moal wrote:
>> With the introduction of zoned block device support in the kernel, accessing
>> discovering if a block device is zoned and accessing its zone layout information
>> does not require using SG_IO anymore. The file /sys/block/<dev>/queue/zoned
>> indicates the device zone model and the ioctls BLKREPORTZONE and BLKRESETZONE
>> defined in include/uapi/linux/blkzoned.h allow manipulating zones more easily.
>>
>> This patch series brings in support for this new interface in place of the
>> direct SG_IO-zbc commands. In addition, it enforces some formtating options
>> for host-managed zoned block devices and straighten device zone layout checks
>> to make sure that the device can be used.
>>
>> Finally, as discard does not result in write pointer zone reset, the ioctl
>> BLKRESETZONE is used during formatting to properly initialize all sequential
>> zones of the device.
>>
>> Damien Le Moal (7):
>>   f2fs-tools: Add executable files to .gitignore
>>   f2fs-tools: Use zoned block device terminology
>>   f2fs-tools: Introduce support for zoned block devices
>>   mkfs.f2fs: Check options for zoned block devices
>>   mkfs.f2fs: Reset sequential zones on device discard
>>   mkfs.f2fs: Check zoned block devices configuration
>>   fsck.f2fs: Check BLKZONED feature on mount
>>
>>  .gitignore               |   4 +
>>  configure.ac             |   2 +-
>>  fsck/mount.c             |  11 +-
>>  include/f2fs_fs.h        | 111 +++++---
>>  lib/Makefile.am          |   2 +-
>>  lib/libf2fs.c            |  40 ++-
>>  lib/libf2fs_zoned.c      | 296 ++++++++++++++++++++++
>>  lib/zbc.c                | 647 -----------------------------------------------
>>  lib/zbc.h                | 361 --------------------------
>>  mkfs/f2fs_format.c       |  24 +-
>>  mkfs/f2fs_format_main.c  |  24 +-
>>  mkfs/f2fs_format_utils.c |   2 +
>>  12 files changed, 464 insertions(+), 1060 deletions(-)
>>  create mode 100644 lib/libf2fs_zoned.c
>>  delete mode 100644 lib/zbc.c
>>  delete mode 100644 lib/zbc.h
>>
>> -- 
>> 2.7.4
>>
>> Western Digital Corporation (and its subsidiaries) E-mail Confidentiality Notice & Disclaimer:
>>
>> This e-mail and any files transmitted with it may contain confidential or legally privileged information of WDC and/or its affiliates, and are intended solely for the use of the individual or entity to which they are addressed. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited. If you have received this e-mail in error, please notify the sender immediately and delete the e-mail in its entirety from your system.

-- 
Damien Le Moal, Ph.D.
Sr Manager, System Software Group,
Shared Technology Research, Western Digital
Damien.LeMoal@hgst.com
Tel: (+81) 0466-98-3593 (Ext. 51-3593)
1 kirihara-cho, Fujisawa, Kanagawa, 252-0888 Japan
www.wdc.com, www.hgst.com
Western Digital Corporation (and its subsidiaries) E-mail Confidentiality Notice & Disclaimer:

This e-mail and any files transmitted with it may contain confidential or legally privileged information of WDC and/or its affiliates, and are intended solely for the use of the individual or entity to which they are addressed. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited. If you have received this e-mail in error, please notify the sender immediately and delete the e-mail in its entirety from your system.


------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi

  reply	other threads:[~2016-11-01  8:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-28  7:56 [PATCH 0/7] f2fs-tools: zoned block device support Damien Le Moal
2016-10-28  7:56 ` [PATCH 1/7] f2fs-tools: Add executable files to .gitignore Damien Le Moal
2016-10-28  7:56 ` [PATCH 1/7] Gitignore: add executable files Damien Le Moal
2016-10-28  7:56 ` [PATCH 2/7] f2fs-tools: Use zoned block device terminology Damien Le Moal
2016-10-28  7:57 ` [PATCH 3/7] f2fs-tools: Introduce support for zoned block devices Damien Le Moal
2016-10-28  7:57 ` [PATCH 4/7] mkfs.f2fs: Check options " Damien Le Moal
2016-10-28  7:57 ` [PATCH 5/7] mkfs.f2fs: Reset sequential zones on device discard Damien Le Moal
2016-10-28  7:57 ` [PATCH 6/7] mkfs.f2fs: Check zoned block devices configuration Damien Le Moal
2016-10-28  7:57 ` [PATCH 7/7] fsck.f2fs: Check BLKZONED feature on mount Damien Le Moal
2016-11-01  3:46 ` [PATCH 0/7] f2fs-tools: zoned block device support Jaegeuk Kim
2016-11-01  8:25   ` Damien Le Moal [this message]
2016-11-01 18:22     ` Jaegeuk Kim

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=d948f7b5-a37b-52f2-6ca9-5f0c750f71d3@wdc.com \
    --to=damien.lemoal@wdc.com \
    --cc=hare@suse.de \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=shaun@tancheff.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.