Precedence: list
MIME-Version: 1.0
From: Puneeth Aditya <myakampuneeth@gmail.com>
Date: Tue, 24 Feb 2026 11:35:55 +0530
Message-ID: <CAMdT05qew=4T_ifjH+JTuFqgk6Sy2zRV0TvdBhC9-wtF6dtYrA@mail.gmail.com>
Subject: 
To: linux-erofs@lists.ozlabs.org
Content-Type: multipart/alternative; boundary="000000000000ecfb20064b8baeb1"

--000000000000ecfb20064b8baeb1
Content-Type: text/plain; charset="UTF-8"

hi everyone,

i am puneeth aditya (mugiwaraluffy56 github), an undergrad student
interested in contributing to erofs as part of GSoC 2026. i just sent my
first patch to the list today (blobchunk: fix 48-bit format detection to
use final remapped block addresses, message id
20260224055712.14110-1-myakampuneeth@gmail.com) and have been spending the
past week going through the erofs-utils codebase to understand how things
fit together.

i went through the roadmap at erofs.docs.kernel.org and i am particularly
interested in the multi-threaded userspace decompression work. the current
single-threaded decompression path is a real bottleneck on large images and
i think there is good scope for a structured GSoC project around it.

would love any guidance on what a good proposal would look like, and
whether there are specific parts of the decompression pipeline you would
want a GSoC contributor to focus on first.

thanks, puneeth aditya

--000000000000ecfb20064b8baeb1
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail-messagesContainer_07S1Yg" style=3D"ove=
rflow:hidden auto;display:flex;background-color:rgb(1,4,9);min-width:0px;pa=
dding:20px 20px 40px"><div class=3D"gmail-message_07S1Yg gmail-timelineMess=
age_07S1Yg" style=3D"color:rgb(230,237,243);display:flex;padding:8px 0px 8p=
x 30px"><span class=3D"gmail-root_-a7MRw" style=3D"overflow-x:hidden;width:=
1142px"><p style=3D"margin-top:0.1em;margin-bottom:0.2em">hi everyone,</p><=
p style=3D"margin-top:0.1em;margin-bottom:0.2em">i am puneeth aditya (mugiw=
araluffy56 github), an undergrad student interested in contributing to erof=
s as part of GSoC 2026. i just sent my first patch to the list today (blobc=
hunk: fix 48-bit format detection to use final remapped block addresses, me=
ssage id <a href=3D"mailto:20260224055712.14110-1-myakampuneeth@gmail.com" =
target=3D"_blank" rel=3D"noopener noreferrer" style=3D"color:rgb(47,129,247=
);text-decoration-line:initial;text-decoration-color:rgb(47,129,247)">20260=
224055712.14110-1-myakampuneeth@gmail.com</a>) and have been spending the p=
ast week going through the erofs-utils codebase to understand how things fi=
t together.</p><p style=3D"margin-top:0.1em;margin-bottom:0.2em">i went thr=
ough the roadmap at <a href=3D"http://erofs.docs.kernel.org">erofs.docs.ker=
nel.org</a> and i am particularly interested in the multi-threaded userspac=
e decompression work. the current single-threaded decompression path is a r=
eal bottleneck on large images and i think there is good scope for a struct=
ured GSoC project around it.</p><p style=3D"margin-top:0.1em;margin-bottom:=
0.2em">would love any guidance on what a good proposal would look like, and=
 whether there are specific parts of the decompression pipeline you would w=
ant a GSoC contributor to focus on first.</p><p style=3D"margin-top:0.1em;m=
argin-bottom:0.2em">thanks,
puneeth aditya</p></span></div></div><div class=3D"gmail-inputContainer_07S=
1Yg" style=3D"display:flex"><div><div class=3D"gmail-inputWrapper_cKsPxg" s=
tyle=3D"width:680px;max-width:680px;margin:0px auto"><form><fieldset class=
=3D"gmail-inputContainer_cKsPxg" style=3D"background:none 0% 0%/auto repeat=
 scroll padding-box border-box rgb(22,27,34);border-color:rgb(69,69,69);bor=
der-style:solid;border-width:1px;border-radius:8px;color:rgb(230,237,243);d=
isplay:flex;min-width:0px;margin:0px;padding:0px"><div class=3D"gmail-messa=
geInputContainer_cKsPxg" style=3D"display:flex;font-family:-apple-system,&q=
uot;system-ui&quot;,&quot;Segoe UI&quot;,Roboto,sans-serif;font-size:13px">=
<br class=3D"gmail-Apple-interchange-newline"></div></fieldset></form></div=
></div></div></div>

--000000000000ecfb20064b8baeb1--