From: Linus Torvalds <torvalds@osdl.org>
To: Lars Hjemli <hjemli@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [ANNOUNCE] CGit v0.1-pre
Date: Mon, 11 Dec 2006 09:33:38 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0612110929510.12500@woody.osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0612110859200.12500@woody.osdl.org>
On Mon, 11 Dec 2006, Linus Torvalds wrote:
>
> The point is, if you have races, you will hit them _occasionally_. It may
> not be a performance problem in real life, BUT:
Side note: another problem with races is that
- exactly because they are rare, any potential problems they cause are
really hard to debug - you may have a hard time reproducing things.
- some loads may be able to trigger them thanks to very unlucky timing,
so even if the problem is "just a theoretical performance issue",
sometimes that theoretical performance problem that only happens once
in a blue moon ends up happening a _lot_ for a particular user.
I'm probably biased, simply because I've done system programming for so
long (and race conditions etc are one of the most common source of subtle
bugs), but I've long since come to the very strong opinion that locking is
simply too important to not do right.
Even if you can argue that "it doesn't matter" (and you may even be
right), I personally tend to just consider dodgy locking to be a serious
bug _whether_ it really matters or not.
Just a hangup of mine.
next prev parent reply other threads:[~2006-12-11 17:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-10 23:42 [ANNOUNCE] CGit v0.1-pre Lars Hjemli
2006-12-11 0:08 ` Jakub Narebski
[not found] ` <8c5c35580612101616g179715ecyd02fcbb023246ecc@mail.gmail.com>
2006-12-11 0:29 ` Jakub Narebski
2006-12-11 13:37 ` Michael
2006-12-11 1:04 ` Linus Torvalds
2006-12-11 8:33 ` Lars Hjemli
2006-12-11 11:59 ` Lars Hjemli
2006-12-11 17:01 ` Linus Torvalds
2006-12-11 17:33 ` Linus Torvalds [this message]
2006-12-11 17:40 ` Lars Hjemli
2006-12-11 18:18 ` Linus Torvalds
2006-12-11 18:38 ` Lars Hjemli
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=Pine.LNX.4.64.0612110929510.12500@woody.osdl.org \
--to=torvalds@osdl.org \
--cc=git@vger.kernel.org \
--cc=hjemli@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).