From: Rusty Russell <rusty@rustcorp.com.au>
To: Kiran <geekazoid@phreaker.net>
Cc: linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: Patch 2.5.25: Ensure xtime_lock and timerlist_lock are on difft cachelines
Date: Fri, 26 Jul 2002 17:56:19 +1000 [thread overview]
Message-ID: <20020726080211.3E71E4824@lists.samba.org> (raw)
In-Reply-To: Your message of "Fri, 26 Jul 2002 12:56:05 +0530." <20020726125605.A2822@phreaker.net>
In message <20020726125605.A2822@phreaker.net> you write:
> This patch was not meant to be a definitive fix for do_gettimeofday.
> I thought having diffrent locks on the same cacheline was bad. Atleast,
> I don't think there'd be any negative performance impact due to my patch.
> Pls correct me if I am wrong.
Did you ever wonder why we don't declare spinlock to be ____cacheline_aligned?
While it's probably justified in this case, you pay for it in a slight
increase in size...
> I want to get some nos too .. and probably will...(still waiting for my
> turn to use the 4way here :-) ). But, I decided to post this patch
> as a follow up to the 2.5 profiler discussion on lse-tech.
> Anywayz, point taken. Next time I submit an optimization patch to you,
> I'll post the measuements too.
Sure!
Thanks,
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
next prev parent reply other threads:[~2002-07-26 7:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-25 15:15 Patch 2.5.25: Ensure xtime_lock and timerlist_lock are on difft cachelines Ravikiran G Thirumalai
2002-07-26 6:24 ` Rusty Russell
2002-07-26 7:26 ` Kiran
2002-07-26 7:56 ` Rusty Russell [this message]
2002-07-26 9:23 ` Kiran
2002-07-27 4:17 ` Rusty Russell
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=20020726080211.3E71E4824@lists.samba.org \
--to=rusty@rustcorp.com.au \
--cc=geekazoid@phreaker.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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.