All of lore.kernel.org
 help / color / mirror / Atom feed
From: mcatos@ics.forth.gr
To: linux-kernel@vger.kernel.org
Subject: Block device request queue processing question
Date: Sun, 10 Jun 2007 14:01:35 +0300	[thread overview]
Message-ID: <1181473295.466bda0f80347@webmail.ics.forth.gr> (raw)

I am developing a stacking block driver and so far the driver was accepting
requests using the 'make_request' function (without a queue). When I switched to
using a request queue, I noticed that the driver received much more reuquests in a
single call, which is very good for me.

The problem is that the driver must initiate I/O towards the physical device,
which cannot be done inside the function that services the requests. Is there a
way I can process all the request in a context where sleeping is permitted?

I tried to dequeue all the requests using 'blkdev_dequeue_request' but I do not
know how to properly handle request completion.

Thanx in advance.



-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/


                 reply	other threads:[~2007-06-10 11:52 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1181473295.466bda0f80347@webmail.ics.forth.gr \
    --to=mcatos@ics.forth.gr \
    --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.