Re: understanding the map_task*/do_task split

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Sorry, forgot to CC the list.

On Thu, Jun 09, 2011 at 09:40:11AM -0400, Christoph Hellwig wrote:
> Hi Nick,
> 
> can you explain what the rationale for the split between the
> map_task* and do_task methods for the backend is?  We run map_task*
> fairly early, depending on the fabric possible in the callers context,
> while do_task is run to finally execute the task.  The map_task*
> methods are only implemented by the iblock and pscsi backends, and
> are used to prepare the bio or request.  Both of these actually may
> block (especially for pscsi when it hits the request limits) and thus
> block any progress in the front-end thread.  To me it would seem
> much more logical to remove map_task* and always do these allocations
> in do_task as well, just as we do everything there for the file backend.
---end quoted text---
--
To unsubscribe from this list: send the line "unsubscribe target-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux SCSI]     [Kernel Newbies]     [Linux SCSI Target Infrastructure]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Device Mapper]

  Powered by Linux