From: "Randy.Dunlap" <rddunlap@osdl.org>
To: selvakumar nagendran <kernelselva@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Pipefs : doubts
Date: Sun, 09 Jan 2005 21:57:43 -0800 [thread overview]
Message-ID: <41E21957.7030406@osdl.org> (raw)
In-Reply-To: <20050110050450.51158.qmail@web60608.mail.yahoo.com>
selvakumar nagendran wrote:
> Hello linux-experts,
> I went through the kernel source code file
> /fs/pipe.c and I found that the pipe file system
> configured as a module. But in lsmod I am unable to
> see it. This is my first doubt.
Where do you see that?
fs/pipe.o is always built into the kernel image.
> My second doubt is, in pipe.c we have lot of
> symbols like
>
> PIPE_WAITING_READERS(*inode)
> PIPE_WAIT(*inode)
> PIPE_MAX_RCHUNK(*inode)
> What are they? funtions or macros? What they do or
> where are their implementation in the kernel source
> tree?
Macros.
See include/linux/pipe_fs_i.h
--
~Randy
next prev parent reply other threads:[~2005-01-10 6:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-10 5:04 Pipefs : doubts selvakumar nagendran
2005-01-10 5:57 ` Randy.Dunlap [this message]
2005-01-10 6:38 ` Module : " selvakumar nagendran
2005-01-10 14:48 ` Randy.Dunlap
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=41E21957.7030406@osdl.org \
--to=rddunlap@osdl.org \
--cc=kernelselva@yahoo.com \
--cc=linux-kernel@vger.kernel.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).