mirror of
https://github.com/amd/blis.git
synced 2026-04-30 04:21:12 +00:00
Details:
- Retrofitted a new data structure, known as a context, into virtually
all internal APIs for computational operations in BLIS. The structure
is now present within the type-aware APIs, as well as many supporting
utility functions that require information stored in the context. User-
level object APIs were unaffected and continue to be "context-free,"
however, these APIs were duplicated/mirrored so that "context-aware"
APIs now also exist, differentiated with an "_ex" suffix (for "expert").
These new context-aware object APIs (along with the lower-level, type-
aware, BLAS-like APIs) contain the the address of a context as a last
parameter, after all other operands. Contexts, or specifically, cntx_t
object pointers, are passed all the way down the function stack into
the kernels and allow the code at any level to query information about
the runtime, such as kernel addresses and blocksizes, in a thread-
friendly manner--that is, one that allows thread-safety, even if the
original source of the information stored in the context changes at
run-time; see next bullet for more on this "original source" of info).
(Special thanks go to Lee Killough for suggesting the use of this kind
of data structure in discussions that transpired during the early
planning stages of BLIS, and also for suggesting such a perfectly
appropriate name.)
- Added a new API, in frame/base/bli_gks.c, to define a "global kernel
structure" (gks). This data structure and API will allow the caller to
initialize a context with the kernel addresses, blocksizes, and other
information associated with the currently active kernel configuration.
The currently active kernel configuration within the gks cannot be
changed (for now), and is initialized with the traditional cpp macros
that define kernel function names, blocksizes, and the like. However,
in the future, the gks API will be expanded to allow runtime management
of kernels and runtime parameters. The most obvious application of this
new infrastructure is the runtime detection of hardware (and the
implied selection of appropriate kernels). With contexts in place,
kernels may even be "hot swapped" at runtime within the gks. Once
execution enters a level-3 _front() function, the memory allocator will
be reinitialized on-the-fly, if necessary, to accommodate the new
kernels' blocksizes. If another application thread is executing with
another (previously loaded) kernel, it will finish in a deterministic
fashion because its kernel information was loaded into its context
before computation began, and also because the blocks it checked out
from the internal memory pools will be unaffected by the newer threads'
reinitialization of the allocator.
- Reorganized and streamlined the 'ind' directory, which contains much of
the code enabling use of induced methods for complex domain matrix
multiplication; deprecated bli_bsv_query.c and bli_ukr_query.c, as
those APIs' functionality is now mostly subsumed within the global
kernel structure.
- Updated bli_pool.c to define a new function, bli_pool_reinit_if(),
that will reinitialize a memory pool if the necessary pool block size
has increased.
- Updated bli_mem.c to use bli_pool_reinit_if() instead of
bli_pool_reinit() in the definition of bli_mem_pool_init(), and placed
usage of contexts where appropriate to communicate cache and register
blocksizes to bli_mem_compute_pool_block_sizes().
- Simplified control trees now that much of the information resides in
the context and/or the global kernel structure:
- Removed blocksize object pointers (blksz_t*) fields from all control
tree node definitions and replaced them with blocksize id (bszid_t)
values instead, which may be passed into a context query routine in
order to extract the corresponding blocksize from the given context.
- Removed micro-kernel function pointers (func_t*) fields from all
control tree node definitions. Now, any code that needs these function
pointers can query them from the local context, as identified by a
level-3 micro-kernel id (l3ukr_t), level-1f kernel id, (l1fkr_t), or
level-1v kernel id (l1vkr_t).
- Removed blksz_t object creation and initialization, as well as kernel
function object creation and initialization, from all operation-
specific control tree initialization files (bli_*_cntl.c), since this
information will now live in the gks and, secondarily, in the context.
- Removed blocksize multiples from blksz_t objects. Now, we track
blocksize multiples for each blocksize id (bszid_t) in the context
object.
- Removed the bool_t's that were required when a func_t was initialized.
These bools are meant to allow one to track the micro-kernel's storage
preferences (by rows or columns). This preference is now tracked
separately within the gks and contexts.
- Merged and reorganized many separate-but-related functions into single
files. This reorganization affects frame/0, 1, 1d, 1m, 1f, 2, 3, and
util directories, but has the most obvious effect of allowing BLIS
to compile noticeably faster.
- Reorganized execution paths for level-1v, -1d, -1m, and -2 operations
in an attempt to reduce overhead for memory-bound operations. This
includes removal of default use of object-based variants for level-2
operations. Now, by default, level-2 operations will directly call a
low-level (non-object based) loop over a level-1v or -1f kernel.
- Converted many common query functions in blk_blksz.c (renamed from
bli_blocksize.c) and bli_func.c into cpp macros, now defined in their
respective header files.
- Defined bli_mbool.c API to create and query "multi-bools", or
heterogeneous bool_t's (one for each floating-point datatype), in the
same spirit as blksz_t and func_t.
- Introduced two key parameters of the hardware: BLIS_SIMD_NUM_REGISTERS
and BLIS_SIMD_SIZE. These values are needed in order to compute a third
new parameter, which may be set indirectly via the aforementioned
macros or directly: BLIS_STACK_BUF_MAX_SIZE. This value is used to
statically allocate memory in macro-kernels and the induced methods'
virtual kernels to be used as temporary space to hold a single
micro-tile. These values are now output by the testsuite. The default
value of BLIS_STACK_BUF_MAX_SIZE is computed as
"2 * BLIS_SIMD_NUM_REGISTERS * BLIS_SIMD_SIZE".
- Cleaned up top-level 'kernels' directory (for example, renaming the
embarrassingly misleading "avx" and "avx2" directories to "sandybridge"
and "haswell," respectively, and gave more consistent and meaningful
names to many kernel files (as well as updating their interfaces to
conform to the new context-aware kernel APIs).
- Updated the testsuite to query blocksizes from a locally-initialized
context for test modules that need those values: axpyf, dotxf,
dotxaxpyf, gemm_ukr, gemmtrsm_ukr, and trsm_ukr.
- Reformatted many function signatures into a standard format that will
more easily facilitate future API-wide changes.
- Updated many "mxn" level-0 macros (ie: those used to inline double loops
for level-1m-like operations on small matrices) in frame/include/level0
to use more obscure local variable names in an effort to avoid variable
shaddowing. (Thanks to Devin Matthews for pointing these gcc warnings,
which are only output using -Wshadow.)
- Added a conj argument to setm, so that its interface now mirrors that
of scalm. The semantic meaning of the conj argument is to optionally
allow implicit conjugation of the scalar prior to being populated into
the object.
- Deprecated all type-aware mixed domain and mixed precision APIs. Note
that this does not preclude supporting mixed types via the object APIs,
where it produces absolutely zero API code bloat.
279 lines
9.7 KiB
C
279 lines
9.7 KiB
C
/*
|
|
|
|
BLIS
|
|
An object-based framework for developing high-performance BLAS-like
|
|
libraries.
|
|
|
|
Copyright (C) 2014, The University of Texas at Austin
|
|
|
|
Redistribution and use in source and binary forms, with or without
|
|
modification, are permitted provided that the following conditions are
|
|
met:
|
|
- Redistributions of source code must retain the above copyright
|
|
notice, this list of conditions and the following disclaimer.
|
|
- Redistributions in binary form must reproduce the above copyright
|
|
notice, this list of conditions and the following disclaimer in the
|
|
documentation and/or other materials provided with the distribution.
|
|
- Neither the name of The University of Texas at Austin nor the names
|
|
of its contributors may be used to endorse or promote products
|
|
derived from this software without specific prior written permission.
|
|
|
|
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
|
|
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
|
|
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
|
|
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
|
|
HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
|
|
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
|
|
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
|
|
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
|
|
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
|
|
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
|
|
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
|
|
|
*/
|
|
|
|
#include "blis.h"
|
|
|
|
|
|
|
|
void bli_strsm_u_opt_mxn
|
|
(
|
|
float* restrict a11,
|
|
float* restrict b11,
|
|
float* restrict c11, inc_t rs_c, inc_t cs_c,
|
|
auxinfo_t* restrict data,
|
|
cntx_t* restrict cntx
|
|
)
|
|
{
|
|
/* Just call the reference implementation. */
|
|
BLIS_STRSM_U_UKERNEL_REF
|
|
(
|
|
a11,
|
|
b11,
|
|
c11, rs_c, cs_c,
|
|
data,
|
|
cntx
|
|
);
|
|
}
|
|
|
|
|
|
|
|
void bli_dtrsm_u_opt_mxn(
|
|
double* restrict a11,
|
|
double* restrict b11,
|
|
double* restrict c11, inc_t rs_c, inc_t cs_c,
|
|
auxinfo_t* data
|
|
)
|
|
(
|
|
double* restrict a11,
|
|
double* restrict b11,
|
|
double* restrict c11, inc_t rs_c, inc_t cs_c,
|
|
auxinfo_t* restrict data,
|
|
cntx_t* restrict cntx
|
|
)
|
|
{
|
|
/*
|
|
Template trsm_u micro-kernel implementation
|
|
|
|
This function contains a template implementation for a double-precision
|
|
real trsm micro-kernel, coded in C, which can serve as the starting point
|
|
for one to write an optimized micro-kernel on an arbitrary architecture.
|
|
(We show a template implementation for only double-precision real because
|
|
the templates for the other three floating-point types would be nearly
|
|
identical.)
|
|
|
|
This micro-kernel performs the following operation:
|
|
|
|
C11 := inv(A11) * B11
|
|
|
|
where A11 is MR x MR and upper triangular, B11 is MR x NR, and C11 is
|
|
MR x NR.
|
|
|
|
Parameters:
|
|
|
|
- a11: The address of A11, which is the MR x MR upper triangular
|
|
submatrix within the packed micro-panel of matrix A. A11 is
|
|
stored by columns with leading dimension PACKMR, where
|
|
typically PACKMR = MR. Note that A11 contains elements in both
|
|
triangles, though elements in the unstored triangle are not
|
|
guaranteed to be zero and thus should not be referenced.
|
|
- b11: The address of B11, which is an MR x NR submatrix of the
|
|
packed micro-panel of B. B11 is stored by rows with leading
|
|
dimension PACKNR, where typically PACKNR = NR.
|
|
- c11: The address of C11, which is an MR x NR submatrix of matrix C,
|
|
stored according to rs_c and cs_c. C11 is the submatrix within
|
|
C that corresponds to the elements which were packed into B11.
|
|
Thus, C is the original input matrix B to the overall trsm
|
|
operation.
|
|
- rs_c: The row stride of C11 (ie: the distance to the next row of C11,
|
|
in units of matrix elements).
|
|
- cs_c: The column stride of C11 (ie: the distance to the next column of
|
|
C11, in units of matrix elements).
|
|
- data: The address of an auxinfo_t object that contains auxiliary
|
|
information that may be useful when optimizing the trsm
|
|
micro-kernel implementation. (See BLIS KernelsHowTo wiki for
|
|
more info.)
|
|
- cntx: The address of the runtime context. The context can be queried
|
|
for implementation-specific values such as cache and register
|
|
blocksizes. However, most micro-kernels intrinsically "know"
|
|
these values already, and thus the cntx argument usually can
|
|
be safely ignored. (The following template micro-kernel code
|
|
does in fact query MR, NR, PACKMR, and PACKNR, as needed, but
|
|
only because those values are not hard-coded, as they would be
|
|
in a typical optimized micro-kernel implementation.)
|
|
|
|
Diagrams for trsm
|
|
|
|
Please see the diagram for gemmtrsm_u to see depiction of the trsm_u and
|
|
where it fits in with its preceding gemm subproblem.
|
|
|
|
Implementation Notes for trsm
|
|
|
|
- Register blocksizes. See Implementation Notes for gemm.
|
|
- Leading dimensions of a11 and b11: PACKMR and PACKNR. See
|
|
Implementation Notes for gemm.
|
|
- Edge cases in MR, NR dimensions. See Implementation Notes for gemm.
|
|
- Alignment of a11 and b11. See Implementation Notes for gemmtrsm.
|
|
- Unrolling loops. Most optimized implementations should unroll all
|
|
three loops within the trsm micro-kernel.
|
|
- Prefetching next micro-panels of A and B. We advise against using
|
|
the bli_auxinfo_next_a() and bli_auxinfo_next_b() macros from within
|
|
the trsm_l and trsm_u micro-kernels, since the values returned usually
|
|
only make sense in the context of the overall gemmtrsm subproblem.
|
|
- Diagonal elements of A11. At the time this micro-kernel is called,
|
|
the diagonal entries of triangular matrix A11 contain the inverse of
|
|
the original elements. This inversion is done during packing so that
|
|
we can avoid expensive division instructions within the micro-kernel
|
|
itself. If the diag parameter to the higher level trsm operation was
|
|
equal to BLIS_UNIT_DIAG, the diagonal elements will be explicitly
|
|
unit.
|
|
- Zero elements of A11. Since A11 is lower triangular (for trsm_l), the
|
|
strictly upper triangle implicitly contains zeros. Similarly, the
|
|
strictly lower triangle of A11 implicitly contains zeros when A11 is
|
|
upper triangular (for trsm_u). However, the packing function may or
|
|
may not actually write zeros to this region. Thus, the implementation
|
|
should not reference these elements.
|
|
- Output. This micro-kernel must write its result to two places: the
|
|
submatrix B11 of the current packed micro-panel of B and the submatrix
|
|
C11 of the output matrix C.
|
|
|
|
For more info, please refer to the BLIS website and/or contact the
|
|
blis-devel mailing list.
|
|
|
|
-FGVZ
|
|
*/
|
|
const dim_t mr = bli_cntx_get_blksz_def_dt( dt, BLIS_MR, cntx );
|
|
const dim_t nr = bli_cntx_get_blksz_def_dt( dt, BLIS_NR, cntx );
|
|
|
|
const inc_t packmr = bli_cntx_get_blksz_max_dt( dt, BLIS_MR, cntx );
|
|
const inc_t packnr = bli_cntx_get_blksz_max_dt( dt, BLIS_NR, cntx );
|
|
|
|
const dim_t m = mr;
|
|
const dim_t n = nr;
|
|
|
|
const inc_t rs_a = 1;
|
|
const inc_t cs_a = packmr;
|
|
|
|
const inc_t rs_b = packnr;
|
|
const inc_t cs_b = 1;
|
|
|
|
dim_t iter, i, j, l;
|
|
dim_t n_behind;
|
|
|
|
double* restrict alpha11;
|
|
double* restrict a12t;
|
|
double* restrict alpha12;
|
|
double* restrict X2;
|
|
double* restrict x1;
|
|
double* restrict x21;
|
|
double* restrict chi21;
|
|
double* restrict chi11;
|
|
double* restrict gamma11;
|
|
double rho11;
|
|
|
|
for ( iter = 0; iter < m; ++iter )
|
|
{
|
|
i = m - iter - 1;
|
|
n_behind = iter;
|
|
alpha11 = a11 + (i )*rs_a + (i )*cs_a;
|
|
a12t = a11 + (i )*rs_a + (i+1)*cs_a;
|
|
x1 = b11 + (i )*rs_b + (0 )*cs_b;
|
|
X2 = b11 + (i+1)*rs_b + (0 )*cs_b;
|
|
|
|
/* x1 = x1 - a12t * X2; */
|
|
/* x1 = x1 / alpha11; */
|
|
for ( j = 0; j < n; ++j )
|
|
{
|
|
chi11 = x1 + (0 )*rs_b + (j )*cs_b;
|
|
x21 = X2 + (0 )*rs_b + (j )*cs_b;
|
|
gamma11 = c11 + (i )*rs_c + (j )*cs_c;
|
|
|
|
/* chi11 = chi11 - a12t * x21; */
|
|
bli_dset0s( rho11 );
|
|
for ( l = 0; l < n_behind; ++l )
|
|
{
|
|
alpha12 = a12t + (l )*cs_a;
|
|
chi21 = x21 + (l )*rs_b;
|
|
|
|
bli_daxpys( *alpha12, *chi21, rho11 );
|
|
}
|
|
bli_dsubs( rho11, *chi11 );
|
|
|
|
/* chi11 = chi11 / alpha11; */
|
|
/* NOTE: The INVERSE of alpha11 (1.0/alpha11) is stored instead
|
|
of alpha11, so we can multiply rather than divide. We store
|
|
the inverse of alpha11 intentionally to avoid expensive
|
|
division instructions within the micro-kernel. */
|
|
bli_dscals( *alpha11, *chi11 );
|
|
|
|
/* Output final result to matrix C. */
|
|
bli_dcopys( *chi11, *gamma11 );
|
|
}
|
|
}
|
|
}
|
|
|
|
|
|
|
|
void bli_ctrsm_u_opt_mxn
|
|
(
|
|
scomplex* restrict a11,
|
|
scomplex* restrict b11,
|
|
scomplex* restrict c11, inc_t rs_c, inc_t cs_c,
|
|
auxinfo_t* restrict data,
|
|
cntx_t* restrict cntx
|
|
)
|
|
{
|
|
/* Just call the reference implementation. */
|
|
BLIS_CTRSM_U_UKERNEL_REF
|
|
(
|
|
a11,
|
|
b11,
|
|
c11, rs_c, cs_c,
|
|
data,
|
|
cntx
|
|
);
|
|
}
|
|
|
|
|
|
|
|
void bli_ztrsm_u_opt_mxn
|
|
(
|
|
dcomplex* restrict a11,
|
|
dcomplex* restrict b11,
|
|
dcomplex* restrict c11, inc_t rs_c, inc_t cs_c,
|
|
auxinfo_t* restrict data,
|
|
cntx_t* restrict cntx
|
|
)
|
|
{
|
|
/* Just call the reference implementation. */
|
|
BLIS_ZTRSM_U_UKERNEL_REF
|
|
(
|
|
a11,
|
|
b11,
|
|
c11, rs_c, cs_c,
|
|
data,
|
|
cntx
|
|
);
|
|
}
|
|
|