The document discusses processes and threads in an operating system. It defines a process as the basic unit of work that includes instructions, data, and resources. Key points include:
- Processes have states like ready, running, waiting. The OS manages processes through system calls for creation, termination, suspension, and more.
- Threads are lightweight processes that share resources within a process and allow for concurrency. Thread switching is faster than process switching.
- The OS maintains process information in a process control block and switches between processes and threads through context switching.
Gives an overview about Process, PCB, Process States, Process Operations, Scheduling, Schedulers, Interprocess communication, shared memory and message passing systems
In the given presentation, process overview,process management scheduling typesand some more basic concepts were explained.
Kindly refere the presentation.
Operating system - Process and its conceptsKaran Thakkar
This presentation gives an overview of Process concepts in Operating System. The presentation aims at alleviating most of the overheads while understanding the process concept in operating system. this tailor made presentation will help individuals to understand the overall meaning of process and its underlying concepts used in an operating system.
Gives an overview about Process, PCB, Process States, Process Operations, Scheduling, Schedulers, Interprocess communication, shared memory and message passing systems
In the given presentation, process overview,process management scheduling typesand some more basic concepts were explained.
Kindly refere the presentation.
Operating system - Process and its conceptsKaran Thakkar
This presentation gives an overview of Process concepts in Operating System. The presentation aims at alleviating most of the overheads while understanding the process concept in operating system. this tailor made presentation will help individuals to understand the overall meaning of process and its underlying concepts used in an operating system.
Builder.ai Founder Sachin Dev Duggal's Strategic Approach to Create an Innova...Ramesh Iyer
In today's fast-changing business world, Companies that adapt and embrace new ideas often need help to keep up with the competition. However, fostering a culture of innovation takes much work. It takes vision, leadership and willingness to take risks in the right proportion. Sachin Dev Duggal, co-founder of Builder.ai, has perfected the art of this balance, creating a company culture where creativity and growth are nurtured at each stage.
LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...DanBrown980551
Do you want to learn how to model and simulate an electrical network from scratch in under an hour?
Then welcome to this PowSyBl workshop, hosted by Rte, the French Transmission System Operator (TSO)!
During the webinar, you will discover the PowSyBl ecosystem as well as handle and study an electrical network through an interactive Python notebook.
PowSyBl is an open source project hosted by LF Energy, which offers a comprehensive set of features for electrical grid modelling and simulation. Among other advanced features, PowSyBl provides:
- A fully editable and extendable library for grid component modelling;
- Visualization tools to display your network;
- Grid simulation tools, such as power flows, security analyses (with or without remedial actions) and sensitivity analyses;
The framework is mostly written in Java, with a Python binding so that Python developers can access PowSyBl functionalities as well.
What you will learn during the webinar:
- For beginners: discover PowSyBl's functionalities through a quick general presentation and the notebook, without needing any expert coding skills;
- For advanced developers: master the skills to efficiently apply PowSyBl functionalities to your real-world scenarios.
Essentials of Automations: Optimizing FME Workflows with ParametersSafe Software
Are you looking to streamline your workflows and boost your projects’ efficiency? Do you find yourself searching for ways to add flexibility and control over your FME workflows? If so, you’re in the right place.
Join us for an insightful dive into the world of FME parameters, a critical element in optimizing workflow efficiency. This webinar marks the beginning of our three-part “Essentials of Automation” series. This first webinar is designed to equip you with the knowledge and skills to utilize parameters effectively: enhancing the flexibility, maintainability, and user control of your FME projects.
Here’s what you’ll gain:
- Essentials of FME Parameters: Understand the pivotal role of parameters, including Reader/Writer, Transformer, User, and FME Flow categories. Discover how they are the key to unlocking automation and optimization within your workflows.
- Practical Applications in FME Form: Delve into key user parameter types including choice, connections, and file URLs. Allow users to control how a workflow runs, making your workflows more reusable. Learn to import values and deliver the best user experience for your workflows while enhancing accuracy.
- Optimization Strategies in FME Flow: Explore the creation and strategic deployment of parameters in FME Flow, including the use of deployment and geometry parameters, to maximize workflow efficiency.
- Pro Tips for Success: Gain insights on parameterizing connections and leveraging new features like Conditional Visibility for clarity and simplicity.
We’ll wrap up with a glimpse into future webinars, followed by a Q&A session to address your specific questions surrounding this topic.
Don’t miss this opportunity to elevate your FME expertise and drive your projects to new heights of efficiency.
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
Neuro-symbolic is not enough, we need neuro-*semantic*Frank van Harmelen
Neuro-symbolic (NeSy) AI is on the rise. However, simply machine learning on just any symbolic structure is not sufficient to really harvest the gains of NeSy. These will only be gained when the symbolic structures have an actual semantics. I give an operational definition of semantics as “predictable inference”.
All of this illustrated with link prediction over knowledge graphs, but the argument is general.
Search and Society: Reimagining Information Access for Radical FuturesBhaskar Mitra
The field of Information retrieval (IR) is currently undergoing a transformative shift, at least partly due to the emerging applications of generative AI to information access. In this talk, we will deliberate on the sociotechnical implications of generative AI for information access. We will argue that there is both a critical necessity and an exciting opportunity for the IR community to re-center our research agendas on societal needs while dismantling the artificial separation between the work on fairness, accountability, transparency, and ethics in IR and the rest of IR research. Instead of adopting a reactionary strategy of trying to mitigate potential social harms from emerging technologies, the community should aim to proactively set the research agenda for the kinds of systems we should build inspired by diverse explicitly stated sociotechnical imaginaries. The sociotechnical imaginaries that underpin the design and development of information access technologies needs to be explicitly articulated, and we need to develop theories of change in context of these diverse perspectives. Our guiding future imaginaries must be informed by other academic fields, such as democratic theory and critical theory, and should be co-developed with social science scholars, legal scholars, civil rights and social justice activists, and artists, among others.
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
Let's dive deeper into the world of ODC! Ricardo Alves (OutSystems) will join us to tell all about the new Data Fabric. After that, Sezen de Bruijn (OutSystems) will get into the details on how to best design a sturdy architecture within ODC.
Key Trends Shaping the Future of Infrastructure.pdfCheryl Hung
Keynote at DIGIT West Expo, Glasgow on 29 May 2024.
Cheryl Hung, ochery.com
Sr Director, Infrastructure Ecosystem, Arm.
The key trends across hardware, cloud and open-source; exploring how these areas are likely to mature and develop over the short and long-term, and then considering how organisations can position themselves to adapt and thrive.
2. Out line
Concept of process
Process management
System calls for process management
Implicit and explicit task
Process relation ship
Process state
Implementation of process
Thread
3. What is process?
process is defined as an entity which represents the
basic unit of work to be implemented in the system.
A process is a program in execution.
The execution of a process must progress in a
sequential fashion.
we can define a process is an executing program,
including the current values of the program counter,
registers, and variables.
4. Cont….
A process includes:
Program counter:-Stores the code that the processor
executes
Stack:-Stores instructions and local variables for
active procedure calls
Data section:-Stores variables and dynamically
allocated memory
The subtle difference between a process and a
program is that:
Program is: the activity.
A group of instructions
Static entity
5. Cont…
Exist in a single space and continue to exist.
Programs contain instructions
Process
Dynamic entity
A group of instructions
Exist in a limited span of time.
Executes instruction, so Program ≠ process
6. Process management
A process needs certain resources,
including CPU time,
memory, files, and I/O devices, to
accomplish its task
The operating system is responsible for
the following activities in connection
with process management:
Process creation and deletion.
Termination of the process
7. Cont…
Controlling the progress of the process
Dispatching
Interrupt handling / Exceptional handling
Switching between the processes
Management of Process Control Blocks.
Process suspension and resumption (scheduling).
8. System call
System calls provide the interface between a process
and the operating system.
These system calls are the routine services of the
operating system.
As an example of how system calls are used, consider
writing a simple program to read data from one file and
to copy them to another file.
There are two names of two different files in which one
input file and the other is the output file.
One approach is for the program to ask the user for the
names of the two files.
9. Cot…
Examples of some operating system calls are:
Create: In response to the create call the operating system
creates a new process with the specified or default
attributes and identifier.
Some of the parameters definable at the process
creation time include:
Level of privilege, such as system or user
priority
size and memory requirements
10. Cont..
Delete: The delete service is also called destroy, terminate
or exit. Its execution causes the
operating system to destroy the designated process and
remove it from the system.
Abort: It is used to terminate the process forcibly.
Although a process could conceivably abort itself, the most
frequent use of this call is for involuntary terminations,
11. Cont…
Fork/Join: Another method of process creation and
termination is by means of FORK/JOIN pair, originally
introduced as primitives for multiprocessor system.
The FORK operations are used to split a sequence of
instruction into two concurrently executable sequences.
JOIN is used to merge the two sequences of code
divided by the FORK and it is available to a parent
process for synchronization with a child.
12. Cont..
Suspend: The suspend system call is also called BLOCK in
some systems.
The designated process is suspended indefinitely and
placed in the suspend state.
Resume: The resume system call is also called WAKEUP
in some systems.
Delay: The system call delay is also known as SLEEP.
13. Cont…
The target process is suspended for the duration of the
specified time period.
Get Attributes: It is an enquiry to which the operating
system responds by providing the current values of the
process attributes, or their specified subset, from the
PCB.
Change Priority: It is an instance of a more general SET-
PROCESS-ATTRIBUTES system call.
14. Implicit and Explicit Tasking
A separate process at run time can be either
Implicit tasking or Explicit tasking.
Implicit tasking means that processes are defined by the
system.
It is commonly encountered in general purpose
multiprogramming systems.
In this approach, each program submitted for execution is
treated by the operating system as an independent process.
15. Cont..
Explicit tasking means that programs explicitly
define each process and some of its attributes.
To improve the performance, a single logical
application is divided into various related
processes.
Explicit tasking is used in situations where high
performance in desired.
system programs such as parts of the operating
system and real time applications are common
examples of programs defined processes.
16. Processes Relationship
In the concurrent environment basically processes have
two relationships, competition and cooperation.
In the concurrent environment, processes compete
with each other for allocation of system resources to
execute their instructions.
In the competition, there should be proper resource
allocation and protection in address generation.
17. Cont…..
Cooperating process: In contrast to independent
processes, cooperating processes can affect or be
affected by other processes executing the system.
They are characterized by:
Their states are shared by other processes.
Their execution is not deterministic, i.e.,
the results of execution depend on relative execution
sequence and cannot be predicted in advance.
Their execution is irreproducible.
18. Process States
As defined, a process is an independent entity
with its own input values, output values, and
internal state.
A process often needs to interact with other
processes.
One process may generate some outputs that
other process uses as input.
It is also possible for a process that is ready and
able to run to be blocked because the operating
system is decided to allocate the CPU to other
process for a while.
19. Cont…
A process state may be in one of the following:
New: The process is being created.
After a process is created: parent and child have their own
distinct address spaces;
If either process changes a word in its address space:
Change is not visible to the other process;
20. Cont..
Ready: The process is waiting to be assigned to a
processor.
Running: Instructions are being executed.
Waiting/Suspended/Blocked: The process is waiting for
some event to occur.
Halted/Terminated: The process has finished execution.
21. Cont..
the process will terminate, usually due to one
of the following:
Normal exit (voluntary).
Error exit (voluntary).
Fatal error (involuntary).
Killed by another process (involuntary).
During the lifetime of a process, its state will
change a number of times:
23. Implementation of Processes
To implement the process model, the operating
system maintains a table, an array of structures,
called the process table or process control block
(PCB) or Switch frame.
Each entry identifies a process with information
such as process state, its program counter, stack
pointer, memory allocation, the status of its open
files, its accounting and scheduling information.
24. The following are the information stored in a PCB.
Process state, Process number( process ID)
CPU registers, Memory management information
I/O status information Processor scheduling information,
List of open files.
25. Context Switch
A context switch (also sometimes referred to as a
process switch or a task switch).
Is the switching of the CPU (central processing
unit) from one process or to another.
A context switch is sometimes described as the
kernel suspending execution of one process on
the CPU and resuming execution of some other
process that had previously been suspended.
27. Process Hierarchy
Modern general purpose operating systems permit a
user to create and destroy processes.
Aprocess may create several new processes during its
time of execution.
The creating process is called parent process, while the
new processes are called child processes.
28. Cont..
Execution: The parent process continues to execute
concurrently with its children processes or it waits until
all of its children processes have terminated.
Sharing: Either of them may share all resources, or the
children processes share only a subset of their parent’s
resources or the parent and children processes share no
resources in common.
29. What is thread
A thread is a flow of execution through the process
code, with its own program counter, system
registers and stack.
A thread is also called a light weight process. T
Each thread belongs to exactly one process and no
thread can exist outside a process.
Each thread represents a separate flow of control.
30. Difference between Process
and Thread
Process is heavy weight or resource intensive.
Thread is light weight taking lesser resources than a
process.
Process switching needs interaction with operating
system.
Thread switching does not need to interact with
operating system.
In multiple processing environments each process
executes the same code but has its own memory and
file resources.
31. Cont..
All threads can share same set of open files, child
processes.
If one process is blocked then no other process can
execute until the first process is unblocked.
While one thread is blocked and waiting, second
thread in the same task can run.
Multiple processes without using threads use more
resources. Multiple threaded processes use fewer
resources.
In multiple processes each process operates
independently of the others. One thread can read,
write or change
32. Advantages of Thread
Thread minimizes context switching time.
Use of threads provides concurrency within a
process.
Efficient communication.
Economy- It is more economical to create
and context switch threads.
Utilization of multiprocessor architectures to
a greater scale and efficiency
33. Disadvantages
In a typical operating system, most system
calls are blocking.
Multithreaded application cannot take
advantage of multiprocessing.
34. Types of Thread
Threads are implemented in following two ways
1, User Level Threads -- User managed threads
2, Kernel Level Threads -- Operating System managed
threads acting on kernel, an operating system core.
User Level Threads In this case, application manages
thread management kernel is not aware of the
existence of threads.
36. Cont..
Advantages Thread switching does not require Kernel
mode privileges.
User level thread can run on any operating system.
Scheduling can be application specific in the user level
thread.
User level threads are fast to create and manage.
Disadvantages In a typical operating system, most system
calls are blocking.
37. Kernel Level Threads
thread management done by the Kernel.
Kernel threads are supported directly by the operating
system.
Any application can be programmed to be multithreaded.
All of the threads within an application are supported
within a single process.
The Kernel performs thread creation, scheduling and
management in Kernel space. Kernel threads are generally
slower to create and manage than the user threads.
38. Cont…
Advantages Kernel can simultaneously schedule multiple
threads from the same process on multiple processes.
If one thread in a process is blocked, the Kernel can
schedule another thread of the same process.
Kernel routines themselves can multithreaded.
Disadvantages Kernel threads are generally slower to
create and manage than the user threads.
Transfer of control from one thread to another within
same process requires a mode switch to the Kernel.
40. Many to One Model
Many to one model maps many user level threads to one
Kernel level thread.
Thread management is done in user space.
When thread makes a blocking system call, the entire
process will be blocks.
Only one thread can access the Kernel at a time, so multiple
threads are unable to run in parallel on multiprocessors.
41. One to One Model
There is one to one relationship of user level
thread to the kernel level thread.
This model provides more concurrency than the
many to one model.
It also another thread to run when a thread
makes a blocking system call.
It support multiple thread to execute in parallel
on microprocessors.
42. Difference between User Level &
Kernel Level Thread
User level threads are faster to create and
manage.
Kernel level threads are slower to create and
manage.
In user level Implementation is by a thread library
at the user level.
In kernel level Operating system supports creation
of Kernel threads.