From: "Liu, Yong" <yong.liu@intel.com>
To: gowrishankar <gowrishankar.m@linux.vnet.ibm.com>
Cc: dts <dts@dpdk.org>
Subject: Re: [dts] framework v2: hugepages, cpuinfo, connect x3 support and bug fixes
Date: Fri, 11 Mar 2016 09:26:39 +0000 [thread overview]
Message-ID: <86228AFD5BCD8E4EBFD2B90117B5E81E14EC190E@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <56E13E57.7000701@linux.vnet.ibm.com>
Thanks, Gowrishankar. My suggestion is to install util-linux in yocto.
We'd better use those tools which can make our life easier.
> -----Original Message-----
> From: gowrishankar [mailto:gowrishankar.m@linux.vnet.ibm.com]
> Sent: Thursday, March 10, 2016 5:29 PM
> To: Liu, Yong
> Cc: dts; Xu, HuilongX
> Subject: Re: [dts] framework v2: hugepages, cpuinfo, connect x3 support
> and bug fixes
>
> On Wednesday 09 March 2016 10:04 AM, Liu, Yong wrote:
> > Thanks, Gowrishankar. Your patches have been merged into next branch.
> There'll be some basic validations on it before merged back to master.
> Thank you Yong.
>
> As far as yocto specific need on lscpu, either their os image itself
> need to include concerned util package
> or we need to fallback to /proc/cpuinfo parsing only for yocto in run
> time. If latter option is considered,
> Is huilongx planning to add patch on top of next ?.
>
> Regards,
> Gowrishankar
>
> >
> >> -----Original Message-----
> >> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Gowrishankar
> >> Sent: Tuesday, March 08, 2016 6:07 PM
> >> To: dts
> >> Subject: [dts] framework v2: hugepages, cpuinfo, connect x3 support
> and
> >> bug fixes
> >>
> >> Following are set of patches addressing below:
> >>
> >> 1. hugepages setting and cpu info parsing for powerpc environment in a
> >> platform
> >> independent way.
> >> 2. enable connect x3 support to run DTS.
> >> 3. some bug fixes in framework as well as tests handling numa, cpu
> >> coremask
> >> and expected output.
> >>
> >> Changes from version 1:
> >> - interface name for second port sharing same PCI id is stored in
> >> variable 'intf2'
> >> instead 'peer' as earlier, also relavant function names.
> >> - check interface name and mac retrieved from DUT scan.
> >>
> >>
> >> Thanks,
> >> Gowrishankar
> >
>
prev parent reply other threads:[~2016-03-11 9:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-08 10:06 Gowrishankar
2016-03-08 10:06 ` [dts] [PATCH v2 1/9] framework: check hugepage size and add pages Gowrishankar
2016-03-08 10:06 ` [dts] [PATCH v2 2/9] framework: platform independent cpu info parsing Gowrishankar
2016-03-08 10:06 ` [dts] [PATCH v2 3/9] framework: include domain id in pci tuple Gowrishankar
2016-03-08 10:06 ` [dts] [PATCH v2 4/9] framework: enable connect X3 support Gowrishankar
2016-03-08 10:06 ` [dts] [PATCH v2 5/9] framework: fix numa number lookup for a dev Gowrishankar
2016-03-08 10:06 ` [dts] [PATCH v2 6/9] framework: fix get_core_list to return all lcores Gowrishankar
2016-03-08 10:06 ` [dts] [PATCH v2 7/9] tests: fix multiprocess test to set coremask through library Gowrishankar
2016-03-08 10:06 ` [dts] [PATCH v2 8/9] tests: fix coremask test to check expected EAL output Gowrishankar
2016-03-08 10:06 ` [dts] [PATCH v2 9/9] tests: fix blacklist test to discard extra pci domain id in verification string Gowrishankar
2016-03-09 4:34 ` [dts] framework v2: hugepages, cpuinfo, connect x3 support and bug fixes Liu, Yong
2016-03-10 9:28 ` gowrishankar
2016-03-11 9:26 ` Liu, Yong [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=86228AFD5BCD8E4EBFD2B90117B5E81E14EC190E@SHSMSX103.ccr.corp.intel.com \
--to=yong.liu@intel.com \
--cc=dts@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).