From: Jens Axboe <jens.axboe@oracle.com>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: Jeff Moyer <jmoyer@redhat.com>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [PATCH 2/2] cfq-iosched: get rid of the need for __GFP_FAIL in cfq_find_alloc_queue()
Date: Thu, 9 Jul 2009 22:15:11 +0200 [thread overview]
Message-ID: <20090709201510.GU23611@kernel.dk> (raw)
In-Reply-To: <20090709195941.GE30832@redhat.com>
On Thu, Jul 09 2009, Vivek Goyal wrote:
> Sure. Here you go.
>
> In case memory is scarce, we now default to oom_cfqq. Once memory is
> available again, we should allocate a new cfqq and stop using oom_cfqq for
> a particular io context.
>
> Once a new request comes in, check if we are using oom_cfqq, and if yes,
> try to allocate a new cfqq.
>
> Tested the patch by forcing the use of oom_cfqq and upon next request thread
> realized that it was using oom_cfqq and it allocated a new cfqq.
Thanks, applied!
--
Jens Axboe
next prev parent reply other threads:[~2009-07-09 20:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-26 9:05 [PATCH 0/2] cfq-iosched: get rid of __GFP_NOFAIL Jens Axboe
2009-06-26 9:05 ` [PATCH 1/2] cfq-iosched: move cfqq initialization out of cfq_find_alloc_queue() Jens Axboe
2009-06-26 16:09 ` Jeff Moyer
2009-06-26 9:05 ` [PATCH 2/2] cfq-iosched: get rid of the need for __GFP_FAIL in cfq_find_alloc_queue() Jens Axboe
2009-06-26 16:25 ` Jeff Moyer
2009-06-27 18:26 ` Jens Axboe
2009-06-29 13:46 ` Jeff Moyer
2009-06-29 17:34 ` Jens Axboe
2009-06-29 17:44 ` Jeff Moyer
2009-06-29 17:48 ` Jens Axboe
2009-07-09 15:44 ` Vivek Goyal
2009-07-09 17:38 ` Jens Axboe
2009-07-09 19:59 ` Vivek Goyal
2009-07-09 20:15 ` Jens Axboe [this message]
2009-07-01 9:28 ` Shan Wei
2009-07-01 9:32 ` Jens Axboe
2009-07-02 0:49 ` Shan Wei
2009-07-02 6:33 ` Jens Axboe
2009-06-26 16:05 ` [PATCH 0/2] cfq-iosched: get rid of __GFP_NOFAIL Jeff Moyer
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=20090709201510.GU23611@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=jmoyer@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--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