Re: [PATCH] mm: Drop "PFNs busy" printk in an expected path.

On 12/30/2016 11:52 AM, Michal Hocko wrote: > On Thu 29-12-16 23:22:20, Michal Nazarewicz wrote: >> On Thu, Dec 29 2016, Eric Anholt wrote: >>> Michal Hocko writes: >>> This has been already brought up http://lkml.kernel.org/r/20161130092239.gd18...@dhcp22.suse.cz and

Re: [PATCH] mm: Drop "PFNs busy" printk in an expected path.

On 12/30/2016 11:52 AM, Michal Hocko wrote: > On Thu 29-12-16 23:22:20, Michal Nazarewicz wrote: >> On Thu, Dec 29 2016, Eric Anholt wrote: >>> Michal Hocko writes: >>> This has been already brought up http://lkml.kernel.org/r/20161130092239.gd18...@dhcp22.suse.cz and there was a

Re: [PATCH] mm: Drop "PFNs busy" printk in an expected path.

On Fri, Dec 30 2016, Eric Anholt wrote: > OK, so the design is bad. When you said bug, I definitely thought you > were saying that the message shouldn't happen in the design. > > Given CMA's current design, should everyone using CMA see their logs > slowly growing with this message that is an

Re: [PATCH] mm: Drop "PFNs busy" printk in an expected path.

On Fri, Dec 30 2016, Eric Anholt wrote: > OK, so the design is bad. When you said bug, I definitely thought you > were saying that the message shouldn't happen in the design. > > Given CMA's current design, should everyone using CMA see their logs > slowly growing with this message that is an

Re: [PATCH] mm: Drop "PFNs busy" printk in an expected path.

Michal Nazarewicz writes: > On Thu, Dec 29 2016, Eric Anholt wrote: >> Michal Nazarewicz writes: >> >>> On Thu, Dec 29 2016, Eric Anholt wrote: Michal Hocko writes: > This has been already brought up >

Re: [PATCH] mm: Drop "PFNs busy" printk in an expected path.

Michal Nazarewicz writes: > On Thu, Dec 29 2016, Eric Anholt wrote: >> Michal Nazarewicz writes: >> >>> On Thu, Dec 29 2016, Eric Anholt wrote: Michal Hocko writes: > This has been already brought up > http://lkml.kernel.org/r/20161130092239.gd18...@dhcp22.suse.cz and there

Re: [PATCH] mm: Drop "PFNs busy" printk in an expected path.

On Thu 29-12-16 23:22:20, Michal Nazarewicz wrote: > On Thu, Dec 29 2016, Eric Anholt wrote: > > Michal Hocko writes: > > > >> This has been already brought up > >> http://lkml.kernel.org/r/20161130092239.gd18...@dhcp22.suse.cz and there > >> was a proposed patch for that which

Re: [PATCH] mm: Drop "PFNs busy" printk in an expected path.

On Thu 29-12-16 23:22:20, Michal Nazarewicz wrote: > On Thu, Dec 29 2016, Eric Anholt wrote: > > Michal Hocko writes: > > > >> This has been already brought up > >> http://lkml.kernel.org/r/20161130092239.gd18...@dhcp22.suse.cz and there > >> was a proposed patch for that which ratelimited the

Re: [PATCH] mm: Drop "PFNs busy" printk in an expected path.

On Thu, Dec 29 2016, Eric Anholt wrote: > Michal Nazarewicz writes: > >> On Thu, Dec 29 2016, Eric Anholt wrote: >>> Michal Hocko writes: >>> This has been already brought up http://lkml.kernel.org/r/20161130092239.gd18...@dhcp22.suse.cz and there

Re: [PATCH] mm: Drop "PFNs busy" printk in an expected path.

On Thu, Dec 29 2016, Eric Anholt wrote: > Michal Nazarewicz writes: > >> On Thu, Dec 29 2016, Eric Anholt wrote: >>> Michal Hocko writes: >>> This has been already brought up http://lkml.kernel.org/r/20161130092239.gd18...@dhcp22.suse.cz and there was a proposed patch for that

Re: [PATCH] mm: Drop "PFNs busy" printk in an expected path.

Michal Nazarewicz writes: > On Thu, Dec 29 2016, Eric Anholt wrote: >> Michal Hocko writes: >> >>> This has been already brought up >>> http://lkml.kernel.org/r/20161130092239.gd18...@dhcp22.suse.cz and there >>> was a proposed patch for that which

Re: [PATCH] mm: Drop "PFNs busy" printk in an expected path.

Michal Nazarewicz writes: > On Thu, Dec 29 2016, Eric Anholt wrote: >> Michal Hocko writes: >> >>> This has been already brought up >>> http://lkml.kernel.org/r/20161130092239.gd18...@dhcp22.suse.cz and there >>> was a proposed patch for that which ratelimited the output >>>

Re: [PATCH] mm: Drop "PFNs busy" printk in an expected path.

On Thu, Dec 29 2016, Eric Anholt wrote: > Michal Hocko writes: > >> This has been already brought up >> http://lkml.kernel.org/r/20161130092239.gd18...@dhcp22.suse.cz and there >> was a proposed patch for that which ratelimited the output >>

Re: [PATCH] mm: Drop "PFNs busy" printk in an expected path.

On Thu, Dec 29 2016, Eric Anholt wrote: > Michal Hocko writes: > >> This has been already brought up >> http://lkml.kernel.org/r/20161130092239.gd18...@dhcp22.suse.cz and there >> was a proposed patch for that which ratelimited the output >>

Re: [PATCH] mm: Drop "PFNs busy" printk in an expected path.

Michal Hocko writes: > This has been already brought up > http://lkml.kernel.org/r/20161130092239.gd18...@dhcp22.suse.cz and there > was a proposed patch for that which ratelimited the output > http://lkml.kernel.org/r/20161130132848.gg18...@dhcp22.suse.cz resp. >

Re: [PATCH] mm: Drop "PFNs busy" printk in an expected path.

Michal Hocko writes: > This has been already brought up > http://lkml.kernel.org/r/20161130092239.gd18...@dhcp22.suse.cz and there > was a proposed patch for that which ratelimited the output > http://lkml.kernel.org/r/20161130132848.gg18...@dhcp22.suse.cz resp. >

Re: [PATCH] mm: Drop "PFNs busy" printk in an expected path.

This has been already brought up http://lkml.kernel.org/r/20161130092239.gd18...@dhcp22.suse.cz and there was a proposed patch for that which ratelimited the output http://lkml.kernel.org/r/20161130132848.gg18...@dhcp22.suse.cz resp.

Re: [PATCH] mm: Drop "PFNs busy" printk in an expected path.

This has been already brought up http://lkml.kernel.org/r/20161130092239.gd18...@dhcp22.suse.cz and there was a proposed patch for that which ratelimited the output http://lkml.kernel.org/r/20161130132848.gg18...@dhcp22.suse.cz resp.

[PATCH] mm: Drop "PFNs busy" printk in an expected path.

For CMA allocations, we expect to occasionally hit this error path, at which point CMA will retry. Given that, we shouldn't be spamming dmesg about it. The Raspberry Pi graphics driver does frequent CMA allocations, and during regression testing this printk was sometimes occurring 100s of times

[PATCH] mm: Drop "PFNs busy" printk in an expected path.

For CMA allocations, we expect to occasionally hit this error path, at which point CMA will retry. Given that, we shouldn't be spamming dmesg about it. The Raspberry Pi graphics driver does frequent CMA allocations, and during regression testing this printk was sometimes occurring 100s of times