Re: [PATCH V2 1/4] arm: mvebu: increase atomic coherent pool size for armada 370/XP

2012-11-06 Thread Sören Moch
>>> For Armada 370/XP we have the same problem that for the commit >>> cb01b63, so we applied the same solution: "The default 256 KiB >>> coherent pool may be too small for some of the Kirkwood devices, so >>> increase it to make sure that devices will be able to allocate their >>> buffers with

Re: [PATCH V2 1/4] arm: mvebu: increase atomic coherent pool size for armada 370/XP

2012-11-06 Thread Sebastian Hesselbarth
On 11/06/2012 11:32 PM, Andrew Lunn wrote: On Tue, Nov 06, 2012 at 10:28:45PM +0100, S?ren Moch wrote: I see a regression from linux-3.5 to linux-3.6 and think there might be a fundamental problem with this patch. On my Kirkwood system (guruplug server plus) with linux-3.6.2 I see following

Re: [PATCH V2 1/4] arm: mvebu: increase atomic coherent pool size for armada 370/XP

2012-11-06 Thread Andrew Lunn
On Tue, Nov 06, 2012 at 10:28:45PM +0100, S?ren Moch wrote: > resent as plain text, sorry. > > > > For Armada 370/XP we have the same problem that for the commit > > cb01b63, so we applied the same solution: "The default 256 KiB > > coherent pool may be too small for some of the Kirkwood

Re: [PATCH V2 1/4] arm: mvebu: increase atomic coherent pool size for armada 370/XP

2012-11-06 Thread Sören Moch
resent as plain text, sorry. > For Armada 370/XP we have the same problem that for the commit > cb01b63, so we applied the same solution: "The default 256 KiB > coherent pool may be too small for some of the Kirkwood devices, so > increase it to make sure that devices will be able to allocate

Re: [PATCH V2 1/4] arm: mvebu: increase atomic coherent pool size for armada 370/XP

2012-11-06 Thread Sören Moch
resent as plain text, sorry. For Armada 370/XP we have the same problem that for the commit cb01b63, so we applied the same solution: The default 256 KiB coherent pool may be too small for some of the Kirkwood devices, so increase it to make sure that devices will be able to allocate their

Re: [PATCH V2 1/4] arm: mvebu: increase atomic coherent pool size for armada 370/XP

2012-11-06 Thread Andrew Lunn
On Tue, Nov 06, 2012 at 10:28:45PM +0100, S?ren Moch wrote: resent as plain text, sorry. For Armada 370/XP we have the same problem that for the commit cb01b63, so we applied the same solution: The default 256 KiB coherent pool may be too small for some of the Kirkwood devices, so

Re: [PATCH V2 1/4] arm: mvebu: increase atomic coherent pool size for armada 370/XP

2012-11-06 Thread Sebastian Hesselbarth
On 11/06/2012 11:32 PM, Andrew Lunn wrote: On Tue, Nov 06, 2012 at 10:28:45PM +0100, S?ren Moch wrote: I see a regression from linux-3.5 to linux-3.6 and think there might be a fundamental problem with this patch. On my Kirkwood system (guruplug server plus) with linux-3.6.2 I see following

Re: [PATCH V2 1/4] arm: mvebu: increase atomic coherent pool size for armada 370/XP

2012-11-06 Thread Sören Moch
For Armada 370/XP we have the same problem that for the commit cb01b63, so we applied the same solution: The default 256 KiB coherent pool may be too small for some of the Kirkwood devices, so increase it to make sure that devices will be able to allocate their buffers with GFP_ATOMIC flag

[PATCH V2 1/4] arm: mvebu: increase atomic coherent pool size for armada 370/XP

2012-10-26 Thread Gregory CLEMENT
For Armada 370/XP we have the same problem that for the commit cb01b63, so we applied the same solution: "The default 256 KiB coherent pool may be too small for some of the Kirkwood devices, so increase it to make sure that devices will be able to allocate their buffers with GFP_ATOMIC flag"

[PATCH V2 1/4] arm: mvebu: increase atomic coherent pool size for armada 370/XP

2012-10-26 Thread Gregory CLEMENT
For Armada 370/XP we have the same problem that for the commit cb01b63, so we applied the same solution: The default 256 KiB coherent pool may be too small for some of the Kirkwood devices, so increase it to make sure that devices will be able to allocate their buffers with GFP_ATOMIC flag