mbox series

[00/12] bcache patches for Linux v4.21

Message ID 20181213145357.38528-1-colyli@suse.de (mailing list archive)
Headers show
Series bcache patches for Linux v4.21 | expand

Message

Coly Li Dec. 13, 2018, 2:53 p.m. UTC
Hi Jens,

Here are the patches for Linux v4.21.

The patches from me are for a set of disabled-by-default optimization
for writeback cache mode, which are used by some users I know. Guoju
Fang contributes a patch to add number of keys in
trace_bcache_journal_write(). And there are 6 patchges are from Shenghui
Wang, which removes an unncessary NULL check for
debugfs_remove_recursive() and debugfs_remove(), adds useful code
comments for bcache, and improves sysfs information display for bcache
writeback rate parameters.

We don't have important or big change in this run. Please take these
patches.

Thanks in advance.

Coly Li
---
Coly Li (5):
  bcache: introduce force_wake_up_gc()
  bcache: option to automatically run gc thread after writeback
    accomplished
  bcache: add MODULE_DESCRIPTION information
  bcache: make cutoff_writeback and cutoff_writeback_sync tunnable
  bcache: set writeback_percent in a flexible range

Guoju Fang (1):
  bcache: print number of keys in trace_bcache_journal_write

Shenghui Wang (6):
  bcache: add comment for cache_set->fill_iter
  bcache: do not check if debug dentry is ERR or NULL explicitly on
    remove
  bcache: update comment for bch_data_insert
  bcache: update comment in sysfs.c
  bcache: do not mark writeback_running until backing dev attached to
    cache_set
  bcache: cannot set writeback_running via sysfs if no writeback kthread
    created

 drivers/md/bcache/bcache.h    | 20 +++++++++++++-
 drivers/md/bcache/btree.c     |  5 ++++
 drivers/md/bcache/btree.h     | 18 +++++++++++++
 drivers/md/bcache/debug.c     |  3 +--
 drivers/md/bcache/journal.c   |  2 +-
 drivers/md/bcache/request.c   |  6 ++---
 drivers/md/bcache/super.c     | 48 +++++++++++++++++++++++++++++++---
 drivers/md/bcache/sysfs.c     | 61 +++++++++++++++++++++++++++++--------------
 drivers/md/bcache/writeback.c | 30 ++++++++++++++++++++-
 drivers/md/bcache/writeback.h | 12 +++++++--
 include/trace/events/bcache.h | 27 ++++++++++++++++---
 11 files changed, 195 insertions(+), 37 deletions(-)

Comments

Jens Axboe Dec. 13, 2018, 3:16 p.m. UTC | #1
On 12/13/18 7:53 AM, Coly Li wrote:
> Hi Jens,
> 
> Here are the patches for Linux v4.21.
> 
> The patches from me are for a set of disabled-by-default optimization
> for writeback cache mode, which are used by some users I know. Guoju
> Fang contributes a patch to add number of keys in
> trace_bcache_journal_write(). And there are 6 patchges are from Shenghui
> Wang, which removes an unncessary NULL check for
> debugfs_remove_recursive() and debugfs_remove(), adds useful code
> comments for bcache, and improves sysfs information display for bcache
> writeback rate parameters.
> 
> We don't have important or big change in this run. Please take these
> patches.

Applied, thanks.

Note that I reformated some of the commit messages and patch headers.
Keep them within 72 chars, then everything is much more readable
in git log.
Coly Li Dec. 14, 2018, 8:25 a.m. UTC | #2
On 12/13/18 11:16 PM, Jens Axboe wrote:
> On 12/13/18 7:53 AM, Coly Li wrote:
>> Hi Jens,
>>
>> Here are the patches for Linux v4.21.
>>
>> The patches from me are for a set of disabled-by-default optimization
>> for writeback cache mode, which are used by some users I know. Guoju
>> Fang contributes a patch to add number of keys in
>> trace_bcache_journal_write(). And there are 6 patchges are from Shenghui
>> Wang, which removes an unncessary NULL check for
>> debugfs_remove_recursive() and debugfs_remove(), adds useful code
>> comments for bcache, and improves sysfs information display for bcache
>> writeback rate parameters.
>>
>> We don't have important or big change in this run. Please take these
>> patches.
> 
> Applied, thanks.
> 
> Note that I reformated some of the commit messages and patch headers.
> Keep them within 72 chars, then everything is much more readable
> in git log.

Hi Jens,

Sure I will take more attention on the 72 chars limit, thanks for your
remind.

Coly Li