From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: "Theodore Tso" <tytso@mit.edu>
Cc: Jonathan Corbet <corbet@lwn.net>, Sasha Levin <sashal@kernel.org>,
ksummit@lists.linux.dev
Subject: Re: [MAINTAINERS SUMMIT] Other LLM-related topics - tags, newcomers, etc
Date: Tue, 21 Jul 2026 20:21:43 +0200 [thread overview]
Message-ID: <20260721202143.5506c36f@foz.lan> (raw)
In-Reply-To: <20260719110103.04896f34@foz.lan>
On Sun, 19 Jul 2026 11:01:03 +0200
Mauro Carvalho Chehab <mchehab+huawei@kernel.org> wrote:
> On Thu, 16 Jul 2026 22:27:54 -0400
> "Theodore Tso" <tytso@mit.edu> wrote:
>
> > I guess we could try running Sashiko using ollama-mlx on a Macbook
> > with 128GB, and see how it works, but my assumption is that the answer
> > is "not well" --- which is why I really want to look at fine-tuning
> > one of these smaller models first.
>
> I'm currently attempting to run Sashiko locally with ollama:
> https://github.com/sashiko-dev/sashiko/issues/200
>
> It sounds that a patch is needed for it to work. I'm working on it
> at this RFC (I'm using LLM to generate Rust code):
>
> https://github.com/sashiko-dev/sashiko/pull/338
Sashiko merged today the Ollama patches from my PR. It should now be
easier to test running it on your local machine for the ones that
prefer running it locally.
On my tests so far (on a cheap AMD rDNA4 GPU with 16GB VRAM), it
doesn't take too much time to review one or two patchs (something like
10-20 minutes per patch, using a model with thinking).
Considering such preliminary results, that's probably not good enough
for real reviews, but, as technology advances, maybe we might have
something doable to use locally in the next few years.
I'm now running some tests on some machines I have access do do more
GPU testing. They have high end old GPUs. My main goal is to see how
it performs there.
The major problem I got is that those models sometimes don't produce
proper JSON output. Such errors reduced when I increased the context
and token size, but we're limited to the maximum context size that
such models accept. The models I tested had either 128k or 262k
max size. There are some open-weight models with bigger ones.
For instance, mistral3 has 393216 max. There is one model I have
at ollama (but I didn't test yet) that has 1MB max context size:
Model: Maoyue/mistral-nemo-instruct-2407:latest
-----------------------------------------------
family: llama
parameter_size: 12.2B
quantization_level: Q4_K_M
architecture: llama
finetune: Instruct
license: apache-2.0
parameter_count: 12247782400
context_length: 1024000
model: gpt2
modified_at: 2026-07-08
parameters:
stop "[INST]"
stop "[/INST]"
capabilities: completion, tools
but it is gpt2, so probably not good enough.
Thanks,
Mauro
next prev parent reply other threads:[~2026-07-21 18:21 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-16 15:09 [MAINTAINERS SUMMIT] Other LLM-related topics - tags, newcomers, etc Jonathan Corbet
2026-07-16 15:28 ` Sasha Levin
2026-07-16 16:08 ` Mark Brown
2026-07-16 16:24 ` Sasha Levin
2026-07-16 20:38 ` Laurent Pinchart
2026-07-17 14:09 ` Sasha Levin
2026-07-21 23:15 ` Laurent Pinchart
2026-07-22 0:23 ` Guenter Roeck
2026-07-17 14:25 ` Mark Brown
2026-07-21 23:58 ` Jori Koolstra
2026-07-22 0:57 ` Linus Torvalds
2026-07-16 18:36 ` Jonathan Corbet
2026-07-16 19:53 ` Mauro Carvalho Chehab
2026-07-16 23:59 ` Theodore Tso
2026-07-17 0:58 ` Mauro Carvalho Chehab
2026-07-17 2:27 ` Theodore Tso
2026-07-17 7:19 ` Mauro Carvalho Chehab
2026-07-19 9:01 ` Mauro Carvalho Chehab
2026-07-21 18:21 ` Mauro Carvalho Chehab [this message]
2026-07-18 9:26 ` Takashi Iwai
2026-07-19 9:29 ` Mauro Carvalho Chehab
2026-07-17 13:55 ` Konstantin Ryabitsev
2026-07-17 14:24 ` Andrew Lunn
2026-07-17 14:32 ` Konstantin Ryabitsev
2026-07-17 14:50 ` Andrew Lunn
2026-07-17 20:21 ` Theodore Tso
2026-07-18 12:54 ` Mauro Carvalho Chehab
2026-07-16 20:05 ` Bart Van Assche
2026-07-16 20:52 ` James Bottomley
2026-07-16 20:23 ` Liam R. Howlett
2026-07-17 7:49 ` Laurent Pinchart
2026-07-17 15:55 ` Liam R. Howlett
2026-07-17 11:57 ` James Bottomley
2026-07-17 15:53 ` Liam R. Howlett
2026-07-17 18:12 ` James Bottomley
2026-07-17 18:27 ` Dan Carpenter
2026-07-17 18:42 ` James Bottomley
2026-07-18 1:13 ` Theodore Tso
2026-07-18 3:07 ` James Bottomley
2026-07-17 14:54 ` Johannes Weiner
2026-07-17 16:09 ` Liam R. Howlett
2026-07-16 21:23 ` Theodore Tso
2026-07-17 13:59 ` Sasha Levin
2026-07-17 14:09 ` Konstantin Ryabitsev
2026-07-21 23:24 ` Jori Koolstra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260721202143.5506c36f@foz.lan \
--to=mchehab+huawei@kernel.org \
--cc=corbet@lwn.net \
--cc=ksummit@lists.linux.dev \
--cc=sashal@kernel.org \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.