From: Jeff Moyer <jmoyer@redhat.com>
To: Corrado Zoccolo <czoccolo@gmail.com>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>,
Jens Axboe <jens.axboe@oracle.com>
Subject: Re: [RFC V2 PATCH 2/5] cfq-iosched: preparation to handle multiple service trees
Date: Wed, 21 Oct 2009 12:27:26 -0400 [thread overview]
Message-ID: <x49y6n47lw1.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <4e5e476b0910210925v7b44273flc22827d21fa1d6b9@mail.gmail.com> (Corrado Zoccolo's message of "Wed, 21 Oct 2009 18:25:47 +0200")
Corrado Zoccolo <czoccolo@gmail.com> writes:
> Hi Jeff,
> On Wed, Oct 21, 2009 at 5:31 PM, Jeff Moyer <jmoyer@redhat.com> wrote:
>> Corrado Zoccolo <czoccolo@gmail.com> writes:
>>
>>> We embed a pointer to the service tree in each queue, to handle multiple
>>> service trees easily.
>>> Service trees are enriched with a counter.
>>> cfq_add_rq_rb is invoked after putting the rq in the fifo, to ensure
>>> that all fields in rq are properly initialized.
>>>
>>> @@ -115,6 +116,9 @@ struct cfq_queue {
>>> unsigned short ioprio_class, org_ioprio_class;
>>>
>>> pid_t pid;
>>> +
>>> + struct cfq_rb_root *service_tree;
>>> + struct cfq_io_context *cic;
>>> };
>>
>> This change worries me. For async queues, there is not a 1:1 mapping
>> between cfqq and cic.
>
> Currently, I need it only for sync queues. And it is used only to
> determine if a queue is seeky, so if we can mark it in the queue
> instead of the cic, this will not be needed any more.
Ah ha! I have the same requirement for breaking the queues apart, so I
think this won't be an issue.
Thanks!
Jeff
prev parent reply other threads:[~2009-10-21 16:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-20 18:11 Corrado Zoccolo
2009-10-21 15:31 ` Jeff Moyer
2009-10-21 16:25 ` Corrado Zoccolo
2009-10-21 16:27 ` Jeff Moyer [this message]
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=x49y6n47lw1.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@redhat.com \
--cc=czoccolo@gmail.com \
--cc=jens.axboe@oracle.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
all inboxes | Powered by JetHome®