From: Peter Zijlstra <peterz@infradead.org>
To: Yong Zhang <yong.zhang0@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
rusty <rusty@rustcorp.com.au>
Subject: Re: [RFC 0/2 PATCH] remove member rt_se from struct rt_rq
Date: Fri, 29 Jan 2010 17:51:07 +0100 [thread overview]
Message-ID: <1264783867.24455.11.camel@laptop> (raw)
In-Reply-To: <2674af741001282256l3058d356p752b49c024c47e1c@mail.gmail.com>
On Fri, 2010-01-29 at 14:56 +0800, Yong Zhang wrote:
> member rt_se of struct rt_rq is a duplicate of tg->rt_se[cpu].
> So we can remove one of them. After checking CFS, I think
> rt_rq->rt_se can be removed for some kinds of consistence.
Looks good I think.
next prev parent reply other threads:[~2010-01-29 16:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-29 6:56 [RFC 0/2 PATCH] remove member rt_se from struct rt_rq Yong Zhang
2010-01-29 16:51 ` Peter Zijlstra [this message]
2010-02-01 5:12 ` Yong Zhang
2010-02-01 9:21 ` Peter Zijlstra
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=1264783867.24455.11.camel@laptop \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rusty@rustcorp.com.au \
--cc=tglx@linutronix.de \
--cc=yong.zhang0@gmail.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