From: Jeff Moyer <jmoyer@redhat.com>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: "Theodore Ts'o" <tytso@mit.edu>, Vivek Goyal <vgoyal@redhat.com>,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [patch,rfc v2] ext3/4: enhance fsync performance when using cfq
Date: Thu, 08 Apr 2010 15:10:58 -0400 [thread overview]
Message-ID: <x497hohpxod.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <20100408110045.GJ10103@kernel.dk> (Jens Axboe's message of "Thu, 8 Apr 2010 13:00:45 +0200")
Jens Axboe <jens.axboe@oracle.com> writes:
>> @@ -2065,7 +2065,7 @@ static void cfq_choose_cfqg(struct cfq_data *cfqd)
>> cfqd->serving_group = cfqg;
>>
>> /* Restore the workload type data */
>> - if (cfqg->saved_workload_slice) {
>> + if (cfqg && cfqg->saved_workload_slice) {
>> cfqd->workload_expires = jiffies + cfqg->saved_workload_slice;
>> cfqd->serving_type = cfqg->saved_workload;
>> cfqd->serving_prio = cfqg->saved_serving_prio;
>
> Unrelated change?
Probably not needed for this incarnation of the patch, though previous
iterations would Oops on boot w/o this. If you look through all of the
code in this code path, cfqg == NULL seems to be handled, so it's
probably safe to take this. I'll pull it out of this patch, though.
>> +static void cfq_yield(struct request_queue *q)
>> +{
>> + struct cfq_data *cfqd = q->elevator->elevator_data;
>> + struct cfq_io_context *cic;
>> + struct cfq_queue *cfqq;
>> + unsigned long flags;
>> +
>> + cic = cfq_cic_lookup(cfqd, current->io_context);
>> + if (!cic)
>> + return;
>> +
>> + spin_lock_irqsave(q->queue_lock, flags);
>
> spin_lock_irq() is sufficient here.
OK, thanks!
Jeff
prev parent reply other threads:[~2010-04-08 19:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-07 21:18 [patch,rfc v2] ext3/4: enhance fsync performance when using cfq Jeff Moyer
2010-04-07 21:46 ` Vivek Goyal
2010-04-08 11:04 ` Jens Axboe
2010-04-08 14:05 ` Vivek Goyal
2010-04-08 14:09 ` Jens Axboe
2010-04-08 14:17 ` Vivek Goyal
2010-04-08 14:24 ` Jeff Moyer
2010-04-08 19:23 ` Jens Axboe
2010-04-21 20:42 ` Mike Snitzer
2010-04-21 20:52 ` Jeff Moyer
2010-04-08 11:00 ` Jens Axboe
2010-04-08 13:59 ` Vivek Goyal
2010-04-08 14:03 ` Jens Axboe
2010-04-08 14:03 ` Jeff Moyer
2010-04-08 14:06 ` Jens Axboe
2010-04-08 14:10 ` Vivek Goyal
2010-04-08 14:25 ` Jeff Moyer
2010-04-08 14:31 ` Vivek Goyal
2010-04-08 19:10 ` 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=x497hohpxod.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@redhat.com \
--cc=jens.axboe@oracle.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=vgoyal@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).