public inbox for cluster-cvs@sourceware.org
help / color / mirror / Atom feed
From: cfeist@sourceware.org
To: cluster-cvs@sources.redhat.com, cluster-devel@redhat.com
Subject: Cluster Project tag, dlm-kernel_2_6_9_54, created. gfs-kernel_2_6_9_76-43-g8dc51a6
Date: Mon, 21 Apr 2008 18:32:00 -0000	[thread overview]
Message-ID: <20080421183231.25487.qmail@sourceware.org> (raw)

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


                 reply	other threads:[~2008-04-21 18:32 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20080421183231.25487.qmail@sourceware.org \
    --to=cfeist@sourceware.org \
    --cc=cluster-cvs@sources.redhat.com \
    --cc=cluster-devel@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: 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).