Skip to content
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

Adopt polymorphic memory resources from AliceO2 #54

Open
dennisklein opened this issue Jun 15, 2018 · 9 comments
Open

Adopt polymorphic memory resources from AliceO2 #54

dennisklein opened this issue Jun 15, 2018 · 9 comments
Assignees
Labels
feature New feature or request

Comments

@dennisklein
Copy link
Member

@mkrzewic @ktf Action item from today's Framework & Friends meeting.

@dennisklein dennisklein added the feature New feature or request label Jun 15, 2018
@dennisklein dennisklein added this to the v1.3 milestone Jun 15, 2018
@dennisklein dennisklein self-assigned this Jul 18, 2018
@dennisklein dennisklein mentioned this issue Jul 30, 2018
3 tasks
@dennisklein dennisklein assigned mkrzewic and unassigned dennisklein Sep 6, 2018
@mkrzewic
Copy link
Contributor

basic integration done: https://github.com/mkrzewic/FairMQ/tree/pmr
now on to tests.

@dennisklein
Copy link
Member Author

thx, just the clang format seems broken, if I apply it on my machine, it converts everything back. Which version of clang-format do you use? Are you sure, you use the config from the FairMQ repo?

@mkrzewic
Copy link
Contributor

@dennisklein was not there yet :) my version of clang format seems outdated compared to what your config requires, i'll update and see what happens.

@mkrzewic
Copy link
Contributor

mkrzewic commented Sep 20, 2018

also: the unit tests are ported and working. Now would be the time to take a step back and think about how to do this better, since up till now I was just porting the O2 implementation/prototype. I'm sure a number of things can be done much more elegantly directly at the level of fairmq.

@mkrzewic
Copy link
Contributor

@dennisklein what version of clang format is needed? the best I can do on centos7 is 5.0 (via llvm-toolset-7), and that seems not to work:

YAML:26:16: error: unknown key 'IncludeBlocks'
IncludeBlocks: Regroup
               ^~~~~~~
Error reading /home/mkrzewic/o2/FairMQ/.clang-format: Invalid argument
error: `clang-format -lines=1:169 test/memory_resources/_memory_resources.cxx` failed

@dennisklein
Copy link
Member Author

clang-format version 6.0.1 (tags/RELEASE_601/final)

Then I would say do not apply clang-format and we will do it once it is merged. It is anyways not a strict requirement yet. Most important is, that the code is readable and somewhat consistently formatted, which I have no doubts you will deliver anyways.

also: the unit tests are ported and working.

Thanks!

Now would be the time to take a step back and think about how to do this better, since up till now I was just porting the O2 implementation/prototype. I'm sure a number of things can be done much more elegantly directly at the level of fairmq.

Possibly, I will also have a look the next days and give you some feedback latest on Monday.

@dennisklein
Copy link
Member Author

Ah, could you please open a [WIP] pull request already?

@mkrzewic
Copy link
Contributor

ok, i'll apply whatever my clang-format can digest and squash everything together for a WIP PR

@dennisklein
Copy link
Member Author

#93 got merged, container adoption topic still pending in #110, needs a bit more time.

@dennisklein dennisklein modified the milestones: v1.3, v1.4 Oct 31, 2018
@rbx rbx modified the milestones: v1.4, v1.5 Apr 17, 2019
@dennisklein dennisklein modified the milestones: v1.5, v1.6 Aug 12, 2022
@rbx rbx removed this from the v1.6 milestone Sep 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants