Hello,

On Wed, Oct 02, 2013 at 12:48:23PM +0200, Alexander Gordeev wrote:
> +static int foo_driver_enable_msi(struct foo_adapter *adapter, int nvec)
> +{
> +     rc = pci_get_msi_cap(adapter->pdev);
> +     if (rc < 0)
> +             return rc;
> +
> +     nvec = min(nvec, rc);
> +     if (nvec < FOO_DRIVER_MINIMUM_NVEC) {
> +             return -ENOSPC;
> +
> +     rc = pci_enable_msi_block(adapter->pdev, nvec);
> +     return rc;
> +}

If there are many which duplicate the above pattern, it'd probably be
worthwhile to provide a helper?  It's usually a good idea to reduce
the amount of boilerplate code in drivers.

>  static int foo_driver_enable_msix(struct foo_adapter *adapter, int nvec)
>  {
> +     rc = pci_msix_table_size(adapter->pdev);
> +     if (rc < 0)
> +             return rc;
> +
> +     nvec = min(nvec, rc);
> +     if (nvec < FOO_DRIVER_MINIMUM_NVEC) {
> +             return -ENOSPC;
> +
> +     for (i = 0; i < nvec; i++)
> +             adapter->msix_entries[i].entry = i;
> +
> +     rc = pci_enable_msix(adapter->pdev, adapter->msix_entries, nvec);
> +     return rc;
>  }

Ditto.

> @@ -975,7 +951,7 @@ int pci_enable_msix(struct pci_dev *dev, struct 
> msix_entry *entries, int nvec)
>       if (nr_entries < 0)
>               return nr_entries;
>       if (nvec > nr_entries)
> -             return nr_entries;
> +             return -EINVAL;
>  
>       /* Check for any invalid entries */
>       for (i = 0; i < nvec; i++) {

If we do things this way, it breaks all drivers using this interface
until they're converted, right?  Also, it probably isn't the best idea
to flip the behavior like this as this can go completely unnoticed (no
compiler warning or anything, the same function just behaves
differently).  Maybe it'd be a better idea to introduce a simpler
interface that most can be converted to?

Thanks.

-- 
tejun

------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk
_______________________________________________
E1000-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel&#174; Ethernet, visit 
http://communities.intel.com/community/wired

Reply via email to