All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Domsch <Matt_Domsch@dell.com>
To: axboe@suse.de
Cc: linux-kernel@vger.kernel.org
Subject: rq_flag_bits and bio bi_rw flags
Date: Thu, 17 Aug 2006 17:27:52 -0500	[thread overview]
Message-ID: <20060817222752.GA19442@lists.us.dell.com> (raw)

Jens, I'm hoping you can clear something up for me.

ll_rw_blk.c:
void blk_rq_bio_prep(request_queue_t *q, struct request *rq, struct
bio *bio)
{
        /* first three bits are identical in rq->flags and bio->bi_rw
	*/
        rq->flags |= (bio->bi_rw & 7);

That was recently changed to be the first 2 bits not 3.  But it made
me look.

/*
 * bio bi_rw flags
 *
 * bit 0 -- read (not set) or write (set)
 * bit 1 -- rw-ahead when set
 * bit 2 -- barrier
 * bit 3 -- fail fast, don't want low level driver retries
 * bit 4 -- synchronous I/O hint: the block layer will unplug immediately
 */
#define BIO_RW          0
#define BIO_RW_AHEAD    1
#define BIO_RW_BARRIER  2
#define BIO_RW_FAILFAST 3
#define BIO_RW_SYNC     4


/*
 * first three bits match BIO_RW* bits, important
 */
enum rq_flag_bits {
        __REQ_RW,               /* not set, read. set, write */
        __REQ_FAILFAST,         /* no low level driver retries */
        __REQ_SORTED,           /* elevator knows about this request
	*/


The first bit matches.  The second doesn't (BIO_RW_AHEAD vs
__REQ_FAILFAST).  And obviously you just fixed the third bit.

Should BIO_RW_FAILFAST == __REQ_FAILFAST instead?

Thanks,
Matt

-- 
Matt Domsch
Software Architect
Dell Linux Solutions linux.dell.com & www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com

             reply	other threads:[~2006-08-17 22:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-17 22:27 Matt Domsch [this message]
2006-08-18  6:30 ` rq_flag_bits and bio bi_rw flags 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=20060817222752.GA19442@lists.us.dell.com \
    --to=matt_domsch@dell.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 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.