[dpdk-dev] [PATCH] Use pthread_setname APIs

[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 <rkerur at gmail.com> 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):
> >   Use pthread_setname apis
> > 
> >  config/common_bsdapp                               |  5 +++++
> >  config/common_linuxapp                             |  5 +++++
> >  examples/vhost/Makefile                            |  1 +
> >  examples/vhost/main.c                              | 18 ++++++++++++++++--
> >  examples/vhost_xen/Makefile                        |  1 +
> >  examples/vhost_xen/main.c                          | 20 ++++++++++++++++++--
> >  lib/librte_eal/bsdapp/eal/eal.c                    |  7 +++++++
> >  lib/librte_eal/linuxapp/eal/Makefile               |  2 ++
> >  lib/librte_eal/linuxapp/eal/eal.c                  | 11 +++++++++++
> >  lib/librte_eal/linuxapp/eal/eal_interrupts.c       | 20 +++++++++++++++++---
> >  lib/librte_eal/linuxapp/eal/eal_pci_vfio_mp_sync.c | 16 ++++++++++++++--
> >  lib/librte_eal/linuxapp/eal/eal_timer.c            | 11 ++++++++++-
> >  12 files changed, 107 insertions(+), 10 deletions(-)
> > 
> 
> 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.

Can you be a bit more specific as to what your concern here is? This looks a good
idea to me.

/Bruce