DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Sunil Kumar Kori <skori@marvell.com>,
	Timothy McDaniel <timothy.mcdaniel@intel.com>
Cc: Jerin Jacob <jerinjacobk@gmail.com>, dev <dev@dpdk.org>,
	 Erik Gabriel Carrillo <erik.g.carrillo@intel.com>,
	Gage Eads <gage.eads@intel.com>,
	 Van Haaren Harry <harry.van.haaren@intel.com>
Subject: Re: [dpdk-dev] [EXT] Re: [PATCH 1/1] eal: increase TRACE CTF SIZE to recommended size
Date: Wed, 7 Oct 2020 14:34:29 +0200	[thread overview]
Message-ID: <CAJFAV8zxLVPy1PMjsqPj2PvbEUDn2TdmYHriaudeatssbZ9cZw@mail.gmail.com> (raw)
In-Reply-To: <CY4PR18MB1622EED1D78EA3648252FC8BB40A0@CY4PR18MB1622.namprd18.prod.outlook.com>

On Wed, Oct 7, 2020 at 12:07 PM Sunil Kumar Kori <skori@marvell.com> wrote:
>> it is on a slow path. 448 is OK.
> >
> >Ah yes, this is for the ctf description.
> >Could it be changed to rely on dynamic allocations and we simply remove this
> >limit?
> Changing it to dynamic allocation is difficult because if we do this then every time memory is to reallocated.
> So IMO, It is okay to keep it static with enough size.

I will take this as a ack from both Jerin and you and push with the
suggested commitlog.

David Marchand

  reply	other threads:[~2020-10-07 12:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-05 20:02 [dpdk-dev] " Timothy McDaniel
2020-10-06  8:45 ` David Marchand
2020-10-06  9:22   ` [dpdk-dev] [EXT] " Sunil Kumar Kori
2020-10-06  9:39     ` David Marchand
2020-10-06  9:58       ` Jerin Jacob
2020-10-07  9:04         ` David Marchand
2020-10-07 10:07           ` Sunil Kumar Kori
2020-10-07 12:34             ` David Marchand [this message]
2020-10-08  7:33 ` [dpdk-dev] " David Marchand

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=CAJFAV8zxLVPy1PMjsqPj2PvbEUDn2TdmYHriaudeatssbZ9cZw@mail.gmail.com \
    --to=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=erik.g.carrillo@intel.com \
    --cc=gage.eads@intel.com \
    --cc=harry.van.haaren@intel.com \
    --cc=jerinjacobk@gmail.com \
    --cc=skori@marvell.com \
    --cc=timothy.mcdaniel@intel.com \


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