From: Christoph Hellwig <hch@lst.de>
To: Himanshu Madhani <himanshu.madhani@cavium.com>
Cc: bhelgaas@google.com, linux-pci@vger.kernel.org, hch@lst.de
Subject: Re: [PATCH] PCI/MSI: Only disable affinity settings if pre and post vector count is equal to max_vecs and not min_vecs
Date: Wed, 1 Mar 2017 16:20:56 +0100 [thread overview]
Message-ID: <20170301152056.GA12708@lst.de> (raw)
In-Reply-To: <1487883699-3528-1-git-send-email-himanshu.madhani@cavium.com>
> @@ -1206,16 +1228,6 @@ int pci_alloc_irq_vectors_affinity(struct pci_dev *dev, unsigned int min_vecs,
> if (flags & PCI_IRQ_AFFINITY) {
> if (!affd)
> affd = &msi_default_affd;
> -
> - if (affd->pre_vectors + affd->post_vectors > min_vecs)
> - return -EINVAL;
Actually I think we can leave this check here.
> -
> - /*
> - * If there aren't any vectors left after applying the pre/post
> - * vectors don't bother with assigning affinity.
> - */
> - if (affd->pre_vectors + affd->post_vectors == min_vecs)
> - affd = NULL;
And only move this one down into the allocator helpers.
next prev parent reply other threads:[~2017-03-01 15:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-23 21:01 [PATCH] PCI/MSI: Only disable affinity settings if pre and post vector count is equal to max_vecs and not min_vecs Himanshu Madhani
2017-02-28 22:05 ` Madhani, Himanshu
2017-03-01 15:20 ` Christoph Hellwig [this message]
2017-03-01 23:27 ` Madhani, Himanshu
-- strict thread matches above, loose matches on Subject: below --
2017-04-18 1:19 Himanshu Madhani
2017-05-17 22:28 ` Bjorn Helgaas
2017-05-18 16:02 ` Himanshu Madhani
2017-04-17 21:26 Himanshu Madhani
2017-04-18 0:01 ` kbuild test robot
2017-03-01 23:31 Himanshu Madhani
2017-03-01 23:49 ` Christoph Hellwig
2017-03-07 19:00 ` Madhani, Himanshu
2017-03-07 21:08 ` Bjorn Helgaas
2017-03-23 17:29 ` Bjorn Helgaas
2017-03-30 23:21 ` Bjorn Helgaas
2017-03-30 23:25 ` Himanshu Madhani
2017-03-31 0:09 ` Bjorn Helgaas
2017-02-23 6:12 Himanshu Madhani
2017-02-23 10:30 ` Christoph Hellwig
2017-02-21 17:34 Himanshu Madhani
2017-02-23 0:27 ` Martin K. Petersen
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=20170301152056.GA12708@lst.de \
--to=hch@lst.de \
--cc=bhelgaas@google.com \
--cc=himanshu.madhani@cavium.com \
--cc=linux-pci@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.