From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jan-Benedict Glaw <jbglaw@lug-owl.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ATA over Ethernet driver for 2.6.9
Date: Mon, 06 Dec 2004 16:11:59 +0000 [thread overview]
Message-ID: <1102349517.14472.9.camel@localhost.localdomain> (raw)
In-Reply-To: <20041206162153.GH16958@lug-owl.de>
On Llu, 2004-12-06 at 16:21, Jan-Benedict Glaw wrote:
> > Like IP, AoE is an ethernet-level network protocol, registered with
> > the IEEE. Unlike IP, AoE is not routable.
>
> So AoE is out of scope for many uses...
Take a look at their product range and you'll see the intended uses. For
those I'm not sure routability actually matters too much. In addition
you'd want to tunnel it on a shared LAN to add crypto.
> > + n = lhget32(p+4);
> > + n <<= 32;
> > + return n |= lhget32(p);
> > +}
>
> There are function available for this, look at the endianess header
> files.
Ed:
cpu_to_le32() and friends to be more exact. These also have the
advantage they've been optimised and are asm on some systems.
> After all, especially keeping in mind that AoE isn't routeable, my
> thinking is that this had better written as a (E)NBD server process
> running in userspace. This way, you'd use the in-kernel NBD driver (or
> the ENBD which isn't in the kernel) and you the the routing stuff for
> free :)
Different problem space IMHO.
next prev parent reply other threads:[~2004-12-06 17:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-06 15:51 Ed L Cashin
2004-12-06 16:14 ` Arjan van de Ven
2004-12-10 16:19 ` Ed L Cashin
2004-12-06 16:21 ` Jan-Benedict Glaw
2004-12-06 16:11 ` Alan Cox [this message]
2004-12-06 17:06 ` Ed L Cashin
2004-12-07 13:00 ` Pavel Machek
2004-12-08 10:02 ` Helge Hafting
2004-12-08 15:44 ` Ed L Cashin
2004-12-08 15:53 ` Pavel Machek
2004-12-06 16:28 ` Adam Heath
2004-12-06 16:45 ` Ed L Cashin
2004-12-06 16:09 ` Alan Cox
2004-12-06 17:10 ` Adam Heath
2004-12-06 21:54 ` Greg KH
2004-12-09 15:48 ` Ed L Cashin
2004-12-09 16:37 ` Greg KH
2004-12-09 15:57 ` Ed L Cashin
2004-12-09 16:40 ` Greg KH
[not found] ` <87zn0n5vyd.fsf@coraid.com>
2004-12-09 16:42 ` Greg KH
2004-12-08 9:53 ` Pekka Enberg
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=1102349517.14472.9.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=jbglaw@lug-owl.de \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome