[lkml]   [2003]   [Jan]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: More on Linux and iSCSI [info, not flame :)]
On Sat, 11 Jan 2003, Oliver Xymoron wrote:

> On Sat, Jan 11, 2003 at 12:01:05AM -0800, Andre Hedrick wrote:
> >
> > Oliver et al.
> >
> >
> >
> >
> > This self extracting file contains the firmware and software for the
> > upgrading to 0.8 iSCSI specification.
> >
> > I own this product, and have to install RH 7.1 w/ 2.4.2 kernels to use and
> > test with it.
> Which means, like every other binary module, it's pretty much
> worthless. Though I'm guessing that's not the point you're trying to
> make.
> (For the record, there's not much value in iSCSI NICs, or TCP offload
> in general at the moment, except to avoid potential deadlock issues
> with trying to do network buffer allocation down in the block layer)

Well if you restrict the transport of the protocol to on Network Fabric,
you have a small point. However moving off the Network stack to MPI
transports is real power of the protocol. Classic example is the IBM
iSCSI Shark running Linux, and where are the their drivers? Recall they
are the "Peace, Love, Linux" company. However, transports like Myrinet,
SCI, Quads, etc ... are the place to be for local SAN banks.

When NIC's or TOEs support native ipsec, have a CRC32C offload core, and a
few other issues them they will have value.

All the ones I have tested or seen, offload the network stack, do not
support ipsec or handle the CRC32C offload.

Only the MPI fabric cards provide the tools desired.


Andre Hedrick, CTO & Founder
iSCSI Software Solutions Provider

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:32    [W:0.048 / U:0.392 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site