From: Jens Axboe <axboe@kernel.dk>
To: Jan Kara <jack@suse.cz>
Cc: Tejun Heo <tj@kernel.org>,
linux-kernel@vger.kernel.org, Jeff Moyer <jmoyer@redhat.com>
Subject: Re: [PATCH 0/5 v3] SYNC_NOIDLE preemption for ancestor cgroups
Date: Thu, 4 Feb 2016 09:47:20 -0700 [thread overview]
Message-ID: <56B38098.6000703@kernel.dk> (raw)
In-Reply-To: <20160204164344.GA28384@quack.suse.cz>
On 02/04/2016 09:43 AM, Jan Kara wrote:
> On Tue 12-01-16 10:10:35, Jens Axboe wrote:
>> On 01/12/2016 08:24 AM, Jan Kara wrote:
>>> Hello Jens,
>>>
>>> This is v3 of the patch series.
>>>
>>> Changes since v2:
>>> * added acks from Tejun
>>> * fixed some typos pointed out by Tejun
>>> * fixed condition checking for too long think time in patch 1/5
>>>
>>> Changes since v1:
>>> * added missing export of cgroup_is_descendant()
>>>
>>> If you find the series too hasty for the current merge window, just postpone it
>>> for the next one.
>>
>> This series looks good to me, I'd like to push it in this round. Good work,
>> Jan!
>
> So did this happen? I don't see patches anywhere in your tree or in Linus'?
Spinning it off real soon, it'll get there.
--
Jens Axboe
prev parent reply other threads:[~2016-02-04 16:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-12 15:24 [PATCH 0/5 v3] SYNC_NOIDLE preemption for ancestor cgroups Jan Kara
2016-01-12 15:24 ` [PATCH 1/5] cfq-iosched: Don't group_idle if cfqq has big thinktime Jan Kara
2016-01-12 16:17 ` Tejun Heo
2016-01-12 15:24 ` [PATCH 2/5] cfq-iosched: Reorder checks in cfq_should_preempt() Jan Kara
2016-01-12 15:24 ` [PATCH 3/5] cfq-iosched: Allow sync noidle workloads to preempt each other Jan Kara
2016-01-12 15:24 ` [PATCH 4/5] cgroup: Export cgroup_is_descendant() Jan Kara
2016-01-12 15:24 ` [PATCH 5/5] cfq-iosched: Allow parent cgroup to preempt its child Jan Kara
2016-01-12 17:10 ` [PATCH 0/5 v3] SYNC_NOIDLE preemption for ancestor cgroups Jens Axboe
2016-02-04 16:43 ` Jan Kara
2016-02-04 16:47 ` Jens Axboe [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=56B38098.6000703@kernel.dk \
--to=axboe@kernel.dk \
--cc=jack@suse.cz \
--cc=jmoyer@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@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 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.