From: Xiaochen Shen <xiaochen.shen@intel.com>
To: Borislav Petkov <bp@alien8.de>
Cc: tony.luck@intel.com, x86@kernel.org, mingo@redhat.com,
bp@suse.de, reinette.chatre@intel.com, hpa@zytor.com,
tglx@linutronix.de, mingo@kernel.org,
linux-kernel@vger.kernel.org, fenghua.yu@intel.com,
linux-tip-commits@vger.kernel.org,
Xiaochen Shen <xiaochen.shen@intel.com>
Subject: Re: [tip:x86/cache] x86/resctrl: Initialize a new resource group with default MBA values
Date: Thu, 18 Apr 2019 16:20:57 +0800 [thread overview]
Message-ID: <27c69929-58ee-0a96-0953-e7cfa8976e78@intel.com> (raw)
In-Reply-To: <20190418072845.GA27160@zn.tnic>
Hi Boris,
On 4/18/2019 15:28, Borislav Petkov wrote:
> On Thu, Apr 18, 2019 at 03:03:35PM +0800, Xiaochen Shen wrote:
>> In my opinion, this newline is unnecessary. Thank you.
>
> See commit message:
>
>> [ bp: Add newlines between code blocks for better readability. ]
>
I got this commit message and the code changes.
Really appreciated that you helped add several newlines between code
blocks. The newlines really make the readability of the code better.
> for_each_alloc_enabled_rdt_resource(r) {
> ...;
> ret = update_domains(r, rdtgrp->closid);
> if (ret < 0) {
> rdt_last_cmd_puts("Failed to initialize allocations\n");
> return ret;
> }
> +
> }
But is this newline an exception?
This newline is in the middle of two "}"s - the first "}" is the end of
if condition, and the second "}" is the end of
"for_each_alloc_enabled_rdt_resource" loop. I don't think the newline is
necessary.
> And I didn't add enough. That code is too crammed.
>
> For example, the new __init_one_rdt_domain() could use some newlines
> too, to separate code blocks for better readability. At least before
> each comment so that one can visually distinguish code groups
> better/faster.
>
> Here the whole function pasted with newlines added where I think they
> make sense. This way you have visual separation between the code blocks
> and not one big fat clump of code which one has to painstakingly pick
> apart.
Thank you very much for pointing this out and helping make the changes.
Should I submit a separate fixing patch for __init_one_rdt_domain()?
Thank you.
>
> static int __init_one_rdt_domain(struct rdt_domain *d, struct rdt_resource *r,
> u32 closid)
> {
> struct rdt_resource *r_cdp = NULL;
> struct rdt_domain *d_cdp = NULL;
> u32 used_b = 0, unused_b = 0;
> unsigned long tmp_cbm;
> enum rdtgrp_mode mode;
> u32 peer_ctl, *ctrl;
> int i;
>
> rdt_cdp_peer_get(r, d, &r_cdp, &d_cdp);
> d->have_new_ctrl = false;
> d->new_ctrl = r->cache.shareable_bits;
> used_b = r->cache.shareable_bits;
> ctrl = d->ctrl_val;
>
> for (i = 0; i < closids_supported(); i++, ctrl++) {
> if (closid_allocated(i) && i != closid) {
> mode = rdtgroup_mode_by_closid(i);
> if (mode == RDT_MODE_PSEUDO_LOCKSETUP)
> break;
>
> /*
> * If CDP is active include peer domain's
> * usage to ensure there is no overlap
> * with an exclusive group.
> */
> if (d_cdp)
> peer_ctl = d_cdp->ctrl_val[i];
> else
> peer_ctl = 0;
>
> used_b |= *ctrl | peer_ctl;
> if (mode == RDT_MODE_SHAREABLE)
> d->new_ctrl |= *ctrl | peer_ctl;
> }
> }
>
> if (d->plr && d->plr->cbm > 0)
> used_b |= d->plr->cbm;
>
> unused_b = used_b ^ (BIT_MASK(r->cache.cbm_len) - 1);
> unused_b &= BIT_MASK(r->cache.cbm_len) - 1;
> d->new_ctrl |= unused_b;
>
> /*
> * Force the initial CBM to be valid, user can
> * modify the CBM based on system availability.
> */
> cbm_ensure_valid(&d->new_ctrl, r);
>
> /*
> * Assign the u32 CBM to an unsigned long to ensure that
> * bitmap_weight() does not access out-of-bound memory.
> */
> tmp_cbm = d->new_ctrl;
>
> if (bitmap_weight(&tmp_cbm, r->cache.cbm_len) < r->cache.min_cbm_bits) {
> rdt_last_cmd_printf("No space on %s:%d\n", r->name, d->id);
> return -ENOSPC;
> }
> d->have_new_ctrl = true;
>
> return 0;
> }
>
--
Best regards,
Xiaochen
next prev parent reply other threads:[~2019-04-18 8:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-17 11:08 [PATCH v2 0/2] Initialize a new resource group with default MBA values Xiaochen Shen
2019-04-17 11:08 ` [PATCH v2 1/2] x86/resctrl: Move per RDT domain initialization to a separate function Xiaochen Shen
2019-04-17 19:25 ` [tip:x86/cache] " tip-bot for Xiaochen Shen
2019-04-17 22:13 ` tip-bot for Xiaochen Shen
2019-04-17 11:08 ` [PATCH v2 2/2] x86/resctrl: Initialize a new resource group with default MBA values Xiaochen Shen
2019-04-17 19:26 ` [tip:x86/cache] " tip-bot for Xiaochen Shen
2019-04-17 22:14 ` tip-bot for Xiaochen Shen
2019-04-18 7:03 ` Xiaochen Shen
2019-04-18 7:28 ` Borislav Petkov
2019-04-18 8:20 ` Xiaochen Shen [this message]
2019-04-18 8:29 ` Borislav Petkov
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=27c69929-58ee-0a96-0953-e7cfa8976e78@intel.com \
--to=xiaochen.shen@intel.com \
--cc=bp@alien8.de \
--cc=bp@suse.de \
--cc=fenghua.yu@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.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