[prev in list] [next in list] [prev in thread] [next in thread] 

List:       fedora-devel-list
Subject:    Re: Fedora 32 System-Wide Change proposal: Enable fstrim.timer by default
From:       Lennart Poettering <mzerqung () 0pointer ! de>
Date:       2019-12-20 16:36:02
Message-ID: 20191220163602.GA1973 () gardel-login
[Download RAW message or body]

On Fr, 20.12.19 13:39, Fedora Development ML (devel@lists.fedoraproject.org) wrote:

> On 20.12.2019 10:23, Lennart Poettering wrote:
> > So, if this is desirable, why doesn't the kernel do this on its own?
>
> Kernel's TRIM has issues with data corruption on some SSD controllers.
> You can check drivers/ata/libata-core.c of Linux kernel sources for more
> information.

If that's the case, then what is different with the feature posted
here? in both cases it's the kernel that issues the TRIM, how would it
be safer to trigger that from a userspace program by default rather
than triggering that from a kernel-internal timer by default?

Why involve userspace in this at all? the kernel executes the actual
operation either way,  but why bother userspace with this?

Lennart

--
Lennart Poettering, Berlin
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

[prev in list] [next in list] [prev in thread] [next in thread]