DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Power, Ciara" <ciara.power@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"Laatz, Kevin" <kevin.laatz@intel.com>,
	Stephen Hemminger <stephen@networkplumber.org>,
	"Richardson, Bruce" <bruce.richardson@intel.com>
Subject: Re: [dpdk-dev] [PATCH 20.08] telemetry: add upper limit on connections
Date: Mon, 13 Jul 2020 10:22:01 +0000	[thread overview]
Message-ID: <DM6PR11MB25554CCB1BDA8CB46B3933B7E6600@DM6PR11MB2555.namprd11.prod.outlook.com> (raw)
In-Reply-To: <9665425.xVsip7n7Xm@thomas>

>-----Original Message-----
>From: Thomas Monjalon <thomas@monjalon.net>
>Sent: Friday 10 July 2020 21:51
>To: Power, Ciara <ciara.power@intel.com>
>Cc: dev@dpdk.org; Laatz, Kevin <kevin.laatz@intel.com>; Stephen
>Hemminger <stephen@networkplumber.org>; Richardson, Bruce
>Subject: Re: [dpdk-dev] [PATCH 20.08] telemetry: add upper limit on
>19/05/2020 02:07, Stephen Hemminger:
>> On Mon, 18 May 2020 17:12:32 +0100
>> Ciara Power <ciara.power@intel.com> wrote:
>> > This patch limits the number of client connections to the new
>> > telemetry socket. The limit is set at 10.
>> >
>> > Signed-off-by: Ciara Power <ciara.power@intel.com>
>> The upper limit is fine, but using System V semaphores is not a good
>> way to do this. Please consider using some other atomic primitive.
>Why no reply?

Hi Thomas,

I had contacted Stephen offline for some detail on his suggestion. I thought I would have a patch sent soon after, but it took longer than expected, and I forgot to reply on list.
I have a patch in progress that will hopefully be sent up soon after internal review.


  reply	other threads:[~2020-07-13 10:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-18 16:12 Ciara Power
2020-05-19  0:07 ` Stephen Hemminger
2020-07-10 20:50   ` Thomas Monjalon
2020-07-13 10:22     ` Power, Ciara [this message]
2020-07-15 15:03 ` [dpdk-dev] [PATCH v2] " Ciara Power
2020-07-19 13:45   ` Thomas Monjalon

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DM6PR11MB25554CCB1BDA8CB46B3933B7E6600@DM6PR11MB2555.namprd11.prod.outlook.com \
    --to=ciara.power@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=kevin.laatz@intel.com \
    --cc=stephen@networkplumber.org \
    --cc=thomas@monjalon.net \


* 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).