From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Ravi Kerur <rkerur@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] Add support for pthreads setname.
Date: Tue, 03 Nov 2015 15:34:08 +0100 [thread overview]
Message-ID: <1463695.VJy6XOjk2U@xps13> (raw)
In-Reply-To: <20150729165616.76adab75@urahara>
> > This patch adds support for pthread_setname_np on Linux and
> > pthread_set_name_np on FreeBSD.
> >
> > Changes in V2:
> > Remove config support for max thread name len.
> > Restrict max thread name len to 16 on Linux and FreeBSD.
> > Fix checkpatch.pl errors.
> > Changes based on code review comments from Thomas.
> >
> > Changes in V1:
> > Add support for _setname_ on Linux and FreeBSD.
> >
> > Signed-off-by: Ravi Kerur <rkerur@gmail.com>
>
> Looks like good simple solution.
> Acked-by: Stephen Hemminger <stephen@networkplumber.org>
Applied with update of tep_termination. Thanks
prev parent reply other threads:[~2015-11-03 14:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-29 0:50 [dpdk-dev] [PATCH v2] Add support for pthread_setname Ravi Kerur
2015-07-29 0:51 ` [dpdk-dev] [PATCH v2] Add support for pthreads setname Ravi Kerur
2015-07-29 23:56 ` Stephen Hemminger
2015-11-03 14:34 ` Thomas Monjalon [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=1463695.VJy6XOjk2U@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=rkerur@gmail.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).