I think the deletion_work_list you mentioned is to keep the deletion work runs sequentially, we can queue the next work from the list only after the previous one finishes. thanks, levin On Friday, May 4, 2012, Christoph Hellwig wrote: > On Fri, May 04, 2012 at 10:26:36AM +0800, levin li wrote: > > Creating a work queue seems a good idea, or maybe we can reuse > > the current deletion_queue, I'd try this, since it's more > > acceptable than change the thread model. > > > Btw, why is the current deletion work queue so complicated? The sheepdog > workqueues look fiarly similar to the Linux kernel ones where you queue up > each item individually, but the delete queue keeps an additional list of > items to be deleted. What's the reason for that? > -- levin basiccoder.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.wpkg.org/pipermail/sheepdog/attachments/20120505/77562d78/attachment.html> |