Yahoo Web Search

Search results

1. Top results related to computer system architecture

   • Computer Architecture: How do applications communicate with an operating system?

     Top Answer

     Answered Oct 18, 2017 · 3 votes

     Too broad question, but some points (related to Linux; the principles should be the same for Windows, but you probably are forbidden to understand all of it) :

     The elementary system calls (those listed in syscalls(2)...) are invoked by an elementary machine instruction (e.g. SYSENTER or SYSCALL) which switches the processor into kernel mode (with the system call number and arguments passed through defined registers, following the ABI convention). Hence user-space code can be viewed as running in some virtual machine (defined by user-mode instructions + the system call primitives). BTW the Linux kernel can load kernel modules to e.g. add additional code (such as device drivers) in it, and that is done also thru system calls.

     The inter-process communication facilities are built above these system calls (perhaps used by the standard library in higher level functions, e.g. getaddrinfo(3) might interact indirectly with some DNS service, see nsswitch.conf(5)). Read Advanced Linux Programming for more details. In practice you'll need several server programs (and that idea is pushed to its extreme in microkernel approaches), notably (on recent Linux) systemd. Drivers and kernel modules are loaded by specific system calls and later are part of the kernel so are usable thru other system calls. Play with strace(1) to understand the actual system calls done by some Linux program. Some information is provided by the kernel thru pseudo file systems (see proc(5)...) accessible thru system calls.

     Every communication from user program to kernel is done by IPC (implemented by system calls). Sometimes, the kernel is doing an upcall to user code (on Linux, with signals).

     The Linux framebuffer (and the physical keyboard & mouse) is generally only accessed by a single server which other desktop applications communicate with using usual IPC facilities -sockets-, that server is the X11 or Wayland server.

     Read also some good book on Operating Systems, e.g. the freely downloadable Operating Systems: Three Easy Pieces

     For Windows, MacOSX, Android, it is very similar. However, since Windows (etc...) is a proprietary software, you might not be able to know all the details (and you might not be allowed to reverse-engineer them). In contrast, Linux is free software, so you can study its source code.

     My advice would be to understand in details how Linux work (this would take several years) and study some relevant source code (which is possible for free software). If you need an deep understanding of Windows, you might need to buy some source code license of it (probably millions of dollars) and sign an NDA. I don't know Windows at all, but AFAIK it is only defined by a huge API in C. Rumors tell that the Windows kernel is microkernel like, but Microsoft has economical interest to hide ugly implementation details.

     See also osdev.

     Check all answers on Stack Overflow

     1/5

   • system design vs system architecture

     Top Answer

     Answered Aug 20, 2022 · 3 votes

     No, they are not the same, but they are related.

     System design is the process when you try to come up with a viable solution (or multiple ones) based on the provided requirements. You tries to specify smaller components with well-defined responsibilities. Also you define how (and when) they are interacting with each other.

     System architecture is the artifact of the former process. It captures how did you divide the problem space into smaller chunks and how your components as a whole try to solve the original big problem.

     UPDATE #1: Provide example

     In order to better illustrate the differences let me provide you a super simplified example.

     Context

     Let's suppose you have a bunch of microservices and some of them are abused sometimes. During resource abuse the service becomes slow and unresponsive.

     In order to mitigate this, business decides to introduce rate limiting.

     Design

     The steps are reduced and simplified to ease understanding.

     • Clarify with the business whether they meant request queueing or throttling
     • Agree on terminology to prefer rate limiting over throttling
     • Do some research about industry standard algorithms and data structures
     • Make a comparison between leaky bucket and token bucket
     • Check whether there is an existing solution which can be used in a way that satisfies all requirements
     • Decide which endpoints should be protected
     • Document your finding and decisions

     Artifacts

     • One or multiple Proof of concepts to verify all requirements can be met with the chosen library/libraries
     • An Architecture Decision Record to capture which library should be used in which programming language in case of rate limiting
     • Another ADR to document how should clients handle rate limitation For example: they should retry the request if they have received 429 response code and respect the retry-after header
     • Update(s) on the architecture diagram(s) to indicate which services utilize rate limiting Or an introduction of an API gateway to have a centralized place for common concerns
     • A specification how to setup the rate limiting rules Like: 100 reqs / min, 1 000 reqs / hours

     UPDATE #2: Reflect to the OP's example

     Suppose I am designing tinyUrl, if I am doing system design, I will do the followings:

     • I collect requirements
     • I will check the estimation of usage such as traffic and bandwidth
     • based on this, I can have a database schema,
     • I will check the storage based on the database schema
     • I will create API for my system
     • create abstract system flow ex) client -> application -> server -> database
     • consider data partitioning and replication to accommodate latency, availability and reliability
     • check possible cache usage
     • lastly, do bit more detailed data flow within the system. For example, use load balancing.

     Same example with system architecture would be more about implementation detail what kind of technology I will choose to use?

     As I said before system design is the process whereas system architecture is the outcome of the design process. What you have described is the process, which may/may not include technology selection.

     • In case of a component related feature design you might want to include the suggested technologies/libraries as well in your system architecture
     • In case of an integration design you will focus more on the communication protocols, edge cases, security and so on ...

     Let me try to capture the difference from another angle. Whenever you design a solution for a particular problem then you explore different alternatives and try to choose wisely based on the requirements. Your proposed architecture captures your designs to be able to reason about the system. But this is a living thing. It can change over time as new requirements come in.

     Check all answers on Stack Overflow

     2/5

   • System Architecture

     Top Answer

     Answered Nov 19, 2009 · 1 votes

     It depends on what you mean by "64 bit machine". There are broadly three categories depending on processor family:

     • Supports some 64-bit math operations
     • Can run programs in X-64 mode (64-bit addressing)
     • Has 64-bit kernel support

     I assume that you mean sense "2" here, since that's the most relevant for application code. You don't have to worry about sense "1" unless you need to run on older PowerPC Macs, I believe.

     You specifically mentioned doing this in C code, which doesn't actually make much sense. If you're compiling C code, you can just build your application "fat", with 32- and 64- bit variants, and therefore do the check at compile-time with:

     #if _LP64//64-bit stuff#else//32-bit stuff#endif-

     Check all answers on Stack Overflow

     3/5

   • System Design of Uber App | Uber System Architecture

     Getting the hassle-free transportation service(Uber, Ola) is very easy but is it also simple to build these gigantic applications that have hundreds of software engineers working on them for a decade? surely not. These systems have much more complex architecture and there are a lot of components joined together internally to provide riding services all over the world.

     <img alt="Working-of-Uber-App-(1)">

     Important Topics for the System Design of Uber App

     • Requirements
     • Capacity Estimation
     • Uber App Low-Level Design
     • High-Level Design of Uber App

     1. Requirements

     1.1 Functional requirements

     Users should be able to cancel...

     • Users should be able to see all the cabs available with minimum price and ETA
     • Users should be able to book a cab for their destination
     • Users should be able to see the location of the driver
     • Users should be able to cancel their ride whenever they want

     Check all answers on Geeksforgeeks

     4/5

   • Also try

     computer system architecture by morris mano 3rd edition pdf	computer system architecture notes
     computer system architecture in operating system	computer system architecture ppt
     computer system architecture pdf	computer system architecture tutorial
     morris mano computer system architecture	computer system architecture definition

     5/5

   Show moreShow less

