public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Julien Laganier <Julien.Laganier@Sun.COM>
To: Naveen Kumar Pagidimarri <naveen.pagidimarri@wipro.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Hai
Date: Fri, 06 Jul 2001 14:31:19 +0200	[thread overview]
Message-ID: <3B45AF97.C01C0ABF@Sun.COM> (raw)
In-Reply-To: <GG1WKM00.84G@vindhya.mail.wipro.com>

Naveen Kumar Pagidimarri wrote:
> 
> Hai All,
> 
>           I am trying to display the detailes of freeram and ramfilled
> 
> and number of current processes running thru a programme I don't want to
> 
> use system calls and getting info from proc files.I want to display
> 
> these detailes by accessing from sysinfo.Is it possible.Otherwise
> 
> suggest me where i can get related source.
> 
> Thank u all in advance
> 
#include <linux/kernel.h>
#include <linux/sys.h>

struct sysinfo {
long uptime;
unsigned long loads[3];  //machin's load during last minute, last five
min, and last 15 min.
unsigned long totalram;
unsigned long freeram;
unsigned long sharedram;
unsigned long bufferram;
unsigned long totalswap;
unsigned long freeswap;    
unsigned short procs;      //number of process
char[22] _f;              //padding to reach 64 bytes length
}

int sysinfo(struct sysinfo *info);

To browse the source code of open systems is the key :-)

-- 
"Memory is like gasoline. You use it up when you are running. Of
course you get it all back when you reboot..."; Actual explanation
obtained from the Micro$oft help desk.
--

    Julien Laganier
     Student Intern
Sun Microsystem Laboratories

      reply	other threads:[~2001-07-06 12:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-06 12:12 Hai Naveen Kumar Pagidimarri
2001-07-06 12:31 ` Julien Laganier [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3B45AF97.C01C0ABF@Sun.COM \
    --to=julien.laganier@sun.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=naveen.pagidimarri@wipro.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox