today's leftovers

-
XFS : Project Update
When the number of entries are small enough we can store all the metadata information in inode core data itself, we call it shortform directories. My first task was to test V4 support for shortform directories aggressively, since implementation was correct and simple enough it passed all my tests. Then I tried to read V5 shortform directories and ofcourse it failed and the reason was inode core size. Xfs V4 has 256 bytes while V5 has 512 bytes inode, so the offset at which metadata is stored is different for both the versions. I implemented some helper functions to give us the correct data fork pointer based on the version of xfs and soon we were able to read V5 shortform entries, Later I did some testing and it passed all my tests.
After that I began my work for block directory, ofcourse the number of entries would increase and we will no longer be able to store all metadata in inode itself so we use block directory and the format is changed to extents. Now things started to become interesting, there were new fields introduced in V5 block headers and I needed to elegantly handle it with V4 headers as well.
PulkoMandy suggested I have two options for this: either go with virtual class or templates. I decided we will be using virtual class as it will be more consistent with our xfs code and implement as many methods as we need along with function to create class instance as per version of xfs mounted. Since now we have virtual class with vPtrs we need to be very careful with class and its on-disk structure, for example we now can’t use sizeof() operator on virtual class to match with data stored on disk, I added warnings on code about this on function which should be used instead of sizeof() operator.As the roadmap on how to handle both versions was clear to me I extended V5 read support for leaf, node, B+tree based directory and files as well.
-
Linux Weekly Roundup #192
Welcome to this week's Linux Weekly Roundup.
We have a good week in the world of Linux releases with Garuda Linux 220717 and Pardus 21.3.
I hope you have a wonderful week and a lovely summer!
-
Qualcomm launches wearable chips that may finally meet the moment
Qualcomm has redesigned its silicon designed for wearable devices such as smart watches and activity trackers to launch what it’s calling the Snapdragon W5+ wearable platform. These designs are completely new and hopefully will help the makers of every other smart watch that isn’t an Apple Watch finally compete against the Cupertino-designed device.
The new Qualcomm silicon embraces the concept of an ambient mode, offloading several sensing and other processes to co-processors that save on power without sacrificing performance. The design takes sensors such as heart rate and microphones for voice activation and embeds them on an always-on microprocessor. Qualcomm has also put a smaller GPU on this always-on chip so the screen gets cool visuals in ambient mode. Finally, it has put notifications and audio playback on this lower performance, low-power always-on processor to save on battery life.
-
- Login or register to post comments
Printer-friendly version- 3971 reads
PDF version
More in Tux Machines
- Highlights
- Front Page
- Latest Headlines
- Archive
- Recent comments
- All-Time Popular Stories
- Hot Topics
- New Members
today's howtos
| Open Hardware: XON/XOFF and Raspberry Pi Pico
|
Security Leftovers
| How to Apply Accent Colour in Ubuntu Desktop
A step-by-step tutorial on how to apply accent colour in Ubuntu desktop (GNOME) with tips for Kubuntu and others.
|



This section of TuxMachines will no longer have new stories in it (with some caveats, including this post). To see the latest stories go to

.svg_.png)
Content (where original) is available under CC-BY-SA, copyrighted by original author/s.


Recent comments
2 days 5 hours ago
2 days 9 hours ago
2 days 9 hours ago
3 days 16 hours ago
3 days 17 hours ago
3 days 18 hours ago
3 days 18 hours ago
3 days 19 hours ago
3 days 21 hours ago
3 days 23 hours ago