From: Luca Abeni <luca.abeni@santannapisa.it>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Juri Lelli <juri.lelli@arm.com>,
Claudio Scordino <claudio@evidence.eu.com>,
Steven Rostedt <rostedt@goodmis.org>,
Tommaso Cucinotta <tommaso.cucinotta@sssup.it>,
Daniel Bristot de Oliveira <bristot@redhat.com>,
Joel Fernandes <joelaf@google.com>,
Mathieu Poirier <mathieu.poirier@linaro.org>
Subject: Re: [RFC v5 2/9] sched/deadline: improve the tracking of active utilization
Date: Tue, 25 Jul 2017 08:46:29 +0200 [thread overview]
Message-ID: <20170725084629.7a6b9837@luca> (raw)
In-Reply-To: <20170724091130.y2hldaqdgxtxdskg@hirez.programming.kicks-ass.net>
On Mon, 24 Jul 2017 11:11:30 +0200
Peter Zijlstra <peterz@infradead.org> wrote:
> On Mon, Jul 24, 2017 at 09:54:54AM +0200, Luca Abeni wrote:
> > Hi Peter,
> >
> > I put this change in a local tree together with other fixes / cleanups
> > I plan to submit in the next weeks. Should I send it together with the
> > other patches, or are you going to apply it separately?
>
> Posting them in a series is fine; it is customary to put independent
> things first such that they will not get stuck after the larger changes.
>
> > In the first case, what is the correct authorship / SOB chain (I ask
> > because I keep getting this wrong every time :)
>
> Yes, this is a 'fun' case :-) I'd just merge the change into your patch
> introducing it and forget I 'contributed' the name change.
I think this patch is independent from the other patches I have in my
tree... So, I will go for the solution you describe below.
Thanks,
Luca
>
> For larger patches you could do something like (in your email body):
>
>
> From: Peter Zijlstra <peterz@infradead.org>
>
> Changelog goes here...
>
> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
> Signed-off-by: Luca...
> ---
>
> $PATCH
>
>
> Which says this patch is from me, carried by you, and then I'll stick
> another SoB on to indicated I took it back. Its a bit weird, but we've
> done it before.
next prev parent reply other threads:[~2017-07-25 6:46 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-24 3:52 [RFC v5 0/9] CPU reclaiming for SCHED_DEADLINE luca abeni
2017-03-24 3:52 ` [RFC v5 1/9] sched/deadline: track the active utilization luca abeni
2017-03-26 17:04 ` Mathieu Poirier
2017-03-26 20:55 ` luca abeni
2017-03-24 3:52 ` [RFC v5 2/9] sched/deadline: improve the tracking of " luca abeni
2017-03-24 13:20 ` Peter Zijlstra
2017-03-24 21:47 ` luca abeni
2017-03-25 2:31 ` Steven Rostedt
2017-03-27 8:20 ` Luca Abeni
2017-03-27 8:54 ` Claudio Scordino
2017-03-27 7:17 ` Juri Lelli
2017-03-27 7:43 ` Luca Abeni
2017-03-27 8:45 ` Juri Lelli
2017-03-27 7:36 ` Luca Abeni
2017-07-24 8:06 ` Luca Abeni
2017-07-24 9:04 ` Peter Zijlstra
2017-07-25 6:41 ` Luca Abeni
2017-03-24 13:23 ` Peter Zijlstra
2017-07-24 7:54 ` Luca Abeni
2017-07-24 9:11 ` Peter Zijlstra
2017-07-25 6:46 ` Luca Abeni [this message]
2017-03-26 17:32 ` Mathieu Poirier
2017-03-26 21:01 ` luca abeni
2017-03-24 3:52 ` [RFC v5 3/9] sched/deadline: fix the update of the total -deadline utilization luca abeni
2017-03-24 3:52 ` [RFC v5 4/9] sched/deadline: implement GRUB accounting luca abeni
2017-03-24 3:52 ` [RFC v5 5/9] sched/deadline: do not reclaim the whole CPU bandwidth luca abeni
2017-03-24 14:00 ` Peter Zijlstra
2017-03-24 21:58 ` luca abeni
2017-03-25 2:38 ` Steven Rostedt
2017-03-27 8:35 ` Peter Zijlstra
2017-03-24 3:52 ` [RFC v5 6/9] sched/deadline: make GRUB a task's flag luca abeni
2017-03-24 3:53 ` [RFC v5 7/9] sched/deadline: track the "total rq utilization" too luca abeni
2017-03-24 3:53 ` [RFC v5 8/9] sched/deadline: base GRUB reclaiming on the inactive utilization luca abeni
2017-03-27 14:26 ` Peter Zijlstra
2017-03-27 14:56 ` Luca Abeni
2017-03-27 15:53 ` Peter Zijlstra
2017-03-27 17:02 ` luca abeni
2017-05-08 7:41 ` Luca Abeni
2017-05-08 8:06 ` Peter Zijlstra
2017-05-09 9:37 ` Luca Abeni
2017-03-24 3:53 ` [RFC v5 9/9] sched/deadline: also reclaim bandwidth not used by dl tasks luca abeni
2017-03-27 14:03 ` Peter Zijlstra
2017-03-27 14:48 ` Luca Abeni
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=20170725084629.7a6b9837@luca \
--to=luca.abeni@santannapisa.it \
--cc=bristot@redhat.com \
--cc=claudio@evidence.eu.com \
--cc=joelaf@google.com \
--cc=juri.lelli@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tommaso.cucinotta@sssup.it \
/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