tools/testing/selftests/powerpc/nx-gzip/nx-gzip-test.sh
Source file repositories/reference/linux-study-clean/tools/testing/selftests/powerpc/nx-gzip/nx-gzip-test.sh
File Facts
- System
- Linux kernel
- Corpus path
tools/testing/selftests/powerpc/nx-gzip/nx-gzip-test.sh- Extension
.sh- Size
- 647 bytes
- Lines
- 47
- Domain
- Support Tooling And Documentation
- Bucket
- tools
- Inferred role
- Support Tooling And Documentation: tools
- Status
- atlas-only
Why This File Exists
Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
- Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
Dependency Surface
- No C-style include directives detected by the generator.
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
#!/bin/bash
# SPDX-License-Identifier: GPL-2.0-or-later
if [[ ! -w /dev/crypto/nx-gzip ]]; then
echo "Can't access /dev/crypto/nx-gzip, skipping"
echo "skip: $0"
exit 4
fi
set -e
function cleanup
{
rm -f nx-tempfile*
}
trap cleanup EXIT
function test_sizes
{
local n=$1
local fname="nx-tempfile.$n"
for size in 4K 64K 1M 64M
do
echo "Testing $size ($n) ..."
dd if=/dev/urandom of=$fname bs=$size count=1
./gzfht_test $fname
./gunz_test ${fname}.nx.gz
done
}
echo "Doing basic test of different sizes ..."
test_sizes 0
echo "Running tests in parallel ..."
for i in {1..16}
do
test_sizes $i &
done
wait
echo "OK"
exit 0
Annotation
- Atlas domain: Support Tooling And Documentation / tools.
- Implementation status: atlas-only.
Implementation Notes
- This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
- Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
- Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.