DPDK patches and discussions
 help / color / mirror / Atom feed
From: Matthew Hall <mhall@mhcomputing.net>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] Use pthread_setname APIs
Date: Wed, 22 Apr 2015 17:52:33 -0700	[thread overview]
Message-ID: <20150423005233.GA6573@mhcomputing.net> (raw)
In-Reply-To: <CAOaVG14SD_PxbYcSJomEgBn0jSfaTfNyp5Gq=1-nuwJ9sR1TpQ@mail.gmail.com>

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.

  reply	other threads:[~2015-04-23  0:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-22 21:05 Ravi Kerur
2015-04-22 21:06 ` Ravi Kerur
2015-07-26 21:54   ` Thomas Monjalon
2015-07-27 20:40     ` Ravi Kerur
2015-07-27 21:09       ` Stephen Hemminger
2015-07-27 21:48         ` Ravi Kerur
2015-04-22 22:57 ` Stephen Hemminger
2015-04-23  0:19   ` Matthew Hall
2015-04-23  0:39     ` Stephen Hemminger
2015-04-23  0:52       ` Matthew Hall [this message]
2015-04-23  8:16   ` Bruce Richardson

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=20150423005233.GA6573@mhcomputing.net \
    --to=mhall@mhcomputing.net \
    --cc=dev@dpdk.org \
    --cc=stephen@networkplumber.org \
    /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).