Re: [PATCH 04/11] writeback: switch to per-bdi threads for flushingdata

From: Artem Bityutskiy
Date: Thu May 28 2009 - 10:19:30 EST

Next message: Lennart Poettering: "[PATCH] V4L/pwc - use usb_interface as parent, not usb_device"
Previous message: Lennart Poettering: "[PATCH 3/3] scheduler: introduce SCHED_RESET_ON_FORK schedulingpolicy flag"
In reply to: Jens Axboe: "[PATCH 04/11] writeback: switch to per-bdi threads for flushing data"
Next in thread: Jens Axboe: "Re: [PATCH 04/11] writeback: switch to per-bdi threads forflushing data"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Jens Axboe wrote:

+#define BDI_CAP_FLUSH_FORKER 0x00000200

Would it please be possible to add a comment about
what this flag is, and whether it is for internal
usage or not. Not immediately obvious for me.

Artem.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Next message: Lennart Poettering: "[PATCH] V4L/pwc - use usb_interface as parent, not usb_device"
Previous message: Lennart Poettering: "[PATCH 3/3] scheduler: introduce SCHED_RESET_ON_FORK schedulingpolicy flag"
In reply to: Jens Axboe: "[PATCH 04/11] writeback: switch to per-bdi threads for flushing data"
Next in thread: Jens Axboe: "Re: [PATCH 04/11] writeback: switch to per-bdi threads forflushing data"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]