Jesse Gross b13fbad0fe llm: Separate llamaServer and ollamaServer code paths ...

Originally, llamaServer represented old memory estimates, which
could be used with either the old or new engine. ollamaServer was
used only for the new estimates and new engine. Since these
implementations did not map directly to engine, there was engine-
specific code in common code paths.

Now that new estimates are always used for the new engine, there is
a direct mapping between server type and engine. This separates out
most of the engine-specific code into the correct implementation
to make things easier to understand.

2025-11-11 13:11:08 -08:00

..

llm_darwin.go

Optimize container images for startup (#6547)

2024-09-12 12:10:30 -07:00

llm_linux.go

Optimize container images for startup (#6547)

2024-09-12 12:10:30 -07:00

llm_windows.go

win: lint fix (#10571)

2025-05-05 11:08:12 -07:00

server_test.go

DRY out the runner lifecycle code (#12540)

2025-10-23 11:20:02 -07:00

server.go

llm: Separate llamaServer and ollamaServer code paths

2025-11-11 13:11:08 -08:00

status.go

logs: catch rocm errors (#12888)

2025-10-31 09:54:25 -07:00