Re: [f2fs-dev] [PATCH] f2fs: change the way of handling range.len in F2FS_IOC_SEC_TRIM_FILE

2020-07-10 Thread Chao Yu
On 2020/7/10 14:46, Jaegeuk Kim wrote: > On 07/10, Chao Yu wrote: >> On 2020/7/10 11:52, Jaegeuk Kim wrote: >>> On 07/10, Chao Yu wrote: On 2020/7/10 11:31, Jaegeuk Kim wrote: > On 07/10, Chao Yu wrote: >> On 2020/7/10 11:02, Jaegeuk Kim wrote: >>> On 07/10, Daeho Jeong wrote:

Re: [f2fs-dev] [PATCH] f2fs: don't skip writeback of quota data

2020-07-10 Thread Chao Yu
On 2020/7/10 11:50, Jaegeuk Kim wrote: > On 07/10, Chao Yu wrote: >> On 2020/7/10 11:26, Jaegeuk Kim wrote: >>> On 07/10, Chao Yu wrote: On 2020/7/10 3:05, Jaegeuk Kim wrote: > On 07/09, Chao Yu wrote: >> On 2020/7/9 13:30, Jaegeuk Kim wrote: >>> It doesn't need to bypass flushing

Re: [f2fs-dev] IO hang due to f2fs checkpoint and writeback stuck

2020-07-10 Thread Chao Yu
On 2020/7/10 11:02, Gao Xiang wrote: > On Fri, Jul 10, 2020 at 10:54:13AM +0800, Chao Yu wrote: >> Hi Sahitya, >> >> It looks block plug has already been removed by Jaegeuk with >> below commit: >> >> commit 1f5f11a3c41e2b23288b2769435a00f74e02496b >> Author: Jaegeuk Kim >> Date: Fri May 8 12:25

Re: [f2fs-dev] [PATCH] f2fs: don't skip writeback of quota data

2020-07-10 Thread Jaegeuk Kim
On 07/10, Chao Yu wrote: > On 2020/7/10 11:50, Jaegeuk Kim wrote: > > On 07/10, Chao Yu wrote: > >> On 2020/7/10 11:26, Jaegeuk Kim wrote: > >>> On 07/10, Chao Yu wrote: > On 2020/7/10 3:05, Jaegeuk Kim wrote: > > On 07/09, Chao Yu wrote: > >> On 2020/7/9 13:30, Jaegeuk Kim wrote: > >>

Re: [f2fs-dev] IO hang due to f2fs checkpoint and writeback stuck

2020-07-10 Thread Chao Yu
On 2020/7/10 11:39, Sahitya Tummala wrote: > Hi Chao, > > On Fri, Jul 10, 2020 at 10:54:13AM +0800, Chao Yu wrote: >> Hi Sahitya, >> >> It looks block plug has already been removed by Jaegeuk with >> below commit: >> >> commit 1f5f11a3c41e2b23288b2769435a00f74e02496b >> Author: Jaegeuk Kim >> Dat

Re: [f2fs-dev] IO hang due to f2fs checkpoint and writeback stuck

2020-07-10 Thread Sahitya Tummala
On Fri, Jul 10, 2020 at 04:40:19PM +0800, Chao Yu wrote: > On 2020/7/10 11:39, Sahitya Tummala wrote: > > Hi Chao, > > > > On Fri, Jul 10, 2020 at 10:54:13AM +0800, Chao Yu wrote: > >> Hi Sahitya, > >> > >> It looks block plug has already been removed by Jaegeuk with > >> below commit: > >> > >> c

[f2fs-dev] [PATCH v2 0/1] f2fs: zns zone-capacity support

2020-07-10 Thread Aravind Ramesh
NVM Express Zoned Namespace command set specification allows host software to communicate with a NVM subsystem using zones. ZNS defines a host-managed zoned block device model for NVMe devices. It divides the logical address space of a namespace into zones. Each zone provides a LBA range that shall

[f2fs-dev] [PATCH v2 1/1] f2fs: support zone capacity less than zone size

2020-07-10 Thread Aravind Ramesh
NVMe Zoned Namespace devices can have zone-capacity less than zone-size. Zone-capacity indicates the maximum number of sectors that are usable in a zone beginning from the first sector of the zone. This makes the sectors sectors after the zone-capacity till zone-size to be unusable. This patch set

Re: [f2fs-dev] [PATCH 1/2] f2fs: support zone capacity less than zone size

2020-07-10 Thread Aravind Ramesh
Hello Chao, I have sent the second version of this patch, with below changes. Have merged the 2 patches into one. Updated commit message with nvme-cli output, as you suggested. Updated check_block_count(). Updated f2fs.rst. Changed kvfree() to kfree(). Please see inline, regarding one comment on