From: "Török Edwin" <edwintorok@gmail.com>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: LatencyTOP: sync_page description
Date: Fri, 15 Feb 2008 23:56:23 +0200 [thread overview]
Message-ID: <47B60A87.8000605@gmail.com> (raw)
Hi Arjan,
LatencyTOP says that sync_page is 'Writing a page to disk', however
I see that even when no writes are involved, such as during a
readdir, lseek, etc.
Naming it a write is misleading, as no program is running that is
doing constant writes to the disk. The only program is writing to a
temp dir in /dev/shm.
What would be a better description for sync_page?
Here are some /proc/latency_stats containing sync_page:
125 6937678 210821 sync_page sync_page_killable sync_page_killable
__lock_page_killable wake_bit_function generic_file_aio_read
get_unused_fd_flags path_walk do_sync_read autoremove_wake_function
security_file_permission rw_verify_area
306 5677749 215746 sync_page sync_page_killable sync_page_killable
__lock_page_killable wake_bit_function generic_file_aio_read
do_sync_read autoremove_wake_function security_file_permission
rw_verify_area vfs_read vfs_llseek
21 435657 59966 sync_page sync_page __lock_page wake_bit_function
read_cache_page_async ntfs_readpage read_cache_page map_mft_record
ntfs_read_locked_inode ntfs_alloc_big_inode iget5_locked
ntfs_test_inode
195 2716409 133660 blk_unplug sync_page sync_page __lock_page
wake_bit_function read_cache_page_async ntfs_readpage
read_cache_page map_mft_record ntfs_read_locked_inode
ntfs_alloc_big_inode iget5_locked
28 1881278 181986 add_to_page_cache_lru sync_page sync_page_killable
sync_page_killable __lock_page_killable wake_bit_function
generic_file_aio_read get_unused_fd_flags path_walk do_sync_read
autoremove_wake_function security_file_permission
2 17132 9746 add_to_page_cache_lru sync_page sync_page_killable
sync_page_killable __lock_page_killable wake_bit_function
generic_file_aio_read do_sync_read autoremove_wake_function
security_file_permission rw_verify_area vfs_read
1 70 70 irq_exit sync_page sync_page_killable sync_page_killable
__lock_page_killable wake_bit_function generic_file_aio_read
do_sync_read autoremove_wake_function security_file_permission
rw_verify_area vfs_read
23 306682 114514 blk_unplug sync_page sync_page_killable
sync_page_killable __lock_page_killable wake_bit_function
generic_file_aio_read do_sync_read autoremove_wake_function
security_file_permission rw_verify_area vfs_read
1 153 153 hrtimer_interrupt smp_apic_timer_interrupt sync_page
sync_page_killable sync_page_killable __lock_page_killable
wake_bit_function generic_file_aio_read do_sync_read
autoremove_wake_function cfq_idle_slice_timer security_file_permission
Thanks,
--Edwin
next reply other threads:[~2008-02-15 21:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-15 21:56 Török Edwin [this message]
2008-02-18 3:40 ` LatencyTOP: sync_page description Nick Piggin
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=47B60A87.8000605@gmail.com \
--to=edwintorok@gmail.com \
--cc=arjan@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.