David, This looks like a good suggestion to me. I will update the manpage content like you suggest, and get the case materials updated.
On 10/08/08 00:47, David Kahn wrote: > You might want to replace DESCRIPTION section > with something like this: (basically replacing > your 2nd paragraph with 2 new paragraphs.) > > The ddi_intr_set_nreq() function changes the number of > interrupts requested by a device driver instance. > > The nreq parameter is the total number of interrupt > resources that this instance of the device driver > would like to have available. nreq includes any > interrupt resources already allocated by the driver. > > For example, the driver instance is currently using > two MSI-X vectors, and it wants access to four additional > unique MSI-X vectors. In that case it should call > this function with nreq parameter set to the value six. > > The nreq parameter can be any value between 1 and the maximum > number of interrupts supported by the device hardware, as reported > by a call to the ddi_intr_get_nintrs(9F) function. The driver will > receive a callback notifying it in cases when it must release any > previously allocated interrupts, or when it is allowed to allocate > more interrupts as a result of its new nreq parameter. > > The ddi_intr_set_nreq() function is not supported unless a driver > is already consuming interrupts, and if it has a registered callback > handler that can process actions related to changes in interrupt > availability. See ddi_cb_register(9F) for an explanation on how > to enable this functionality. -- Scott
