[no subject]

[taka]

To agk@xxxxxxxxxxxxxx
cc: dm-devel@xxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx
Subject: [RFC][PATCH 0/10] I/O context inheritance
From: Hirokazu Takahashi <taka@xxxxxxxxxxxxx>
X-Mailer: Mew version 5.1.52 on Emacs 21.4 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi,

This series of patches make the block I/O layer and the I/O schedulers
be able to determine the right io_context of every I/O.

The current implementation of the block I/O layer and the I/O schedulers
assume that the current process is the one which issued the given I/O,
then use the io_context of this process to control the I/O.
But this assumption isn't quite right because several kernel threads
will handle I/O requests on behalf of the processes which originated them.
This often happens when you want to use device mapper modules.

The patches make every bio has a pointer to an io_context, which will
be set when it is allocated or cloned. So it makes it possible to find
the right io_context from any bio at any place.

I'm waiting for your comments.

Thank you,
Hirokazu Takahashi.





--
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/