On 11/13/2009 03:46 AM, Chris Mason wrote: > On Thu, Nov 12, 2009 at 05:00:05PM -0500, Chris Mason wrote: > > [ ...] > >> >> The punch line is that the btrfs guy thinks we can solve all of this with >> just one more thread. If we change dm-crypt to have a thread dedicated >> to sync IO and a thread dedicated to async IO the system should smooth >> out.
Please, can you cc DM maintainers with these kind of patches? dm-devel list at least. Note that the crypt requests can be already processed synchronously or asynchronously, depending on used crypto module (async it is in the case of some hw acceleration). Adding another queue make the situation more complicated and because the crypt requests can be queued in crypto layer I am not sure that this solution will help in this situation at all. (Try to run that with AES-NI acceleration for example.) Milan -- [email protected] -- To unsubscribe from this list: send the line "unsubscribe kernel-testers" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
