From: Jens Axboe <jaxboe@fusionio.com>
To: Jeff Moyer <jmoyer@redhat.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
Zach Brown <zab@redhat.com>, Dave Chinner <david@fromorbit.com>,
"jeder@redhat.com" <jeder@redhat.com>
Subject: Re: [patch,v3] bdi: add a user-tunable cpu_list for the bdi flusher threads
Date: Wed, 5 Dec 2012 20:13:28 +0100 [thread overview]
Message-ID: <50BF9CD8.4020209@fusionio.com> (raw)
In-Reply-To: <x49ip8g9w66.fsf@segfault.boston.devel.redhat.com>
On 2012-12-05 19:43, Jeff Moyer wrote:
> In realtime environments, it may be desirable to keep the per-bdi
> flusher threads from running on certain cpus. This patch adds a
> cpu_list file to /sys/class/bdi/* to enable this. The default is to tie
> the flusher threads to the same numa node as the backing device (though
> I could be convinced to make it a mask of all cpus to avoid a change in
> behaviour).
This looks fine to me now. I'll queue it up for 3.8.
--
Jens Axboe
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Jens Axboe <jaxboe@fusionio.com>
To: Jeff Moyer <jmoyer@redhat.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
Zach Brown <zab@redhat.com>, Dave Chinner <david@fromorbit.com>,
"jeder@redhat.com" <jeder@redhat.com>
Subject: Re: [patch,v3] bdi: add a user-tunable cpu_list for the bdi flusher threads
Date: Wed, 5 Dec 2012 20:13:28 +0100 [thread overview]
Message-ID: <50BF9CD8.4020209@fusionio.com> (raw)
In-Reply-To: <x49ip8g9w66.fsf@segfault.boston.devel.redhat.com>
On 2012-12-05 19:43, Jeff Moyer wrote:
> In realtime environments, it may be desirable to keep the per-bdi
> flusher threads from running on certain cpus. This patch adds a
> cpu_list file to /sys/class/bdi/* to enable this. The default is to tie
> the flusher threads to the same numa node as the backing device (though
> I could be convinced to make it a mask of all cpus to avoid a change in
> behaviour).
This looks fine to me now. I'll queue it up for 3.8.
--
Jens Axboe
next prev parent reply other threads:[~2012-12-05 19:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-05 18:43 [patch,v3] bdi: add a user-tunable cpu_list for the bdi flusher threads Jeff Moyer
2012-12-05 18:43 ` Jeff Moyer
2012-12-05 19:13 ` Jens Axboe [this message]
2012-12-05 19:13 ` Jens Axboe
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=50BF9CD8.4020209@fusionio.com \
--to=jaxboe@fusionio.com \
--cc=david@fromorbit.com \
--cc=jeder@redhat.com \
--cc=jmoyer@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=zab@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.