2. www.spiceworks.com › tech › tech-generalComputer Architecture: Components, Types and Examples -...

   www.spiceworks.com › tech › tech-general

   • Cached

   May 11, 2023 · Computer architecture refers to the end-to-end structure of a computer system that determines how its components interact with each other in helping to execute the machine’s purpose (i.e., processing data), often avoiding any reference to the actual technical implementation.

3. en.wikipedia.org › wiki › Computer_architectureComputer architecture - Wikipedia

   en.wikipedia.org › wiki › Computer_architecture

   • Cached

   Computer architecture is concerned with balancing the performance, efficiency, cost, and reliability of a computer system. The case of instruction set architecture can be used to illustrate the balance of these competing factors.

4. www.geeksforgeeks.org › computer-organization-and-architecture-tutorialsComputer Organization and Architecture Tutorial - GeeksforGeeks

   www.geeksforgeeks.org › computer-organization-and-architecture-tutorials

   • Cached

   4 days ago · Computer architecture is the conceptual design and fundamental operational structure of a computer system. It encompasses the layout of the hardware, the design of the instruction set, and the techniques for data handling and processing.

5. www.tutorialspoint.com › Computer-System-ArchitectureComputer System Architecture - Online Tutorials Library

   www.tutorialspoint.com › Computer-System-Architecture

   • Cached

   Sep 2, 2023 · A computer system is basically a machine that simplifies complicated tasks. It should maximize performance and reduce costs as well as power consumption. The different components in the Computer System Architecture are Input Unit, Output Unit, Storage Unit, Arithmetic Logic Unit , Control Unit etc.

6. ocw.mit.edu › courses › 6-823-computer-system-architecture-fall-2005Computer System Architecture | Electrical Engineering and ...

   ocw.mit.edu › courses › 6-823-computer-system-architecture-fall-2005

   • Cached

   6.823 is a course in the department’s “Computer Systems and Architecture” concentration. 6.823 is a study of the evolution of computer architecture and the factors influencing the design of hardware and software elements of computer systems.

7. ocw.ece.cornell.edu › courses › ece-4750-computer-architectureECE 4750 Computer Architecture – Cornell ECE Open Courseware

   ocw.ece.cornell.edu › courses › ece-4750-computer-architecture

   • Cached

   This course provides a strong foundation in modern computer system architecture by drawing together concepts from across the electrical and computer engineering curriculum including digital logic design, computer organization, system-level software techniques, and engineering design.

8. www.coursera.org › learn › comparchComputer Architecture | Coursera

   www.coursera.org › learn › comparch

   • Cached

   Computer architecture encompasses the design and organization of a computer's components, determining its performance and functionality.

9. ocw.mit.edu › courses › 6-823-computer-system-architecture-fall-2005Lecture Notes | Computer System Architecture | Electrical...

   ocw.mit.edu › courses › 6-823-computer-system-architecture-fall-2005

   • Cached

   Lecture Notes. The course material is divided into five modules, each covering a set of related topics. This section contains the lecture notes for the course.

10. www.codecademy.com › learn › computer-architecture-introductionComputer Architecture: Introduction | Codecademy

    www.codecademy.com › learn › computer-architecture-introduction

    • Cached

    Take Computer Architecture: Introduction and dive into the world of the computer and its inner workings. Computer architecture describes the rules, organization of components, and processes that make a computer functional.

11. www.codecademy.com › learn › computer-architectureComputer Architecture | Codecademy

    www.codecademy.com › learn › computer-architecture

    • Cached

    In this course, you’ll learn about what the main physical components of a computer are, why 0 and 1 are such important numbers within computing, how instruction set architecture (ISA) establishes communication between the hardware and software components of a computer, and more.