All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: Vasily Tarasov <vtaras@openvz.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Kirill Korotaev <dev@openvz.org>,
	OpenVZ Developers List <devel@openvz.org>
Subject: Re: [PATCH] cfq: wrong sync writes detection
Date: Mon, 11 Dec 2006 17:08:17 +0100	[thread overview]
Message-ID: <20061211160817.GS4576@kernel.dk> (raw)
In-Reply-To: <200612111545.kBBFjJEl012709@vass.7ka.mipt.ru>

On Mon, Dec 11 2006, Vasily Tarasov wrote:
> CFQ I/O scheduler does the following actions to
> find out whether the request is sync:
> 
> rw = rq_data_dir(rq); => possible values for rw are 0 or 1
> 
> static inline pid_t cfq_queue_pid(struct task_struct *task, int rw)
> {
>         if (rw == READ || rw == WRITE_SYNC) => second condition is always false
>                 return task->pid;
> 
>         return CFQ_KEY_ASYNC;
> }
> 
> The following patch fixes the bug by adding sync parameter,
> wich is obtained through bio_sync macros.

Good catch! Applied.

-- 
Jens Axboe


      reply	other threads:[~2006-12-11 16:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-11 15:45 [PATCH] cfq: wrong sync writes detection Vasily Tarasov
2006-12-11 16:08 ` Jens Axboe [this message]

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=20061211160817.GS4576@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=dev@openvz.org \
    --cc=devel@openvz.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vtaras@openvz.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 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.