On 1/18/18 1:02 AM, Thomas Gleixner wrote:
On Thu, 18 Jan 2018, Yang Shi wrote:
On 1/17/18 4:21 AM, Thomas Gleixner wrote:
There are two things which can be done here:
1) The collected objects can be put on a global free list and work
scheduled to free them piecewise.
I don't get
On 1/18/18 1:02 AM, Thomas Gleixner wrote:
On Thu, 18 Jan 2018, Yang Shi wrote:
On 1/17/18 4:21 AM, Thomas Gleixner wrote:
There are two things which can be done here:
1) The collected objects can be put on a global free list and work
scheduled to free them piecewise.
I don't get
On Thu, 18 Jan 2018, Peter Zijlstra wrote:
> On Thu, Jan 18, 2018 at 10:02:25AM +0100, Thomas Gleixner wrote:
> > > > 2) We can do a cond_resched() if not in atomic context and interrupts
> > > > are
> > > > enabled.
> > >
> > > I did try this before I went with touching softlockup
On Thu, 18 Jan 2018, Peter Zijlstra wrote:
> On Thu, Jan 18, 2018 at 10:02:25AM +0100, Thomas Gleixner wrote:
> > > > 2) We can do a cond_resched() if not in atomic context and interrupts
> > > > are
> > > > enabled.
> > >
> > > I did try this before I went with touching softlockup
On Thu, Jan 18, 2018 at 10:02:25AM +0100, Thomas Gleixner wrote:
> > > 2) We can do a cond_resched() if not in atomic context and interrupts
> > > are
> > > enabled.
> >
> > I did try this before I went with touching softlockup watchdog approach. The
> > problem is in_atomic() can't tell
On Thu, Jan 18, 2018 at 10:02:25AM +0100, Thomas Gleixner wrote:
> > > 2) We can do a cond_resched() if not in atomic context and interrupts
> > > are
> > > enabled.
> >
> > I did try this before I went with touching softlockup watchdog approach. The
> > problem is in_atomic() can't tell
On Thu, 18 Jan 2018, Yang Shi wrote:
> On 1/17/18 4:21 AM, Thomas Gleixner wrote:
> > There are two things which can be done here:
> >
> > 1) The collected objects can be put on a global free list and work
> > scheduled to free them piecewise.
>
> I don't get your point here. objects free
On Thu, 18 Jan 2018, Yang Shi wrote:
> On 1/17/18 4:21 AM, Thomas Gleixner wrote:
> > There are two things which can be done here:
> >
> > 1) The collected objects can be put on a global free list and work
> > scheduled to free them piecewise.
>
> I don't get your point here. objects free
On 1/17/18 4:21 AM, Thomas Gleixner wrote:
On Thu, 4 Jan 2018, Yang Shi wrote:
There are nested loops on debug objects free path, sometimes it may take
over hundred thousands of loops, then cause soft lockup with !CONFIG_PREEMPT
occasionally, like below:
Please trim back traces. The whole
On 1/17/18 4:21 AM, Thomas Gleixner wrote:
On Thu, 4 Jan 2018, Yang Shi wrote:
There are nested loops on debug objects free path, sometimes it may take
over hundred thousands of loops, then cause soft lockup with !CONFIG_PREEMPT
occasionally, like below:
Please trim back traces. The whole
On Thu, 4 Jan 2018, Yang Shi wrote:
> There are nested loops on debug objects free path, sometimes it may take
> over hundred thousands of loops, then cause soft lockup with !CONFIG_PREEMPT
> occasionally, like below:
Please trim back traces. The whole module info and whatever is completely
On Thu, 4 Jan 2018, Yang Shi wrote:
> There are nested loops on debug objects free path, sometimes it may take
> over hundred thousands of loops, then cause soft lockup with !CONFIG_PREEMPT
> occasionally, like below:
Please trim back traces. The whole module info and whatever is completely
There are nested loops on debug objects free path, sometimes it may take
over hundred thousands of loops, then cause soft lockup with !CONFIG_PREEMPT
occasionally, like below:
NMI watchdog: BUG: soft lockup - CPU#15 stuck for 22s! [stress-ng-getde:110342]
Modules linked in: binfmt_misc(E)
There are nested loops on debug objects free path, sometimes it may take
over hundred thousands of loops, then cause soft lockup with !CONFIG_PREEMPT
occasionally, like below:
NMI watchdog: BUG: soft lockup - CPU#15 stuck for 22s! [stress-ng-getde:110342]
Modules linked in: binfmt_misc(E)
On 12/28/17 7:36 AM, Thomas Gleixner wrote:
On Fri, 8 Dec 2017, Yang Shi wrote:
Hi Thomas,
Waiman has reviewed the patches, any comment from you is appreciated.
I'm confused there is a V3 and a V8 of the 2/2 patch in my inbox. Can you
please resend both patches in their final version?
On 12/28/17 7:36 AM, Thomas Gleixner wrote:
On Fri, 8 Dec 2017, Yang Shi wrote:
Hi Thomas,
Waiman has reviewed the patches, any comment from you is appreciated.
I'm confused there is a V3 and a V8 of the 2/2 patch in my inbox. Can you
please resend both patches in their final version?
On Fri, 8 Dec 2017, Yang Shi wrote:
> Hi Thomas,
>
> Waiman has reviewed the patches, any comment from you is appreciated.
I'm confused there is a V3 and a V8 of the 2/2 patch in my inbox. Can you
please resend both patches in their final version?
Thanks,
tglx
On Fri, 8 Dec 2017, Yang Shi wrote:
> Hi Thomas,
>
> Waiman has reviewed the patches, any comment from you is appreciated.
I'm confused there is a V3 and a V8 of the 2/2 patch in my inbox. Can you
please resend both patches in their final version?
Thanks,
tglx
Hi Thomas,
Waiman has reviewed the patches, any comment from you is appreciated.
Thanks,
Yang
On 11/28/17 12:24 PM, Waiman Long wrote:
On 11/28/2017 02:45 PM, Yang Shi wrote:
There are nested loops on debug objects free path, sometimes it may take
over hundred thousands of loops, then cause
Hi Thomas,
Waiman has reviewed the patches, any comment from you is appreciated.
Thanks,
Yang
On 11/28/17 12:24 PM, Waiman Long wrote:
On 11/28/2017 02:45 PM, Yang Shi wrote:
There are nested loops on debug objects free path, sometimes it may take
over hundred thousands of loops, then cause
On 11/28/2017 02:45 PM, Yang Shi wrote:
> There are nested loops on debug objects free path, sometimes it may take
> over hundred thousands of loops, then cause soft lockup with !CONFIG_PREEMPT
> occasionally, like below:
>
> NMI watchdog: BUG: soft lockup - CPU#15 stuck for 22s!
>
On 11/28/2017 02:45 PM, Yang Shi wrote:
> There are nested loops on debug objects free path, sometimes it may take
> over hundred thousands of loops, then cause soft lockup with !CONFIG_PREEMPT
> occasionally, like below:
>
> NMI watchdog: BUG: soft lockup - CPU#15 stuck for 22s!
>
There are nested loops on debug objects free path, sometimes it may take
over hundred thousands of loops, then cause soft lockup with !CONFIG_PREEMPT
occasionally, like below:
NMI watchdog: BUG: soft lockup - CPU#15 stuck for 22s! [stress-ng-getde:110342]
Modules linked in: binfmt_misc(E)
There are nested loops on debug objects free path, sometimes it may take
over hundred thousands of loops, then cause soft lockup with !CONFIG_PREEMPT
occasionally, like below:
NMI watchdog: BUG: soft lockup - CPU#15 stuck for 22s! [stress-ng-getde:110342]
Modules linked in: binfmt_misc(E)
24 matches
Mail list logo
