public inbox for linux-perf-users@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Veronika Molnarova <vmolnaro@redhat.com>
Cc: linux-perf-users@vger.kernel.org, acme@redhat.com,
	adrian.hunter@intel.com, atrajeev@linux.vnet.ibm.com,
	irogers@google.com, jolsa@kernel.org, kjain@linux.ibm.com,
	mpetlan@redhat.com, rstoyano@redhat.com
Subject: Re: [PATCH v3] perf test record.sh: Raise limit of open file descriptors
Date: Wed, 14 Aug 2024 12:54:51 -0300	[thread overview]
Message-ID: <ZrzTS46l3Ct_I0Oj@x1> (raw)
In-Reply-To: <d847f760-896e-4bdf-9f8c-933f52a5aed8@redhat.com>

On Wed, Aug 14, 2024 at 05:42:01PM +0200, Veronika Molnarova wrote:
> 
> 
> On 8/14/24 17:35, Arnaldo Carvalho de Melo wrote:
> > On Wed, Aug 14, 2024 at 12:32:39PM -0300, Arnaldo Carvalho de Melo wrote:
> >> On Wed, Aug 14, 2024 at 05:17:34PM +0200, vmolnaro@redhat.com wrote:
> >>> From: Veronika Molnarova <vmolnaro@redhat.com>
> >>
> >> Ok? I'm applying it with this change. Thanks,
> > 
> > So I added this to the log message:
> > 
> > Committer notes:
> > 
> > Instead of disabling ShellCheck warnings all the uses of 'uname -n',
> > i.e. those:
> > 
> >   In tests/shell/record.sh line 35:
> >   default_fd_limit=$(ulimit -Sn)
> >                             ^-^ SC3045 (warning): In POSIX sh, ulimit -S is undefined.
> > 
> > We can just switch from using '/bin/sh' to '/bin/bash' for this test, as
> > bash _has_ 'ulimit -n', so ShellCheck will not emit that warning.
> > 
> > There are dozens of 'perf test' shell tests that do just that,
> > '/bin/bash' is a reasonable expectation for those tests.
> > 
> > ----------------------------------------------------------
> > 
> > Please let me know if you find any issues with this course of action,
> > 
> > Thanks,
> > 
> > - Arnaldo
> > 
> If so then the check whether the ulimit is supported doesn't need to be done
> as bash is given as a requirement. Thought that it should be supporting all
> possible shells, even though couldn't find shell not supporting 'ulimit -Sn'.
> 
> Can I send a quick fix that just changes to the '/bin/bash' so that the code
> won't have unnecessary code?

See my last message, I went with your v2 + switch from /bin/sh to
/bin/bash, as you suggest above.

- Arnaldo

  reply	other threads:[~2024-08-14 15:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-14 15:17 [PATCH v3] perf test record.sh: Raise limit of open file descriptors vmolnaro
2024-08-14 15:32 ` Arnaldo Carvalho de Melo
2024-08-14 15:35   ` Arnaldo Carvalho de Melo
2024-08-14 15:42     ` Veronika Molnarova
2024-08-14 15:54       ` Arnaldo Carvalho de Melo [this message]
2024-08-14 15:56         ` Arnaldo Carvalho de Melo
2024-08-14 16:04           ` Veronika Molnarova
2024-08-14 16:39             ` Arnaldo Carvalho de Melo
2024-08-14 15:58         ` Veronika Molnarova
2024-08-14 15:53     ` Arnaldo Carvalho de Melo
  -- strict thread matches above, loose matches on Subject: below --
2024-08-14 15:47 vmolnaro

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=ZrzTS46l3Ct_I0Oj@x1 \
    --to=acme@kernel.org \
    --cc=acme@redhat.com \
    --cc=adrian.hunter@intel.com \
    --cc=atrajeev@linux.vnet.ibm.com \
    --cc=irogers@google.com \
    --cc=jolsa@kernel.org \
    --cc=kjain@linux.ibm.com \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mpetlan@redhat.com \
    --cc=rstoyano@redhat.com \
    --cc=vmolnaro@redhat.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