[dpdk-dev] [PATCH] Use pthread_setname APIs

2015-07-27 Thread Ravi Kerur
On Mon, Jul 27, 2015 at 2:09 PM, Stephen Hemminger < stephen at networkplumber.org> wrote: > On Mon, 27 Jul 2015 13:40:08 -0700 > Ravi Kerur wrote: > > > On Sun, Jul 26, 2015 at 2:54 PM, Thomas Monjalon < > thomas.monjalon at 6wind.com> > > wrote: > > > > > Hi Ravi, > > > It seems to be a nice im

[dpdk-dev] [PATCH] Use pthread_setname APIs

2015-07-27 Thread Stephen Hemminger
On Mon, 27 Jul 2015 13:40:08 -0700 Ravi Kerur wrote: > On Sun, Jul 26, 2015 at 2:54 PM, Thomas Monjalon 6wind.com> > wrote: > > > Hi Ravi, > > It seems to be a nice improvement but it needs some cleanup. > > > > Checkpatch returns some errors. > > > > 2015-04-22 14:06, Ravi Kerur: > > > use pth

[dpdk-dev] [PATCH] Use pthread_setname APIs

2015-07-27 Thread Ravi Kerur
On Sun, Jul 26, 2015 at 2:54 PM, Thomas Monjalon wrote: > Hi Ravi, > It seems to be a nice improvement but it needs some cleanup. > > Checkpatch returns some errors. > > 2015-04-22 14:06, Ravi Kerur: > > use pthread_setname_np and pthread_set_name_np for Linux and > > FreeBSD respectively. > > Re

[dpdk-dev] [PATCH] Use pthread_setname APIs

2015-07-26 Thread Thomas Monjalon
Hi Ravi, It seems to be a nice improvement but it needs some cleanup. Checkpatch returns some errors. 2015-04-22 14:06, Ravi Kerur: > use pthread_setname_np and pthread_set_name_np for Linux and > FreeBSD respectively. > Restrict pthread name len to 16 via config for both Linux and FreeBSD. One

[dpdk-dev] [PATCH] Use pthread_setname APIs

2015-04-23 Thread Bruce Richardson
On Wed, Apr 22, 2015 at 03:57:44PM -0700, Stephen Hemminger wrote: > On Wed, 22 Apr 2015 14:05:48 -0700 > Ravi Kerur wrote: > > > Add code to set names to threads via pthread APIs. > > In Linux corresponding _getname_ is available, however, FreeBSD > > doesn't have corresponding _get_name API ava

[dpdk-dev] [PATCH] Use pthread_setname APIs

2015-04-22 Thread Matthew Hall
On Wed, Apr 22, 2015 at 05:39:40PM -0700, Stephen Hemminger wrote: > In our application we already use setname and have a policy for what the > names look like. > This won't help Not everybody does.

[dpdk-dev] [PATCH] Use pthread_setname APIs

2015-04-22 Thread Stephen Hemminger
In our application we already use setname and have a policy for what the names look like. This won't help On Wed, Apr 22, 2015 at 5:19 PM, Matthew Hall wrote: > On Wed, Apr 22, 2015 at 03:57:44PM -0700, Stephen Hemminger wrote: > > Since it possible to have multiple DPDK applications in same env

[dpdk-dev] [PATCH] Use pthread_setname APIs

2015-04-22 Thread Matthew Hall
On Wed, Apr 22, 2015 at 03:57:44PM -0700, Stephen Hemminger wrote: > Since it possible to have multiple DPDK applications in same environment, > and the thread name size is so limited, I wonder if this is a good idea. Why not try to opportunistically make the code easier to debug? DPDK is not alw

[dpdk-dev] [PATCH] Use pthread_setname APIs

2015-04-22 Thread Stephen Hemminger
On Wed, 22 Apr 2015 14:05:48 -0700 Ravi Kerur wrote: > Add code to set names to threads via pthread APIs. > In Linux corresponding _getname_ is available, however, FreeBSD > doesn't have corresponding _get_name API available yet. Hence _getname_ > is not yet used in the code. > > Ravi Kerur (1):

[dpdk-dev] [PATCH] Use pthread_setname APIs

2015-04-22 Thread Ravi Kerur
use pthread_setname_np and pthread_set_name_np for Linux and FreeBSD respectively. Restrict pthread name len to 16 via config for both Linux and FreeBSD. Testing: Linux: Compiled with both clang and gcc (x86_64-native-linuxapp-gcc and x86_64-native-linuxapp-clang). Compiled examples/vhost. make te

[dpdk-dev] [PATCH] Use pthread_setname APIs

2015-04-22 Thread Ravi Kerur
Add code to set names to threads via pthread APIs. In Linux corresponding _getname_ is available, however, FreeBSD doesn't have corresponding _get_name API available yet. Hence _getname_ is not yet used in the code. Ravi Kerur (1): Use pthread_setname apis config/common_bsdapp