From: Boaz Harrosh <bharrosh@panasas.com>
To: James Bottomley <James.Bottomley@HansenPartnership.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 15:24:12 +0300 [thread overview]
Message-ID: <4815C1EC.7090109@panasas.com> (raw)
In-Reply-To: <1209384784.3367.1.camel@localhost.localdomain>
On Mon, Apr 28 2008 at 15:13 +0300, James Bottomley <James.Bottomley@HansenPartnership.com> wrote:
> 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.
This is not an excuse ;-). So is a simple pointer.
> 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.
>
Ok that is what I thought, but inspecting the code, I can't find it. Is there
a config option or an external mechanism that let you do that? If not, is/was
there a ready made external patch that will enable such facility in someway?
Should there be one?
> James
>
Boaz
next prev parent reply other threads:[~2008-04-28 14:48 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
2008-04-28 12:24 ` Boaz Harrosh [this message]
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=4815C1EC.7090109@panasas.com \
--to=bharrosh@panasas.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.org \
--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