Ofer Levi(SW) <ofe...@mellanox.com>
> Cc: ru...@rustcorp.com.au; mi...@redhat.com;
> vineet.gup...@synopsys.com; linux-kernel@vger.kernel.org; Tejun Heo
> <t...@kernel.org>
> Subject: Re: hotplug support for arch/arc/plat-eznps platform
>
> On Thu, Aug 10, 2017 at 11
fer Levi(SW)
> Cc: ru...@rustcorp.com.au; mi...@redhat.com;
> vineet.gup...@synopsys.com; linux-kernel@vger.kernel.org; Tejun Heo
>
> Subject: Re: hotplug support for arch/arc/plat-eznps platform
>
> On Thu, Aug 10, 2017 at 11:19:05AM +0200, Peter Zijlstra wrote:
> > On T
On Thu, Aug 10, 2017 at 11:19:05AM +0200, Peter Zijlstra wrote:
> On Thu, Aug 10, 2017 at 07:40:16AM +, Ofer Levi(SW) wrote:
> > Well, this definitely have pleased the little toy :)
> > Thank you. I really appreciate your time and effort.
> >
> > If I may, one more newbie question. What do I
On Thu, Aug 10, 2017 at 11:19:05AM +0200, Peter Zijlstra wrote:
> On Thu, Aug 10, 2017 at 07:40:16AM +, Ofer Levi(SW) wrote:
> > Well, this definitely have pleased the little toy :)
> > Thank you. I really appreciate your time and effort.
> >
> > If I may, one more newbie question. What do I
l@vger.kernel.org; Tejun Heo
> <t...@kernel.org>
> Subject: Re: hotplug support for arch/arc/plat-eznps platform
>
> On Thu, Aug 10, 2017 at 07:40:16AM +, Ofer Levi(SW) wrote:
> > Well, this definitely have pleased the little toy :) Thank you. I
> > really appre
o
>
> Subject: Re: hotplug support for arch/arc/plat-eznps platform
>
> On Thu, Aug 10, 2017 at 07:40:16AM +, Ofer Levi(SW) wrote:
> > Well, this definitely have pleased the little toy :) Thank you. I
> > really appreciate your time and effort.
> >
> > If
On Thu, Aug 10, 2017 at 07:40:16AM +, Ofer Levi(SW) wrote:
> Well, this definitely have pleased the little toy :)
> Thank you. I really appreciate your time and effort.
>
> If I may, one more newbie question. What do I need to do for the two patches
> to find
> their way into formal kernel
On Thu, Aug 10, 2017 at 07:40:16AM +, Ofer Levi(SW) wrote:
> Well, this definitely have pleased the little toy :)
> Thank you. I really appreciate your time and effort.
>
> If I may, one more newbie question. What do I need to do for the two patches
> to find
> their way into formal kernel
jlstra [mailto:pet...@infradead.org]
> Sent: Wednesday, August 9, 2017 6:35 PM
> To: Ofer Levi(SW) <ofe...@mellanox.com>
> Cc: ru...@rustcorp.com.au; mi...@redhat.com;
> vineet.gup...@synopsys.com; linux-kernel@vger.kernel.org; Tejun Heo
> <t...@kernel.org>
> Subject: R
jlstra [mailto:pet...@infradead.org]
> Sent: Wednesday, August 9, 2017 6:35 PM
> To: Ofer Levi(SW)
> Cc: ru...@rustcorp.com.au; mi...@redhat.com;
> vineet.gup...@synopsys.com; linux-kernel@vger.kernel.org; Tejun Heo
>
> Subject: Re: hotplug support for arch/arc/plat-eznps plat
On Wed, Aug 09, 2017 at 03:19:02PM +, Ofer Levi(SW) wrote:
> I appreciate your effort and detailed reply, however I'm still experiencing
> performance hit at
> partition_sched_domains(). It seems the issue is due to the large magnitude
> of cpus.
> I used he suggested method 2, patched in
On Wed, Aug 09, 2017 at 03:19:02PM +, Ofer Levi(SW) wrote:
> I appreciate your effort and detailed reply, however I'm still experiencing
> performance hit at
> partition_sched_domains(). It seems the issue is due to the large magnitude
> of cpus.
> I used he suggested method 2, patched in
hat.com;
> vineet.gup...@synopsys.com; linux-kernel@vger.kernel.org; Tejun Heo
> <t...@kernel.org>
> Subject: Re: hotplug support for arch/arc/plat-eznps platform
>
> On Tue, Aug 08, 2017 at 06:49:39AM +, Ofer Levi(SW) wrote:
>
> > The idea behind implementing hotplug for thi
.com; linux-kernel@vger.kernel.org; Tejun Heo
>
> Subject: Re: hotplug support for arch/arc/plat-eznps platform
>
> On Tue, Aug 08, 2017 at 06:49:39AM +, Ofer Levi(SW) wrote:
>
> > The idea behind implementing hotplug for this arch is to shorten time
> > to traffic pr
On Tue, Aug 08, 2017 at 06:49:39AM +, Ofer Levi(SW) wrote:
> The idea behind implementing hotplug for this arch is to shorten time
> to traffic processing. This way instead of waiting ~5 min for all
> cpus to boot, application running on cpu 0 will Loop booting other
> cpus and assigning
On Tue, Aug 08, 2017 at 06:49:39AM +, Ofer Levi(SW) wrote:
> The idea behind implementing hotplug for this arch is to shorten time
> to traffic processing. This way instead of waiting ~5 min for all
> cpus to boot, application running on cpu 0 will Loop booting other
> cpus and assigning
> On Monday, August 7, 2017 6:10 PM +, Ofer Levi(SW) wrote:
>
> On Mon, Aug 07, 2017 at 01:41:38PM +, Ofer Levi(SW) wrote:
> > > You've failed to explain why you think hotplug should be a
> > > performance critical path.
> > 1. hotplug bring up of 4K cpus takes 40 minutes. Way too much
> On Monday, August 7, 2017 6:10 PM +, Ofer Levi(SW) wrote:
>
> On Mon, Aug 07, 2017 at 01:41:38PM +, Ofer Levi(SW) wrote:
> > > You've failed to explain why you think hotplug should be a
> > > performance critical path.
> > 1. hotplug bring up of 4K cpus takes 40 minutes. Way too much
On Mon, Aug 07, 2017 at 01:41:38PM +, Ofer Levi(SW) wrote:
> > You've failed to explain why you think hotplug should be a performance
> > critical path.
> 1. hotplug bring up of 4K cpus takes 40 minutes. Way too much for any user.
> 2. plat-eznps is a network processor, where bring up time is
On Mon, Aug 07, 2017 at 01:41:38PM +, Ofer Levi(SW) wrote:
> > You've failed to explain why you think hotplug should be a performance
> > critical path.
> 1. hotplug bring up of 4K cpus takes 40 minutes. Way too much for any user.
> 2. plat-eznps is a network processor, where bring up time is
> You've failed to explain why you think hotplug should be a performance
> critical path.
1. hotplug bring up of 4K cpus takes 40 minutes. Way too much for any user.
2. plat-eznps is a network processor, where bring up time is sensitive.
> I'm also not seeing how it would be different from boot;
> You've failed to explain why you think hotplug should be a performance
> critical path.
1. hotplug bring up of 4K cpus takes 40 minutes. Way too much for any user.
2. plat-eznps is a network processor, where bring up time is sensitive.
> I'm also not seeing how it would be different from boot;
On Sun, Aug 06, 2017 at 05:53:37AM +, Ofer Levi(SW) wrote:
> I'm adding hot-plug support for the above arch and ran into performance issue
> with execution of
> partition_sched_domains () - About 0.5 sec per cpu, which is unacceptable
> with the arch supported 4k cpus.
> To my limited
On Sun, Aug 06, 2017 at 05:53:37AM +, Ofer Levi(SW) wrote:
> I'm adding hot-plug support for the above arch and ran into performance issue
> with execution of
> partition_sched_domains () - About 0.5 sec per cpu, which is unacceptable
> with the arch supported 4k cpus.
> To my limited
I'm adding hot-plug support for the above arch and ran into performance issue
with execution of
partition_sched_domains () - About 0.5 sec per cpu, which is unacceptable with
the arch supported 4k cpus.
To my limited understanding, on the plat-eznps arch, where each cpu is always
running a
I'm adding hot-plug support for the above arch and ran into performance issue
with execution of
partition_sched_domains () - About 0.5 sec per cpu, which is unacceptable with
the arch supported 4k cpus.
To my limited understanding, on the plat-eznps arch, where each cpu is always
running a
26 matches
Mail list logo
