FIG_Z3FOLD=y from defconfigs.
>
> [1]https://lore.kernel.org/lkml/CAJD7tkbRF6od-2x_L8-A1QL3=2ww13scj4s3i4bnndqf+3+...@mail.gmail.com/
> [2]https://lore.kernel.org/lkml/ef0abd3e-a239-4111-a8ab-5c442e759...@gmail.com/
> [3]https://lore.kernel.org/lkml/CAJD7tkbnmeVugfunffSovJf9FAgy9rhBVt_tx=
On Fri, Jan 12, 2024 at 8:31 PM Yosry Ahmed wrote:
>
> The z3fold compressed pages allocator is not widely used, most users use
> zsmalloc. The only disadvantage of zsmalloc in comparison is the
> dependency on MMU, and zbud is a more common option for !MMU as it was
> the default zswap allocator
On Sat, Sep 18, 2010 at 5:34 PM, Kumar Gala wrote:
> I don't think either of these should be EXPORT_SYMBOL_GPL. Why shouldn't a
> binary module be allowed to know these frequencies? My view is why preclude
> anyone from using this how they want. If they want to live in the gray area
> so be
Hi,
> diff --git a/arch/powerpc/kernel/crash.c b/arch/powerpc/kernel/crash.c
> index 6f4613d..341d8af 100644
> --- a/arch/powerpc/kernel/crash.c
> +++ b/arch/powerpc/kernel/crash.c
> @@ -375,6 +375,9 @@ void default_machine_crash_shutdown(struct pt_regs *regs)
> for_each_irq(i) {
>
Hi,
> There were very few tests done with later kernel versions, and in all
> practical system configurations we tested we found that XIP did not
> give real benefits. Usually execution from flash was slower than when
> running from RAM, and even booting a (inevitably uncompressed) kernel
> from f
