From: Jes Sorensen <jes@wildopensource.com>
To: James Bottomley <James.Bottomley@steeleye.com>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
jeremy@sgi.com
Subject: Re: [patch] qla1280 update for 2.6.1-mm4
Date: 19 Jan 2004 16:18:42 -0500 [thread overview]
Message-ID: <yq01xpvocwd.fsf@wildopensource.com> (raw)
In-Reply-To: <1074531798.1894.17.camel@mulgrave>
>>>>> "James" == James Bottomley <James.Bottomley@steeleye.com> writes:
James> Something to think about (I'm not asking you to change it) is
James> whether you really want to use 64 bit descriptors on all 64 bit
James> machines. The way the qla1280 single issue queue is organised
James> it looks like we eat up slots (and, worse, overflow slots)
James> quite a bit faster in 64 bit addressing mode. Therefore, it
James> seems like the driver would operate more efficiently in 32 bit
James> mode, so it might be worth a runtime check even on 64 bit
James> machines to see whether the addressing mode is really necessary
James> (i.e. no physical memory > 4GB for instance).
Hi James,
Certainly a valid concern, however it would probably more likely be
based on available IOMMU slots, ie. with loads of 1280's in a box or
other devices causing a lot of packets going through the system, it
will probably be preferred to use 64 bit addressing where on smaller
boxes I think you suggestion will be a pretty decent win. The driver
also needs to handle it's busy situation a lot better, the current
busy wait loop in qla1280_req_pkt is ehm ... no comment. Even if we
decide to do dynamic switching between 64 and 32 bit mappings then I
think it will be desirable to merge the two queuecommand versions for
cache locality.
Cheers,
Jes
prev parent reply other threads:[~2004-01-19 21:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-19 12:08 [patch] qla1280 update for 2.6.1-mm4 Jes Sorensen
2004-01-19 12:14 ` Christoph Hellwig
2004-01-19 12:27 ` Jes Sorensen
2004-01-19 17:03 ` James Bottomley
2004-01-19 21:18 ` Jes Sorensen [this message]
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=yq01xpvocwd.fsf@wildopensource.com \
--to=jes@wildopensource.com \
--cc=James.Bottomley@steeleye.com \
--cc=akpm@osdl.org \
--cc=jeremy@sgi.com \
--cc=linux-scsi@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