From: James Bottomley <James.Bottomley@SteelEye.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: NBD (vs. iSCSI vs. EATA vs...) (fwd)
Date: Sat, 28 May 2005 15:12:00 -0400 [thread overview]
Message-ID: <1117307520.5192.3.camel@mulgrave> (raw)
In-Reply-To: <Pine.LNX.4.60.0505281030510.3721@poirot.grange>
On Sat, 2005-05-28 at 10:32 +0200, Guennadi Liakhovetski wrote:
> So, just pass ioctl()'s directly and convert the rest (filesystem)
> block
> requests separately - wouldn't it be easier and avoid any
> modifications to
> other drivers?
Before you go any further, I suggest you think about what an ioctl is
and why we're going through a process of trying to get rid of them in
the kernel: They're structured streams of information, where the
structure is architecture and 64/32 bit dependent (look at all the
issues over compat ioctls). Inherently these things will be incredibly
nasty to convert to an architecture neutral network protocol, and you'll
have to provide a translator to and from every possible ioctl...they're
inherently unsuitable things for building a protocol on top of. On the
other hand, the current nbd protocol is block request based, which is
why I suggested looking at that instead.
James
next prev parent reply other threads:[~2005-05-28 19:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-28 8:32 NBD (vs. iSCSI vs. EATA vs...) (fwd) Guennadi Liakhovetski
2005-05-28 19:12 ` James Bottomley [this message]
2005-05-28 22:37 ` Guennadi Liakhovetski
2005-06-13 19:57 ` Guennadi Liakhovetski
2005-05-31 18:18 ` Bryan Henderson
-- strict thread matches above, loose matches on Subject: below --
2005-05-28 8:30 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=1117307520.5192.3.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=g.liakhovetski@gmx.de \
--cc=linux-scsi@vger.kernel.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 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.