Re: [PATCH, RFC] simplify writeback thread creation

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 2010-07-08 at 00:52 +0200, Christoph Hellwig wrote:
> @@ -503,18 +359,10 @@ int bdi_register(struct backing_dev_info
>          * and add other bdi's to the list. They will get a thread
> created
>          * on-demand when they need it.
>          */

Just noticed that this comment should be killed as well.

> -       if (bdi_cap_flush_forker(bdi)) {
> -               struct bdi_writeback *wb = &bdi->wb;
> -
> -               wb->task = kthread_run(bdi_forker_task, wb, "bdi-%s",
> -                                               dev_name(dev));
> -               if (IS_ERR(wb->task)) {
> -                       wb->task = NULL;
> -                       ret = -ENOMEM;
> -
> -                       bdi_remove_from_list(bdi);
> +       if (bdi_cap_writeback_dirty(bdi)) {
> +               ret = bdi_writeback_enable(bdi, dev);
> +               if (ret)
>                         goto exit;
> 
> 
-- 
Best Regards,
Artem Bityutskiy (Артём Битюцкий)

--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux