From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Boaz Harrosh <bharrosh@panasas.com>
Cc: Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PATCH] another tranche of SCSI updates for 2.6.26
Date: Mon, 28 Apr 2008 08:13:03 -0400 [thread overview]
Message-ID: <1209384784.3367.1.camel@localhost.localdomain> (raw)
In-Reply-To: <48157B6A.60307@panasas.com>
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
next prev parent reply other threads:[~2008-04-28 12:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-27 18:14 [GIT PATCH] another tranche of SCSI updates for 2.6.26 James Bottomley
2008-04-28 1:34 ` Ingo Molnar
2008-04-28 1:45 ` Ingo Molnar
2008-04-28 2:51 ` James Bottomley
2008-04-28 7:15 ` Kamalesh Babulal
2008-04-28 7:23 ` Boaz Harrosh
2008-04-28 8:34 ` FUJITA Tomonori
2008-04-28 8:40 ` Boaz Harrosh
2008-04-28 12:13 ` James Bottomley [this message]
2008-04-28 12:24 ` Boaz Harrosh
2008-04-28 16:05 ` Linus Torvalds
2008-04-28 18:25 ` James Bottomley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1209384784.3367.1.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=bharrosh@panasas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox