Maxalt

Differences between revisions 1 and 2
⇤ ← Revision 1 as of 2006-06-30 20:33:05 →
Size: 508
Editor: scfwpr03
Comment:
← Revision 2 as of 2006-07-01 17:07:50 → ⇥
Size: 1182
Editor: scfwpr03
Comment:
Deletions are marked like this. Additions are marked like this.
Line 21: Line 21:
Resolve overhead of interception algorithm when to use unchanged glibc/strncmp and optimized strcmp:
when inlining and by call.

strcmp will contain generic optimizations and will not be microarchitecture specific. The code is single threaded itself, so the shared cache architecture does not affect optimizations directly.
Proposed code would :
- take care of alignment/length of the string
- prefetch into cache if reused or threaded
- use correct optimized compiler flags and intrinsics

ld.so would benefit out of optimization as well, as optimized ld would be shared architecture aware and will prefetch into cache shared strings for multi-threaded compare

This is MaxAlt optimization page

Summary

Rationale

Use Cases

Scope

  • Changes in glibc

Design

Resolve overhead of interception algorithm when to use unchanged glibc/strncmp and optimized strcmp: when inlining and by call.

strcmp will contain generic optimizations and will not be microarchitecture specific. The code is single threaded itself, so the shared cache architecture does not affect optimizations directly. Proposed code would : - take care of alignment/length of the string - prefetch into cache if reused or threaded - use correct optimized compiler flags and intrinsics

ld.so would benefit out of optimization as well, as optimized ld would be shared architecture aware and will prefetch into cache shared strings for multi-threaded compare

Summary

Rationale

Implementation

Outstanding Issues

BoF agenda and discussion

CategorySpec

Maxalt (last edited 2008-08-06 16:16:29 by localhost)