All of lore.kernel.org
 help / color / mirror / Atom feed
From: Prarit Bhargava <prarit@redhat.com>
To: Tadeusz Struk <tadeusz.struk@intel.com>
Cc: herbert@gondor.apana.org.au, bruce.w.allan@intel.com,
	qat-linux@intel.com, john.griffin@intel.com,
	linux-crypto@vger.kernel.org, naleksan@redhat.com,
	davem@davemloft.net
Subject: Re: [PATCH 2/2] crypto: qat - Enforce valid numa configuration.
Date: Fri, 10 Oct 2014 07:23:53 -0400	[thread overview]
Message-ID: <5437C1C9.7050505@redhat.com> (raw)
In-Reply-To: <5437165E.6030008@intel.com>



On 10/09/2014 07:12 PM, Tadeusz Struk wrote:
> On 10/09/2014 02:42 PM, Prarit Bhargava wrote:
>>>> I don't think cpu hotplug matters here. This is one (probe) time
>>>> determination if the configuration is optimal or not and if it makes
>>>> sense to use this accelerator or not.
>> It absolutely matters.  num_online_cpus() *changes* depending on the # of cpus.
> 
> Sure, but I still think that we are safe here.
> 

No, you're not.  Dropping a single CPU changes num_online_cpus(), which results in

static uint8_t adf_get_dev_node_id(struct pci_dev *pdev)
{
        unsigned int bus_per_cpu = 0;
        struct cpuinfo_x86 *c = &cpu_data(num_online_cpus() - 1);  <<< this
being different.

        if (!c->phys_proc_id)
                return 0;

        bus_per_cpu = 256 / (c->phys_proc_id + 1);  <<< this being different

        if (bus_per_cpu != 0)
                return pdev->bus->number / bus_per_cpu; <<< and this being different
        return 0;
}

P.

  reply	other threads:[~2014-10-10 11:24 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-08 17:38 [PATCH 0/2] crypto: qat - Fix for invalid dma mapping and numa Tadeusz Struk
2014-10-08 17:38 ` [PATCH 1/2] crypto: qat - Prevent dma mapping zero length assoc data Tadeusz Struk
2014-10-08 17:38 ` [PATCH 2/2] crypto: qat - Enforce valid numa configuration Tadeusz Struk
2014-10-08 17:57   ` Prarit Bhargava
2014-10-08 18:11     ` Tadeusz Struk
2014-10-08 18:35       ` Prarit Bhargava
2014-10-08 18:57         ` Tadeusz Struk
2014-10-08 19:01           ` Prarit Bhargava
2014-10-08 19:25             ` Tadeusz Struk
2014-10-09 11:23               ` Prarit Bhargava
2014-10-09 16:14                 ` Tadeusz Struk
2014-10-09 17:32                   ` Prarit Bhargava
2014-10-09 19:55                     ` Tadeusz Struk
2014-10-09 21:42                       ` Prarit Bhargava
2014-10-09 23:12                         ` Tadeusz Struk
2014-10-10 11:23                           ` Prarit Bhargava [this message]
2014-10-10 13:25                             ` Tadeusz Struk
2014-10-10 22:15                               ` Prarit Bhargava
2014-10-11 17:05                                 ` Tadeusz Struk

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=5437C1C9.7050505@redhat.com \
    --to=prarit@redhat.com \
    --cc=bruce.w.allan@intel.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=john.griffin@intel.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=naleksan@redhat.com \
    --cc=qat-linux@intel.com \
    --cc=tadeusz.struk@intel.com \
    /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.