All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brett Russ <bruss@netezza.com>
To: linux-btrace@vger.kernel.org
Subject: Re: [PATCH] blktrace: disallow -o when using multiple devices
Date: Thu, 16 Sep 2010 14:20:51 +0000	[thread overview]
Message-ID: <4C9227C3.7000404@netezza.com> (raw)

On 09/16/2010 08:33 AM, Alan D. Brunelle wrote:
> Document that "-o" does not work when specyfing multiple devices to
> blktrace, also: enforce this by stopping blktrace when one tries do
> do this.
>
> The technical reason why "-o" doesn't work with multiple devices is
> because we use multiple threads of execution - one per device/CPU pair -
> and each of them opens a file named "<prefix>.blktrace.<cpu>". With the
> "-o" all of the"<prefix>" values are the same - so multiple threads
> open the same file and try to do output. Not good. Without the "-o"
> we get unique files named: "<device>.blktrace.<cpu>"  - as the tuple
> (<device>,<cpu>) is unique.

Alan,

-Wouldn't it be a good idea to just add <prefix> before the filename(s) 
that would have been created in either the single or multiple device 
case?  I.e. in the multiple device case, how about 
"<prefix>.<device>.blktrace.<cpu>"?  That way the program always does 
what the user wants, no special case documentation required.

-I just tested that the blktrace "-D" option (output dir, create if 
doesn't exist) works for the multiple device case as long as the -o 
option isn't also used.  So, this is another alternative.

-I found the following inconsistencies between the doc and the command 
line help, these would probably be a separate patch:
--blktrace
---doc is missing -[Dhlps]
---doc still contains deprecated option -k
--blkparse
---doc is missing -[aAD]
---doc still contains deprecated option -m


Thanks,
Brett

             reply	other threads:[~2010-09-16 14:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-16 14:20 Brett Russ [this message]
2010-09-16 21:17 ` [PATCH] blktrace: disallow -o when using multiple devices Brett Russ
2010-09-20 14:35 ` Alan D. Brunelle
2010-09-20 14:39 ` Brett Russ

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=4C9227C3.7000404@netezza.com \
    --to=bruss@netezza.com \
    --cc=linux-btrace@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.