public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Max Kanushin <rextuz@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Question about request queues in I/O scheduling
Date: Sun, 24 Apr 2016 21:42:24 +0300	[thread overview]
Message-ID: <571D1390.6060204@gmail.com> (raw)

Hello,

I was searching for a way to find out the length of a request_queue 
(that is defined as a structure in linux/include/linux/blkdev.h). 
However I am new to the kernel development and can't figure out where is 
the actual list of requests to be processed by an elevator.
Is there a way to iterate requests in a queue or at least find a number 
of them?

Please make a personal CC for me. I will really appreciate your help.
Best regards

   Max Kanushin.

             reply	other threads:[~2016-04-24 18:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-24 18:42 Max Kanushin [this message]
2016-04-29 15:31 ` Question about request queues in I/O scheduling Jeff Moyer
     [not found]   ` <CAL+kshPDB8j3j7Gp4Zm5WK3W8HbO2pm3SQcB28p0LMF3KtdOBQ@mail.gmail.com>
2016-04-29 16:22     ` Jeff Moyer
2016-05-12  5:33       ` Max Kanushin

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=571D1390.6060204@gmail.com \
    --to=rextuz@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox