public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: axboe@suse.de
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: cfq: depth 4 reached, tagging now on
Date: Sat, 19 Feb 2005 15:59:07 -0500	[thread overview]
Message-ID: <1108846748.10705.31.camel@krustophenia.net> (raw)

Starting around 2.6.11-rc4 I get this printk during the boot process
after kjournald starts, and again if I stress the filesystem.

cfq: depth 4 reached, tagging now on

Is this printk intentional?  I am sure users will wonder about it,
especially because (presumably) cfq turns tagging off at some point in
between, and doesn't say anything about it.

Lee



             reply	other threads:[~2005-02-19 20:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-19 20:59 Lee Revell [this message]
2005-02-21  8:20 ` cfq: depth 4 reached, tagging now on Jens Axboe
2005-02-22 21:10   ` Lee Revell
  -- strict thread matches above, loose matches on Subject: below --
2005-03-04  8:52 Chuck Ebbert
2005-03-04  9:00 ` Jens Axboe
2005-03-04 20:33   ` Lee Revell

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=1108846748.10705.31.camel@krustophenia.net \
    --to=rlrevell@joe-job.com \
    --cc=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    /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