All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Stephen Hurd <shurd@broadcom.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH v2] app/testpmd Fix max_socket detection
Date: Thu, 14 Jan 2016 13:44:19 +0000	[thread overview]
Message-ID: <20160114134418.GA18000@bricha3-MOBL3> (raw)
In-Reply-To: <1452723816-73141-1-git-send-email-shurd@broadcom.com>

On Wed, Jan 13, 2016 at 02:23:36PM -0800, Stephen Hurd wrote:
> Previously, max_socket was set to the highest numbered socket with
> an enabled lcore.  The intent is to set it to the highest socket
> regardless of it being enabled.
> 

Can you clarify why this changes is necessary? Is it causing a bug somewhere?

thanks,
/Bruce

  reply	other threads:[~2016-01-14 13:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <533710CFB86FA344BFBF2D6802E6028621BAF050@SHSMSX101.ccr.corp.intel.com>
     [not found] ` <156984479488CD49A184F5CAB4AF93460719DEC4@IRVEXCHMB14.corp.ad.broadcom.com>
     [not found]   ` <533710CFB86FA344BFBF2D6802E6028621BAF45F@SHSMSX101.ccr.corp.intel.com>
     [not found]     ` <156984479488CD49A184F5CAB4AF93460719E1D1@IRVEXCHMB14.corp.ad.broadcom.com>
2015-12-19  1:33       ` Issue with patch "app/testpmd: detect numa socket count" Qiu, Michael
2016-01-13 22:20         ` [PATCH] app/testpmd Fix max_socket detection Stephen Hurd
2016-01-13 22:23         ` [PATCH v2] " Stephen Hurd
2016-01-14 13:44           ` Bruce Richardson [this message]
2016-01-15  0:59             ` Stephen Hurd
2016-01-15  1:01             ` Stephen Hurd
2016-01-15 10:42               ` Bruce Richardson
2016-03-02 11:04           ` De Lara Guarch, Pablo
2016-03-05 19:10             ` Thomas Monjalon

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=20160114134418.GA18000@bricha3-MOBL3 \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=shurd@broadcom.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.