DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Raslan Darawsheh <rasland@mellanox.com>,
	Michael Baum <michaelba@mellanox.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: Matan Azrad <matan@mellanox.com>,
	Slava Ovsiienko <viacheslavo@mellanox.com>
Subject: Re: [dpdk-dev] [PATCH] net/mlx5: optimize stuck memory in probe
Date: Wed, 22 Jul 2020 17:33:43 +0100	[thread overview]
Message-ID: <f7fceb9c-d496-88c6-e897-dff0cfd16196@intel.com> (raw)
In-Reply-To: <AM0PR05MB670718754EDA6C16762F22CEC2790@AM0PR05MB6707.eurprd05.prod.outlook.com>

On 7/22/2020 4:30 PM, Raslan Darawsheh wrote:
> Hi,
> 
>> -----Original Message-----
>> From: dev <dev-bounces@dpdk.org> On Behalf Of Michael Baum
>> Sent: Tuesday, July 21, 2020 3:05 PM
>> To: dev@dpdk.org
>> Cc: Matan Azrad <matan@mellanox.com>; Slava Ovsiienko
>> <viacheslavo@mellanox.com>
>> Subject: [dpdk-dev] [PATCH] net/mlx5: optimize stuck memory in probe
>>
>> The device configuration stuck is not small enough to be used as

I guess s/stuck/stack/, will fix while merging.

>> function argument by value.
>>
>> Call spawn function with device configuration by value.
>>
>> Signed-off-by: Michael Baum <michaelba@mellanox.com>
>> Acked-by: Matan Azrad <matan@mellanox.com>
> 
> Patch applied to next-net-mlx,
> 
> Kindest regards,
> Raslan Darawsheh
> 


  reply	other threads:[~2020-07-22 16:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-21 12:05 Michael Baum
2020-07-22 15:30 ` Raslan Darawsheh
2020-07-22 16:33   ` Ferruh Yigit [this message]
2020-07-22 16:36     ` Ferruh Yigit

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=f7fceb9c-d496-88c6-e897-dff0cfd16196@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=matan@mellanox.com \
    --cc=michaelba@mellanox.com \
    --cc=rasland@mellanox.com \
    --cc=viacheslavo@mellanox.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).