On 2018/1/24 10:39, Jaegeuk Kim wrote:
> On 01/24, Chao Yu wrote:
>> On 2018/1/24 10:22, Jaegeuk Kim wrote:
>>> On 01/24, Chao Yu wrote:
On 2018/1/24 6:19, Jaegeuk Kim wrote:
> On 01/23, Jaegeuk Kim wrote:
>> On 01/23, Chao Yu wrote:
>>> On 2018/1/23 7:00, Jaegeuk Kim wrote:
On 01/24, Chao Yu wrote:
> On 2018/1/24 10:22, Jaegeuk Kim wrote:
> > On 01/24, Chao Yu wrote:
> >> On 2018/1/24 6:19, Jaegeuk Kim wrote:
> >>> On 01/23, Jaegeuk Kim wrote:
> On 01/23, Chao Yu wrote:
> > On 2018/1/23 7:00, Jaegeuk Kim wrote:
> >> On 01/17, Chao Yu wrote:
> >>> Hi
On 2018/1/24 10:22, Jaegeuk Kim wrote:
> On 01/24, Chao Yu wrote:
>> On 2018/1/24 6:19, Jaegeuk Kim wrote:
>>> On 01/23, Jaegeuk Kim wrote:
On 01/23, Chao Yu wrote:
> On 2018/1/23 7:00, Jaegeuk Kim wrote:
>> On 01/17, Chao Yu wrote:
>>> Hi Jaegeuk,
>>>
>>> On 2018/1/17
On 01/24, Chao Yu wrote:
> On 2018/1/24 6:19, Jaegeuk Kim wrote:
> > On 01/23, Jaegeuk Kim wrote:
> >> On 01/23, Chao Yu wrote:
> >>> On 2018/1/23 7:00, Jaegeuk Kim wrote:
> On 01/17, Chao Yu wrote:
> > Hi Jaegeuk,
> >
> > On 2018/1/17 8:47, Jaegeuk Kim wrote:
> >> Hi Chao,
>
On 2018/1/24 6:19, Jaegeuk Kim wrote:
> On 01/23, Jaegeuk Kim wrote:
>> On 01/23, Chao Yu wrote:
>>> On 2018/1/23 7:00, Jaegeuk Kim wrote:
On 01/17, Chao Yu wrote:
> Hi Jaegeuk,
>
> On 2018/1/17 8:47, Jaegeuk Kim wrote:
>> Hi Chao,
>>
>> On 01/15, Chao Yu wrote:
On 01/23, Jaegeuk Kim wrote:
> On 01/23, Chao Yu wrote:
> > On 2018/1/23 7:00, Jaegeuk Kim wrote:
> > > On 01/17, Chao Yu wrote:
> > >> Hi Jaegeuk,
> > >>
> > >> On 2018/1/17 8:47, Jaegeuk Kim wrote:
> > >>> Hi Chao,
> > >>>
> > >>> On 01/15, Chao Yu wrote:
> > Previously, our total node
On 01/23, Chao Yu wrote:
> On 2018/1/23 7:00, Jaegeuk Kim wrote:
> > On 01/17, Chao Yu wrote:
> >> Hi Jaegeuk,
> >>
> >> On 2018/1/17 8:47, Jaegeuk Kim wrote:
> >>> Hi Chao,
> >>>
> >>> On 01/15, Chao Yu wrote:
> Previously, our total node number (nat_bitmap) and total nat segment
>
On 2018/1/23 7:00, Jaegeuk Kim wrote:
> On 01/17, Chao Yu wrote:
>> Hi Jaegeuk,
>>
>> On 2018/1/17 8:47, Jaegeuk Kim wrote:
>>> Hi Chao,
>>>
>>> On 01/15, Chao Yu wrote:
Previously, our total node number (nat_bitmap) and total nat segment count
will not monotonously increase along with
On 01/17, Chao Yu wrote:
> Hi Jaegeuk,
>
> On 2018/1/17 8:47, Jaegeuk Kim wrote:
> > Hi Chao,
> >
> > On 01/15, Chao Yu wrote:
> >> Previously, our total node number (nat_bitmap) and total nat segment count
> >> will not monotonously increase along with image size, and max nat_bitmap
> >> size
Hi Xiang,
On 2018/1/17 11:35, Gao Xiang wrote:
> Hi Chao Yu,
>
>
> On 2018/1/17 11:15, Chao Yu wrote:
>> Hi Jaegeuk,
>>
>> On 2018/1/17 8:47, Jaegeuk Kim wrote:
>>> Hi Chao,
>>>
>>> On 01/15, Chao Yu wrote:
Previously, our total node number (nat_bitmap) and total nat segment count
Hi Chao Yu,
On 2018/1/17 11:15, Chao Yu wrote:
Hi Jaegeuk,
On 2018/1/17 8:47, Jaegeuk Kim wrote:
Hi Chao,
On 01/15, Chao Yu wrote:
Previously, our total node number (nat_bitmap) and total nat segment count
will not monotonously increase along with image size, and max nat_bitmap size
is
Hi Jaegeuk,
On 2018/1/17 8:47, Jaegeuk Kim wrote:
> Hi Chao,
>
> On 01/15, Chao Yu wrote:
>> Previously, our total node number (nat_bitmap) and total nat segment count
>> will not monotonously increase along with image size, and max nat_bitmap size
>> is limited by "CHECKSUM_OFFSET -
Hi Chao,
On 01/15, Chao Yu wrote:
> Previously, our total node number (nat_bitmap) and total nat segment count
> will not monotonously increase along with image size, and max nat_bitmap size
> is limited by "CHECKSUM_OFFSET - sizeof(struct f2fs_checkpoint) + 1", it is
> with bad scalability when
Previously, our total node number (nat_bitmap) and total nat segment count
will not monotonously increase along with image size, and max nat_bitmap size
is limited by "CHECKSUM_OFFSET - sizeof(struct f2fs_checkpoint) + 1", it is
with bad scalability when user wants to create more inode/node in
14 matches
Mail list logo