linux-kernel - Re: [GIT PATCH] another tranche of SCSI updates for 2.6.26

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 28 Apr 2008 08:13:03 -0400
From:	James Bottomley <James.Bottomley@...senPartnership.com>
To:	Boaz Harrosh <bharrosh@...asas.com>
Cc:	Ingo Molnar <mingo@...e.hu>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-scsi <linux-scsi@...r.kernel.org>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PATCH] another tranche of SCSI updates for 2.6.26

On Mon, 2008-04-28 at 10:23 +0300, Boaz Harrosh wrote:
> If we are already on the subject. It looks like we always have at most 1 command in the 
> free list, so why the free list at all? or am I reading the code wrong?

Because list handlers are well understood mechanisms within the kernel.
Also because in low memory situations, one command per host is
sufficient to guarantee forward progress, but it's not going to be very
efficient.  Embedded and other low memory environments can increase the
size of the free list to improve their I/O path.

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/