From: Dmitry Yusupov <dmitry_yus@yahoo.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
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: Fri, 13 May 2005 09:18:10 -0700 [thread overview]
Message-ID: <1116001090.25161.211.camel@beastie> (raw)
In-Reply-To: <20050513081617.GC32546@infradead.org>
On Fri, 2005-05-13 at 09:16 +0100, Christoph Hellwig wrote:
> On Thu, May 12, 2005 at 12:44:18PM -0700, Dmitry Yusupov wrote:
> > i'm just reacting on "bloated" wording. It really depends on
> > implementation and design. If you were talking about amount of code in
> > the kernel, than take a look on open-iscsi(just one file iscsi_tcp.c)
> > and IET where we doing a lot of management stuff in user-space. It is
> > not that much code in the kernel, really, but it is doing x10 times more
> > useful things comparing to nbd and yet compliant with RFC.
>
> Keeping code out of the kernel is really nice, but that doesn't meant it
> isn't bloat - the bloat is just in userland.
well, "userland" == "bloatland" anyways... Multiple discovery methods,
configuration database, bunch of security protocols, etc... all this of
course will make it "slightly" :) bigger than nbd. But again, for a good
reason and better usefulness.
Dmitry
next prev parent reply other threads:[~2005-05-13 16:18 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
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 [this message]
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=1116001090.25161.211.camel@beastie \
--to=dmitry_yus@yahoo.com \
--cc=James.Bottomley@SteelEye.com \
--cc=dhollis@davehollis.com \
--cc=g.liakhovetski@gmx.de \
--cc=hch@infradead.org \
--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