You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A large part of populate_mram is dedicated to allocating and reallocating buffers. For readability and maintainability it should (or could) be put in a separate function which returns 0 if allocation was successful.
We could then focus on loading the dpu in populate_mram.
The text was updated successfully, but these errors were encountered:
/** * @brief Allocate buffers * @param table_id embedding table number. * @param nr_rows number of rows of the embedding table * @param nr_cols number of columns of the embedding table * @param table_data a pointer of the size nr_rows*nr_cols containing table's data * @return 0 on success, ENOMEM on allocation failure */staticintalloc_buffers(uint32_ttable_id, uint64_tnr_rows, uint64_tnr_cols, constint32_t*table_data);
I see! so every time before calling populate_mram on each table this function will be called. So then populate_mram() will only be copying data to buffers and allocating dpus when needed and copying to dpus?
A large part of
populate_mram
is dedicated to allocating and reallocating buffers. For readability and maintainability it should (or could) be put in a separate function which returns0
if allocation was successful.We could then focus on loading the dpu in
populate_mram
.The text was updated successfully, but these errors were encountered: