From: Thomas Gleixner <tglx@linutronix.de>
To: Lars Segerlund <lars.segerlund@gmail.com>
Cc: linux-rt-users <linux-rt-users@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [ANNOUNCE] 3.0-rt4 , Follow up question
Date: Thu, 28 Jul 2011 18:27:27 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.02.1107281253451.2660@ionos> (raw)
In-Reply-To: <CAF-VNapwgfr66ib9OPcpJO-4K+6F-0VZA2Tc=4Fp==TDPKwkRQ@mail.gmail.com>
On Thu, 28 Jul 2011, Lars Segerlund wrote:
> How much is there left to do for mainline inclusion ?
>
> A rough guess would be nice, just to assess the amount of work and severity.
http://dilbert.com/strips/comic/2010-06-26/
If that doesn't answer your question, then you might try:
# tar -xjf patches-3.0-rtx.tar.bz2
# ls patches/*.patch
# wc -l patches/*.patch
# for each patch in patches; do read $patch; done
> As I understand it , a lot of subsystes are trying to go lockless, so
> things should become easier.
Not really, they just use different mechanisms. Serialization and
synchronization are not restricted to locks and some of these
mechanisms are even more evil than a plain old lock.
Thanks,
tglx
parent reply other threads:[~2011-07-28 16:27 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAF-VNapwgfr66ib9OPcpJO-4K+6F-0VZA2Tc=4Fp==TDPKwkRQ@mail.gmail.com>]
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=alpine.LFD.2.02.1107281253451.2660@ionos \
--to=tglx@linutronix.de \
--cc=lars.segerlund@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
/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