Re: [PATCH v2] buffer: Avoid setting buffer bits that are already set

2018-02-02 Thread Jens Axboe
On 2/2/18 1:07 AM, kemi wrote: > Hi, Jens > Could you help to merge this patch to your tree? Thanks Yes, I'll queue it up, thanks. -- Jens Axboe

Re: [PATCH v2] buffer: Avoid setting buffer bits that are already set

2018-02-02 Thread Jens Axboe
On 2/2/18 1:07 AM, kemi wrote: > Hi, Jens > Could you help to merge this patch to your tree? Thanks Yes, I'll queue it up, thanks. -- Jens Axboe

Re: [PATCH v2] buffer: Avoid setting buffer bits that are already set

2018-02-02 Thread kemi
Hi, Jens Could you help to merge this patch to your tree? Thanks On 2017年11月03日 10:29, kemi wrote: > > > On 2017年10月24日 09:16, Kemi Wang wrote: >> It's expensive to set buffer flags that are already set, because that >> causes a costly cache line transition. >> >> A common case is setting the

Re: [PATCH v2] buffer: Avoid setting buffer bits that are already set

2018-02-02 Thread kemi
Hi, Jens Could you help to merge this patch to your tree? Thanks On 2017年11月03日 10:29, kemi wrote: > > > On 2017年10月24日 09:16, Kemi Wang wrote: >> It's expensive to set buffer flags that are already set, because that >> causes a costly cache line transition. >> >> A common case is setting the

Re: [PATCH v2] buffer: Avoid setting buffer bits that are already set

2017-11-02 Thread kemi
On 2017年10月24日 09:16, Kemi Wang wrote: > It's expensive to set buffer flags that are already set, because that > causes a costly cache line transition. > > A common case is setting the "verified" flag during ext4 writes. > This patch checks for the flag being set first. > > With the

Re: [PATCH v2] buffer: Avoid setting buffer bits that are already set

2017-11-02 Thread kemi
On 2017年10月24日 09:16, Kemi Wang wrote: > It's expensive to set buffer flags that are already set, because that > causes a costly cache line transition. > > A common case is setting the "verified" flag during ext4 writes. > This patch checks for the flag being set first. > > With the

[PATCH v2] buffer: Avoid setting buffer bits that are already set

2017-10-23 Thread Kemi Wang
It's expensive to set buffer flags that are already set, because that causes a costly cache line transition. A common case is setting the "verified" flag during ext4 writes. This patch checks for the flag being set first. With the AIM7/creat-clo benchmark testing on a 48G ramdisk based-on ext4

[PATCH v2] buffer: Avoid setting buffer bits that are already set

2017-10-23 Thread Kemi Wang
It's expensive to set buffer flags that are already set, because that causes a costly cache line transition. A common case is setting the "verified" flag during ext4 writes. This patch checks for the flag being set first. With the AIM7/creat-clo benchmark testing on a 48G ramdisk based-on ext4