Repository navigation
Conversation
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
IRON provides an alternative for open-source developers to implement end-to-end models. FastFlowLM's
flmbinary provides a user-friendly interface to interact with models, such as pulling and serving models. By adding an IRON-backend toflm, users can use the sameflmcommands to run IRON's model implementations, similarly to the RyzenAI Software backend. As a first step, the IRON backend is offered as an alternative for the Llama3.2 1B model and as the main implementation for a new EmbeddingGemma-2 model that was not previously supported by FastFlowLM.Technical Details
The user/developer is expected to install IRON according to the installation instruction themselves.
When FLM is built with the
FLM_ENABLE_IRONCMake flag, it contains the new IRON backend. IRON runs as a Python server subprocess, and FLM communicates with it through a pipe.There is a very simple JSON-based protocol between the two.
The FLM part of the implementation contains no Python. IRON itself is written in Python so runs as a Python interpreter process; all of the tensor management, dispatch, model graph logic is Python, so cannot be easily ported.
Test Plan
A simple infrastructure test testing that the IRON backend correctly communicates through the JSON protocol is included. Correctness on the IRON side is tested in the IRON project; this only tests that FLM sends the correct kinds of requests to IRON.
The IRON repository counterpart of this will contain an end-to-end test that also builds FLM and makes sure the integration works.
Test Result
Pass.
Submission Checklist