Re: [RFC PATCH 4/6] isci: hardware / topology event handling

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

 



On Mon, Mar 28, 2011 at 6:11 PM, Dan Williams <dan.j.williams@xxxxxxxxx> wrote:
>> If the process context of delayed work items provices a significant
>> benefit to your execution model you can convert the timers to delayed
>> work items now, and remove the irqsafe locking.  Given that the
>> isci code still does some non-trivial work from it's interrupt
>> handlers and tasklets I'm not sure it's going to buy you much, though.
>
> The irqsafe locking is an external requirement imposed by libata,
> although we already drop the lock
>

<hit 'send' too early>

I was going to say we (and the other libsas drivers that call
task->done() or sas_task_abort() from lldd_execute_task_context)
already drop the lock in error conditions.  If that is a safe
operation then perhaps we could up level that lock drop or otherwise
move ata submission to an unlocked context to allow libsas drivers to
use sleeping locks and threaded interrupts.

--
Dan
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [SCSI Target Devel]     [Linux SCSI Target Infrastructure]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Samba]     [Device Mapper]
  Powered by Linux