[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090525101323.GD23546@duck.suse.cz>
Date: Mon, 25 May 2009 12:13:24 +0200
From: Jan Kara <jack@...e.cz>
To: Jens Axboe <jens.axboe@...cle.com>
Cc: linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
chris.mason@...cle.com, david@...morbit.com, hch@...radead.org,
akpm@...ux-foundation.org, jack@...e.cz,
yanmin_zhang@...ux.intel.com
Subject: Re: [PATCH 06/12] writeback: separate the flushing state/task from
the bdi
On Mon 25-05-09 09:34:41, Jens Axboe wrote:
> Add a struct bdi_writeback for tracking and handling dirty IO. This
> is in preparation for adding > 1 flusher task per bdi.
>
> Signed-off-by: Jens Axboe <jens.axboe@...cle.com>
...
> static int bdi_start_fn(void *ptr)
> {
> - struct backing_dev_info *bdi = ptr;
> + struct bdi_writeback *wb = ptr;
> + struct backing_dev_info *bdi = wb->bdi;
> struct task_struct *tsk = current;
> -
> - /*
> - * Add us to the active bdi_list
> - */
> - mutex_lock(&bdi_lock);
> - list_add(&bdi->bdi_list, &bdi_list);
> - mutex_unlock(&bdi_lock);
I'm probably missing something but I cannot find where the bdi is added
to the bdi_list after this patch...
Honza
--
Jan Kara <jack@...e.cz>
SUSE Labs, CR
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists