From: Oliver Xymoron <oxymoron@waste.org>
To: Andre Hedrick <andre@pyxtechnologies.com>
Cc: Jeff Garzik <jgarzik@pobox.com>, linux-kernel@vger.kernel.org
Subject: Re: More on Linux and iSCSI [info, not flame :)]
Date: Sat, 11 Jan 2003 02:14:40 -0600 [thread overview]
Message-ID: <20030111081440.GU14778@waste.org> (raw)
In-Reply-To: <Pine.LNX.4.10.10301102353000.31168-100000@master.linux-ide.org>
On Sat, Jan 11, 2003 at 12:01:05AM -0800, Andre Hedrick wrote:
>
> Oliver et al.
>
> http://downloadfinder.intel.com/scripts-df/filter_results.asp?strOSs=19%2C24%2C39&strTypes=DRV%2CFRM%2CUTL&ProductID=844&OSFullName=&submit=Go%21
> http://downloadfinder.intel.com/scripts-df/proc/T8Clearance.asp?url=/4461/eng/Zama2_1.0.8_Linux_42715.tgz&agr=N
>
> 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)
--
"Love the dolphins," she advised him. "Write by W.A.S.T.E.."
next prev parent reply other threads:[~2003-01-11 8:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-11 3:36 More on Linux and iSCSI [info, not flame :)] Jeff Garzik
2003-01-11 5:34 ` Oliver Xymoron
2003-01-11 7:10 ` Andre Hedrick
2003-01-11 8:01 ` Andre Hedrick
2003-01-11 8:14 ` Oliver Xymoron [this message]
2003-01-11 8:27 ` Andre Hedrick
2003-01-11 8:34 ` Jeff Garzik
2003-01-11 8:04 ` Oliver Xymoron
2003-01-11 8:19 ` Andre Hedrick
-- strict thread matches above, loose matches on Subject: below --
2003-01-11 16:15 Brian Jackson
2003-01-11 21:20 ` Andre Hedrick
[not found] <mailman.1042256580.21471.linux-kernel2news@redhat.com>
2003-01-12 2:59 ` Pete Zaitcev
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=20030111081440.GU14778@waste.org \
--to=oxymoron@waste.org \
--cc=andre@pyxtechnologies.com \
--cc=jgarzik@pobox.com \
--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