lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 12 Jun 2008 09:18:27 -0500 From: James Bottomley <James.Bottomley@...senPartnership.com> To: Tejun Heo <htejun@...il.com> Cc: Elias Oltmanns <eo@...ensachen.de>, Alan Cox <alan@...rguk.ukuu.org.uk>, Jens Axboe <jens.axboe@...cle.com>, linux-ide@...r.kernel.org, linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: Prevent busy looping On Thu, 2008-06-12 at 22:43 +0900, Tejun Heo wrote: > It busy loops but it won't lock up as command completion is the loop > breaker and command completion comes via IRQ and the busy looping > doesn't happen solely in the IRQ context. Still needs to be fixed tho. > Anyways, this is only limited to ->qc_defer for simplex and the reason > why there's busy loop is because we're trying to schedule two > independent hosts and SCSI midlayer (of course) doesn't have the notion > of cross host deferring. It would if the host were at the right level. We have the whole concept of starved list processing for blocked queues that was supposed to be designed for this (well, for a corresponding SCSI situation). James -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists