Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8215965
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 7, 20262026-06-07T11:58:02+00:00 2026-06-07T11:58:02+00:00

I have a daemon written in C running under a RHEL 4 machine. The

  • 0

I have a daemon written in C running under a RHEL 4 machine.

The daemon access a segment of shared memory (nothing more than a big array of 65536 elements). No malloc/free are done.

I observed that ps aux shows that the daemon has the size of shared memory + some kb as VSZ and just some kb as RSS.

Then, the more the daemon access shared memory array, the more RSS increase until reaching circa the same size of VSZ.

Why Linux calculate the RSS in this way?

I mean… shared memory shouldn’t be ignored as memory consumpted (RSS) by a single process, because it can be accessed by many others runnables?

And why it raise the RSS just accessing shared memory?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-07T11:58:03+00:00Added an answer on June 7, 2026 at 11:58 am

    RSS is the amount of physical memory mapped to your process.

    Linux employs demand paging so that physical memory only gets mapped on the first access. VSZ is virtual memory which gets backed by physical memory on demand. This explains why your RSS grows as you access more of the shared memory mapping.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have a daemon app written in C and is currently running with no
I have started a service daemon , by running the binary(written in C++) through
I have written a linux daemon that will be (and must be) running as
I have a daemon I have written using Python. When it is running, it
Is it so memory consuming to have a daemon written on php (which listens/process
I have a daemon process written in Perl that uses Inotify2 to watch directories
We have a small daemon application written in C for a couple of various
I have written a server daemon (Linux, Ubuntu) which communicates with PHP as frontend
I have written a simple Java dispatcher with a daemon thread to handle the
I have a python daemon running as a part of my web app/ How

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.