All of lore.kernel.org
 help / color / mirror / Atom feed
From: agk@sourceware.org
To: dm-cvs@sourceware.org, dm-devel@redhat.com
Subject: device-mapper ./WHATS_NEW lib/libdm-common.c
Date: 5 Dec 2007 18:57:38 -0000	[thread overview]
Message-ID: <20071205185738.16401.qmail@sourceware.org> (raw)

CVSROOT:	/cvs/dm
Module name:	device-mapper
Changes by:	agk@sourceware.org	2007-12-05 18:57:34

Modified files:
	.              : WHATS_NEW 
	lib            : libdm-common.c 

Log message:
	Fix minimum readahead debug message.

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/device-mapper/WHATS_NEW.diff?cvsroot=dm&r1=1.214&r2=1.215
http://sourceware.org/cgi-bin/cvsweb.cgi/device-mapper/lib/libdm-common.c.diff?cvsroot=dm&r1=1.54&r2=1.55

--- device-mapper/WHATS_NEW	2007/12/05 17:14:30	1.214
+++ device-mapper/WHATS_NEW	2007/12/05 18:57:33	1.215
@@ -1,5 +1,6 @@
 Version 1.02.24 -
 ===================================
+  Fix minimum readahead debug message.
 
 Version 1.02.23 - 5th December 2007
 ===================================
--- device-mapper/lib/libdm-common.c	2007/12/05 14:11:26	1.54
+++ device-mapper/lib/libdm-common.c	2007/12/05 18:57:34	1.55
@@ -438,8 +438,8 @@
 			return_0;
 
 		if (current_read_ahead > read_ahead) {
-			log_debug("%s: read ahead %" PRIu32
-				  " below minimum of %" PRIu32,
+			log_debug("%s: retaining kernel read ahead of %" PRIu32
+				  " (requested %" PRIu32 ")",           
 				  dev_name, current_read_ahead, read_ahead);
 			return 1;
 		}

             reply	other threads:[~2007-12-05 18:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-05 18:57 agk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-12-13  2:25 device-mapper ./WHATS_NEW lib/libdm-common.c agk
2007-12-14 17:26 agk

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=20071205185738.16401.qmail@sourceware.org \
    --to=agk@sourceware.org \
    --cc=dm-cvs@sourceware.org \
    --cc=dm-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 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.