DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: "Etelson, Gregory" <getelson@nvidia.com>
Cc: "Bruce Richardson" <bruce.richardson@intel.com>,
	dev@dpdk.org,   <mkashani@nvidia.com>,
	rasland@nvidia.com, alialnu@nvidia.com
Subject: Re: [PATCH] cmdline: configure input buffer size
Date: Wed, 1 May 2024 07:42:38 -0700	[thread overview]
Message-ID: <20240501074238.0033d275@hermes.local> (raw)
In-Reply-To: <96d1ac1-b2cf-f6db-1e24-aead628a9d16@nvidia.com>

On Wed, 1 May 2024 13:06:47 +0300 (IDT)
"Etelson, Gregory" <getelson@nvidia.com> wrote:

> > Basic question, what would be the impact of increasing the default from 512
> > to 1k or 2k? Do we get a large memory footprint increase, or is it just an
> > extra 1 or 2k of memory used?
> >
> > /Bruce
> >  
> 
> Increasing the RDLINE_BUF_SIZE size will also increase application memory usage.
> However, that memory increase was required, because application could not fit 
> it's command line into the default buffer.
> 
> Applications that can run with the default RDLINE_BUF_SIZE are not affected by 
> that patch.
> 
> Regards,
> Gregory


The buffer is transient so should have little impact.
Why not just use LINE_MAX from limits.h?

  reply	other threads:[~2024-05-01 14:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-01  5:26 Gregory Etelson
2024-05-01  9:08 ` Bruce Richardson
2024-05-01 10:06   ` Etelson, Gregory
2024-05-01 14:42     ` Stephen Hemminger [this message]
2024-05-01 15:56       ` Etelson, Gregory
2024-05-01 16:30         ` Bruce Richardson
2024-05-01 17:18 ` [PATCH v2] cmdline: increase " Gregory Etelson
2024-05-01 18:26   ` Morten Brørup
2024-05-02  7:27     ` Bruce Richardson
2024-05-03  4:27 ` [PATCH v3] " Gregory Etelson
2024-05-15  8:41   ` Gregory Etelson

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=20240501074238.0033d275@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=alialnu@nvidia.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=getelson@nvidia.com \
    --cc=mkashani@nvidia.com \
    --cc=rasland@nvidia.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).