From: li nux <lnxluv@yahoo.com>
To: linux <linux-kernel@vger.kernel.org>
Subject: ext2: buffer_head usage with and without O_DIRECT
Date: Sun, 24 Jul 2005 06:16:04 -0700 (PDT) [thread overview]
Message-ID: <20050724131604.89173.qmail@web33308.mail.mud.yahoo.com> (raw)
This is with respect to 2.4.28 on
http://lxr.linux.no/source/?v=2.4.18
When i do read/write on ext2 without opening files
with O_DIRECT, i can see buffer_head constantly
increasing in /proc/slabinfo.
But when I open files with O_DIRECT, the i/o is done
without using buffer_head, /proc/slabinfo shows this
as constant throughout the i/o.
There is no other i/o activity on the box.
Stacks below show that both of them creates
buffer_head's. Any idea why this is happening ?
As per the code, Without O_DIRECT, stack is:
(See fs/buffer.c)
submit_bh_rsector
submit_bh
block_read_full_page (This calls create_buffers to
create buffer_head's)
ext2_readpage
do_generic_file_read
generic_file_new_read
generic_file_read
With O_DIRECT:
brw_kiovec (This creates buffer_head's)
generic_direct_sector_IO (cals
prepare_direct_IO_iobuf)
ext2_direct_IO
generic_file_direct_IO
generic_file_new_read
generic_file_read
-Thanks.
____________________________________________________
Start your day with Yahoo! - make it your home page
http://www.yahoo.com/r/hs
reply other threads:[~2005-07-24 13:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20050724131604.89173.qmail@web33308.mail.mud.yahoo.com \
--to=lnxluv@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
all inboxes | Powered by JetHome®