From: "Theodore Tso" <tytso@mit.edu>
To: johannes.goede@oss.qualcomm.com
Cc: Jiri Kosina <jikos@kernel.org>,
ksummit@lists.linux.dev, sashiko@lists.linux.dev
Subject: Re: Patch pre-submission to Sashiko
Date: Mon, 19 Oct 2026 16:27:47 -0400 [thread overview]
Message-ID: <atZ4J86j7CXF82HX@mit.edu> (raw)
In-Reply-To: <3354ebda-5158-489b-a577-5cb10e5d5fb0@oss.qualcomm.com>
On Mon, Oct 19, 2026 at 01:02:55PM -0500, johannes.goede@oss.qualcomm.com wrote:
> > It's not that hard for people to set up a local Sashiko. and then use
> > either an local LLM, or their own cloud-hosted AI tokens. Perhaps
> > that's something we can encourage.
>
> Actually it is that hard. Even if you spend the 2000 - 3000usd
> necessary to run somewhat large-ish models locally the results are
> still quite slow (which by itself would be ok) and they catch
> a lot less then the actual Shashiko service.
I was thinking about difficulty in setting up, but it's fair to point
out that not everyone will have access to a high-end GPU or a M5 Max
or RTX/DGX Spark setup. On the other hand, not everyone is going to
big development/build machine. either.
So we might need to consider what a hobbyist or student might have
access to, versus a corproate-sponsored emplyoee/contractor at
different companies, etc. The former might only have a personal "Pro"
level subscription, but some other folks might have company sponsored
token budgets which even in the post-token-maxxing era, might be a bit
more generous than a subscription plan.
As someone else has pointed out, students / hobbyists just use
OpenCode with the review prompts with one of their free models, such
as "Big Pickle". That or a local quen3-coder-next (my current local
LLM, when I'm not using my employer's cloud hosted models) might not
be as good as Sashiko, but you can find a lot of the obvious issues
first, before you send it to the public list.
- Ted
next prev parent reply other threads:[~2026-10-19 20:29 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-17 17:28 Patch pre-submission to Sashiko Jiri Kosina
2026-10-17 18:02 ` Theodore Tso
2026-10-19 11:02 ` johannes.goede
2026-10-19 20:27 ` Theodore Tso [this message]
2026-10-20 14:20 ` Bart Van Assche
2026-10-20 19:21 ` Theodore Tso
2026-10-20 20:15 ` Miguel Ojeda
2026-10-20 20:43 ` Shuah Khan
2026-10-17 18:20 ` Alexei Starovoitov
2026-10-17 18:38 ` Arnaldo Melo
2026-10-19 7:02 ` Dan Carpenter
2026-10-18 11:46 ` Mark Brown
2026-10-17 18:20 ` Linus Torvalds
2026-10-17 20:10 ` Roman Gushchin
2026-10-18 13:41 ` Steven Rostedt
2026-10-18 18:41 ` Kees Cook
2026-10-18 18:58 ` Linus Torvalds
2026-10-19 5:55 ` Oliver Slapinski
2026-10-17 19:42 ` Andrew Lunn
2026-10-18 11:54 ` Mark Brown
2026-10-18 16:48 ` Laurent Pinchart
2026-10-19 6:25 ` Krzysztof Kozlowski
2026-10-19 7:26 ` David Woodhouse
2026-10-19 11:40 ` Michal Simek
2026-10-19 12:02 ` Julia Lawall
2026-10-19 12:46 ` Michal Simek
2026-10-19 12:57 ` Julia Lawall
2026-10-19 17:30 ` Rodrigo Vivi
2026-10-19 17:53 ` Shuah Khan
2026-10-19 18:17 ` Arnaldo Melo
2026-10-19 20:35 ` Theodore Tso
2026-10-20 2:28 ` Chen-Yu Tsai
2026-10-20 8:36 ` Jiri Kosina
2026-10-20 8:48 ` Vlastimil Babka (SUSE)
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=atZ4J86j7CXF82HX@mit.edu \
--to=tytso@mit.edu \
--cc=jikos@kernel.org \
--cc=johannes.goede@oss.qualcomm.com \
--cc=ksummit@lists.linux.dev \
--cc=sashiko@lists.linux.dev \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox