From: Thomas Gleixner <tglx@linutronix.de>
To: Peter LaDow <petela@gocougs.wsu.edu>
Cc: Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org,
linux-rt-users <linux-rt-users@vger.kernel.org>,
Carsten Emde <C.Emde@osadl.org>, John Kacur <jkacur@redhat.com>
Subject: Re: [PATCH RT 3/4] net: netfilter: Serialize xt_write_recseq sections on RT
Date: Fri, 2 Nov 2012 00:01:59 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.02.1211012358280.2756@ionos> (raw)
In-Reply-To: <CAN8Q1Ecq9T5HC60_ta8Xr9kKyAe8Fjrd8znV9MpDTYqkSSptOw@mail.gmail.com>
On Thu, 1 Nov 2012, Peter LaDow wrote:
> On Thu, Nov 1, 2012 at 2:26 PM, Thomas Gleixner <tglx@linutronix.de> wrote:
> > Cough. You are missing a boat load of crucial fixes. There is a damned
> > good reason why 3.0.stable got 12 updates and the -rt version 14.
>
> I don't doubt there are. But we've only experienced one problem
> between 3.0.36-rt58 and 3.0.48-rt72. Indeed, it might be easier to
> evaluate the risk if all the changelogs were readily available. So
> far, however, we haven't discovered any other issues that give us any
> concerns.
>
> > Your risk assessment is definitley interesting.
>
> We have specifically tested 3.0.36-rt58 for performance in our
> application. Moving to 3.0.48-rt72 poses risk about whether would
> still be able to meet our performance requirements. And with regard
> to stability, the only issue we've had since our earlier moved to
> 3.0.36-rt58 was the netfilter problem. We initially only saw the
> problem on PPP related interfaces, so we reverted to 3.0.3 (non-rt)
> for PPP related issues.
>
> Now, if you think there are some issues that should raise eyebrows, or
> can point me to a list of changelogs, I'd be happy to evaluate them.
git log v3.0.36-rt58..3.0.48-rt72
That's what a source version control system is designed for AFAICT
Thanks,
tglx
next prev parent reply other threads:[~2012-11-01 23:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-31 0:32 [PATCH RT 0/4] [ANNOUNCE] 3.0.48-rt72-rc1 stable review Steven Rostedt
2012-10-31 0:32 ` [PATCH RT 1/4] hrtimer: Raise softirq if hrtimer irq stalled Steven Rostedt
2012-10-31 0:33 ` [PATCH RT 2/4] rcu: Disable RCU_FAST_NO_HZ on RT Steven Rostedt
2012-10-31 0:33 ` [PATCH RT 3/4] net: netfilter: Serialize xt_write_recseq sections " Steven Rostedt
2012-10-31 18:25 ` Peter LaDow
2012-11-01 21:26 ` Thomas Gleixner
2012-11-01 22:30 ` Peter LaDow
2012-11-01 22:58 ` Steven Rostedt
2012-11-01 23:01 ` Thomas Gleixner [this message]
2012-11-02 0:40 ` Peter LaDow
2012-11-02 0:36 ` Peter LaDow
2012-11-02 22:25 ` Peter LaDow
2012-11-02 22:28 ` Peter LaDow
2012-10-31 0:33 ` [PATCH RT 4/4] Linux 3.0.48-rt72-rc1 Steven Rostedt
-- strict thread matches above, loose matches on Subject: below --
2012-10-31 0:31 [PATCH RT 0/4] [ANNOUNCE] 3.2.32-rt49-rc1 stable review Steven Rostedt
2012-10-31 0:31 ` [PATCH RT 3/4] net: netfilter: Serialize xt_write_recseq sections on RT Steven Rostedt
2012-10-31 0:29 [PATCH RT 0/4] [ANNOUNCE] 3.4.15-rt26-rc1 stable review Steven Rostedt
2012-10-31 0:29 ` [PATCH RT 3/4] net: netfilter: Serialize xt_write_recseq sections on RT Steven Rostedt
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.1211012358280.2756@ionos \
--to=tglx@linutronix.de \
--cc=C.Emde@osadl.org \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=petela@gocougs.wsu.edu \
--cc=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).