This is the mail archive of the
cluster-cvs@sourceware.org
mailing list for the cluster.
Cluster Project tag, dlm-kernel_2_6_9_54, created. gfs-kernel_2_6_9_76-43-g8dc51a6
- From: cfeist at sourceware dot org
- To: cluster-cvs at sources dot redhat dot com, cluster-devel at redhat dot com
- Date: 21 Apr 2008 18:32:31 -0000
- Subject: Cluster Project tag, dlm-kernel_2_6_9_54, created. gfs-kernel_2_6_9_76-43-g8dc51a6
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Cluster Project".
http://sources.redhat.com/git/gitweb.cgi?p=cluster.git;a=commitdiff;h=8dc51a64cf9a0bc1b467353a4161220a7cec0de0
The tag, dlm-kernel_2_6_9_54 has been created
at 8dc51a64cf9a0bc1b467353a4161220a7cec0de0 (commit)
- Log -----------------------------------------------------------------
commit 8dc51a64cf9a0bc1b467353a4161220a7cec0de0
Author: Christine Caulfield <ccaulfie@redhat.com>
Date: Tue Apr 15 16:34:48 2008 +0100
[DLM] Add tcp_nodelay option to DLM comms
Under some very odd loads, the TCP nagle algorithm can cause
annoying delays in lock traffic. This option allows it to
be switched off with
echo "1" > /proc/cluster/config/dlm/tcp_nodelay
This should NOT be a default, in most cases it will cause
a huge performance drop. It is global to all DLM communications
and cannot be changed per lockspace.
It is included specifically for bz#244708.
Signed-off-by: Christine Caulfield <ccaulfie@redhat.com>
-----------------------------------------------------------------------
hooks/post-receive
--
Cluster Project