public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vladislav Bolkhovitin <vst@vlnb.net>
To: Matthew Wilcox <willy@debian.org>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [ANNOUNCE] Generic SCSI Target Middle Level for Linux (SCST) with target drivers
Date: Thu, 17 Jun 2004 16:15:17 +0400	[thread overview]
Message-ID: <40D18B55.1020704@vlnb.net> (raw)
In-Reply-To: <20040616182131.GV20511@parcelfarce.linux.theplanet.co.uk>

Matthew Wilcox wrote:
> On Wed, Jun 16, 2004 at 08:31:22PM +0400, Vladislav Bolkhovitin wrote:
> 
>>Any comments would be appreciated.
> 
> 
> The first obvious question is: Why does this need to be done in kernel
> space?  My impression was that an iSCSI target would best be done in
> userspace.
> 
The answer is quite obvious as well. There is not only iSCSI target 
(i.e. software one) in the world. For hardware targets if you were 
switch on each command (IRQ) to user space and back, it would be huge 
performance penalty, especially for commands that request small data 
transfers. Take a look on the Qlogic target: all job is done in the 
tasklet, without ever context switch. The same is for upcoming iSCSI 
hardware, like Qlogic QLA4010, which also supports target mode.

BTW, the processing is simple enough, the main SCST module is only about 
  60Kb long. The main point is that this processing must be done in 
_each_ SCSI target driver. So, consider SCSI target mid-level like a 
library (framework) for such drivers, exectly as the regular SCSI 
mid-level for regular SCSI drivers.

Thanks,
Vlad

  reply	other threads:[~2004-06-17 12:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-16 16:31 [ANNOUNCE] Generic SCSI Target Middle Level for Linux (SCST) with target drivers Vladislav Bolkhovitin
2004-06-16 18:21 ` Matthew Wilcox
2004-06-17 12:15   ` Vladislav Bolkhovitin [this message]
2004-06-17 12:22 ` Christoph Hellwig
2004-06-17 13:22   ` Vladislav Bolkhovitin

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=40D18B55.1020704@vlnb.net \
    --to=vst@vlnb.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=willy@debian.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