[dpdk-dev] [PATCH] drivers: make driver names consistent

2016-10-19 Thread Yuanhan Liu
On Tue, Oct 18, 2016 at 06:46:40PM +0200, Thomas Monjalon wrote: > 2016-10-18 22:18, Yuanhan Liu: > > On Tue, Oct 18, 2016 at 03:42:54PM +0200, Thomas Monjalon wrote: > > > 2016-10-18 21:06, Yuanhan Liu: > > > > On Tue, Oct 18, 2016 at 02:50:16PM +0200, Jan Blunck wrote: > > > > > >From my understa

[dpdk-dev] [PATCH] drivers: make driver names consistent

2016-10-19 Thread Bruce Richardson
On Tue, Oct 18, 2016 at 05:26:22PM +0200, Jan Blunck wrote: > On Tue, Oct 18, 2016 at 3:42 PM, Thomas Monjalon > wrote: > > 2016-10-18 21:06, Yuanhan Liu: > >> On Tue, Oct 18, 2016 at 02:50:16PM +0200, Jan Blunck wrote: > >> > >From my understanding this is a massive API breakage. This forces all

[dpdk-dev] [PATCH] drivers: make driver names consistent

2016-10-19 Thread Thomas Monjalon
2016-10-19 18:05, Yuanhan Liu: > On Tue, Oct 18, 2016 at 06:46:40PM +0200, Thomas Monjalon wrote: > > 2016-10-18 22:18, Yuanhan Liu: > > > On Tue, Oct 18, 2016 at 03:42:54PM +0200, Thomas Monjalon wrote: > > > > 2016-10-18 21:06, Yuanhan Liu: > > > > > On Tue, Oct 18, 2016 at 02:50:16PM +0200, Jan

[dpdk-dev] [PATCH] drivers: make driver names consistent

2016-10-18 Thread Yuanhan Liu
On Tue, Oct 18, 2016 at 03:42:54PM +0200, Thomas Monjalon wrote: > 2016-10-18 21:06, Yuanhan Liu: > > On Tue, Oct 18, 2016 at 02:50:16PM +0200, Jan Blunck wrote: > > > >From my understanding this is a massive API breakage. This forces all > > > existing users of the virtual PMDs to change with zero

[dpdk-dev] [PATCH] drivers: make driver names consistent

2016-10-18 Thread Yuanhan Liu
On Tue, Oct 18, 2016 at 02:50:16PM +0200, Jan Blunck wrote: > >From my understanding this is a massive API breakage. This forces all > existing users of the virtual PMDs to change with zero benefit. Even > if that isn't enough it also makes it impossible to switch between > releases by recompiling.

[dpdk-dev] [PATCH] drivers: make driver names consistent

2016-10-18 Thread Thomas Monjalon
2016-10-18 22:18, Yuanhan Liu: > On Tue, Oct 18, 2016 at 03:42:54PM +0200, Thomas Monjalon wrote: > > 2016-10-18 21:06, Yuanhan Liu: > > > On Tue, Oct 18, 2016 at 02:50:16PM +0200, Jan Blunck wrote: > > > > >From my understanding this is a massive API breakage. This forces all > > > > existing user

[dpdk-dev] [PATCH] drivers: make driver names consistent

2016-10-18 Thread Thomas Monjalon
2016-10-18 17:26, Jan Blunck: > On Tue, Oct 18, 2016 at 3:42 PM, Thomas Monjalon > wrote: > > 2016-10-18 21:06, Yuanhan Liu: > >> On Tue, Oct 18, 2016 at 02:50:16PM +0200, Jan Blunck wrote: > >> > >From my understanding this is a massive API breakage. This forces all > >> > existing users of the v

[dpdk-dev] [PATCH] drivers: make driver names consistent

2016-10-18 Thread Jan Blunck
On Tue, Oct 18, 2016 at 3:42 PM, Thomas Monjalon wrote: > 2016-10-18 21:06, Yuanhan Liu: >> On Tue, Oct 18, 2016 at 02:50:16PM +0200, Jan Blunck wrote: >> > >From my understanding this is a massive API breakage. This forces all >> > existing users of the virtual PMDs to change with zero benefit. E

[dpdk-dev] [PATCH] drivers: make driver names consistent

2016-10-18 Thread Thomas Monjalon
2016-10-18 21:06, Yuanhan Liu: > On Tue, Oct 18, 2016 at 02:50:16PM +0200, Jan Blunck wrote: > > >From my understanding this is a massive API breakage. This forces all > > existing users of the virtual PMDs to change with zero benefit. Even > > if that isn't enough it also makes it impossible to sw

[dpdk-dev] [PATCH] drivers: make driver names consistent

2016-10-18 Thread Jan Blunck
>From my understanding this is a massive API breakage. This forces all existing users of the virtual PMDs to change with zero benefit. Even if that isn't enough it also makes it impossible to switch between releases by recompiling. Can we please revert these changes and work on some aliasing suppo

[dpdk-dev] [PATCH] drivers: make driver names consistent

2016-09-16 Thread Thomas Monjalon
2016-08-24 22:37, Mcnamara, John: > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Pablo de Lara > > > > ... > > > > -$RTE_TARGET/app/testpmd -c '0xf' -n 4 --vdev > > 'eth_pcap0,rx_pcap=/path/to/ file_rx.pcap,tx_pcap=/path/to/file_tx.pcap' -- > > --port-topology=chained > > +$RTE

[dpdk-dev] [PATCH] drivers: make driver names consistent

2016-08-24 Thread Pablo de Lara
As discussed in the past release, driver names are modified to be more consistent, and the future driver should follow this new convention. Driver names consist of: "driver category"_"driver folder name"_"optional extra name". For example: - Crypto null driver -> "crypto_null" - Network IXG

[dpdk-dev] [PATCH] drivers: make driver names consistent

2016-08-24 Thread Mcnamara, John
> -Original Message- > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Pablo de Lara > Sent: Wednesday, August 24, 2016 11:25 PM > To: dev at dpdk.org > Cc: De Lara Guarch, Pablo > Subject: [dpdk-dev] [PATCH] drivers: make driver names consistent > > ...

[dpdk-dev] [PATCH] drivers: make driver names consistent

2016-08-24 Thread De Lara Guarch, Pablo
> -Original Message- > From: De Lara Guarch, Pablo > Sent: Wednesday, August 24, 2016 3:25 PM > To: dev at dpdk.org > Cc: De Lara Guarch, Pablo > Subject: [PATCH] drivers: make driver names consistent > > As discussed in the past release, driver names are modified > to be more consistent