Re: [RFC] printk: allow increasing the ring buffer depending on the number of CPUs

2014-06-16 Thread Chris Metcalf
On 6/12/2014 2:45 PM, Joe Perches wrote: (adding Chris Metcalf for arch/tile, I think this change might impact that arch) Thanks for the Cc. I've been following the discussion and I think it's on the right track for arch/tile. -- Chris Metcalf, Tilera Corp. http://www.tilera.com -- To uns

Re: [RFC] printk: allow increasing the ring buffer depending on the number of CPUs

2014-06-12 Thread Luis R. Rodriguez
On Thu, Jun 12, 2014 at 11:45 AM, Joe Perches wrote: > > trivia: s/loosing/losing/ Amended, thanks. Luis -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-inf

Re: [RFC] printk: allow increasing the ring buffer depending on the number of CPUs

2014-06-12 Thread Luis R. Rodriguez
On Thu, Jun 12, 2014 at 11:01 AM, Davidlohr Bueso wrote: > On Wed, 2014-06-11 at 11:34 +0200, Petr Mládek wrote: >> On Tue 2014-06-10 18:04:45, Luis R. Rodriguez wrote: >> > From: "Luis R. Rodriguez" >> > >> > The default size of the ring buffer is too small for machines >> > with a large amount

Re: [RFC] printk: allow increasing the ring buffer depending on the number of CPUs

2014-06-12 Thread Luis R. Rodriguez
On Thu, Jun 12, 2014 at 03:05:32PM +0200, Petr Mládek wrote: > On Wed 2014-06-11 23:47:41, Luis R. Rodriguez wrote: > > On Wed, Jun 11, 2014 at 11:34:47AM +0200, Petr Mládek wrote: > > > On Tue 2014-06-10 18:04:45, Luis R. Rodriguez wrote: > > > > From: "Luis R. Rodriguez" > > > > diff --git a/ini

Re: [RFC] printk: allow increasing the ring buffer depending on the number of CPUs

2014-06-12 Thread Joe Perches
(adding Chris Metcalf for arch/tile, I think this change might impact that arch) On Thu, 2014-06-12 at 11:01 -0700, Davidlohr Bueso wrote: > On Wed, 2014-06-11 at 11:34 +0200, Petr Mládek wrote: > > On Tue 2014-06-10 18:04:45, Luis R. Rodriguez wrote: > > > From: "Luis R. Rodriguez" > > > > > >

Re: [RFC] printk: allow increasing the ring buffer depending on the number of CPUs

2014-06-12 Thread Davidlohr Bueso
On Wed, 2014-06-11 at 11:34 +0200, Petr Mládek wrote: > On Tue 2014-06-10 18:04:45, Luis R. Rodriguez wrote: > > From: "Luis R. Rodriguez" > > > > The default size of the ring buffer is too small for machines > > with a large amount of CPUs under heavy load. What ends up > > happening when debug

Re: [RFC] printk: allow increasing the ring buffer depending on the number of CPUs

2014-06-12 Thread Petr Mládek
On Wed 2014-06-11 23:47:41, Luis R. Rodriguez wrote: > On Wed, Jun 11, 2014 at 11:34:47AM +0200, Petr Mládek wrote: > > On Tue 2014-06-10 18:04:45, Luis R. Rodriguez wrote: > > > From: "Luis R. Rodriguez" > > > diff --git a/init/Kconfig b/init/Kconfig > > > index 9d3585b..1814436 100644 > > > ---

Re: [RFC] printk: allow increasing the ring buffer depending on the number of CPUs

2014-06-11 Thread Luis R. Rodriguez
On Wed, Jun 11, 2014 at 11:34:47AM +0200, Petr Mládek wrote: > On Tue 2014-06-10 18:04:45, Luis R. Rodriguez wrote: > > From: "Luis R. Rodriguez" > > diff --git a/init/Kconfig b/init/Kconfig > > index 9d3585b..1814436 100644 > > --- a/init/Kconfig > > +++ b/init/Kconfig > > @@ -806,6 +806,34 @@ co

Re: [RFC] printk: allow increasing the ring buffer depending on the number of CPUs

2014-06-11 Thread Petr Mládek
On Tue 2014-06-10 18:04:45, Luis R. Rodriguez wrote: > From: "Luis R. Rodriguez" > > The default size of the ring buffer is too small for machines > with a large amount of CPUs under heavy load. What ends up > happening when debugging is the ring buffer overlaps and chews > up old messages making

[RFC] printk: allow increasing the ring buffer depending on the number of CPUs

2014-06-10 Thread Luis R. Rodriguez
From: "Luis R. Rodriguez" The default size of the ring buffer is too small for machines with a large amount of CPUs under heavy load. What ends up happening when debugging is the ring buffer overlaps and chews up old messages making debugging impossible unless the size is passed as a kernel param