-
Notifications
You must be signed in to change notification settings - Fork 113
docs: add code structure documentation. #607
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
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
add Chinese version.
|
/gemini review |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request introduces comprehensive documentation on the core modules and architecture of the xLLM system. The document is well-structured and detailed, providing a valuable technical overview. My review focuses on improving the clarity and accuracy of the information presented. I've pointed out a minor inconsistency in code paths within the summary table and a potential inaccuracy in a method name description for the Worker module. Overall, this is a great addition to the project's documentation.
|
|
||
| | Module Name | Code Path | Core Functionality | Key Responsibilities | | ||
| | :--- | :--- | :--- | :--- | | ||
| | **APIService** | `api_service/` | External Interface Service | Receives external requests (e.g., OpenAI-compatible API calls), translates them into the internal request format, and forwards them to the Master. | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For consistency, it's better to use specific file paths in the 'Code Path' column of the table, rather than directory paths. The detailed description for APIService already points to api_service/api_service.cpp as the entry point.
| | **APIService** | `api_service/` | External Interface Service | Receives external requests (e.g., OpenAI-compatible API calls), translates them into the internal request format, and forwards them to the Master. | | |
| | **APIService** | `api_service/api_service.cpp` | External Interface Service | Receives external requests (e.g., OpenAI-compatible API calls), translates them into the internal request format, and forwards them to the Master. | |
|
|
||
| **Code Entry Point**: `core/runtime/llm_worker_impl.cpp` | ||
|
|
||
| * **Local Resource Management**: The Worker is responsible for allocating the local physical memory for the KV Cache (`allocate_kv_cache`) during its initialization phase. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The documentation mentions that the Worker is responsible for allocating KV Cache via the allocate_kv_cache method. However, this method doesn't seem to exist in core/runtime/llm_worker_impl.cpp. Please verify if the method name is correct or if it belongs to a base class, and update the documentation accordingly for accuracy.
No description provided.