From: Andreas Dilger <adilger@dilger.ca>
To: Andy Lutomirski <luto@amacapital.net>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: Latency writing to an mlocked ext4 mapping
Date: Wed, 19 Oct 2011 19:02:46 -0600 [thread overview]
Message-ID: <ACE78D84-0E94-4E7A-99BF-C20583018697@dilger.ca> (raw)
In-Reply-To: <CALCETrXbPWsgaZmsvHZGEX-CxB579tG+zusXiYhR-13RcEnGvQ@mail.gmail.com>
What kernel are you using? A change to keep pages consistent during writeout was landed not too long ago (maybe Linux 3.0) in order to allow checksumming of the data.
We discussed doing copy-on-write, but there are relatively few mmap users and it wasn't clear whether the complexity was worth it.
Cheers, Andreas
On 2011-10-19, at 6:39 PM, Andy Lutomirski <luto@amacapital.net> wrote:
> I have a real-time program that has everything mlocked (i.e.
> mlockall(MCL_CURRENT | MCL_FUTURE)). It has some log files opened for
> writing. Those files are opened and memset to zero in another thread
> to fault everything in. The system is under light I/O load with very
> little memory pressure.
>
> Latencytop shows frequent latency in the real-time threads. The main
> offenders are:
>
> schedule sleep_on_page wait_on_page_bit ext4_page_mkwrite do_wp_page
> handle_pte_fault handle_mm_fault do_page_fault page_fault
>
> schedule do_get_write_access jbd2_journal_get_write_access
> __ext4_journal_get_write_access ext4_reserve_inode_write
> ext4_mark_inode_dirty ext4_dirty_inode __mark_inode_dirty
> file_update_time do_wp_page handle_pte_fault handle_mm_fault
>
>
> I imagine the problem is that the system is periodically writing out
> my dirty pages and marking them clean (and hence write protected).
> When I try to write to them, the kernel makes them writable again,
> which causes latency either due to updating the inode mtime or because
> the file is being written to disk when I try to write to it.
>
> Is there any way to prevent this? One possibility would be a way to
> ask the kernel not to write the file out to disk. Another would be a
> way to ask the kernel to make a copy of the file when it writes it
> disk and leave the original mapping writable.
>
> Obviously I can fix this by mapping anonymous memory, but then I need
> another thread to periodically write my logs out to disk, and if that
> crashes, I lose data.
>
> --
> Andy Lutomirski
> AMA Capital Management, LLC
> Office: (310) 553-5322
> Mobile: (650) 906-0647
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-10-20 1:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-20 0:39 Andy Lutomirski
2011-10-20 1:02 ` Andreas Dilger [this message]
2011-10-20 1:15 ` Andy Lutomirski
2011-10-20 2:17 ` Andy Lutomirski
2011-10-20 5:59 ` Andy Lutomirski
2011-10-25 12:26 ` Jan Kara
2011-10-28 23:37 ` Andy Lutomirski
2011-10-28 23:39 ` [PATCH] mm: Improve cmtime update on shared writable mmaps Andy Lutomirski
2011-11-01 22:53 ` Jan Kara
2011-11-01 23:02 ` Andy Lutomirski
2011-11-02 7:38 ` Christoph Hellwig
2011-11-02 15:02 ` Jan Kara
2011-11-02 15:19 ` Ted Ts'o
2011-10-31 23:10 ` Latency writing to an mlocked ext4 mapping Jan Kara
2011-10-31 23:14 ` Andy Lutomirski
2011-11-01 23:03 ` Jan Kara
2011-11-01 23:10 ` Andy Lutomirski
2011-11-02 1:51 ` Andy Lutomirski
2011-11-02 20:17 ` Jan Kara
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=ACE78D84-0E94-4E7A-99BF-C20583018697@dilger.ca \
--to=adilger@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@amacapital.net \
/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