Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Leonid Yegoshin <Leonid.Yegoshin@imgtec.com>
To: Florian Fainelli <f.fainelli@gmail.com>,
	Justin Chen <justinpopo6@gmail.com>
Cc: <linux-mips@linux-mips.org>,
	<bcm-kernel-feedback-list@broadcom.com>,
	Justin Chen <justin.chen@broadcom.com>
Subject: Re: [RFC] MIPS: Add cacheinfo support
Date: Mon, 12 Dec 2016 12:45:37 -0800	[thread overview]
Message-ID: <584F0C71.5010004@imgtec.com> (raw)
In-Reply-To: <3004fca6-3688-65bb-7c86-248603482088@gmail.com>

On 12/12/2016 10:24 AM, Florian Fainelli wrote:
>
> What Justin's patch is about is not so much about providing hints to
> user-space to bypass the kernel's own management of caches, (even though
> that has been used as an argument by the original introduction of
> cacheinfo), but more to provide some information to user-space about the
> cache topology and hierarchy.

I missed that, if it is for information purpose only, then it is OK.

>
> Even though this is limited information this is still helpful to
> applications like lshw and others out there.
>
> What would be needed from your perspective to get cacheinfo added to
> MIPS, shall we go back and address your initial comment about all the
> little details about coherency, snooping and re-filling strategy?

It depends. Initially, I thought Justin wants to replace 
arch/mips/mm/c-XXX.c with some universal approach and listed the missed 
stuff for that (I actually missed some more points in that list).

But for information purpose I don't have any more addition to Justin's 
patch... may be the coherency status, it has impact on performance: 
coherency of L1D->L2, L2->memory and L1I->L1D/L2.


- Leonid

WARNING: multiple messages have this Message-ID (diff)
From: Leonid Yegoshin <Leonid.Yegoshin@imgtec.com>
To: Florian Fainelli <f.fainelli@gmail.com>,
	Justin Chen <justinpopo6@gmail.com>
Cc: linux-mips@linux-mips.org, bcm-kernel-feedback-list@broadcom.com,
	Justin Chen <justin.chen@broadcom.com>
Subject: Re: [RFC] MIPS: Add cacheinfo support
Date: Mon, 12 Dec 2016 12:45:37 -0800	[thread overview]
Message-ID: <584F0C71.5010004@imgtec.com> (raw)
Message-ID: <20161212204537.E0qPEYB-HbSbwFYvVGDdSzOrRjCYhChn9mVnR20Mn4o@z> (raw)
In-Reply-To: <3004fca6-3688-65bb-7c86-248603482088@gmail.com>

On 12/12/2016 10:24 AM, Florian Fainelli wrote:
>
> What Justin's patch is about is not so much about providing hints to
> user-space to bypass the kernel's own management of caches, (even though
> that has been used as an argument by the original introduction of
> cacheinfo), but more to provide some information to user-space about the
> cache topology and hierarchy.

I missed that, if it is for information purpose only, then it is OK.

>
> Even though this is limited information this is still helpful to
> applications like lshw and others out there.
>
> What would be needed from your perspective to get cacheinfo added to
> MIPS, shall we go back and address your initial comment about all the
> little details about coherency, snooping and re-filling strategy?

It depends. Initially, I thought Justin wants to replace 
arch/mips/mm/c-XXX.c with some universal approach and listed the missed 
stuff for that (I actually missed some more points in that list).

But for information purpose I don't have any more addition to Justin's 
patch... may be the coherency status, it has impact on performance: 
coherency of L1D->L2, L2->memory and L1I->L1D/L2.


- Leonid

  reply	other threads:[~2016-12-12 20:45 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-08  1:16 [RFC] MIPS: Add cacheinfo support justinpopo6
2016-12-08 23:26 ` Leonid Yegoshin
2016-12-08 23:26   ` Leonid Yegoshin
2016-12-09  0:28   ` Justin Chen
2016-12-09  1:01     ` Leonid Yegoshin
2016-12-09  1:01       ` Leonid Yegoshin
2016-12-12 18:24       ` Florian Fainelli
2016-12-12 20:45         ` Leonid Yegoshin [this message]
2016-12-12 20:45           ` Leonid Yegoshin
2016-12-12 21:57           ` Florian Fainelli
2016-12-13  0:19             ` Leonid Yegoshin
2016-12-13  0:19               ` Leonid Yegoshin
2016-12-13 11:09               ` Maciej W. Rozycki
2016-12-13 11:09                 ` Maciej W. Rozycki
2016-12-13 19:18                 ` Leonid Yegoshin
2016-12-13 19:18                   ` Leonid Yegoshin
2016-12-13 20:01                   ` Justin Chen
2016-12-13 20:05                     ` Florian Fainelli
2016-12-13 20:15                       ` Leonid Yegoshin
2016-12-13 20:15                         ` Leonid Yegoshin
2016-12-13 21:53           ` Ralf Baechle
2016-12-13 21:48       ` Ralf Baechle

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=584F0C71.5010004@imgtec.com \
    --to=leonid.yegoshin@imgtec.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=f.fainelli@gmail.com \
    --cc=justin.chen@broadcom.com \
    --cc=justinpopo6@gmail.com \
    --cc=linux-mips@linux-mips.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