Too many I/O controller patches
- From: Dave Hansen <dave@xxxxxxxxxxxxxxxxxx>
- Date: Mon, 04 Aug 2008 10:20:33 -0700
On Mon, 2008-08-04 at 17:51 +0900, Ryo Tsuruta wrote:
This series of patches of dm-ioband now includes "The bio tracking mechanism,"
which has been posted individually to this mailing list.
This makes it easy for anybody to control the I/O bandwidth even when
the I/O is one of delayed-write requests.
During the Containers mini-summit at OLS, it was mentioned that there
are at least *FOUR* of these I/O controllers floating around. Have you
talked to the other authors? (I've cc'd at least one of them).
We obviously can't come to any kind of real consensus with people just
tossing the same patches back and forth.
-- Dave
--
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/
- Follow-Ups:
- RFC: I/O bandwidth controller (was Re: Too many I/O controller patches)
- From: Fernando Luis Vázquez Cao
- Re: Too many I/O controller patches
- From: Balbir Singh
- Re: Too many I/O controller patches
- From: Andrea Righi
- RFC: I/O bandwidth controller (was Re: Too many I/O controller patches)
- References:
- [PATCH 0/7] I/O bandwidth controller and BIO tracking
- From: Ryo Tsuruta
- [PATCH 0/7] I/O bandwidth controller and BIO tracking
- Prev by Date: Re: [RFC] ftrace: support tracing functions in one module
- Next by Date: Re: [PATCH] Export shmem_file_setup and shmem_getpage for DRM-GEM
- Previous by thread: Re: [PATCH 4/7] bio-cgroup: Split the cgroup memory subsystem into two parts
- Next by thread: Re: Too many I/O controller patches
- Index(es):
Relevant Pages
|
