lkml.org 
[lkml]   [2016]   [Apr]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [PATCH v4 0/10] x86/xsaves: Fix XSAVES known issues

    * Dave Hansen <dave.hansen@linux.intel.com> wrote:

    > But I also think it would be pretty nice if 'ls' didn't pay the 2k cost to have
    > AVX-512 state if it's not using AVX-512. [...]

    A C library might decide to use AVX-512 memset(). RAM is cheap, while allocation
    complexity, especially in the kernel, has various other costs.

    I mean, we should not worry about per thread allocation sizes that can be compared
    to the kernel stack size.

    We can still use the compacted area handling instructions, because presumably
    those are the fastest and are also the most optimized ones? But I wouldn't use
    them to do dynamic allocation: just allocate the maximum possible FPU save area at
    task creation time and never again worry about that detail.

    Ok?

    Thanks,

    Ingo

    \
     
     \ /
      Last update: 2016-04-30 10:01    [W:4.483 / U:0.256 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site