Tags: terrelln/linux
Tags
Update zstd to the latest upstream release v1.5.7. Imported cleanly f… …rom the upstream tag v1.5.7-kernel, which is signed by upstream's signing key EF8FE99528B52FFD. Link: https://github.com/facebook/zstd/releases/tag/v1.5.7 Link: https://github.com/facebook/zstd/releases/tag/v1.5.7-kernel Link: https://keyserver.ubuntu.com/pks/lookup?search=EF8FE99528B52FFD&fingerprint=on&op=index Signed-off-by: Nick Terrell <[email protected]>
Zstd fixes for v6.7 Only a single line change to fix a benign UBSAN warning that has been baking in linux-next for a month. I just missed the merge window, but I think it is worthwhile to include this fix in the v6.7 kernel. If you would like me to wait for v6.8 please let me know. Signed-off-by: Nick Terrell <[email protected]>
Zstd fixes for v6.3 A small number of fixes for zstd-v1.5.2. I'm not pulling in zstd-v1.5.4 from upstream this release because it didn't have any time to bake in linux-next, but I'm aiming for the next update in v6.4. I've rebased my tree onto v6.2 to remove the incorrect back merges as suggested by Linus in my initial PR for v6.3 [0]. [0] https://lore.kernel.org/lkml/[email protected]/ Signed-off-by: Nick Terrell <[email protected]>
Zstd fixes for v6.3 A small number of fixes for zstd-v1.5.2. I'm not pulling in zstd-v1.5.4 from upstream this release because it didn't have any time to bake in linux-next, but I'm aiming for the next update in v6.4. Signed-off-by: Nick Terrell <[email protected]>
Update to zstd-1.5.2 The major goal of this PR is to update the kernel to upstream zstd v1.5.2 [0]. Specifically to the tag v1.5.2-kernel [1] which includes several cherrypicked fixes for the kernel on top of v1.5.2. Excepting the MAINTAINERS change, all the changes in this PR can be generated by: ``` git clone https://github.com/facebook/zstd cd zstd/contrib/linux-kernel git checkout v1.5.2-kernel LINUX=/path/to/linux/repo make import ``` These changes have been baking in linux-next since 2022/10/24 when I put up my patchset [2]. Notably the first commit is a small refactor of the only zstd commit since the last update [3] to fit the upstream import scheme. Additionally, this PR includes several minor typo fixes, which have all been fixed upstream so they are maintained on the next import. [0] https://github.com/facebook/zstd/releases/tag/v1.5.2 [1] https://github.com/facebook/zstd/tree/v1.5.2-kernel [2] https://lore.kernel.org/lkml/[email protected]/ [3] torvalds@637a642 Signed-off-by: Nick Terrell <[email protected]>
Update to zstd-1.5.2 The major goal of this PR is to update the kernel to upstream zstd v1.5.2 [0]. Specifically to the tag v1.5.2-kernel [1] which includes several cherrypicked fixes for the kernel on top of v1.5.2. Excepting the MAINTAINERS change, all the changes in this PR can be generated by: ``` git clone https://github.com/facebook/zstd cd zstd/contrib/linux-kernel git checkout v1.5.2-kernel LINUX=/path/to/linux/repo make import ``` These changes have been baking in linux-next since 2022/10/24 when I put up my patchset [2]. Notably the first commit is a small refactor of the only zstd commit since the last update [3] to fit the upstream import scheme. Additionally, this PR includes several minor typo fixes, which have all been fixed upstream so they are maintained on the next import. [0] https://github.com/facebook/zstd/releases/tag/v1.5.2 [1] https://github.com/facebook/zstd/tree/v1.5.2-kernel [2] https://lore.kernel.org/lkml/[email protected]/ [3] torvalds@637a642 Signed-off-by: Nick Terrell <[email protected]>
zstd fixes for v5.16-rc1 Fix stack usage on parisc & improve code size bloat This PR contains 3 commits: 1. Fixes a minor unused variable warning reported by Kernel test robot [0]. 2. Improves the reported code bloat (-88KB / 374KB) [1] by outlining some functions that are unlikely to be used in performance sensitive workloads. 3. Fixes the reported excess stack usage on parisc [2] by removing -O3 from zstd's compilation flags. -O3 triggered bugs in the hppa-linux-gnu gcc-8 compiler. -O2 performance is acceptable: neutral compression, about -1% decompression speed. We also reduce code bloat (-105KB / 374KB). After this commit our code bloat is cut from 374KB to 105KB with gcc-11. If we wanted to cut the remaining 105KB we'd likely have to trade signicant performance, so I want to say that this is enough for now. We should be able to get further gains without sacrificing speed, but that will take some significant optimization effort, and isn't suitable for a quick fix. I've opened an upstream issue [3] to track the code size, and try to avoid future regressions, and improve it in the long term. [0] https://lore.kernel.org/linux-mm/[email protected]/T/ [1] https://lkml.org/lkml/2021/11/15/710 [2] https://lkml.org/lkml/2021/11/14/189 [3] facebook/zstd#2867 Link: https://lore.kernel.org/r/[email protected]/ Link: https://lore.kernel.org/r/[email protected]/ Signed-off-by: Nick Terrell <[email protected]>
PreviousNext