On Tue, Jan 29, 2019 at 8:34 PM Ard Biesheuvel
wrote:
>
> (+ Bjorn)
>
> On Mon, 28 Jan 2019 at 12:27, Vivek Gautam
> wrote:
> >
> > Hi Ard,
> >
> > On Thu, Jan 24, 2019 at 1:25 PM Ard Biesheuvel
> > wrote:
> > >
> > > On Thu, 24 Jan 2019 at 07:58, Vivek Gautam
> > > wrote:
> > > >
> > > > On
(+ Bjorn)
On Mon, 28 Jan 2019 at 12:27, Vivek Gautam wrote:
>
> Hi Ard,
>
> On Thu, Jan 24, 2019 at 1:25 PM Ard Biesheuvel
> wrote:
> >
> > On Thu, 24 Jan 2019 at 07:58, Vivek Gautam
> > wrote:
> > >
> > > On Mon, Jan 21, 2019 at 7:55 PM Ard Biesheuvel
> > > wrote:
> > > >
> > > > On Mon, 21
Hi Ard,
On Thu, Jan 24, 2019 at 1:25 PM Ard Biesheuvel
wrote:
>
> On Thu, 24 Jan 2019 at 07:58, Vivek Gautam
> wrote:
> >
> > On Mon, Jan 21, 2019 at 7:55 PM Ard Biesheuvel
> > wrote:
> > >
> > > On Mon, 21 Jan 2019 at 14:56, Robin Murphy wrote:
> > > >
> > > > On 21/01/2019 13:36, Ard
On Thu, 24 Jan 2019 at 07:58, Vivek Gautam wrote:
>
> On Mon, Jan 21, 2019 at 7:55 PM Ard Biesheuvel
> wrote:
> >
> > On Mon, 21 Jan 2019 at 14:56, Robin Murphy wrote:
> > >
> > > On 21/01/2019 13:36, Ard Biesheuvel wrote:
> > > > On Mon, 21 Jan 2019 at 14:25, Robin Murphy wrote:
> > > >>
> >
On Mon, Jan 21, 2019 at 7:55 PM Ard Biesheuvel
wrote:
>
> On Mon, 21 Jan 2019 at 14:56, Robin Murphy wrote:
> >
> > On 21/01/2019 13:36, Ard Biesheuvel wrote:
> > > On Mon, 21 Jan 2019 at 14:25, Robin Murphy wrote:
> > >>
> > >> On 21/01/2019 10:50, Ard Biesheuvel wrote:
> > >>> On Mon, 21 Jan
On 21/01/2019 14:24, Ard Biesheuvel wrote:
On Mon, 21 Jan 2019 at 14:56, Robin Murphy wrote:
On 21/01/2019 13:36, Ard Biesheuvel wrote:
On Mon, 21 Jan 2019 at 14:25, Robin Murphy wrote:
On 21/01/2019 10:50, Ard Biesheuvel wrote:
On Mon, 21 Jan 2019 at 11:17, Vivek Gautam wrote:
Hi,
On Mon, 21 Jan 2019 at 14:56, Robin Murphy wrote:
>
> On 21/01/2019 13:36, Ard Biesheuvel wrote:
> > On Mon, 21 Jan 2019 at 14:25, Robin Murphy wrote:
> >>
> >> On 21/01/2019 10:50, Ard Biesheuvel wrote:
> >>> On Mon, 21 Jan 2019 at 11:17, Vivek Gautam
> >>> wrote:
>
> Hi,
>
>
On 21/01/2019 13:36, Ard Biesheuvel wrote:
On Mon, 21 Jan 2019 at 14:25, Robin Murphy wrote:
On 21/01/2019 10:50, Ard Biesheuvel wrote:
On Mon, 21 Jan 2019 at 11:17, Vivek Gautam wrote:
Hi,
On Mon, Jan 21, 2019 at 12:56 PM Ard Biesheuvel
wrote:
On Mon, 21 Jan 2019 at 06:54, Vivek
On Mon, 21 Jan 2019 at 14:25, Robin Murphy wrote:
>
> On 21/01/2019 10:50, Ard Biesheuvel wrote:
> > On Mon, 21 Jan 2019 at 11:17, Vivek Gautam
> > wrote:
> >>
> >> Hi,
> >>
> >>
> >> On Mon, Jan 21, 2019 at 12:56 PM Ard Biesheuvel
> >> wrote:
> >>>
> >>> On Mon, 21 Jan 2019 at 06:54, Vivek
On 21/01/2019 10:50, Ard Biesheuvel wrote:
On Mon, 21 Jan 2019 at 11:17, Vivek Gautam wrote:
Hi,
On Mon, Jan 21, 2019 at 12:56 PM Ard Biesheuvel
wrote:
On Mon, 21 Jan 2019 at 06:54, Vivek Gautam wrote:
Qualcomm SoCs have an additional level of cache called as
System cache, aka. Last
On Mon, 21 Jan 2019 at 11:17, Vivek Gautam wrote:
>
> Hi,
>
>
> On Mon, Jan 21, 2019 at 12:56 PM Ard Biesheuvel
> wrote:
> >
> > On Mon, 21 Jan 2019 at 06:54, Vivek Gautam
> > wrote:
> > >
> > > Qualcomm SoCs have an additional level of cache called as
> > > System cache, aka. Last level cache
Hi,
On Mon, Jan 21, 2019 at 12:56 PM Ard Biesheuvel
wrote:
>
> On Mon, 21 Jan 2019 at 06:54, Vivek Gautam
> wrote:
> >
> > Qualcomm SoCs have an additional level of cache called as
> > System cache, aka. Last level cache (LLC). This cache sits right
> > before the DDR, and is tightly coupled
On Mon, 21 Jan 2019 at 06:54, Vivek Gautam wrote:
>
> Qualcomm SoCs have an additional level of cache called as
> System cache, aka. Last level cache (LLC). This cache sits right
> before the DDR, and is tightly coupled with the memory controller.
> The clients using this cache request their
Qualcomm SoCs have an additional level of cache called as
System cache, aka. Last level cache (LLC). This cache sits right
before the DDR, and is tightly coupled with the memory controller.
The clients using this cache request their slices from this
system cache, make it active, and can then start
14 matches
Mail list logo