> On Mar 8, 2016, at 11:02 AM, Slawa Olhovchenkov wrote:
>
> On Tue, Mar 08, 2016 at 10:56:39AM -0800, Scott Long wrote:
>
>>
>>> On Mar 8, 2016, at 10:48 AM, Slawa Olhovchenkov wrote:
>>>
>>> On Tue, Mar 08, 2016 at 10:34:23AM -0800, Scott Long wrote:
>>>
> On Mar 8, 2016, at 10:
On Tue, Mar 08, 2016 at 10:56:39AM -0800, Scott Long wrote:
>
> > On Mar 8, 2016, at 10:48 AM, Slawa Olhovchenkov wrote:
> >
> > On Tue, Mar 08, 2016 at 10:34:23AM -0800, Scott Long wrote:
> >
> >>
> >>> On Mar 8, 2016, at 10:07 AM, Slawa Olhovchenkov wrote:
> >>>
> >>> On Mon, Mar 07, 2016
> On Mar 8, 2016, at 10:48 AM, Slawa Olhovchenkov wrote:
>
> On Tue, Mar 08, 2016 at 10:34:23AM -0800, Scott Long wrote:
>
>>
>>> On Mar 8, 2016, at 10:07 AM, Slawa Olhovchenkov wrote:
>>>
>>> On Mon, Mar 07, 2016 at 02:10:12PM +0300, Slawa Olhovchenkov wrote:
>>>
This allocated on
On Tue, Mar 08, 2016 at 10:34:23AM -0800, Scott Long wrote:
>
> > On Mar 8, 2016, at 10:07 AM, Slawa Olhovchenkov wrote:
> >
> > On Mon, Mar 07, 2016 at 02:10:12PM +0300, Slawa Olhovchenkov wrote:
> >
> >> This allocated one for all controllers, or allocated for every
> >> controller?
> On Mar 8, 2016, at 10:07 AM, Slawa Olhovchenkov wrote:
>
> On Mon, Mar 07, 2016 at 02:10:12PM +0300, Slawa Olhovchenkov wrote:
>
>> This allocated one for all controllers, or allocated for every
>> controller?
>
> It’s per-controller.
>
> I’ve thought about making t
On Mon, Mar 07, 2016 at 02:10:12PM +0300, Slawa Olhovchenkov wrote:
> > >>> This allocated one for all controllers, or allocated for every
> > >>> controller?
> > >>
> > >> It’s per-controller.
> > >>
> > >> I’ve thought about making the tuning be dynamic at runtime. I
> > >> implemented simil
On Sun, Mar 06, 2016 at 11:40:55PM -0800, Scott Long wrote:
>
> > On Mar 6, 2016, at 10:04 PM, Slawa Olhovchenkov wrote:
> >
> > On Sun, Mar 06, 2016 at 06:20:06PM -0800, Scott Long wrote:
> >
> >>
> >>> On Mar 6, 2016, at 1:27 PM, Slawa Olhovchenkov wrote:
> >>>
> >>> On Sun, Mar 06, 2016
> On Mar 6, 2016, at 10:04 PM, Slawa Olhovchenkov wrote:
>
> On Sun, Mar 06, 2016 at 06:20:06PM -0800, Scott Long wrote:
>
>>
>>> On Mar 6, 2016, at 1:27 PM, Slawa Olhovchenkov wrote:
>>>
>>> On Sun, Mar 06, 2016 at 01:10:42PM -0800, Scott Long wrote:
>>>
Hi,
The message is
On Sun, Mar 06, 2016 at 06:20:06PM -0800, Scott Long wrote:
>
> > On Mar 6, 2016, at 1:27 PM, Slawa Olhovchenkov wrote:
> >
> > On Sun, Mar 06, 2016 at 01:10:42PM -0800, Scott Long wrote:
> >
> >> Hi,
> >>
> >> The message is harmless, it's a reminder that you should tune the kernel
> >> for
> On Mar 6, 2016, at 1:27 PM, Slawa Olhovchenkov wrote:
>
> On Sun, Mar 06, 2016 at 01:10:42PM -0800, Scott Long wrote:
>
>> Hi,
>>
>> The message is harmless, it's a reminder that you should tune the kernel for
>> your workload. When the message is triggered, it means that a potential
>> c
l: mps3: Out of chain frames, consider
> > increasing hw.mps.max_chains.
> > Mar 6 22:28:28 edge02 kernel: mps1: Out of chain frames, consider
> > increasing hw.mps.max_chains.
> > Mar 6 22:28:28 edge02 kernel: mps0: Out of chain frames, consider
> > increasing hw.mp
es like this:
>
> Mar 6 22:28:27 edge02 kernel: mps3: Out of chain frames, consider increasing
> hw.mps.max_chains.
> Mar 6 22:28:28 edge02 kernel: mps1: Out of chain frames, consider increasing
> hw.mps.max_chains.
> Mar 6 22:28:28 edge02 kernel: mps0: Out of chain fram
frames, consider increasing
hw.mps.max_chains.
Mar 6 22:28:28 edge02 kernel: mps1: Out of chain frames, consider increasing
hw.mps.max_chains.
Mar 6 22:28:28 edge02 kernel: mps0: Out of chain frames, consider increasing
hw.mps.max_chains.
Mar 6 22:29:39 edge02 kernel: mps0: Out of chain frames
13 matches
Mail list logo
