Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1391281
| Path | csiph.com!eternal-september.org!feeder.eternal-september.org!border1.nntp.ams1.giganews.com!nntp.giganews.com!news.panservice.it!bofh.it!news.nic.it!robomod |
|---|---|
| From | Jeff Moyer <jmoyer@redhat.com> |
| Newsgroups | linux.kernel |
| Subject | Re: Question about request queues in I/O scheduling |
| Date | Fri, 29 Apr 2016 18:30:05 +0200 |
| Message-ID | <rtjsN-HD-77@gated-at.bofh.it> (permalink) |
| References | <rrxgt-Hd-9@gated-at.bofh.it> <rtiGl-8rB-1@gated-at.bofh.it> <rtjsN-HD-79@gated-at.bofh.it> |
| X-Original-To | Max Kanushin <rextuz@gmail.com> |
| X-PGP-Keyid | 1F78E1B4 |
| X-PGP-Certkey | F6FE 280D 8293 F72C 65FD 5A58 1FF8 A7CA 1F78 E1B4 |
| X-Pcloadletter | What the f**k does that mean? |
| User-Agent | Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) |
| MIME-Version | 1.0 |
| Content-Type | text/plain |
| X-Scanned-By | MIMEDefang 2.68 on 10.5.11.27 |
| Sender | robomod@news.nic.it |
| List-ID | <linux-kernel.vger.kernel.org> |
| X-Mailing-List | linux-kernel@vger.kernel.org |
| Approved | robomod@news.nic.it |
| Lines | 46 |
| Organization | linux.* mail to news gateway |
| X-Original-Cc | linux-kernel@vger.kernel.org |
| X-Original-Date | Fri, 29 Apr 2016 12:22:48 -0400 |
| X-Original-Message-ID | <x494makcrl3.fsf@segfault.boston.devel.redhat.com> |
| X-Original-References | <571D1390.6060204@gmail.com> <x49d1p8ctxu.fsf@segfault.boston.devel.redhat.com> <CAL+kshPDB8j3j7Gp4Zm5WK3W8HbO2pm3SQcB28p0LMF3KtdOBQ@mail.gmail.com> |
| X-Original-Sender | linux-kernel-owner@vger.kernel.org |
| Xref | csiph.com linux.kernel:1391281 |
Show key headers only | View raw
Max Kanushin <rextuz@gmail.com> writes: > Thank you very much for the reply. My general idea is take control of all > request queues to block and unblock them manually depending on their load. > One of my steps is to find a length of a queue to decide if to block it. > Actually I think I've found the way. If I got it right, I can move from one > request to another within the list: > struct list_head queue_head; > So that I can calculate how many requests are there in the queue. Hi, Max, The queue_head is the dispatch list for I/O, so it does not represent all I/O queued for a request_queue. The number of requests in the scheduler would be reflected by q->nr_sorted. The number of dispatched requests is in an array, in_flight. Cheers, Jeff > > Best regards, > Max Kanushin. > On Apr 29, 2016 6:32 PM, "Jeff Moyer" <jmoyer@redhat.com> wrote: > >> Max Kanushin <rextuz@gmail.com> writes: >> >> > 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? >> >> Hi, Max, >> >> What exactly are you trying to accomplish? >> >> Cheers, >> Jeff >>
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: Question about request queues in I/O scheduling Jeff Moyer <jmoyer@redhat.com> - 2016-04-29 17:40 +0200
Re: Question about request queues in I/O scheduling Jeff Moyer <jmoyer@redhat.com> - 2016-04-29 18:30 +0200
Re: Question about request queues in I/O scheduling Max Kanushin <rextuz@gmail.com> - 2016-05-12 07:40 +0200
csiph-web