public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Yusupov <dmitry_yus@yahoo.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
	Sander <sander@humilis.net>,
	David Hollis <dhollis@davehollis.com>,
	Maciej Soltysiak <solt2@dns.toxicfilms.tv>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: Re[2]: ata over ethernet question
Date: Thu, 12 May 2005 12:05:47 -0700	[thread overview]
Message-ID: <1115924747.25161.150.camel@beastie> (raw)
In-Reply-To: <1115923927.5042.18.camel@mulgrave>

On Thu, 2005-05-12 at 14:52 -0400, James Bottomley wrote:
> On Wed, 2005-05-11 at 00:00 +0200, Guennadi Liakhovetski wrote:
> > A follow up question - I recently used nbd to access a CD-ROM. It worked 
> > nice, but, I had to read in 7 CDs, so, each time I had to replace a CD, I 
> > had to stop the client, the server, then replace the CD, re-start the 
> > server, re-start the client... I thought about extending NBD to (better) 
> > support removable media, but then you start thinking about all those 
> > features that your local block device has that don't get exported over 
> > NBD...
> 
> That's correct; NBD is basically just a remote data pipe type block
> device.  It doesn't understand arbitrary packet commands.
> 
> > Now, my understanding (sorry, without looking at any docs - yet) is, that 
> > iSCSI is (or at least should be) free from these limitations. So, does it 
> > make any sense at all extending NBD or just switch to iSCSI? Should NBD be 
> > just kept simple as it is or would it be completely superseeded by iSCSI, 
> > or is there still something that NBD does that iSCSI wouldn't (easily) do?
> 
> Caveat: I've done quite a bit of work on nbd, so I'm biased.  However,
> for what it does, nbd is extremely small, simple and efficient, so I
> think we'd want a hole in our head to replace it with something as
> complex and bloated as iSCSI---remember we'd need both a target and an
> initiator to do what nbd does today.

oh, please! don't compare nbd and iSCSI this way...
iSCSI is an emerging SAN technology, and the only technology to compare
is FC.

> However, there is room for improvement in nbd, notably the handling of
> packet commands, which looks to be eminently doable in the current
> infrastructure (this would basically make nbd a replicator for the linux
> block system, and would probably necessitate some client side changes to
> achieve).  If you have any thoughts in this direction, you could drop an
> email to the maintainer.
> 
> James
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


  reply	other threads:[~2005-05-12 19:05 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1416215015.20050504193114@dns.toxicfilms.tv>
     [not found] ` <1115236116.7761.19.camel@dhollis-lnx.sunera.com>
     [not found]   ` <1104082357.20050504231722@dns.toxicfilms.tv>
     [not found]     ` <1115305794.3071.5.camel@dhollis-lnx.sunera.com>
     [not found]       ` <20050507150538.GA800@favonius>
2005-05-10 22:00         ` Re[2]: ata over ethernet question Guennadi Liakhovetski
2005-05-10 23:14           ` Dmitry Yusupov
2005-05-11  5:42             ` [Iscsitarget-devel] " FUJITA Tomonori
2005-05-11  8:56           ` Vladislav Bolkhovitin
2005-05-11 21:26             ` several messages Guennadi Liakhovetski
2005-05-12  2:16               ` Ming Zhang
2005-05-12 18:32                 ` Dmitry Yusupov
2005-05-13  8:12                   ` Christoph Hellwig
2005-05-13 15:04                     ` Dmitry Yusupov
2005-05-13 15:07                       ` Christoph Hellwig
2005-05-13 15:38                         ` Dmitry Yusupov
2005-05-12 10:17               ` Vladislav Bolkhovitin
2005-05-12 19:42                 ` SCSI/ISCSI, hardware/software Bryan Henderson
2005-05-13  4:55                   ` Douglas Gilbert
2005-05-13 10:34                   ` Vladislav Bolkhovitin
2005-05-13 23:58                     ` Bryan Henderson
2005-05-12 18:52           ` Re[2]: ata over ethernet question James Bottomley
2005-05-12 19:05             ` Dmitry Yusupov [this message]
2005-05-12 19:15               ` James Bottomley
2005-05-12 19:44                 ` Dmitry Yusupov
2005-05-13  8:16                   ` Christoph Hellwig
2005-05-13 16:18                     ` Dmitry Yusupov
2005-05-13  8:14               ` Christoph Hellwig
2005-05-13 18:50             ` iSCSI vs. NBD (was Re: ata over ethernet question) Guennadi Liakhovetski
2005-05-13 20:21               ` James Bottomley
2005-05-13 22:49                 ` Guennadi Liakhovetski
2005-05-25 23:41             ` NBD (vs. iSCSI vs. EATA vs...) Guennadi Liakhovetski
2005-05-26  1:19               ` James Bottomley
2005-05-26 17:48                 ` Guennadi Liakhovetski

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=1115924747.25161.150.camel@beastie \
    --to=dmitry_yus@yahoo.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=dhollis@davehollis.com \
    --cc=g.liakhovetski@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=sander@humilis.net \
    --cc=solt2@dns.toxicfilms.tv \
    /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