Open Hub
Open Hub

 Settings |  Report Duplicate

0
I Use This!
Activity Not Available

Commits : Listings

Analyzed 4 months ago. based on code collected 4 months ago.
Jul 20, 2025 — Jul 20, 2026
Commit Message Contributor Files Modified Lines Added Lines Removed Code Location Date
Updated VIRGO design document
ka_shrinivaasan
More... over 11 years ago
virgo_kernel_analytics_config type has been defined for extern-ed config key-value array EXPORTed from VIRGO kernel analytics module
ka_shrinivaasan
More... over 11 years ago
virgo_kernel_analytics_conf key-value pair array has been EXPORTed for other VIRGO Linux modules to import and use.
ka_shrinivaasan
More... over 11 years ago
- Updated VIRGO config driver build which looks-up the exported kernel_analytics key-value configs set manually and by Apache Spark(mined from /var/log/kern.log Uncomplicated FireWall logs)
ka_shrinivaasan
More... over 11 years ago
Updated kernel_analytics kernel objects, symbols build
ka_shrinivaasan
More... over 11 years ago
Kern.log for below code changes in VIRGO config and kernel_analytics: -------------------------------------------------------------- - Config variables in /etc/virgo_kernel_analytics.conf are read by kernel_analytics and exported - Above variables are looked-up in config driver and printed (EXPORT_SYMBOL and merged Module.symvers) - The config key-value "SRC = 111.123.180.44" was mined by Apache Spark Transformation RDD MapReduce of /var/log/kern.log Uncomplicated FireWall logs and set in /etc/virgo_kernel_analytics.conf
ka_shrinivaasan
More... over 11 years ago
Updated Modules Load Order
ka_shrinivaasan
More... over 11 years ago
Updated VIRGO Design Document
ka_shrinivaasan
More... over 11 years ago
header file for VIRGO kernel_analytics kernel module
ka_shrinivaasan
More... over 11 years ago
Updated comment
ka_shrinivaasan
More... over 11 years ago
new config file for VIRGO kernel_analytics in /etc
ka_shrinivaasan
More... over 11 years ago
Updated /etc/modules for kernel_analytics
ka_shrinivaasan
More... over 11 years ago
kern.log for kernel_analytics module load and parsing of /etc/virgo_kernel_analytics.conf
ka_shrinivaasan
More... over 11 years ago
Initial commits for Kernel Analytics Module which reads the /etc/virgo_kernel_analytics.conf config ---------------------------------------------------------------------------------------------------- 1. This config file virgo_kernel_analytics.conf having csv(s) of key-value pairs of analytics variables set by AsFer or any other Machine Learning code. With this VIRGO Linux Kernel is endowed with abilities to dynamically evolve than being just a platform for user code. Implications are huge - for example, a config variable "MaxNetworkBandwidth=255" set by the ML miner in userspace based on a Perceptron or Logistic Regression executed on network logs can be read by a kernel module that limits the network traffic to 255Mbps. Thus kernel dynamically changes behaviour.
ka_shrinivaasan
More... over 11 years ago
VIRGO Linux Kernel Key-Value Store Architecture (memorypooling driver) and all VIRGO kernel Modules Interaction Overview Diagrams
ka_shrinivaasan
More... over 11 years ago
Updated ProductOwnerProfile
ka_shrinivaasan
More... over 11 years ago
Updated ProductOwnerProfile
ka_shrinivaasan
More... over 11 years ago
Updated VIRGO Design Document
ka_shrinivaasan
More... almost 12 years ago
Updated VIRGO Design Document
ka_shrinivaasan
More... almost 12 years ago
EventNet vertex file append bugfix: ---------------------------------- - set_fs() start/end clauses scope expanded to entire function - APPEND flag removed for vertices file - kern.log with edge and vertex messages and kernel generated vertices and edges files with this bug resolution - build generated binaries and sources
ka_shrinivaasan
More... almost 12 years ago
- GFP_KERNEL allocs made to GFP_ATOMIC allocs - type int changed to loff_t for prevreadpos due to invalid argument error (-22) - more debug printk(s) - But still the vfs_write() has a problem in writing to the prevreadpos offset. In the logs though prevreadpos is 0 vfs_write() doesnot overwrite the offset from 0 but appends
ka_shrinivaasan
More... almost 12 years ago
kern.log and kernel generated EventNet vertices and edges text files
ka_shrinivaasan
More... almost 12 years ago
Updated ProductOwnerProfile
ka_shrinivaasan
More... almost 12 years ago
code changes for eventnet_vertexmsg bugs, kern.log and screenshots, kernel object files and build sources
ka_shrinivaasan
More... almost 12 years ago
ONGOING:
ka_shrinivaasan
More... almost 12 years ago
Updated VIRGO Design Document
ka_shrinivaasan
More... almost 12 years ago
Bugfix for the eventnet_vertexmsg clause - new vertex or updating an existing vertex partakers and conversations
ka_shrinivaasan
More... almost 12 years ago
Miscellaneous bugfixes,logs and screenshot ------------------------------------------ - virgo_cloudexec_eventnet.c - eventnet messages parser errors and eventnet_func bugs fixed - virgo_cloud_eventnet_kernelspace.c - filp_open() args updated due to vfs_write() kernel panics. The vertexmessage vfs_write is done after looping through the vertice textfile and appending the conversation to the existing vertex.Some more code has to be added. - VIRGO EventNet build script updated for copying Module.symvers from utils driver for merging with eventnet Module.symvers during Kbuild - Other build generated sources and kernel objects - new testlogs directory with screenshot for edgemsg sent to EventNet kernel service and kern.log with previous history for vfs_write() panics due to permissions and the logs for working filp_open() fixed version
ka_shrinivaasan
More... almost 12 years ago
Updated VIRGO Design Document and ModulesListenPorts.txt
ka_shrinivaasan
More... almost 12 years ago
Initial code commits for VIRGO EventNet kernel module service: -------------------------------------------------------------- 1.EventNet Kernel Service listens on port 20000 2.It receives eventnet log messages from VIRGO cloud nodes and writes the log messages after parsing into two text files /var/log/eventnet/EventNetEdges.txt and /var/log/eventnet/EventNetVertices.txt b VFS call$ 3.These text files can then be processed by the EventNet implementations in AsFer (python pygraph and C+$ 4.Two new directories virgo/utils and virgo/eventnet have been added. 5.virgo/eventnet has the new VIRGO EventNet kernel module service implementation that listens on port 20$ 6.virgo/utils is the new generic utilities driver that has a virgo_eventnet_log() export function which $ 7.EventNet log messages have two formats: - Edge message - "eventnet_edgemsg#<id>#<from_event>#<to_event>" - Vertex message - "eventnet_vertextmsg#<id>#<partakers csv>#<partaker conversations csv>" 8.The utilities driver Module.symvers have to be copied to any driver which are then merged with the sym$ 9.virgo/utils driver can be populated with all necessary utility exported functions that might be needed$ 10.Calls to virgo_eventnet_log() have to be #ifdef guarded as this is quite network intensive.
ka_shrinivaasan
More... almost 12 years ago