[dpdk-dev] GitHub sandbox for the DPDK community

2015-05-01 Thread Aaro Koskinen
On Fri, May 01, 2015 at 12:49:51PM -0700, Matthew Hall wrote: > On Fri, May 01, 2015 at 11:09:14AM -0700, Stephen Hemminger wrote: > > With email, the patches are right in front of developers and easier to quote > > for review comments. > > Right in front of that subset of developers who do everyt

[dpdk-dev] DPDK Community Call - Beyond DPDK 2.0

2015-05-01 Thread O'Driscoll, Tim
There's been a good discussion on the mailing list on the Beyond DPDK 2.0 thread. To supplement this, we'd like to have a community call for people to air their views, and to help progress things towards a conclusion. It'll be an open format, so people can bring up whatever issues they want, but

[dpdk-dev] GitHub sandbox for the DPDK community

2015-05-01 Thread Aaro Koskinen
Hi, On Fri, May 01, 2015 at 12:45:12PM -0400, Neil Horman wrote: > > - GitHub manages the patches via pull requests and can be easily seen > > via a web browser. > > - The down side is you do have to use a web browser to do some work, but > > the bulk of the everyday work would be done as it i

[dpdk-dev] GitHub sandbox for the DPDK community

2015-05-01 Thread Wiles, Keith
On 5/1/15, 1:48 PM, "Neil Horman" wrote: >On Fri, May 01, 2015 at 10:31:08AM -0700, Matthew Hall wrote: >> On Fri, May 01, 2015 at 12:45:12PM -0400, Neil Horman wrote: >> > Yes, but as you said above, using a web browser doesn't make >>reviewing patches >> > faster. In fact, I would assert tha

[dpdk-dev] DPDK Community Call - Beyond DPDK 2.0

2015-05-01 Thread Dave Neary
Hi Tim, When were you thinking of having the call? It's not been explicit, but can I assume that this call will also be promoted among potential supporters of the project who may not be on this list? I would be interested to get the perspective from the people who are perhaps not developers who d

[dpdk-dev] GitHub sandbox for the DPDK community

2015-05-01 Thread Wiles, Keith
On 5/1/15, 1:09 PM, "Stephen Hemminger" wrote: >On Fri, 1 May 2015 15:56:32 + >"Wiles, Keith" wrote: > >> Hi Everyone, >> >> I believe the DPDK community would benefit from moving to GitHub as the >> primary DPDK site. http://github.com >> >> I believe the DPDK community can benefit from

[dpdk-dev] GitHub sandbox for the DPDK community

2015-05-01 Thread Wiles, Keith
On 5/1/15, 11:45 AM, "Neil Horman" wrote: >On Fri, May 01, 2015 at 03:56:32PM +, Wiles, Keith wrote: >> Hi Everyone, >> >> I believe the DPDK community would benefit from moving to GitHub as the >> primary DPDK site. http://github.com >> >I'm not explicitly opposed to this, but I'm having

[dpdk-dev] GitHub sandbox for the DPDK community

2015-05-01 Thread Wiles, Keith
On 5/1/15, 12:31 PM, "Matthew Hall" wrote: >Normally I'm a big command-line supporter. However I have found reviewing >patches by email for me is about the most painful workflow. > >The emails are pages and pages. > >The replies from commenters are buried in the walls of text. > >Replies to rep

[dpdk-dev] [RFC PATCH] librte_pmd_virtio: add support for PCI Port Hotplug

2015-05-01 Thread Bernard Iremonger
This patch depends on the Port Hotplug Framework. It implements the eth_dev_uninit_t() function for virtio pmd. Signed-off-by: Bernard Iremonger --- lib/librte_pmd_virtio/virtio_ethdev.c | 39 - 1 files changed, 38 insertions(+), 1 deletions(-) diff --git a/lib

[dpdk-dev] [PATCH] eal: whitespace cleanup

2015-05-01 Thread Stephen Hemminger
Go through the linuxapp eal code and cleanup whitespace issues reported by checkpatch. --- lib/librte_eal/linuxapp/eal/eal_alarm.c | 17 ++-- lib/librte_eal/linuxapp/eal/eal_debug.c | 2 +- lib/librte_eal/linuxapp/eal/eal_hugepage_info.c | 57 ++--- lib/librte_eal/linux

[dpdk-dev] GitHub sandbox for the DPDK community

2015-05-01 Thread Wiles, Keith
Hi Everyone, I believe the DPDK community would benefit from moving to GitHub as the primary DPDK site. http://github.com I believe the DPDK community can benefit from being at a very well know world wide site. GitHub seems to have the most eyes of any of the open source Git repos today and it ap

[dpdk-dev] [RFC PATCH] librte_pmd_bond: add support for PCI Port Hotplug

2015-05-01 Thread Bernard Iremonger
This patch depends on the Port Hotplug Framework. It implements the rte_dev_uninit_t() function for the link bonding pmd. Signed-off-by: Bernard Iremonger --- lib/librte_pmd_bond/rte_eth_bond.h | 13 - lib/librte_pmd_bond/rte_eth_bond_api.c | 84

[dpdk-dev] GitHub sandbox for the DPDK community

