public inbox for cluster-cvs@sourceware.org help / color / mirror / Atom feed
From: teigland@sourceware.org To: cluster-cvs@sources.redhat.com Subject: cluster/group/gfs_controld main.c plock.c Date: Tue, 14 Nov 2006 20:33:00 -0000 [thread overview] Message-ID: <20061114203333.8240.qmail@sourceware.org> (raw) CVSROOT: /cvs/cluster Module name: cluster Branch: RHEL5 Changes by: teigland@sourceware.org 2006-11-14 20:33:33 Modified files: group/gfs_controld: main.c plock.c Log message: Add plock rate limit option -l <limit>. Current default is no limit (0). If a limit is set, gfs_controld will send no more than <limit> plock operations (multicast messages) every second. Given a limit of 10, one file system where plocks are used, and a program that does a tight loop of fcntl lock/unlock operations, the max number of loop iterations in 1 second would be 5. If eight nodes were all doing this there would be 80 total network multicasts every second from all nodes in the cluster. We also record the volume of plock messages accepted locally and received from the network in the debug log. A log entry is written for every 1000 locally accepted plock operations and for every 1000 operations received from the network. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/group/gfs_controld/main.c.diff?cvsroot=cluster&only_with_tag=RHEL5&r1=1.18&r2=1.18.2.1 http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/group/gfs_controld/plock.c.diff?cvsroot=cluster&only_with_tag=RHEL5&r1=1.25&r2=1.25.2.1
next reply other threads:[~2006-11-14 20:33 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-11-14 20:33 teigland [this message] -- strict thread matches above, loose matches on Subject: below -- 2006-11-14 21:31 teigland 2006-11-14 20:20 teigland 2006-10-09 21:49 teigland
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=20061114203333.8240.qmail@sourceware.org \ --to=teigland@sourceware.org \ --cc=cluster-cvs@sources.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: linkBe 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 read-only IMAP folder(s) and NNTP newsgroup(s).