Skip to content

client: use vectors for context lists#59171

Merged
batrick merged 1 commit intoceph:mainfrom
batrick:client-vector-context
Aug 27, 2024
Merged

client: use vectors for context lists#59171
batrick merged 1 commit intoceph:mainfrom
batrick:client-vector-context

Conversation

@batrick
Copy link
Member

@batrick batrick commented Aug 12, 2024

To avoid an allocation for each Context and improved cache locality.

Contribution Guidelines

  • To sign and title your commits, please refer to Submitting Patches to Ceph.

  • If you are submitting a fix for a stable branch (e.g. "quincy"), please refer to Submitting Patches to Ceph - Backports for the proper workflow.

  • When filling out the below checklist, you may click boxes directly in the GitHub web UI. When entering or editing the entire PR message in the GitHub web UI editor, you may also select a checklist item by adding an x between the brackets: [x]. Spaces and capitalization matter when checking off items this way.

Checklist

  • Tracker (select at least one)
    • References tracker ticket
    • Very recent bug; references commit where it was introduced
    • New feature (ticket optional)
    • Doc update (no ticket needed)
    • Code cleanup (no ticket needed)
  • Component impact
    • Affects Dashboard, opened tracker ticket
    • Affects Orchestrator, opened tracker ticket
    • No impact that needs to be tracked
  • Documentation (select at least one)
    • Updates relevant documentation
    • No doc update is appropriate
  • Tests (select at least one)
Show available Jenkins commands
  • jenkins retest this please
  • jenkins test classic perf
  • jenkins test crimson perf
  • jenkins test signed
  • jenkins test make check
  • jenkins test make check arm64
  • jenkins test submodules
  • jenkins test dashboard
  • jenkins test dashboard cephadm
  • jenkins test api
  • jenkins test docs
  • jenkins render docs
  • jenkins test ceph-volume all
  • jenkins test ceph-volume tox
  • jenkins test windows
  • jenkins test rook e2e

To avoid an allocation for each Context and improved cache locality.

Signed-off-by: Patrick Donnelly <[email protected]>
@github-actions github-actions bot added the cephfs Ceph File System label Aug 12, 2024
@batrick batrick requested a review from a team August 12, 2024 16:01
@batrick
Copy link
Member Author

batrick commented Aug 13, 2024

jenkins test make check arm64

@batrick
Copy link
Member Author

batrick commented Aug 13, 2024

}

void Client::wait_on_context_list(list<Context*>& ls)
void Client::wait_on_context_list(std::vector<Context*>& ls)
Copy link
Contributor

Choose a reason for hiding this comment

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

We have already brought std::vector into the current scope at line 159 using std::vector;

Copy link
Member Author

Choose a reason for hiding this comment

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

I prefer explicit namespacing (and we generally do so everywhere).

Copy link
Contributor

@dparmar18 dparmar18 Aug 14, 2024

Choose a reason for hiding this comment

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

so should we remove the import at line 159? it doesn't make sense to keep it if we want to keep it explicit.

Copy link
Member Author

Choose a reason for hiding this comment

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

in a separate PR, sure.

@batrick
Copy link
Member Author

batrick commented Aug 14, 2024

jenkins test make check arm64

@batrick
Copy link
Member Author

batrick commented Aug 15, 2024

@batrick
Copy link
Member Author

batrick commented Aug 27, 2024

@batrick batrick merged commit dc8d75f into ceph:main Aug 27, 2024
@batrick batrick deleted the client-vector-context branch August 27, 2024 17:21
pritha-srivastava pushed a commit to pritha-srivastava/ceph that referenced this pull request Aug 28, 2024
* refs/pull/59171/head:
	client: use vectors for context lists

Reviewed-by: Venky Shankar <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants