All of lore.kernel.org
 help / color / mirror / Atom feed
From: Con Kolivas <kernel@kolivas.org>
To: Andrew Morton <akpm@osdl.org>
Cc: ck@vds.kolivas.org, linux-kernel@vger.kernel.org, wli@holomorphy.com
Subject: Re: Preempt Threshold Measurements
Date: Tue, 13 Jul 2004 20:26:52 +1000	[thread overview]
Message-ID: <40F3B8EC.4000301@kolivas.org> (raw)
In-Reply-To: <20040712231406.427caa2a.akpm@osdl.org>

[-- Attachment #1: Type: text/plain, Size: 2121 bytes --]

Andrew Morton wrote:
> Con Kolivas <kernel@kolivas.org> wrote:
> 
>>4ms at blkdev_put+0x48
> 
> 
> This can run under one of two depths of lock_kernel.  filemap_fdatawrite()
> and filemap_fdatawait() both do cond_resched(), so this is odd.
> 
> Try this:
> 

Thanks! I'll certainly give that a shot.

> Need to see the whole trace.

Do you mean the traces from your patch or the ones that come from this 
preempt test like this?

Jul 13 07:22:18 pc kernel: 4ms non-preemptible critical section violated 
1 ms preempt threshold starting at exit_mmap+0x1c/0x188 and ending at 
exit_mmap+0x
118/0x188
Jul 13 07:22:18 pc kernel:  [<c011d769>] dec_preempt_count+0x14f/0x151
Jul 13 07:22:18 pc kernel:  [<c014d0d4>] exit_mmap+0x118/0x188
Jul 13 07:22:18 pc kernel:  [<c014d0d4>] exit_mmap+0x118/0x188
Jul 13 07:22:18 pc kernel:  [<c011df0a>] mmput+0x61/0x7b
Jul 13 07:22:18 pc kernel:  [<c01634dc>] exec_mmap+0x11d/0x248
Jul 13 07:22:18 pc kernel:  [<c016364c>] flush_old_exec+0x45/0x284
Jul 13 07:22:18 pc kernel:  [<c018119f>] load_elf_binary+0x3e8/0xd00
Jul 13 07:22:18 pc kernel:  [<c013a9b1>] do_generic_mapping_read+0x295/0x4f2
Jul 13 07:22:18 pc kernel:  [<c0164312>] search_binary_handler+0xd0/0x34c
Jul 13 07:22:18 pc kernel:  [<c0180db7>] load_elf_binary+0x0/0xd00
Jul 13 07:22:18 pc kernel:  [<c0164329>] search_binary_handler+0xe7/0x34c
Jul 13 07:22:18 pc kernel:  [<c0164759>] do_execve+0x1cb/0x23c
Jul 13 07:22:18 pc kernel:  [<c0165f39>] getname+0x55/0xb8
Jul 13 07:22:18 pc kernel:  [<c0104bcf>] sys_execve+0x35/0x68
Jul 13 07:22:18 pc kernel:  [<c0105fd5>] sysenter_past_esp+0x52/0x71


I can try and extract the exact points from the disassembly after some 
guidance I've received (most of them seem to be buried deep in inlined 
functions.) The exit_mmap one seemed to work out (as you probably saw in 
my previous email) to be set off here:

          profile_exit_mmap(mm);
          lru_add_drain();
c014cfce:       e8 18 72 ff ff          call   c01441eb <lru_add_drain>
          spin_lock(&mm->page_table_lock);
c014cfd3:       e8 16 06 fd ff          call   c011d5ee <inc_preempt_count>


Cheers,
Con

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]

  parent reply	other threads:[~2004-07-13 10:27 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-12 23:43 Preempt Threshold Measurements Gabriel Devenyi
2004-07-12 23:59 ` Con Kolivas
2004-07-13  0:15   ` Gabriel Devenyi
2004-07-13  2:40 ` William Lee Irwin III
2004-07-13  2:48   ` [ck] " Gabriel Devenyi
2004-07-13  2:54     ` Con Kolivas
2004-07-13  4:01       ` Andrew Morton
2004-07-13  5:51         ` Con Kolivas
2004-07-13  6:14           ` Andrew Morton
2004-07-13  8:03             ` Lee Revell
2004-07-13 10:26             ` Con Kolivas [this message]
2004-07-13 21:52             ` Con Kolivas
2004-07-13 10:08         ` William Lee Irwin III
2004-07-13 10:40           ` William Lee Irwin III
2004-07-13 11:07             ` Lenar Lõhmus
2004-07-13 11:13               ` William Lee Irwin III
2004-07-13  2:55     ` [ck] " William Lee Irwin III
2004-07-13  3:09       ` Gabriel Devenyi
2004-07-13  4:07       ` Andrew Morton
2004-07-13  5:34         ` Con Kolivas
2004-07-13  5:48           ` Nick Piggin
2004-07-13 10:14             ` William Lee Irwin III
2004-07-14 10:15 ` [ck] " Jens Bergmann

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=40F3B8EC.4000301@kolivas.org \
    --to=kernel@kolivas.org \
    --cc=akpm@osdl.org \
    --cc=ck@vds.kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wli@holomorphy.com \
    /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.