Re: [f2fs-dev] [PATCH v3] f2fs: don't use GFP_ZERO for page caches

On 2018/4/10 14:40, Jaegeuk Kim wrote: > On 04/10, Chao Yu wrote: >> On 2018/4/10 11:29, Jaegeuk Kim wrote: >>> Change log from v2: >>> - consider IO error case when dealing with metapage >>> - memset by fill_node_footer >>> >>> Change log from v1: >>> - don't memset for recovered page >>>

Re: [f2fs-dev] [PATCH v3] f2fs: don't use GFP_ZERO for page caches

On 04/10, Chao Yu wrote: > On 2018/4/10 11:29, Jaegeuk Kim wrote: > > Change log from v2: > > - consider IO error case when dealing with metapage > > - memset by fill_node_footer > > > > Change log from v1: > > - don't memset for recovered page > > > > Related to

Re: [f2fs-dev] [PATCH v3] f2fs: don't use GFP_ZERO for page caches

On 2018/4/10 11:29, Jaegeuk Kim wrote: > Change log from v2: > - consider IO error case when dealing with metapage > - memset by fill_node_footer > > Change log from v1: > - don't memset for recovered page > > Related to https://lkml.org/lkml/2018/4/8/661 > > Sometimes, we need to write

Re: [f2fs-dev] [PATCH v3] f2fs: don't use GFP_ZERO for page caches

Change log from v2: - consider IO error case when dealing with metapage - memset by fill_node_footer Change log from v1: - don't memset for recovered page Related to https://lkml.org/lkml/2018/4/8/661 Sometimes, we need to write meta data to new allocated block address, then we will