From: Thomas Monjalon <thomas@monjalon.net>
To: Gowrishankar <gowrishankar.m@linux.vnet.ibm.com>
Cc: dev@dpdk.org,
Andriy Berestovskyy <Andriy.Berestovskyy@caviumnetworks.com>
Subject: Re: [PATCH] usertools: fix cpu_layout script for multithreads of more than 2
Date: Sun, 30 Apr 2017 15:29:19 +0200 [thread overview]
Message-ID: <2353390.jtLUV08Iqy@xps> (raw)
In-Reply-To: <ac9f746b-872f-02bd-6c56-21a82be9f21a@caviumnetworks.com>
28/04/2017 14:25, Andriy Berestovskyy:
> Works fine on ThunderX and does not brake Intel either.
>
> Reviewed-by: Andriy Berestovskyy <andriy.berestovskyy@caviumnetworks.com>
> Tested-by: Andriy Berestovskyy <andriy.berestovskyy@caviumnetworks.com>
>
> Andriy
>
> On 28.04.2017 13:58, Thomas Monjalon wrote:
> > Andriy, please would you like to review this patch?
> >
> > 28/04/2017 12:34, Gowrishankar:
> >> From: Gowrishankar Muthukrishnan <gowrishankar.m@linux.vnet.ibm.com>
> >>
> >> Current usertools/cpu_layout.py is broken to handle multithreads of count more
> >> than 2 as in IBM powerpc P8 servers. Below patch addressed this issue. Also,
> >> added minor exception catch on failing to open unavailable sys file in case of
> >> multithread=off configuration in server.
> >>
> >> Patch has been verified not to break existing topology configurations
> >> and also not changing anything in current output.
> >>
> >> Signed-off-by: Gowrishankar Muthukrishnan <gowrishankar.m@linux.vnet.ibm.com>
Applied, thanks
prev parent reply other threads:[~2017-04-30 13:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-28 10:34 [PATCH] usertools: fix cpu_layout script for multithreads of more than 2 Gowrishankar
2017-04-28 11:58 ` Thomas Monjalon
2017-04-28 12:25 ` Andriy Berestovskyy
2017-04-30 13:29 ` Thomas Monjalon [this message]
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=2353390.jtLUV08Iqy@xps \
--to=thomas@monjalon.net \
--cc=Andriy.Berestovskyy@caviumnetworks.com \
--cc=dev@dpdk.org \
--cc=gowrishankar.m@linux.vnet.ibm.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.