mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Vasquez <andrew.vasquez@qlogic.com>
To: Andrew Patterson <andrew.patterson@hp.com>
Cc: Ulrich Windl <ulrich.windl@rz.uni-regensburg.de>,
	linux-kernel@vger.kernel.org
Subject: Re: Q: PCI-X @ 266MHz on HP rx6600 (Qlogic 4Gb FC HBA)
Date: Tue, 31 Jul 2007 09:50:03 -0700	[thread overview]
Message-ID: <20070731165003.GF8842@plap.qlogic.org> (raw)
In-Reply-To: <20070727161120.GB20540@plap.qlogic.org>

> On Fri, 27 Jul 2007, Andrew Patterson wrote:
> 
> > On Thu, 2007-07-26 at 23:23 -0700, Andrew Vasquez wrote:
> >
> > > The 33/66/100/133 values refer to the bus-clock speed at which the
> > > card is operating.  As is seen here (although a bit truncated --
> > > separate issue, I'll try to see if I can reproduce this on one of my
> > > HPQ rigs), the card is inserted into a PCI-X Mode-2 capable 133MHz
> > > (bus clock) slot.  When operating under this mode, each data-phase
> > > between two devices is divided into 2 sub-phases, effectively doubling
> > > the transfer-data-rate to 266Mhz.
> > 
> > I guess the proper terminology would be 266 MT/s (Mega
> > Transfers/second). Looking through the PSI_SIG PCI-X 2.0 marketing
> > blurbs, they use MHz a lot when referring to MT/S. So I would still
> > consider this to be a minor bug.  The user wants to know the transfer
> > rate, not the actual frequency of the bus.  Maybe just print out the
> > mode used instead, e.g., "PCI-X 266"?

Given PCI-X Mode-2 can run at different bus-clock speeds, how about
this as an alternative?

	PCI-X 266 (133Mhz)

it's a bit more descriptive than

	PCI-X Mode 2 (133Mhz)

then again, I don't want to beat this thing to death...

---

diff --git a/drivers/scsi/qla2xxx/qla_os.c b/drivers/scsi/qla2xxx/qla_os.c
index c488996..26f7e54 100644
--- a/drivers/scsi/qla2xxx/qla_os.c
+++ b/drivers/scsi/qla2xxx/qla_os.c
@@ -283,9 +283,9 @@ qla24xx_pci_info_str(struct scsi_qla_host *ha, char *str)
 	} else {
 		strcat(str, "-X ");
 		if (pci_bus & BIT_2)
-			strcat(str, "Mode 2");
+			strcat(str, "266");
 		else
-			strcat(str, "Mode 1");
+			strcat(str, "133");
 		strcat(str, " (");
 		strcat(str, pci_bus_modes[pci_bus & ~BIT_2]);
 	}

  reply	other threads:[~2007-07-31 16:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-26 13:36 Ulrich Windl
2007-07-26 22:03 ` Andrew Patterson
2007-07-27  6:23   ` Andrew Vasquez
2007-07-27 15:46     ` Andrew Patterson
2007-07-27 16:11       ` Andrew Vasquez
2007-07-31 16:50         ` Andrew Vasquez [this message]
2007-08-01  6:13           ` Ulrich Windl
2007-07-30  6:40       ` Ulrich Windl
2007-08-01 22:13     ` [PATCH] qla2xxx: allocate enough space for the full PCI descriptor Andrew Vasquez

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=20070731165003.GF8842@plap.qlogic.org \
    --to=andrew.vasquez@qlogic.com \
    --cc=andrew.patterson@hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ulrich.windl@rz.uni-regensburg.de \
    /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

all inboxes | Powered by JetHome®