kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: martinez.javier@gmail.com (Javier Martinez Canillas)
To: kernelnewbies@lists.kernelnewbies.org
Subject: system call
Date: Sun, 12 Jun 2011 02:59:33 +0900	[thread overview]
Message-ID: <BANLkTi=3rXTPiUSud7GSHOUvkZqni4QSAQ@mail.gmail.com> (raw)
In-Reply-To: <BANLkTinMy1fwbjF04pH=EZ5qM9D=Eht22w@mail.gmail.com>

On Sat, Jun 11, 2011 at 6:39 PM, Venkateswarlu P
<p.venkatesh551@gmail.com> wrote:
>
>
> Where do i find system call implementation code?
>
> for? read, write, open, close

For file system related syscalls, it would depend on the fs
implementation. The Virtual File System only defines a uniform common
high level layer but is the responsibility of every fs to actually
implement the file operations (open, read, write, etc).

There is some generic file operations in linux/fs/read_write.c that
are used for simple fs like romfs and ramfs. I would recommend start
looking at these memory file systems first.

Then you could look how real file systems operations are implemented.
Every fs usually have a file.c file where a struct file_operations is
defined. This structure has a function pointer for every file
operation. The functions asigned to these function pointers are the
ones that actually implements the operations. Some of these could be
generic operations and some of them are fs specific.

Hope it helps,

-- 
Javier Mart?nez Canillas
(+34) 682 39 81 69
PhD Student in High Performance Computing
Computer Architecture and Operating System Department (CAOS)
Universitat Aut?noma de Barcelona
Barcelona, Spain

  parent reply	other threads:[~2011-06-11 17:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-11  9:39 system call Venkateswarlu P
2011-06-11  9:58 ` Rajat Sharma
2011-06-11 17:59 ` Javier Martinez Canillas [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-04-07  6:23 Nitin Varyani
2016-04-07  6:30 ` Giedrius Statkevičius
2016-04-07  6:45 ` Sharath Chandra
2016-04-07  7:38 ` Pranay Srivastava
2016-04-09 11:33   ` Nitin Varyani
2016-04-09 14:09     ` Pranay Srivastava
2016-04-09 14:21       ` Nitin Varyani
2016-04-09 14:34         ` Pranay Srivastava
2016-04-09 14:41           ` Nitin Varyani
2016-04-09 14:46             ` Pranay Srivastava

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='BANLkTi=3rXTPiUSud7GSHOUvkZqni4QSAQ@mail.gmail.com' \
    --to=martinez.javier@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.org \
    /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;
as well as URLs for NNTP newsgroup(s).