Hi Morten,
> Mattias, Konstantin, Honnappa, Stephen,
>
> In my patch for non-temporal memcpy, I have been aiming for using as much
> non-temporal store as possible. E.g. copying 16 byte to a
> 16 byte aligned address will be done using non-temporal store instructions.
>
> Now, I am seriously
On Mon, Oct 10, 2022 at 11:36:11AM +0200, Morten Brørup wrote:
> > For large copies, which I'm guessing is what non-temporal stores are
> > usually used for, this is hair splitting. For DPDK applications, it
> > might well be at least somewhat relevant, because such an application
> > may make an
On Mon, Oct 10, 2022 at 10:58:57AM +0200, Mattias Rönnblom wrote:
> On 2022-10-10 09:35, Morten Brørup wrote:
> > Mattias, Konstantin, Honnappa, Stephen,
> >
> > In my patch for non-temporal memcpy, I have been aiming for using as much
> > non-temporal store as possible. E.g. copying 16 byte to a
> From: Mattias Rönnblom [mailto:hof...@lysator.liu.se]
> Sent: Monday, 10 October 2022 10.59
>
> On 2022-10-10 09:35, Morten Brørup wrote:
> > Mattias, Konstantin, Honnappa, Stephen,
> >
> > In my patch for non-temporal memcpy, I have been aiming for using as
> much non-temporal store as possible
On 2022-10-10 09:35, Morten Brørup wrote:
Mattias, Konstantin, Honnappa, Stephen,
In my patch for non-temporal memcpy, I have been aiming for using as much
non-temporal store as possible. E.g. copying 16 byte to a 16 byte aligned
address will be done using non-temporal store instructions.
Now
Mattias, Konstantin, Honnappa, Stephen,
In my patch for non-temporal memcpy, I have been aiming for using as much
non-temporal store as possible. E.g. copying 16 byte to a 16 byte aligned
address will be done using non-temporal store instructions.
Now, I am seriously considering this alternativ
6 matches
Mail list logo
