Re: [PATCH] fs: don't flush pagecache when expanding block device

2018-03-19 Thread Shunki Fujita
Hi Andrew, > On Fri, 16 Mar 2018 15:55:53 +0900 shunki-fujita > wrote: > > > When changing the size of a block device, its all caches are freed. > > It's necessary on shrinking to prevent spurious I/Os to the disappeared > > region. > > However, on expanding, such

Re: [PATCH] fs: don't flush pagecache when expanding block device

2018-03-19 Thread Shunki Fujita
Hi Andrew, > On Fri, 16 Mar 2018 15:55:53 +0900 shunki-fujita > wrote: > > > When changing the size of a block device, its all caches are freed. > > It's necessary on shrinking to prevent spurious I/Os to the disappeared > > region. > > However, on expanding, such kind of I/Os doesn't happen.

Re: [PATCH] fs: don't flush pagecache when expanding block device

2018-03-16 Thread Andrew Morton
On Fri, 16 Mar 2018 15:55:53 +0900 shunki-fujita wrote: > When changing the size of a block device, its all caches are freed. > It's necessary on shrinking to prevent spurious I/Os to the disappeared > region. > However, on expanding, such kind of I/Os doesn't

Re: [PATCH] fs: don't flush pagecache when expanding block device

2018-03-16 Thread Andrew Morton
On Fri, 16 Mar 2018 15:55:53 +0900 shunki-fujita wrote: > When changing the size of a block device, its all caches are freed. > It's necessary on shrinking to prevent spurious I/Os to the disappeared > region. > However, on expanding, such kind of I/Os doesn't happen. > > Similar things can

[PATCH] fs: don't flush pagecache when expanding block device

2018-03-16 Thread shunki-fujita
When changing the size of a block device, its all caches are freed. It's necessary on shrinking to prevent spurious I/Os to the disappeared region. However, on expanding, such kind of I/Os doesn't happen. Similar things can be considered for btrfs filesystem resize and resize2fs, but they are

[PATCH] fs: don't flush pagecache when expanding block device

2018-03-16 Thread shunki-fujita
When changing the size of a block device, its all caches are freed. It's necessary on shrinking to prevent spurious I/Os to the disappeared region. However, on expanding, such kind of I/Os doesn't happen. Similar things can be considered for btrfs filesystem resize and resize2fs, but they are