From: Vladislav Bolkhovitin <vst@vlnb.net>
To: Mike Christie <michaelc@cs.wisc.edu>
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
johan@capvert.se, iscsitarget-devel@lists.sourceforge.net,
mingz@ele.uri.edu, stgt <stgt-devel@lists.berlios.de>,
Robert Whitehead <WRWHITEHEAD@novell.com>,
scst-devel@lists.sourceforge.net, linux-scsi@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>
Subject: Re: stgt a new version of iscsi target?
Date: Wed, 14 Dec 2005 18:06:40 +0300 [thread overview]
Message-ID: <43A03500.1040500@vlnb.net> (raw)
In-Reply-To: <439B1965.90603@cs.wisc.edu>
Mike Christie wrote:
>>
>> Are you sure that there are no now or will be available in the nearest
>> feature such (eg iSCSI) SCSI arrays with response time/latency so
>> small that having 5 (five) context switches or more per command, some
>> of which include map/unmap operations, will not increase the latency
>> too much? I mean, eg NFS server, which originally was user space
>> daemon and many people didn't want it in the kernel. Eventually, it's
>> in. I don't see any fundamental difference between NFS server and SCSI
>> target server,
>
>
> Isn't the reason a NFS server is still in the kernel is becuase some of
> the locking difficulties?
Might be. But from what I remember, the major reason was the
performance. After googling a bit I found many acknowledgments of that.
Vlad
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
next prev parent reply other threads:[~2005-12-14 15:06 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <OF6932015B.01CF53D9-ONC12570D0.00462028@capvert.ins>
[not found] ` <43972C2D.9060500@cs.wisc.edu>
2005-12-08 18:46 ` Ang: Re: [Stgt-devel] Re: stgt a new version of iscsi target? Vladislav Bolkhovitin
2005-12-08 18:54 ` Ang: Re: [Stgt-devel] Re: [Iscsitarget-devel] " Mike Christie
2005-12-09 15:30 ` Ang: Re: [Stgt-devel] " Vladislav Bolkhovitin
2005-12-09 22:31 ` Ang: Re: [Stgt-devel] Re: [Iscsitarget-devel] " Mike Christie
2005-12-08 19:10 ` Mike Christie
2005-12-08 19:48 ` James Bottomley
2005-12-08 20:09 ` Mike Christie
2005-12-08 21:35 ` Dave C Boutcher
2005-12-08 21:56 ` Mike Christie
2005-12-09 15:29 ` Vladislav Bolkhovitin
2005-12-09 22:31 ` Mike Christie
2005-12-10 15:31 ` Vladislav Bolkhovitin
2005-12-10 18:19 ` Mike Christie
2005-12-10 8:46 ` FUJITA Tomonori
2005-12-09 15:30 ` Vladislav Bolkhovitin
2005-12-09 15:29 ` Vladislav Bolkhovitin
2005-12-21 23:53 ` FUJITA Tomonori
2005-12-22 10:38 ` Vladislav Bolkhovitin
2005-12-26 23:53 ` Ang: " FUJITA Tomonori
2005-12-28 16:32 ` James Bottomley
2005-12-31 3:27 ` Mike Christie
2005-12-31 15:33 ` James Bottomley
2005-12-09 15:28 ` Vladislav Bolkhovitin
2005-12-09 22:23 ` Mike Christie
2005-12-10 1:15 ` Ang: Re: [Stgt-devel] " Mike Christie
2005-12-10 15:30 ` Ang: Re: [Stgt-devel] Re: [Iscsitarget-devel] " Vladislav Bolkhovitin
2005-12-10 18:22 ` Mike Christie
2005-12-10 8:46 ` FUJITA Tomonori
2005-12-10 15:32 ` Ang: Re: [Stgt-devel] " Vladislav Bolkhovitin
2005-12-10 15:54 ` Ang: Re: [Stgt-devel] Re: [Iscsitarget-devel] " FUJITA Tomonori
2005-12-14 15:17 ` [Scst-devel] " Vladislav Bolkhovitin
2005-12-10 18:09 ` Mike Christie
2005-12-14 15:09 ` Ang: Re: [Stgt-devel] " Vladislav Bolkhovitin
2005-12-08 19:47 ` Ang: Re: [Stgt-devel] Re: [Iscsitarget-devel] " James Bottomley
2005-12-09 3:57 ` Mike Christie
2005-12-09 15:00 ` Ang: Re: [Stgt-devel] " Ming Zhang
2005-12-09 15:29 ` [Scst-devel] Re: Ang: Re: [Stgt-devel] Re: [Iscsitarget-devel] " Vladislav Bolkhovitin
2005-12-09 15:48 ` James Bottomley
2005-12-10 15:32 ` Vladislav Bolkhovitin
2005-12-10 18:07 ` Mike Christie
2005-12-14 15:06 ` Vladislav Bolkhovitin [this message]
2005-12-14 19:55 ` Mike Christie
2005-12-15 18:53 ` 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=43A03500.1040500@vlnb.net \
--to=vst@vlnb.net \
--cc=James.Bottomley@SteelEye.com \
--cc=WRWHITEHEAD@novell.com \
--cc=hch@infradead.org \
--cc=iscsitarget-devel@lists.sourceforge.net \
--cc=johan@capvert.se \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
--cc=mingz@ele.uri.edu \
--cc=scst-devel@lists.sourceforge.net \
--cc=stgt-devel@lists.berlios.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.