From: Jeff Moyer <jmoyer@redhat.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: Tejun Heo <tj@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] core block IO bits for 3.8
Date: Mon, 17 Dec 2012 12:15:01 -0500 [thread overview]
Message-ID: <x49ehiowqga.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <50CF50AA.7080600@kernel.dk> (Jens Axboe's message of "Mon, 17 Dec 2012 18:04:42 +0100")
Jens Axboe <axboe@kernel.dk> writes:
> On 2012-12-17 18:00, Tejun Heo wrote:
>> On Mon, Dec 17, 2012 at 11:06:39AM -0500, Jeff Moyer wrote:
>>> Jens Axboe <axboe@kernel.dk> writes:
>>>
>>>> - Export control of bdi flusher thread CPU mask and default to using the
>>>> home node (if known) from Jeff.
>>>
>>> I certainly wouldn't mind this going in, but I think Tejun NACKed this
>>> patch. Tejun?
>>
>> Hmm... yeah, I would much prefer if this doesn't go in this time. I
>> think we need something more generic for threadpools w/ scheduling
>> restrictions. It would be possible to retrofit so that the interface
>> eventually matches but given that this feature isn't an immediate
>> must-have thing, I think it would be better to not do this right now.
>
> OK, if you have something generic for threadpools in mind, we can wait
> with this one. I just thought that a "real" interface was nicer than
> manual setting, especially since the flusher threads come and go. Then
> you'd need some udev hook to get it set, not even sure how easy that
> would be with the weird linkage.
>
> Jeff, lets default to the node mask at least. Can you resend a patch
> that doesn't add the API, but just defaults to setting the affinity to
> the cpu mask of the home node?
Well, it turns out that the numa node is always -1, since bdi devices
always have a null parent. I have a patch set to clean that up, but it
depends on my other numa patches in the scsi area that will hopefully
go in 3.9.
> Linus, how do you want to handle this? I can do a revert and re-send a
> pull.
For now, I think it would be cleanest if we just reverted the change.
Cheers,
Jeff
next prev parent reply other threads:[~2012-12-17 17:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-17 15:34 Jens Axboe
2012-12-17 16:06 ` Jeff Moyer
2012-12-17 17:00 ` Tejun Heo
2012-12-17 17:04 ` Jens Axboe
2012-12-17 17:08 ` Linus Torvalds
2012-12-17 17:09 ` Jens Axboe
2012-12-17 17:15 ` Jeff Moyer [this message]
2012-12-17 19:06 ` Jens Axboe
2012-12-17 19:27 ` Linus Torvalds
2012-12-17 19:28 ` Jens Axboe
2012-12-17 19:38 ` Shentino
2012-12-17 17:47 ` Tejun Heo
2012-12-17 19:07 ` 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=x49ehiowqga.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@redhat.com \
--cc=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.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®