From: Max Kellermann <max.kellermann@ionos.com>
To: David Howells <dhowells@redhat.com>
Cc: netfs@lists.linux.dev
Subject: Re: New cachefilesd implementation
Date: Tue, 7 Jan 2025 12:15:11 +0100 [thread overview]
Message-ID: <CAKPOu+8qbUWCeUvb3eMfkvF6hx8pGWf+o8sU6T3dPSmWr+mXCw@mail.gmail.com> (raw)
In-Reply-To: <CAKPOu+_gzJCN6OKYvUw+H9kDrc3YG8yxJS_YDx41zS==wBKpbA@mail.gmail.com>
On Fri, Dec 6, 2024 at 3:06 PM Max Kellermann <max.kellermann@ionos.com> wrote:
>
> On Fri, Nov 29, 2024 at 5:54 PM David Howells <dhowells@redhat.com> wrote:
> > Now, would you be able to clone this:
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/cachefilesd.git/
> >
> > Then rip out the existing code and put in your code? There's some stuff in
> > there that is necessary to run on SELinux-based systems and it would make it
> > a lot easier for me just to replace the current cachefilesd package by just
> > pulling yours directly.
>
> Here:
>
> https://github.com/CM4all/cash/tree/cachefilesd2
>
> Please check if that's how you envisioned it. License is also changed
> to BSD2 or GPL2+.
> RFC! - it's not yet finalized, and not yet ready for merging.
David, please don't forget this.
Today, I have merged our latest version (0.3 -> 0.5) into the
"cachefilesd2" branch. The new version limits the io_uring
concurrency, because previously, our daemon could lock up the kernel
inside io_uring for exceeding the cgroup memory limit.
Max
prev parent reply other threads:[~2025-01-07 11:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-29 14:54 New cachefilesd implementation Max Kellermann
2024-11-29 16:54 ` David Howells
2024-11-29 18:41 ` Max Kellermann
2024-11-29 18:49 ` David Howells
2024-12-06 14:06 ` Max Kellermann
2025-01-07 11:15 ` Max Kellermann [this message]
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=CAKPOu+8qbUWCeUvb3eMfkvF6hx8pGWf+o8sU6T3dPSmWr+mXCw@mail.gmail.com \
--to=max.kellermann@ionos.com \
--cc=dhowells@redhat.com \
--cc=netfs@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;
as well as URLs for NNTP newsgroup(s).