From: Borislav Petkov <bp@alien8.de>
To: Reinette Chatre <reinette.chatre@intel.com>
Cc: tglx@linutronix.de, fenghua.yu@intel.com, tony.luck@intel.com,
kuo-lang.tseng@intel.com, ravi.v.shankar@intel.com,
mingo@redhat.com, babu.moger@amd.com, hpa@zytor.com,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V6 0/4] x86/resctrl: Enable user to view and select thread throttling mode
Date: Wed, 20 May 2020 20:35:08 +0200 [thread overview]
Message-ID: <20200520183508.GI1457@zn.tnic> (raw)
In-Reply-To: <5c044d17-e42e-1493-28a5-3ecac043c8f1@intel.com>
On Wed, May 20, 2020 at 10:32:02AM -0700, Reinette Chatre wrote:
> I was told that these enhancements really needed to get into v5.8,
> otherwise the OSV intercepts will be much further out. Certainly not of
> concern to you and not your problem, I am just answering your question
> as an explanation for my goal for inclusion into v5.8.
I believe under "OSV" fall distros too and I, with my distro hat on, can
tell you that at least for us, SUSE, it suffices if the patches are in a
maintainer tree on their way upstream to start backporting them.
Which means, if they get queued in tip after 5.8 releases, that would be
like a couple of weeks later.
Dunno if the other OSVs you work with have such relaxed requirements
- just pointing out that if they do, a couple of weeks later is not a
whole cycle later.
> It seems inappropriate that I have the title of maintainer and not be
> able to have patches considered for inclusion during an entire release
> cycle.
Well, we try very hard to be fair when looking at patchsets. In your
case, I already took a patchset from you this cycle and there are other
patchsets waiting for a lot longer than yours - even patchsets from your
colleagues at Intel.
So I understand that you think it might be inappropriate but please try
to understand it also from our standpoint in that we try to round-robin
between everyone as fair as possible.
So I will try to look at yours in the next days but I cannot promise you
anything.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2020-05-20 18:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-19 21:28 [PATCH V6 0/4] x86/resctrl: Enable user to view and select thread throttling mode Reinette Chatre
2020-05-19 21:28 ` [PATCH V6 1/4] " Reinette Chatre
2020-05-19 21:28 ` [PATCH V6 2/4] x86/resctrl: Enumerate per-thread MBA Reinette Chatre
2020-05-19 21:28 ` [PATCH V6 3/4] x86/resctrl: Enable " Reinette Chatre
2020-05-19 21:28 ` [PATCH V6 4/4] x86/resctrl: Use appropriate API for strings terminated by newline Reinette Chatre
2020-05-19 21:47 ` Andy Shevchenko
2020-05-19 21:35 ` [PATCH V6 0/4] x86/resctrl: Enable user to view and select thread throttling mode Borislav Petkov
2020-05-19 22:13 ` Reinette Chatre
2020-05-20 7:11 ` Borislav Petkov
2020-05-20 17:32 ` Reinette Chatre
2020-05-20 18:35 ` Borislav Petkov [this message]
2020-05-20 20:24 ` Reinette Chatre
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=20200520183508.GI1457@zn.tnic \
--to=bp@alien8.de \
--cc=babu.moger@amd.com \
--cc=fenghua.yu@intel.com \
--cc=hpa@zytor.com \
--cc=kuo-lang.tseng@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=ravi.v.shankar@intel.com \
--cc=reinette.chatre@intel.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox