mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Nguyen, Tom L" <tom.l.nguyen@intel.com>
To: Zwane Mwaikambo <zwane@linuxpower.ca>,
	"Nguyen, Tom L" <tom.l.nguyen@intel.com>
Cc: linux-kernel@vger.kernel.org, "Saxena,
	Sunil" <sunil.saxena@intel.com>,
	"Mallick, Asit K" <asit.k.mallick@intel.com>,
	"Nakajima, Jun" <jun.nakajima@intel.com>,
	"Carbonari, Steven" <steven.carbonari@intel.com>
Subject: RE: RFC Proposal to enable MSI support in Linux kernel
Date: Mon, 19 May 2003 14:46:59 -0700	[thread overview]
Message-ID: <C7AB9DA4D0B1F344BF2489FA165E5024136211@orsmsx404.jf.intel.com> (raw)

By default, one single message (MSI) is assigned to any MSI/MSI-X capable
device regardless of whether the device is capable of handling a single or
multiple messages. Due the current implementation of assigning vector in
Linux, the PCI subsystem assigns one single message to the device, which
implements the MSI capability structure. However, for the device
implementing the MSI-X capability structure, the device driver can request
for additional messages by calling the API: 

int msi_alloc_vectors(void* dev_id, int *vector, int nvec) 

Thanks,
Tom

-----Original Message-----
From: Zwane Mwaikambo [mailto:zwane@linuxpower.ca]
Sent: Wednesday, May 14, 2003 12:06 PM
To: Nguyen, Tom L
Cc: linux-kernel@vger.kernel.org; Saxena, Sunil; Mallick, Asit K;
Nakajima, Jun; Carbonari, Steven
Subject: Re: RFC Proposal to enable MSI support in Linux kernel


Do you require mulitple vectors per device? Can't you assign one and then 
multiplex in your handler? Or is there some mode of operation i've not 
taken into account?

	Zwane
-- 
function.linuxpower.ca

             reply	other threads:[~2003-05-19 21:34 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-19 21:46 Nguyen, Tom L [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-30 14:56 Nicolas Mailhot
2003-05-31  2:29 ` William Lee Irwin III
2003-05-31  7:13 ` Zwane Mwaikambo
2003-05-31  7:28   ` Zwane Mwaikambo
2003-05-30  2:14 Nakajima, Jun
2003-05-29 18:12 Nguyen, Tom L
2003-05-29 21:55 ` Zwane Mwaikambo
2003-05-20 19:03 Nguyen, Tom L
2003-05-19 21:22 Nguyen, Tom L
2003-05-20 10:36 ` Martin Schlemmer
2003-05-20 18:49 ` Zwane Mwaikambo
2003-05-28 22:22   ` Zwane Mwaikambo
2003-05-28 23:01     ` Jeff Garzik
2003-05-28 23:06       ` Zwane Mwaikambo
2003-05-28 23:45         ` Jeff Garzik
2003-05-28 23:50           ` Zwane Mwaikambo
2003-05-14 20:43 Nakajima, Jun
2003-05-14 19:57 Nakajima, Jun
2003-05-14 19:54 ` Zwane Mwaikambo
2003-05-14 18:51 Nguyen, Tom L
2003-05-14 15:41 Nguyen, Tom L
2003-05-14 15:22 Nguyen, Tom L
2003-05-14 17:44 ` Greg KH
2003-05-14 18:58 ` Zwane Mwaikambo
2003-05-14 19:06 ` Zwane Mwaikambo

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=C7AB9DA4D0B1F344BF2489FA165E5024136211@orsmsx404.jf.intel.com \
    --to=tom.l.nguyen@intel.com \
    --cc=asit.k.mallick@intel.com \
    --cc=jun.nakajima@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=steven.carbonari@intel.com \
    --cc=sunil.saxena@intel.com \
    --cc=zwane@linuxpower.ca \
    /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®