From: Roland Dreier <rolandd@cisco.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Question about multiple modules talking to one adapter
Date: Mon, 08 Aug 2005 15:13:10 -0700 [thread overview]
Message-ID: <521x54yt55.fsf@cisco.com> (raw)
In-Reply-To: <42F7C853.90901@ammasso.com> (Timur Tabi's message of "Mon, 08 Aug 2005 16:02:11 -0500")
Timur> 1) Each driver registers its own ISR and has its own
Timur> mapping the adapter memory.
This is silly and leads to all sorts of horrible code. For example
you'll have to deal with the fact that only one driver can do
request_mem_region() on the PCI adapter, and no matter what you come
up with, it's going to be ugly.
Timur> 2) Create a single driver which does nothing but register
Timur> an ISR and map the kernel memory. Let's call this the CRM
Timur> driver. The other three drivers can then use XXXXXX to
Timur> provide callbacks for the ISR and obtain the address of the
Timur> mapping. The ISR will then query the adapter and call the
Timur> appropriate callback.
This is the best solution. I don't see any disadvantage to this.
- R.
prev parent reply other threads:[~2005-08-08 22:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-08 21:02 Question about multiple modules talking to one adapter Timur Tabi
2005-08-08 22:13 ` Roland Dreier [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=521x54yt55.fsf@cisco.com \
--to=rolandd@cisco.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