mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: Bagas Sanjaya <bagasdotme@gmail.com>, corbet@lwn.net
Cc: sshefali021@gmail.com, kstewart@linuxfoundation.org,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH v2] docs: add workload-tracing document to admin-guide
Date: Mon, 30 Jan 2023 16:19:48 -0700	[thread overview]
Message-ID: <d532dc0c-4a5d-986e-19d4-1c90071d2cdb@linuxfoundation.org> (raw)
In-Reply-To: <Y9STCwt2FnYf4/X4@debian.me>

On 1/27/23 20:14, Bagas Sanjaya wrote:
> On Fri, Jan 27, 2023 at 04:46:16PM -0700, Shuah Khan wrote:
>> +strace tool can be used to trace system calls made by a process and signals
>> +it receives. a process to the perf, stress-ng, paxtest workloads. System
> 
> "... to trace system calls made by a process (which can be perf, stress-ng,
> paxtest workloads, or neither)."
> 
>> +Before we can get started we will have to get our system ready. We assume
> 
> "Before we can get started the system must be prepared first."
> 
>> +Browsing kernel sources ::
> 
> "To browse kernel sources, you will need:"
> 
>> +Workload overview
>> +=================
>> +
>> +We used strace to trace perf bench, stress-ng and paxtest workloads to
> 
> "In this section, we use strace to trace ..."
> 

Thank you for the review. I will address them in v3.

thanks,
-- Shuah


  reply	other threads:[~2023-01-30 23:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-27 23:46 Shuah Khan
2023-01-28  3:14 ` Bagas Sanjaya
2023-01-30 23:19   ` Shuah Khan [this message]
2023-01-28  5:40 ` Randy Dunlap
2023-01-30 23:20   ` Shuah Khan
2023-01-28  8:35 ` Thorsten Leemhuis
2023-01-30 23:30   ` Shuah Khan
2023-01-30 23:52     ` Jonathan Corbet
2023-01-31 19:20       ` Shuah Khan

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=d532dc0c-4a5d-986e-19d4-1c90071d2cdb@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=bagasdotme@gmail.com \
    --cc=corbet@lwn.net \
    --cc=kstewart@linuxfoundation.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sshefali021@gmail.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
Powered by JetHome