From: Roland Dreier <rdreier@cisco.com>
To: "Bryan O'Sullivan" <bos@pathscale.com>
Cc: rolandd@cisco.com, gregkh@suse.de, akpm@osdl.org,
davem@davemloft.net, linux-kernel@vger.kernel.org,
openib-general@openib.org
Subject: Re: [PATCH 0 of 20] [RFC] ipath driver, latest changes
Date: Thu, 09 Mar 2006 09:21:44 -0800 [thread overview]
Message-ID: <adaacbzlejb.fsf@cisco.com> (raw)
In-Reply-To: <patchbomb.1141922813@localhost.localdomain> (Bryan O'Sullivan's message of "Thu, 9 Mar 2006 08:46:53 -0800")
Bryan> - We've introduced support for our PCI Express chips, so
Bryan> the driver is no longer HyperTransport-specific. It's
Bryan> still a 64-bit driver, because 32-bit platforms don't
Bryan> implement readq or writeq. (It does compile cleanly on
Bryan> i386, but of course fails to link.)
That seems pretty bad. Do you really need to read 64 bits in one bus
transaction, or could you just use two readl()s to get the same effect?
Bryan> - Our hardware only supports MSI interrupts. I don't
Bryan> know how to program it to interrupt us if CONFIG_PCI_MSI is
Bryan> not set. Right now, we have a timer-based hack in place to
Bryan> emulate interrupts.
Is this true for PCI Express too?
Bryan> - There's clearly something wrong with the way we're
Bryan> pinning some pages into memory, but I don't actually know
Bryan> what it is. I'm pretty sure our use of get_user_pages is
Bryan> correct, so I suspect it must be the code that's doing
Bryan> SetPageReserved (see ipath_driver.c and ipath_file_ops.c).
Bryan> I've spent some time trying to figure out what the
Bryan> problem is, but am stumped. If someone knows what we
Bryan> should be doing instead, I'd be delighted to hear from
Bryan> them.
What are the symptoms of the problem?
- R.
parent reply other threads:[~2006-03-09 17:21 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <patchbomb.1141922813@localhost.localdomain>]
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=adaacbzlejb.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=akpm@osdl.org \
--cc=bos@pathscale.com \
--cc=davem@davemloft.net \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=openib-general@openib.org \
--cc=rolandd@cisco.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