From: Michael Tokarev <mjt@tls.msk.ru>
To: Andrew Vasquez <andrew.vasquez@qlogic.com>
Cc: netdev@vger.kernel.org, Ron Mercer <ron.mercer@qlogic.com>
Subject: Re: [PATCH] Qlogic qla3xxx driver v2.02.00-k36 for upstream inclusion.
Date: Thu, 20 Jul 2006 18:59:28 +0400 [thread overview]
Message-ID: <44BF9A50.60207@tls.msk.ru> (raw)
In-Reply-To: <20060720145025.GA305@andrew-vasquezs-powerbook-g4-15.local>
Andrew Vasquez wrote:
> On Thu, 20 Jul 2006, Ron Mercer wrote:
>
>> qla3xxx driver does not support ISP4010.
>
> Exactly... The qla3xxx driver supports the NIC function only.
...which is provided by ISP4010 card, as appears on PCI bus:
04:04.0 Ethernet controller: QLogic Corp. QLA3010 Network Adapter (rev 05)
04:04.1 Network controller: QLogic Corp. QLA4010 iSCSI TOE Adapter (rev 05)
(the first (sub)device). So it *looks* like the card has *both*
a NIC and iSCSI TOE adapter, and the NIC part is pretty much similar
to what qla3xxx driver expects... That's why my curiosity. ;)
(not that it matters much, just.. curious, really.
Well. Not exactly. It'd be nice to compare a NIC w/o Jumbo
frames support (which we have on all machines connected to
the iSCSI segment), with something more.. advanced. So I
wondered if I can utilize the NIC part of the ISP4010 for
the test. iSCSI part of the card works significantly slower
than open-iscsi stack on non-jumbo-frames-aware Tigon GigE NIC).
[]
> You'll need to use the qla4xxx driver to drive the iSCSI function.
Yeah, I know. I posted some results to open-iscsi@ list about a week
ago. It basically works (the new one, with open-iscsi infrastructure),
but is slooow... ;)
Thanks.
/mjt
next prev parent reply other threads:[~2006-07-20 14:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-20 14:32 [PATCH] Qlogic qla3xxx driver v2.02.00-k36 for upstream inclusion Ron Mercer
2006-07-20 14:50 ` Andrew Vasquez
2006-07-20 14:59 ` Michael Tokarev [this message]
[not found] <1090CAF73D6FFE4EA45395454C82937B05214A4B@AVEXCH1.qlogic.org>
[not found] ` <0BB3E5E7462EEA4295BC02D49691DC0705BC91@AVEXCH1.qlogic.org>
2006-07-19 20:41 ` Jeff Garzik
2006-07-20 9:12 ` Michael Tokarev
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=44BF9A50.60207@tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=andrew.vasquez@qlogic.com \
--cc=netdev@vger.kernel.org \
--cc=ron.mercer@qlogic.com \
/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;
as well as URLs for NNTP newsgroup(s).