From: Mark Fasheh <mark.fasheh@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [patch 2/3]OCFS2: allow the ocfs2 heartbeat thread to prioritize I/O --revision 3
Date: Mon Dec 11 14:38:05 2006 [thread overview]
Message-ID: <20061211223801.GD6831@ca-server1.us.oracle.com> (raw)
In-Reply-To: <4579B3C00200000400262DB0@lucius.provo.novell.com>
On Fri, Dec 08, 2006 at 12:48:35AM -0700, Zhen Wei wrote:
> --- trunk.orig/mount.ocfs2/mount.ocfs2.c 2006-12-08 15:09:42.000000000 +0800
> +++ trunk/mount.ocfs2/mount.ocfs2.c 2006-12-08 15:17:59.000000000 +0800
> @@ -393,6 +393,7 @@ int main(int argc, char **argv)
> goto bail;
> }
>
> + run_hb_ctl (hb_ctl_path, mo.dev, "-P");
Don't we need to add another argument for the actual priority value?
--Mark
--
Mark Fasheh
Senior Software Developer, Oracle
mark.fasheh@oracle.com
next prev parent reply other threads:[~2006-12-11 14:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-07 23:49 [Ocfs2-devel] [patch 2/3]OCFS2: allow the ocfs2 heartbeat thread to prioritize I/O --revision 3 Zhen Wei
2006-12-11 14:38 ` Mark Fasheh [this message]
2006-12-11 15:27 ` Mark Fasheh
-- strict thread matches above, loose matches on Subject: below --
2006-12-07 23:49 Zhen Wei
2006-12-08 17:20 ` Mark Fasheh
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=20061211223801.GD6831@ca-server1.us.oracle.com \
--to=mark.fasheh@oracle.com \
--cc=ocfs2-devel@oss.oracle.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 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.