RE: [PATCH] exfat: optimize dir-cache

2020-06-01 Thread Namjae Jeon
> > Optimize directory access based on exfat_entry_set_cache. > > - Hold bh instead of copied d-entry. > > - Modify bh->data directly instead of the copied d-entry. > > - Write back the retained bh instead of rescanning the d-entry-set. > > And > > - Remove unused cache related definitions. > >

RE: [PATCH] exfat: optimize dir-cache

2020-06-01 Thread Sungjong Seo
> Optimize directory access based on exfat_entry_set_cache. > - Hold bh instead of copied d-entry. > - Modify bh->data directly instead of the copied d-entry. > - Write back the retained bh instead of rescanning the d-entry-set. > And > - Remove unused cache related definitions. > > Signed-off

RE: [PATCH] exfat: optimize dir-cache

2020-05-27 Thread Namjae Jeon
> >>> > In order to prevent illegal accesses to bh and dentries, it > >>> would be better to check validation for num and bh. > >>> > >>> There is no new error checking for same reason as above. > >>> > >>> I'll try to add error checking to this v2 patch. > >>> Or is it better to add error

RE: [PATCH] exfat: optimize dir-cache

2020-05-27 Thread Namjae Jeon
> +struct exfat_dentry *exfat_get_dentry_cached( > + struct exfat_entry_set_cache *es, int num); You used a single tab for the continuing line of the prototype here. We usually use two tabs for this. > struct exfat_entry_set_cache *exfat_get_dentry_set(struct super_block *sb, > - s

Re: [PATCH] exfat: optimize dir-cache

2020-05-27 Thread Tetsuhiro Kohada
> In order to prevent illegal accesses to bh and dentries, it would be better to check validation for num and bh. There is no new error checking for same reason as above. I'll try to add error checking to this v2 patch. Or is it better to add error checking in another patch? The latter:

RE: [PATCH] exfat: optimize dir-cache

2020-05-27 Thread Sungjong Seo
> 2020-05-27 17:00 GMT+09:00, > kohada.tetsuh...@dc.mitsubishielectric.co.jp > : > > Thank you for your comment. > > > > >> +for (i = 0; i < es->num_bh; i++) { > > >> +if (es->modified) > > >> +exfat_update_bh(es->sb, es->bh[i], sync); > > > > > > Overall, i

Re: [PATCH] exfat: optimize dir-cache

2020-05-27 Thread Namjae Jeon
2020-05-27 17:00 GMT+09:00, kohada.tetsuh...@dc.mitsubishielectric.co.jp : > Thank you for your comment. > > >> +for (i = 0; i < es->num_bh; i++) { > >> +if (es->modified) > >> +exfat_update_bh(es->sb, es->bh[i], sync); > > > > Overall, it looks good to me.

Re: [PATCH] exfat: optimize dir-cache

2020-05-27 Thread kohada.tetsuh...@dc.mitsubishielectric.co.jp
Thank you for your comment. >> +for (i = 0; i < es->num_bh; i++) { >> +if (es->modified) >> +exfat_update_bh(es->sb, es->bh[i], sync); > > Overall, it looks good to me. > However, if "sync" is set, it looks better to return the result of > exfat_update_b

RE: [PATCH] exfat: optimize dir-cache

2020-05-25 Thread Sungjong Seo
> Optimize directory access based on exfat_entry_set_cache. > - Hold bh instead of copied d-entry. > - Modify bh->data directly instead of the copied d-entry. > - Write back the retained bh instead of rescanning the d-entry-set. > And > - Remove unused cache related definitions. > > Signed-off