All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: shobhit@calsoftinc.com
Cc: linux-kernel@vger.kernel.org, geoff@linux.intel.com, mingo@elte.hu
Subject: Re: [RFC] [PATCH] Performance of del_single_shot_timer_sync
Date: Mon, 4 Oct 2004 01:41:47 -0700	[thread overview]
Message-ID: <20041004014147.776e4ecf.akpm@osdl.org> (raw)
In-Reply-To: <1096874675.11717.33.camel@kuber>

shobhit dayal <shobhit@calsoftinc.com> wrote:
>
> I tried Geoff's patch and it does seem to improve performance.

By how much?  (CPU load, overall runtime, etc)

It's a bit odd to have an expired-timer-intensive workload.  Presumably
postgres has some short-lived nanosleep or select-based polling loop in
there which isn't doing much.

  reply	other threads:[~2004-10-04  8:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-04  7:24 [RFC] [PATCH] Performance of del_single_shot_timer_sync shobhit dayal
2004-10-04  8:41 ` Andrew Morton [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-10-08 13:37 shobhit dayal
2004-10-08 17:19 ` Andrew Morton
2004-10-10 10:29   ` shobhit dayal

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=20041004014147.776e4ecf.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=geoff@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=shobhit@calsoftinc.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.