The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: ooyama eiichi <ooyama@tritech.co.jp>
Cc: linux-kernel@vger.kernel.org
Subject: Re: RAW or BLK in 2.4.21
Date: Fri, 1 Aug 2003 12:27:33 +0200	[thread overview]
Message-ID: <20030801102733.GO7920@suse.de> (raw)
In-Reply-To: <20030801.192419.68158364.ooyama@tritech.co.jp>

On Fri, Aug 01 2003, ooyama eiichi wrote:
> Hi.
> I am developping a block device kernel module in 2.4 series.
> And i want to make a distinction between raw I/O and block I/O,
> in the request function i wrote for my module.
> But i could not find the way.
> 
> my_request_fn(request_queue_t *q, int rw, struct buffer_head * bh)
> 
> Is it possible ?
> I would be happy if someone give me a hint about this.

No, it is not possible to tell the difference inside your request_fn.

-- 
Jens Axboe


  reply	other threads:[~2003-08-01 10:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-01 10:24 RAW or BLK in 2.4.21 ooyama eiichi
2003-08-01 10:27 ` Jens Axboe [this message]
2003-08-01 14:49   ` ooyama eiichi

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=20030801102733.GO7920@suse.de \
    --to=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ooyama@tritech.co.jp \
    /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