2015-05-01 Thread Neil Horman
On Fri, May 01, 2015 at 10:31:08AM -0700, Matthew Hall wrote: > On Fri, May 01, 2015 at 12:45:12PM -0400, Neil Horman wrote: > > Yes, but as you said above, using a web browser doesn't make reviewing > > patches > > faster. In fact, I would assert that it slows the process down, as it > > preven

[dpdk-dev] GitHub sandbox for the DPDK community

2015-05-01 Thread Matthew Hall
On Fri, May 01, 2015 at 10:59:32PM +0300, Aaro Koskinen wrote: > Projects like GCC, GLIBC, binutils, busybox, etc or what? > > A. You'll notice all of these are low-level UNIX hacker sorts of tools mostly, with the partial exception of busybox. But even that is mainly for embedded use. It doesn

[dpdk-dev] GitHub sandbox for the DPDK community

2015-05-01 Thread Matthew Hall
On Fri, May 01, 2015 at 11:09:14AM -0700, Stephen Hemminger wrote: > With email, the patches are right in front of developers and easier to quote > for review comments. Right in front of that subset of developers who do everything kernel-style, perhaps yes. But this sort of workflow is in the min

[dpdk-dev] GitHub sandbox for the DPDK community

2015-05-01 Thread Neil Horman
On Fri, May 01, 2015 at 03:56:32PM +, Wiles, Keith wrote: > Hi Everyone, > > I believe the DPDK community would benefit from moving to GitHub as the > primary DPDK site. http://github.com > I'm not explicitly opposed to this, but I'm having trouble matching up the technical and governance iss

[dpdk-dev] [RFC PATCH] librte_pmd_bond: add support for PCI Port Hotplug

2015-05-01 Thread Neil Horman
On Fri, May 01, 2015 at 03:36:19PM +0100, Bernard Iremonger wrote: > This patch depends on the Port Hotplug Framework. > It implements the rte_dev_uninit_t() function for the link bonding pmd. > > Signed-off-by: Bernard Iremonger > --- > lib/librte_pmd_bond/rte_eth_bond.h | 13 - >

[dpdk-dev] GitHub sandbox for the DPDK community

2015-05-01 Thread Stephen Hemminger
On Fri, 1 May 2015 15:56:32 + "Wiles, Keith" wrote: > Hi Everyone, > > I believe the DPDK community would benefit from moving to GitHub as the > primary DPDK site. http://github.com > > I believe the DPDK community can benefit from being at a very well know > world wide site. GitHub seems t

[dpdk-dev] GitHub sandbox for the DPDK community

2015-05-01 Thread Matthew Hall
On Fri, May 01, 2015 at 12:45:12PM -0400, Neil Horman wrote: > Yes, but as you said above, using a web browser doesn't make reviewing patches > faster. In fact, I would assert that it slows the process down, as it > prevents > quick, easy command line access to patch review (as you have with a pr

[dpdk-dev] NO_AUTOLIB is this variable really needed?

2015-05-01 Thread Bruce Richardson
On Thu, Apr 30, 2015 at 05:26:57PM +0100, Wiles, Keith wrote: > > > On 4/30/15, 11:24 AM, "Richardson, Bruce" > wrote: > > >On Thu, Apr 30, 2015 at 02:55:47PM +, Wiles, Keith wrote: > >> What is the NO_AUTOLIB variable used for anyway, the doc states this: > >> > >> > >> * NO_AUTOLIBS: If

[dpdk-dev] [PATCH v4 1/2] Simplify the ifdefs in rte.app.mk.

2015-05-01 Thread Bruce Richardson
On Thu, Apr 30, 2015 at 05:33:36PM +0100, Wiles, Keith wrote: > > > On 4/30/15, 11:22 AM, "Richardson, Bruce" > wrote: > > >On Thu, Apr 30, 2015 at 02:31:13PM +, Wiles, Keith wrote: > >> > >> > >> On 4/30/15, 8:38 AM, "Olivier MATZ" wrote: > >> > >> >Hi Keith, > >> > > >> >On 04/30/2015

[dpdk-dev] [PATCH] Remove NO_AUTOLIBS option

2015-05-01 Thread Keith Wiles
NO_AUTOLIBS is not required as it was not used or defined in the config files. Signed-off-by: Keith Wiles --- mk/rte.app.mk | 5 - 1 file changed, 5 deletions(-) diff --git a/mk/rte.app.mk b/mk/rte.app.mk index b8030d2..b63e346 100644 --- a/mk/rte.app.mk +++ b/mk/rte.app.mk @@ -54,11 +54,8

[dpdk-dev] [PATCH v6 2/2] Update Docs for new EXTRA_LDLIBS variable

2015-05-01 Thread Keith Wiles
Removed the LDLIBS-y reference as it is not required. Signed-off-by: Keith Wiles --- doc/build-sdk-quick.txt | 1 + doc/guides/prog_guide/build_app.rst | 2 +- doc/guides/prog_guide/dev_kit_build_system.rst | 2 ++ doc/guides/prog_guide/dev_kit_root_make_h

[dpdk-dev] [PATCH v6 1/2] Simplify the ifdefs in rte.app.mk.

2015-05-01 Thread Keith Wiles
Trying to simplify the ifdefs in rte.app.mk to make the code more readable and maintainable by moving LDLIBS variable to use the same style as LDLIBS-y being used in the rest of the code. Added a new variable called EXTRA_LDLIBS to be used by example apps instead of using LDLIBS directly. The new