[PATCH v4 0/4] xarray: add large folio support
by Huang Shijie
The linux kernel supports the large folio for page cache by default.
But the current CRASH does not support the large folio.
So we may meet the errors when we detected the large folio sometimes,
such as in the email:
https://www.spinics.net/linux/fedora/redhat-crash-utility/msg11238.html
------------------------------
files: page_to_nid: invalid page: 0
files: page_to_nid: invalid page: 0
files: page_to_nid: invalid page: 0
files: page_to_nid: invalid page: 10
files: page_to_nid: invalid page: 10
files: page_to_nid: invalid page: 10
files: page_to_nid: invalid page: 20
files: page_to_nid: invalid page: 20
files: page_to_nid: invalid page: 20
files: page_to_nid: invalid page: 30
files: page_to_nid: invalid page: 30
files: page_to_nid: invalid page: 30
files: page_to_nid: invalid page: 40
files: page_to_nid: invalid page: 40
files: page_to_nid: invalid page: 40
files: page_to_nid: invalid page: 50
files: page_to_nid: invalid page: 50
files: page_to_nid: invalid page: 50
files: page_to_nid: invalid page: 60
files: page_to_nid: invalid page: 60
------------------------------
The first 3 patches are used to add large folio support for CRASH.
The last patch is newly version of an old patch:
it add "files -n" command.
v3->>v4:
Fixes the BPF bug by:
1.) patch 1: Add a new type for do_xarray_info
2.) patch 3: Check XARRAY_TYPE_PAGE_CACHE for
do_xarray_count()/do_xarray_dump()/do_xarray_dump_cb()
v2-->v3:
Rewrited the folio_order() in patch 2 to work with different
kernel versions.
v1-->v2:
1.) Rebase the kernel to later 7.0-rc1(merge window)
2.) Fixed a bug in the patch 3, the latest kernel supports folios
whose page order is bigger then 5:
"xarray: add large folio support"
Huang Shijie (4):
xarray: add a new parameter for do_xarray
add folio_order function
xarray: add large folio support
add "files -n" command for an inode
bpf.c | 8 ++---
defs.h | 14 +++++++-
dev.c | 4 +--
diskdump.c | 10 ++++--
filesys.c | 94 +++++++++++++++++++++++++++++++++++++++++++++++-------
help.c | 24 +++++++++++++-
ipcs.c | 4 +--
kernel.c | 4 +--
memory.c | 74 ++++++++++++++++++++++++++++++++++++++++--
symbols.c | 6 ++++
task.c | 4 +--
tools.c | 16 ++++++++--
12 files changed, 230 insertions(+), 32 deletions(-)
--
2.43.0
4 months, 3 weeks
Sewn in beauty parlor
by ameliaemery545＠gmail.com
Step into the world of Sewn in Beauty Parlor, where every stitch tells a story. From delicate hair weaves to intricate embroidery, this isn’t just a salon—it’s an art space. Clients leave with more than beauty; they leave transformed, carrying confidence stitched into their very being. Imagine a place where creativity meets care, and style is tailored like a masterpiece. Have you ever experienced beauty so personal it feels custom-made?
https://ladybsalon.com/sew-in-weaves-hair-extensions-salon/
4 months, 3 weeks
Sewn in beauty parlor
by ameliaemery545＠gmail.com
Step into the world of [url=https://ladybsalon.com/sew-in-weaves-hair-extensions-salon/]Sewn in Beauty Parlor[/url], where every stitch tells a story. From delicate hair weaves to intricate embroidery, this isn’t just a salon—it’s an art space. Clients leave with more than beauty; they leave transformed, carrying confidence stitched into their very being. Imagine a place where creativity meets care, and style is tailored like a masterpiece. Have you ever experienced beauty so personal it feels custom-made.
4 months, 3 weeks
[PATCH 1/1] Fix cross-compilation of eppic.so and snapper.so
by Petr Tesařík
When cross-compiling, the extension modules must be built for the
target architecture, not the host architecture.
Do not hard-code "gcc" (which is usually the host compiler), but
use $(CC) to pick the right compiler.
Signed-off-by: Petr Tesarik <ptesarik(a)suse.com>
---
extensions/eppic.mk | 2 +-
extensions/snap.mk | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/extensions/eppic.mk b/extensions/eppic.mk
index 9435793..b51a84b 100644
--- a/extensions/eppic.mk
+++ b/extensions/eppic.mk
@@ -68,7 +68,7 @@ lib-eppic:
cd eppic/libeppic && make
eppic.so: ../defs.h $(APPFILE) lib-eppic
- gcc -g -O0 -Ieppic/libeppic -I.. -nostartfiles -shared -rdynamic -o eppic.so $(APPFILE) -fPIC $(TARGET_FLAGS) $(GDB_FLAGS) -Leppic/libeppic -leppic
+ $(CC) -g -O0 -Ieppic/libeppic -I.. -nostartfiles -shared -rdynamic -o eppic.so $(APPFILE) -fPIC $(TARGET_FLAGS) $(GDB_FLAGS) -Leppic/libeppic -leppic
clean:
if [ -d eppic/libeppic ]; \
diff --git a/extensions/snap.mk b/extensions/snap.mk
index 2fb4ed6..ac3f723 100644
--- a/extensions/snap.mk
+++ b/extensions/snap.mk
@@ -47,4 +47,4 @@ endif
all: snap.so
snap.so: $(INCDIR)/defs.h snap.c
- gcc -Wall -g -I$(INCDIR) -shared -rdynamic -o snap.so snap.c -fPIC -D$(TARGET) $(TARGET_CFLAGS) $(GDB_FLAGS)
+ $(CC) -Wall -g -I$(INCDIR) -shared -rdynamic -o snap.so snap.c -fPIC -D$(TARGET) $(TARGET_CFLAGS) $(GDB_FLAGS)
--
2.53.0
4 months, 3 weeks
[PATCH v3 0/4] xarray: add large folio support
by Huang Shijie
The linux kernel supports the large folio for page cache by default.
But the current CRASH does not support the large folio.
So we may meet the errors when we detected the large folio sometimes,
such as in the email:
https://www.spinics.net/linux/fedora/redhat-crash-utility/msg11238.html
------------------------------
files: page_to_nid: invalid page: 0
files: page_to_nid: invalid page: 0
files: page_to_nid: invalid page: 0
files: page_to_nid: invalid page: 10
files: page_to_nid: invalid page: 10
files: page_to_nid: invalid page: 10
files: page_to_nid: invalid page: 20
files: page_to_nid: invalid page: 20
files: page_to_nid: invalid page: 20
files: page_to_nid: invalid page: 30
files: page_to_nid: invalid page: 30
files: page_to_nid: invalid page: 30
files: page_to_nid: invalid page: 40
files: page_to_nid: invalid page: 40
files: page_to_nid: invalid page: 40
files: page_to_nid: invalid page: 50
files: page_to_nid: invalid page: 50
files: page_to_nid: invalid page: 50
files: page_to_nid: invalid page: 60
files: page_to_nid: invalid page: 60
------------------------------
The first 3 patches are used to add large folio support for CRASH.
The last patch is newly version of an old patch:
it add "files -n" command.
v2-->v3:
Rewrited the folio_order() in patch 2 to work with different
kernel versions.
v1-->v2:
1.) Rebase the kernel to later 7.0-rc1(merge window)
2.) Fixed a bug in the patch 3, the latest kernel supports folios
whose page order is bigger then 5:
"xarray: add large folio support"
Huang Shijie (4):
xarray: add a new parameter for do_xarray
add folio_order function
xarray: add large folio support
add "files -n" command for an inode
bpf.c | 8 +++---
defs.h | 14 +++++++++-
dev.c | 4 +--
diskdump.c | 10 +++++--
filesys.c | 77 ++++++++++++++++++++++++++++++++++++++++++++++--------
help.c | 24 ++++++++++++++++-
ipcs.c | 4 +--
kernel.c | 4 +--
memory.c | 74 +++++++++++++++++++++++++++++++++++++++++++++++++--
symbols.c | 6 +++++
task.c | 4 +--
tools.c | 16 +++++++++---
12 files changed, 213 insertions(+), 32 deletions(-)
--
2.43.0
5 months
How Case Studies, Reports, and Essays Differ in Academic Expectations
by Lily Johnson
This discussion aims to highlight the differences based on structure, purpose, and evaluation in the use of case studies, reports, and essays in university-based writings. Essays are mainly focused on the development of argumentation and critical analysis of theories, while reports are focused on the use of standardized structures, headings, data presentation, and the provision of recommendations. Case studies, on the other hand, require the application of theoretical knowledge in real-life situations, analysis of the supporting theories, and the provision of solutions.
Understanding these differences is essential in ensuring alignment with the marking criteria and the demonstration of appropriate knowledge in the chosen fields. The challenge often comes in the form of treating the three writing styles with an identical approach. For instance, while undertaking case studies, the application of analysis is critical, while essays require the application of theories. In academic forums, issues such as the provision of case study guidelines in Australia are often presented by the students as they seek to clarify the appropriate application of analysis. This session is expected to assist in the identification of the application of different approaches while maintaining integrity.
( https://www.newassignmenthelpaus.expert/case-study-help )
5 months, 1 week
How Case Studies, Reports, and Essays Differ in Academic Expectations
by Lily Johnson
This discussion aims to highlight the differences based on structure, purpose, and evaluation in the use of case studies, reports, and essays in university-based writings. Essays are mainly focused on the development of argumentation and critical analysis of theories, while reports are focused on the use of standardized structures, headings, data presentation, and the provision of recommendations. Case studies, on the other hand, require the application of theoretical knowledge in real-life situations, analysis of the supporting theories, and the provision of solutions.
Understanding these differences is essential in ensuring alignment with the marking criteria and the demonstration of appropriate knowledge in the chosen fields. The challenge often comes in the form of treating the three writing styles with an identical approach. For instance, while undertaking case studies, the application of analysis is critical, while essays require the application of theories. In academic forums, issues such as the provision of [case study guidelines in Australia](https://www.newassignmenthelpaus.expert/case-study-help) are often presented by the students as they seek to clarify the appropriate application of analysis. This session is expected to help in the identification of the application of different approaches while maintaining integrity.
5 months, 1 week
How Case Studies, Reports, and Essays Differ in Academic Expectations
by Lily Johnson
This discussion aims to highlight the differences based on structure, purpose, and evaluation in the use of case studies, reports, and essays in university-based writings. Essays are mainly focused on the development of argumentation and critical analysis of theories, while reports are focused on the use of standardized structures, headings, data presentation, and the provision of recommendations. Case studies, on the other hand, require the application of theoretical knowledge in real-life situations, analysis of the supporting theories, and the provision of solutions.
Understanding these differences is essential in ensuring alignment with the marking criteria and the demonstration of appropriate knowledge in the chosen fields. The challenge often comes in the form of treating the three writing styles with an identical approach. For instance, while undertaking case studies, the application of analysis is critical, while essays require the application of theories. In academic forums, issues such as the provision of [case study guidelines in Australia](https://www.newassignmenthelpaus.expert/case-study-help) are often presented by the students as they seek to clarify the appropriate application of analysis. This session is expected to help in the identification of the application of different approaches while maintaining integrity.
5 months, 1 week
