Skip to content

add introduction to docs #78

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 17, 2024
Merged

Conversation

bratpiorka
Copy link
Contributor

No description provided.

@bratpiorka bratpiorka marked this pull request as ready for review December 19, 2023 13:20
@bratpiorka bratpiorka requested a review from a team as a code owner December 19, 2023 13:20
@bratpiorka
Copy link
Contributor Author

@bratpiorka bratpiorka force-pushed the rrudnick_doc_ext branch 2 times, most recently from f980b7e to 56ef5d8 Compare December 19, 2023 13:39

The amount of data associated with modern workloads that need to be processed
by modern workloads is continuously growing. To address the increasing demand
memory subsystem of modern server platforms is becoming heterogeneous. For
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's difficult to read this without a comma. To address this increasing demand, the memory subsystem of ...

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

@bratpiorka bratpiorka force-pushed the rrudnick_doc_ext branch 3 times, most recently from bb14dd1 to e6d50d2 Compare January 10, 2024 09:33
@bratpiorka bratpiorka force-pushed the rrudnick_doc_ext branch 5 times, most recently from 3770256 to 8822c0c Compare January 15, 2024 18:05
@bratpiorka
Copy link
Contributor Author

@igchor @PatKamin @DamianDuy @vinser52 @kswiecicki - all, we got > 100 comments here :) I updated the documentation with your suggestions - please resolve all conversations that are ok.

@@ -15,7 +15,9 @@ A UMF memory pool is a combination of a pool allocator and a memory provider. A

Pool allocator can leverage existing allocators (e.g. jemalloc or tbbmalloc) or be written from scratch.

UMF comes with predefined pool allocators (see include/pool) and providers (see include/provider). UMF can also work with user-defined pools and providers that implement a specific interface (see include/umf/memory_pool_ops.h and include/umf/memory_provider_ops.h)
UMF comes with predefined pool allocators (see include/pool) and providers (see include/provider). UMF can also work with user-defined pools and providers that implement a specific interface (see include/umf/memory_pool_ops.h and include/umf/memory_provider_ops.h).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: you can add links in repo to these file:

... (see [include/umf/memory_pool_ops.h](include/umf/memory_pool_ops.h) and [include/umf/memory_provider_ops.h](include/umf/memory_provider_ops.h) ).

@bratpiorka bratpiorka merged commit a848175 into oneapi-src:main Jan 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants