public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@gmail.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Jens Axboe <jaxboe@fusionio.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] block: separate priority boosting from REQ_META
Date: Tue, 23 Aug 2011 11:05:48 +0900	[thread overview]
Message-ID: <87r54cg9vn.fsf@gmail.com> (raw)
In-Reply-To: <20110822165221.GB7257@infradead.org> (Christoph Hellwig's message of "Mon, 22 Aug 2011 12:52:21 -0400")

Hello,


Christoph Hellwig <hch@infradead.org> writes:
> Add a new REQ_PRIO to let requests preempt others in the cfq I/O schedule,
> and lave REQ_META purely for marking requests as metadata in blktrace.
>
> All existing callers of REQ_META except for XFS are updated to also
> set REQ_PRIO for now.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
>

snipped...

> Index: linux-2.6/include/linux/blk_types.h
> ===================================================================
> --- linux-2.6.orig/include/linux/blk_types.h	2011-08-22 04:25:50.373473791 +0200
> +++ linux-2.6/include/linux/blk_types.h	2011-08-22 04:26:44.443473870 +0200
> @@ -124,6 +124,7 @@ enum rq_flag_bits {
>  
>  	__REQ_SYNC,		/* request is sync (sync write or read) */
>  	__REQ_META,		/* metadata io request */
> +	__REQ_PRIO,

It'd be better if it's commented too, IMHO.


>  	__REQ_DISCARD,		/* request to discard sectors */
>  	__REQ_SECURE,		/* secure discard (used with __REQ_DISCARD) */
>  
> @@ -161,13 +162,14 @@ enum rq_flag_bits {
>  #define REQ_FAILFAST_DRIVER	(1 << __REQ_FAILFAST_DRIVER)
>  #define REQ_SYNC		(1 << __REQ_SYNC)
>  #define REQ_META		(1 << __REQ_META)
> +#define REQ_PRIO		(1 << __REQ_PRIO)
>  #define REQ_DISCARD		(1 << __REQ_DISCARD)
>  #define REQ_NOIDLE		(1 << __REQ_NOIDLE)
>  
>  #define REQ_FAILFAST_MASK \
>  	(REQ_FAILFAST_DEV | REQ_FAILFAST_TRANSPORT | REQ_FAILFAST_DRIVER)
>  #define REQ_COMMON_MASK \
> -	(REQ_WRITE | REQ_FAILFAST_MASK | REQ_SYNC | REQ_META | REQ_DISCARD | \
> +	(REQ_WRITE | REQ_FAILFAST_MASK | REQ_SYNC | REQ_PRIO | REQ_DISCARD | \
>  	 REQ_NOIDLE | REQ_FLUSH | REQ_FUA | REQ_SECURE)
>  #define REQ_CLONE_MASK		REQ_COMMON_MASK
>  

I think you need to include REQ_META into REQ_COMMON_MASK in order to
track those requests using blktrace.

Thanks.

  reply	other threads:[~2011-08-23  2:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-19 13:16 [GIT PULL] block bits for 3.1-rc Jens Axboe
2011-08-19 17:50 ` Linus Torvalds
2011-08-19 17:57   ` Jens Axboe
2011-08-20 17:41 ` Christoph Hellwig
2011-08-20 19:15   ` Mike Snitzer
2011-08-21 17:56   ` Jens Axboe
2011-08-21 18:19     ` Christoph Hellwig
2011-08-21 18:37       ` Jens Axboe
2011-08-22 16:52         ` [PATCH 1/2] block: remove READ_META and WRITE_META Christoph Hellwig
2011-08-22 16:52         ` [PATCH 2/2] block: separate priority boosting from REQ_META Christoph Hellwig
2011-08-23  2:05           ` Namhyung Kim [this message]
2011-08-23 10:09             ` [PATCH 2/2 v2] " Christoph Hellwig
2011-08-23 12:31               ` Namhyung Kim
2011-08-23 12:52               ` Jens Axboe

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=87r54cg9vn.fsf@gmail.com \
    --to=namhyung@gmail.com \
    --cc=hch@infradead.org \
    --cc=jaxboe@fusionio.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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