From: Ingo Molnar <mingo@elte.hu>
To: David Miller <davem@davemloft.net>
Cc: herbert@gondor.apana.org.au, a.p.zijlstra@chello.nl,
emil.s.tantilov@intel.com, jeffrey.t.kirsher@intel.com,
netdev@vger.kernel.org, peter.p.waskiewicz.jr@intel.com,
alexander.h.duyck@intel.com, dada1@cosmosbay.com,
linux-kernel@vger.kernel.org
Subject: Re: [patch] locking, percpu counters: introduce separate lock classes
Date: Tue, 30 Dec 2008 08:21:25 +0100 [thread overview]
Message-ID: <20081230072125.GB20225@elte.hu> (raw)
In-Reply-To: <20081229.230438.90548187.davem@davemloft.net>
* David Miller <davem@davemloft.net> wrote:
> From: Ingo Molnar <mingo@elte.hu>
> Date: Tue, 30 Dec 2008 07:56:50 +0100
>
> >
> > * David Miller <davem@davemloft.net> wrote:
> >
> > > From: Ingo Molnar <mingo@elte.hu>
> > > Date: Tue, 30 Dec 2008 07:05:36 +0100
> > >
> > > > One small nit: could you please add the Reported-by line for Jeff Kirscher
> > > > who reported the problem originally:
> > > >
> > > > Reported-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
> > >
> > > I'll make sure to add that to the commit message after
> > > you successfully test Herbert's patch.
> > >
> > > Thanks.
> >
> > early indications are good: after about 15 random bootup tests the lockdep
> > warning has not triggered. (it would trigger on every 2nd kernel before
> > that - there's a 66% chance for lockdep to be enabled in my randconfig
> > tests)
>
> Sounds good. I'll toss this into my net-2.6 tree, with Jeff's
> reported-by and your Tested-by, and send this off to Linus tonight.
cool. If by tonight you dont get a followup mail from me then you can
assume that the patch passed hundreds of tests here.
Ingo
prev parent reply other threads:[~2008-12-30 7:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9929d2390812250225w19bcd2f7n11357ff26de78c52@mail.gmail.com>
[not found] ` <20081225112658.GA7260@gondor.apana.org.au>
2008-12-29 9:57 ` unsafe locks seen with netperf on net-2.6.29 tree Ingo Molnar
[not found] ` <1230300535.9487.292.camel@twins>
[not found] ` <EA929A9653AAE14F841771FB1DE5A1365F56B6648A@rrsmsx501.amr.corp.intel.com>
[not found] ` <1230410308.9487.295.camel@twins>
[not found] ` <EA929A9653AAE14F841771FB1DE5A1365F56B664A3@rrsmsx501.amr.corp.intel.com>
[not found] ` <1230544927.16718.12.camel@twins>
[not found] ` <20081229103154.GA9691@gondor.apana.org.au>
[not found] ` <20081229103735.GA9763@gondor.apana.org.au>
2008-12-29 11:28 ` Ingo Molnar
[not found] ` <20081229114907.GA10170@gondor.apana.org.au>
[not found] ` <20081229115827.GA441@elte.hu>
[not found] ` <20081229120132.GA10363@gondor.apana.org.au>
[not found] ` <20081229121626.GF9628@elte.hu>
[not found] ` <20081229123819.GA18321@elte.hu>
[not found] ` <20081229124444.GA20306@elte.hu>
2008-12-29 14:14 ` [patch] locking, percpu counters: introduce separate lock classes Ingo Molnar
2008-12-30 3:58 ` Herbert Xu
2008-12-30 6:05 ` Ingo Molnar
2008-12-30 6:39 ` David Miller
2008-12-30 6:56 ` Ingo Molnar
2008-12-30 7:04 ` David Miller
2008-12-30 7:21 ` Ingo Molnar [this message]
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=20081230072125.GB20225@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=alexander.h.duyck@intel.com \
--cc=dada1@cosmosbay.com \
--cc=davem@davemloft.net \
--cc=emil.s.tantilov@intel.com \
--cc=herbert@gondor.apana.org.au \
--cc=jeffrey.t.kirsher@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peter.p.waskiewicz.jr@intel.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
all inboxes | Powered by JetHome®