* [PATCH] arm64: Kconfig: Increase NR_CPUS default to 512
@ 2021-01-10 5:36 ` vanshikonda
0 siblings, 0 replies; 16+ messages in thread
From: vanshikonda @ 2021-01-10 5:36 UTC (permalink / raw)
To: linux-arm-kernel
Cc: will, linux-kernel, catalin.marinas, patches, Vanshidhar Konda
From: Vanshidhar Konda <vanshikonda@os.amperecomputing.com>
Increase the default value of NR_CPUS to 512 from 256. This will
enable the defconfig kernel to support platforms that have upto
512 cores.
Signed-off-by: Vanshidhar Konda <vanshikonda@os.amperecomputing.com>
---
arch/arm64/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
index 05e17351e4f3..23fbbf413f58 100644
--- a/arch/arm64/Kconfig
+++ b/arch/arm64/Kconfig
@@ -983,7 +983,7 @@ config SCHED_SMT
config NR_CPUS
int "Maximum number of CPUs (2-4096)"
range 2 4096
- default "256"
+ default "512"
config HOTPLUG_CPU
bool "Support for hot-pluggable CPUs"
--
2.29.2
^ permalink raw reply related [flat|nested] 16+ messages in thread
* [PATCH] arm64: Kconfig: Increase NR_CPUS default to 512
@ 2021-01-10 5:36 ` vanshikonda
0 siblings, 0 replies; 16+ messages in thread
From: vanshikonda @ 2021-01-10 5:36 UTC (permalink / raw)
To: linux-arm-kernel
Cc: catalin.marinas, patches, will, linux-kernel, Vanshidhar Konda
From: Vanshidhar Konda <vanshikonda@os.amperecomputing.com>
Increase the default value of NR_CPUS to 512 from 256. This will
enable the defconfig kernel to support platforms that have upto
512 cores.
Signed-off-by: Vanshidhar Konda <vanshikonda@os.amperecomputing.com>
---
arch/arm64/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
index 05e17351e4f3..23fbbf413f58 100644
--- a/arch/arm64/Kconfig
+++ b/arch/arm64/Kconfig
@@ -983,7 +983,7 @@ config SCHED_SMT
config NR_CPUS
int "Maximum number of CPUs (2-4096)"
range 2 4096
- default "256"
+ default "512"
config HOTPLUG_CPU
bool "Support for hot-pluggable CPUs"
--
2.29.2
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply related [flat|nested] 16+ messages in thread
* Re: [PATCH] arm64: Kconfig: Increase NR_CPUS default to 512
2021-01-10 5:36 ` vanshikonda
@ 2021-01-11 10:56 ` Will Deacon
-1 siblings, 0 replies; 16+ messages in thread
From: Will Deacon @ 2021-01-11 10:56 UTC (permalink / raw)
To: vanshikonda; +Cc: linux-arm-kernel, linux-kernel, catalin.marinas, patches
On Sat, Jan 09, 2021 at 09:36:15PM -0800, vanshikonda@os.amperecomputing.com wrote:
> From: Vanshidhar Konda <vanshikonda@os.amperecomputing.com>
>
> Increase the default value of NR_CPUS to 512 from 256. This will
> enable the defconfig kernel to support platforms that have upto
> 512 cores.
Do we already support such a platform, and what is it? I'm fine with bumping
the number, it's just nice to be able to say specifically _why_ we're dong
it.
Thanks,
Will
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [PATCH] arm64: Kconfig: Increase NR_CPUS default to 512
@ 2021-01-11 10:56 ` Will Deacon
0 siblings, 0 replies; 16+ messages in thread
From: Will Deacon @ 2021-01-11 10:56 UTC (permalink / raw)
To: vanshikonda; +Cc: catalin.marinas, patches, linux-kernel, linux-arm-kernel
On Sat, Jan 09, 2021 at 09:36:15PM -0800, vanshikonda@os.amperecomputing.com wrote:
> From: Vanshidhar Konda <vanshikonda@os.amperecomputing.com>
>
> Increase the default value of NR_CPUS to 512 from 256. This will
> enable the defconfig kernel to support platforms that have upto
> 512 cores.
Do we already support such a platform, and what is it? I'm fine with bumping
the number, it's just nice to be able to say specifically _why_ we're dong
it.
Thanks,
Will
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [PATCH] arm64: Kconfig: Increase NR_CPUS default to 512
2021-01-11 10:56 ` Will Deacon
@ 2021-01-11 17:57 ` Vanshidhar Konda
-1 siblings, 0 replies; 16+ messages in thread
From: Vanshidhar Konda @ 2021-01-11 17:57 UTC (permalink / raw)
To: Will Deacon; +Cc: linux-arm-kernel, linux-kernel, catalin.marinas, patches
On Mon, Jan 11, 2021 at 10:56:36AM +0000, Will Deacon wrote:
>On Sat, Jan 09, 2021 at 09:36:15PM -0800, vanshikonda@os.amperecomputing.com wrote:
>> From: Vanshidhar Konda <vanshikonda@os.amperecomputing.com>
>>
>> Increase the default value of NR_CPUS to 512 from 256. This will
>> enable the defconfig kernel to support platforms that have upto
>> 512 cores.
>
>Do we already support such a platform, and what is it? I'm fine with bumping
>the number, it's just nice to be able to say specifically _why_ we're dong
>it.
I'm not aware of any publicly available systems that run into the 256
core limitation. At Ampere we have internal systems that would benefit
from this change as they support more than 256 cores.
Thanks,
Vanshi
>
>Thanks,
>
>Will
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [PATCH] arm64: Kconfig: Increase NR_CPUS default to 512
@ 2021-01-11 17:57 ` Vanshidhar Konda
0 siblings, 0 replies; 16+ messages in thread
From: Vanshidhar Konda @ 2021-01-11 17:57 UTC (permalink / raw)
To: Will Deacon; +Cc: catalin.marinas, patches, linux-kernel, linux-arm-kernel
On Mon, Jan 11, 2021 at 10:56:36AM +0000, Will Deacon wrote:
>On Sat, Jan 09, 2021 at 09:36:15PM -0800, vanshikonda@os.amperecomputing.com wrote:
>> From: Vanshidhar Konda <vanshikonda@os.amperecomputing.com>
>>
>> Increase the default value of NR_CPUS to 512 from 256. This will
>> enable the defconfig kernel to support platforms that have upto
>> 512 cores.
>
>Do we already support such a platform, and what is it? I'm fine with bumping
>the number, it's just nice to be able to say specifically _why_ we're dong
>it.
I'm not aware of any publicly available systems that run into the 256
core limitation. At Ampere we have internal systems that would benefit
from this change as they support more than 256 cores.
Thanks,
Vanshi
>
>Thanks,
>
>Will
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [PATCH] arm64: Kconfig: Increase NR_CPUS default to 512
2021-01-11 17:57 ` Vanshidhar Konda
@ 2021-01-11 18:03 ` Randy Dunlap
-1 siblings, 0 replies; 16+ messages in thread
From: Randy Dunlap @ 2021-01-11 18:03 UTC (permalink / raw)
To: Vanshidhar Konda, Will Deacon
Cc: linux-arm-kernel, linux-kernel, catalin.marinas, patches
On 1/11/21 9:57 AM, Vanshidhar Konda wrote:
> On Mon, Jan 11, 2021 at 10:56:36AM +0000, Will Deacon wrote:
>> On Sat, Jan 09, 2021 at 09:36:15PM -0800, vanshikonda@os.amperecomputing.com wrote:
>>> From: Vanshidhar Konda <vanshikonda@os.amperecomputing.com>
>>>
>>> Increase the default value of NR_CPUS to 512 from 256. This will
>>> enable the defconfig kernel to support platforms that have upto
>>> 512 cores.
>>
>> Do we already support such a platform, and what is it? I'm fine with bumping.
>> the number, it's just nice to be able to say specifically _why_ we're dong
>> it.
>
> I'm not aware of any publicly available systems that run into the 256
> core limitation. At Ampere we have internal systems that would benefit
> from this change as they support more than 256 cores.
But what does that have to do with the default value?
Do you expect to run defconfig kernels?
I don't ever expect that.
--
~Randy
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [PATCH] arm64: Kconfig: Increase NR_CPUS default to 512
@ 2021-01-11 18:03 ` Randy Dunlap
0 siblings, 0 replies; 16+ messages in thread
From: Randy Dunlap @ 2021-01-11 18:03 UTC (permalink / raw)
To: Vanshidhar Konda, Will Deacon
Cc: catalin.marinas, patches, linux-kernel, linux-arm-kernel
On 1/11/21 9:57 AM, Vanshidhar Konda wrote:
> On Mon, Jan 11, 2021 at 10:56:36AM +0000, Will Deacon wrote:
>> On Sat, Jan 09, 2021 at 09:36:15PM -0800, vanshikonda@os.amperecomputing.com wrote:
>>> From: Vanshidhar Konda <vanshikonda@os.amperecomputing.com>
>>>
>>> Increase the default value of NR_CPUS to 512 from 256. This will
>>> enable the defconfig kernel to support platforms that have upto
>>> 512 cores.
>>
>> Do we already support such a platform, and what is it? I'm fine with bumping.
>> the number, it's just nice to be able to say specifically _why_ we're dong
>> it.
>
> I'm not aware of any publicly available systems that run into the 256
> core limitation. At Ampere we have internal systems that would benefit
> from this change as they support more than 256 cores.
But what does that have to do with the default value?
Do you expect to run defconfig kernels?
I don't ever expect that.
--
~Randy
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [PATCH] arm64: Kconfig: Increase NR_CPUS default to 512
2021-01-11 18:03 ` Randy Dunlap
@ 2021-01-11 18:24 ` Vanshi Konda
-1 siblings, 0 replies; 16+ messages in thread
From: Vanshi Konda @ 2021-01-11 18:24 UTC (permalink / raw)
To: Randy Dunlap
Cc: Vanshidhar Konda, Will Deacon, linux-arm-kernel, linux-kernel,
catalin.marinas, patches
On Mon, Jan 11, 2021 at 10:03:18AM -0800, Randy Dunlap wrote:
>[EXTERNAL EMAIL NOTICE: This email originated from an external sender. Please be mindful of safe email handling and proprietary information protection practices.]
>
>
>On 1/11/21 9:57 AM, Vanshidhar Konda wrote:
>> On Mon, Jan 11, 2021 at 10:56:36AM +0000, Will Deacon wrote:
>>> On Sat, Jan 09, 2021 at 09:36:15PM -0800, vanshikonda@os.amperecomputing.com wrote:
>>>> From: Vanshidhar Konda <vanshikonda@os.amperecomputing.com>
>>>>
>>>> Increase the default value of NR_CPUS to 512 from 256. This will
>>>> enable the defconfig kernel to support platforms that have upto
>>>> 512 cores.
>>>
>>> Do we already support such a platform, and what is it? I'm fine with bumping.
>>> the number, it's just nice to be able to say specifically _why_ we're dong
>>> it.
>>
>> I'm not aware of any publicly available systems that run into the 256
>> core limitation. At Ampere we have internal systems that would benefit
>> from this change as they support more than 256 cores.
>
>But what does that have to do with the default value?
>Do you expect to run defconfig kernels?
>I don't ever expect that.
Sorry. I should have been more clear in my earlier statement. We
currently have systems in development internally, to be available
publicly later, that support more than 256 cores. Given the time it
takes for a kernel version to be adopted by distros it makes sense to
change the defconfig now rather than later.
Thanks,
Vanshi
>
>--
>~Randy
>
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [PATCH] arm64: Kconfig: Increase NR_CPUS default to 512
@ 2021-01-11 18:24 ` Vanshi Konda
0 siblings, 0 replies; 16+ messages in thread
From: Vanshi Konda @ 2021-01-11 18:24 UTC (permalink / raw)
To: Randy Dunlap
Cc: catalin.marinas, linux-kernel, patches, Will Deacon,
Vanshidhar Konda, linux-arm-kernel
On Mon, Jan 11, 2021 at 10:03:18AM -0800, Randy Dunlap wrote:
>[EXTERNAL EMAIL NOTICE: This email originated from an external sender. Please be mindful of safe email handling and proprietary information protection practices.]
>
>
>On 1/11/21 9:57 AM, Vanshidhar Konda wrote:
>> On Mon, Jan 11, 2021 at 10:56:36AM +0000, Will Deacon wrote:
>>> On Sat, Jan 09, 2021 at 09:36:15PM -0800, vanshikonda@os.amperecomputing.com wrote:
>>>> From: Vanshidhar Konda <vanshikonda@os.amperecomputing.com>
>>>>
>>>> Increase the default value of NR_CPUS to 512 from 256. This will
>>>> enable the defconfig kernel to support platforms that have upto
>>>> 512 cores.
>>>
>>> Do we already support such a platform, and what is it? I'm fine with bumping.
>>> the number, it's just nice to be able to say specifically _why_ we're dong
>>> it.
>>
>> I'm not aware of any publicly available systems that run into the 256
>> core limitation. At Ampere we have internal systems that would benefit
>> from this change as they support more than 256 cores.
>
>But what does that have to do with the default value?
>Do you expect to run defconfig kernels?
>I don't ever expect that.
Sorry. I should have been more clear in my earlier statement. We
currently have systems in development internally, to be available
publicly later, that support more than 256 cores. Given the time it
takes for a kernel version to be adopted by distros it makes sense to
change the defconfig now rather than later.
Thanks,
Vanshi
>
>--
>~Randy
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [PATCH] arm64: Kconfig: Increase NR_CPUS default to 512
2021-01-11 18:03 ` Randy Dunlap
@ 2021-01-11 18:25 ` Catalin Marinas
-1 siblings, 0 replies; 16+ messages in thread
From: Catalin Marinas @ 2021-01-11 18:25 UTC (permalink / raw)
To: Randy Dunlap
Cc: Vanshidhar Konda, Will Deacon, linux-arm-kernel, linux-kernel, patches
On Mon, Jan 11, 2021 at 10:03:18AM -0800, Randy Dunlap wrote:
> On 1/11/21 9:57 AM, Vanshidhar Konda wrote:
> > On Mon, Jan 11, 2021 at 10:56:36AM +0000, Will Deacon wrote:
> >> On Sat, Jan 09, 2021 at 09:36:15PM -0800, vanshikonda@os.amperecomputing.com wrote:
> >>> From: Vanshidhar Konda <vanshikonda@os.amperecomputing.com>
> >>>
> >>> Increase the default value of NR_CPUS to 512 from 256. This will
> >>> enable the defconfig kernel to support platforms that have upto
> >>> 512 cores.
> >>
> >> Do we already support such a platform, and what is it? I'm fine with bumping.
> >> the number, it's just nice to be able to say specifically _why_ we're dong
> >> it.
> >
> > I'm not aware of any publicly available systems that run into the 256
> > core limitation. At Ampere we have internal systems that would benefit
> > from this change as they support more than 256 cores.
>
> But what does that have to do with the default value?
> Do you expect to run defconfig kernels?
> I don't ever expect that.
We still aim for the arm64 defconfig to run on all supported SoCs, even
if not optimally. Distros indeed tweak the config to their needs.
--
Catalin
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [PATCH] arm64: Kconfig: Increase NR_CPUS default to 512
@ 2021-01-11 18:25 ` Catalin Marinas
0 siblings, 0 replies; 16+ messages in thread
From: Catalin Marinas @ 2021-01-11 18:25 UTC (permalink / raw)
To: Randy Dunlap
Cc: patches, Will Deacon, Vanshidhar Konda, linux-arm-kernel, linux-kernel
On Mon, Jan 11, 2021 at 10:03:18AM -0800, Randy Dunlap wrote:
> On 1/11/21 9:57 AM, Vanshidhar Konda wrote:
> > On Mon, Jan 11, 2021 at 10:56:36AM +0000, Will Deacon wrote:
> >> On Sat, Jan 09, 2021 at 09:36:15PM -0800, vanshikonda@os.amperecomputing.com wrote:
> >>> From: Vanshidhar Konda <vanshikonda@os.amperecomputing.com>
> >>>
> >>> Increase the default value of NR_CPUS to 512 from 256. This will
> >>> enable the defconfig kernel to support platforms that have upto
> >>> 512 cores.
> >>
> >> Do we already support such a platform, and what is it? I'm fine with bumping.
> >> the number, it's just nice to be able to say specifically _why_ we're dong
> >> it.
> >
> > I'm not aware of any publicly available systems that run into the 256
> > core limitation. At Ampere we have internal systems that would benefit
> > from this change as they support more than 256 cores.
>
> But what does that have to do with the default value?
> Do you expect to run defconfig kernels?
> I don't ever expect that.
We still aim for the arm64 defconfig to run on all supported SoCs, even
if not optimally. Distros indeed tweak the config to their needs.
--
Catalin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [PATCH] arm64: Kconfig: Increase NR_CPUS default to 512
2021-01-11 18:25 ` Catalin Marinas
@ 2021-01-12 5:20 ` Vanshidhar Konda
-1 siblings, 0 replies; 16+ messages in thread
From: Vanshidhar Konda @ 2021-01-12 5:20 UTC (permalink / raw)
To: Catalin Marinas
Cc: Randy Dunlap, Will Deacon, linux-arm-kernel, linux-kernel, patches
On Mon, Jan 11, 2021 at 06:25:27PM +0000, Catalin Marinas wrote:
>On Mon, Jan 11, 2021 at 10:03:18AM -0800, Randy Dunlap wrote:
>> On 1/11/21 9:57 AM, Vanshidhar Konda wrote:
>> > On Mon, Jan 11, 2021 at 10:56:36AM +0000, Will Deacon wrote:
>> >> On Sat, Jan 09, 2021 at 09:36:15PM -0800, vanshikonda@os.amperecomputing.com wrote:
>> >>> From: Vanshidhar Konda <vanshikonda@os.amperecomputing.com>
>> >>>
>> >>> Increase the default value of NR_CPUS to 512 from 256. This will
>> >>> enable the defconfig kernel to support platforms that have upto
>> >>> 512 cores.
>> >>
>> >> Do we already support such a platform, and what is it? I'm fine with bumping.
>> >> the number, it's just nice to be able to say specifically _why_ we're dong
>> >> it.
>> >
>> > I'm not aware of any publicly available systems that run into the 256
>> > core limitation. At Ampere we have internal systems that would benefit
>> > from this change as they support more than 256 cores.
>>
>> But what does that have to do with the default value?
>> Do you expect to run defconfig kernels?
>> I don't ever expect that.
>
>We still aim for the arm64 defconfig to run on all supported SoCs, even
>if not optimally. Distros indeed tweak the config to their needs.
Would "all supported SoCs" mean only SoCs that are currently available
publicly? Could we include support for SoCs/systems in development but
to be available publicly in the next few years?
Thanks,
Vanshi
>
>--
>Catalin
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [PATCH] arm64: Kconfig: Increase NR_CPUS default to 512
@ 2021-01-12 5:20 ` Vanshidhar Konda
0 siblings, 0 replies; 16+ messages in thread
From: Vanshidhar Konda @ 2021-01-12 5:20 UTC (permalink / raw)
To: Catalin Marinas
Cc: patches, Randy Dunlap, Will Deacon, linux-kernel, linux-arm-kernel
On Mon, Jan 11, 2021 at 06:25:27PM +0000, Catalin Marinas wrote:
>On Mon, Jan 11, 2021 at 10:03:18AM -0800, Randy Dunlap wrote:
>> On 1/11/21 9:57 AM, Vanshidhar Konda wrote:
>> > On Mon, Jan 11, 2021 at 10:56:36AM +0000, Will Deacon wrote:
>> >> On Sat, Jan 09, 2021 at 09:36:15PM -0800, vanshikonda@os.amperecomputing.com wrote:
>> >>> From: Vanshidhar Konda <vanshikonda@os.amperecomputing.com>
>> >>>
>> >>> Increase the default value of NR_CPUS to 512 from 256. This will
>> >>> enable the defconfig kernel to support platforms that have upto
>> >>> 512 cores.
>> >>
>> >> Do we already support such a platform, and what is it? I'm fine with bumping.
>> >> the number, it's just nice to be able to say specifically _why_ we're dong
>> >> it.
>> >
>> > I'm not aware of any publicly available systems that run into the 256
>> > core limitation. At Ampere we have internal systems that would benefit
>> > from this change as they support more than 256 cores.
>>
>> But what does that have to do with the default value?
>> Do you expect to run defconfig kernels?
>> I don't ever expect that.
>
>We still aim for the arm64 defconfig to run on all supported SoCs, even
>if not optimally. Distros indeed tweak the config to their needs.
Would "all supported SoCs" mean only SoCs that are currently available
publicly? Could we include support for SoCs/systems in development but
to be available publicly in the next few years?
Thanks,
Vanshi
>
>--
>Catalin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [PATCH] arm64: Kconfig: Increase NR_CPUS default to 512
2021-01-12 5:20 ` Vanshidhar Konda
@ 2021-01-12 14:27 ` Will Deacon
-1 siblings, 0 replies; 16+ messages in thread
From: Will Deacon @ 2021-01-12 14:27 UTC (permalink / raw)
To: Vanshidhar Konda
Cc: Catalin Marinas, Randy Dunlap, linux-arm-kernel, linux-kernel, patches
On Mon, Jan 11, 2021 at 09:20:03PM -0800, Vanshidhar Konda wrote:
> On Mon, Jan 11, 2021 at 06:25:27PM +0000, Catalin Marinas wrote:
> > On Mon, Jan 11, 2021 at 10:03:18AM -0800, Randy Dunlap wrote:
> > > On 1/11/21 9:57 AM, Vanshidhar Konda wrote:
> > > > On Mon, Jan 11, 2021 at 10:56:36AM +0000, Will Deacon wrote:
> > > >> On Sat, Jan 09, 2021 at 09:36:15PM -0800, vanshikonda@os.amperecomputing.com wrote:
> > > >>> From: Vanshidhar Konda <vanshikonda@os.amperecomputing.com>
> > > >>>
> > > >>> Increase the default value of NR_CPUS to 512 from 256. This will
> > > >>> enable the defconfig kernel to support platforms that have upto
> > > >>> 512 cores.
> > > >>
> > > >> Do we already support such a platform, and what is it? I'm fine with bumping.
> > > >> the number, it's just nice to be able to say specifically _why_ we're dong
> > > >> it.
> > > >
> > > > I'm not aware of any publicly available systems that run into the 256
> > > > core limitation. At Ampere we have internal systems that would benefit
> > > > from this change as they support more than 256 cores.
> > >
> > > But what does that have to do with the default value?
> > > Do you expect to run defconfig kernels?
> > > I don't ever expect that.
> >
> > We still aim for the arm64 defconfig to run on all supported SoCs, even
> > if not optimally. Distros indeed tweak the config to their needs.
>
> Would "all supported SoCs" mean only SoCs that are currently available
> publicly? Could we include support for SoCs/systems in development but
> to be available publicly in the next few years?
I don't really see the need to rush that into defconfig, so I'd prefer
to make the update when something actually exists otherwise it's really
hard to keep track of why we made the decision (especially as unreleased
hardware is liable to change).
Will
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [PATCH] arm64: Kconfig: Increase NR_CPUS default to 512
@ 2021-01-12 14:27 ` Will Deacon
0 siblings, 0 replies; 16+ messages in thread
From: Will Deacon @ 2021-01-12 14:27 UTC (permalink / raw)
To: Vanshidhar Konda
Cc: Catalin Marinas, patches, Randy Dunlap, linux-kernel, linux-arm-kernel
On Mon, Jan 11, 2021 at 09:20:03PM -0800, Vanshidhar Konda wrote:
> On Mon, Jan 11, 2021 at 06:25:27PM +0000, Catalin Marinas wrote:
> > On Mon, Jan 11, 2021 at 10:03:18AM -0800, Randy Dunlap wrote:
> > > On 1/11/21 9:57 AM, Vanshidhar Konda wrote:
> > > > On Mon, Jan 11, 2021 at 10:56:36AM +0000, Will Deacon wrote:
> > > >> On Sat, Jan 09, 2021 at 09:36:15PM -0800, vanshikonda@os.amperecomputing.com wrote:
> > > >>> From: Vanshidhar Konda <vanshikonda@os.amperecomputing.com>
> > > >>>
> > > >>> Increase the default value of NR_CPUS to 512 from 256. This will
> > > >>> enable the defconfig kernel to support platforms that have upto
> > > >>> 512 cores.
> > > >>
> > > >> Do we already support such a platform, and what is it? I'm fine with bumping.
> > > >> the number, it's just nice to be able to say specifically _why_ we're dong
> > > >> it.
> > > >
> > > > I'm not aware of any publicly available systems that run into the 256
> > > > core limitation. At Ampere we have internal systems that would benefit
> > > > from this change as they support more than 256 cores.
> > >
> > > But what does that have to do with the default value?
> > > Do you expect to run defconfig kernels?
> > > I don't ever expect that.
> >
> > We still aim for the arm64 defconfig to run on all supported SoCs, even
> > if not optimally. Distros indeed tweak the config to their needs.
>
> Would "all supported SoCs" mean only SoCs that are currently available
> publicly? Could we include support for SoCs/systems in development but
> to be available publicly in the next few years?
I don't really see the need to rush that into defconfig, so I'd prefer
to make the update when something actually exists otherwise it's really
hard to keep track of why we made the decision (especially as unreleased
hardware is liable to change).
Will
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply [flat|nested] 16+ messages in thread
end of thread, other threads:[~2021-01-12 14:28 UTC | newest]
Thread overview: 16+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-01-10 5:36 [PATCH] arm64: Kconfig: Increase NR_CPUS default to 512 vanshikonda
2021-01-10 5:36 ` vanshikonda
2021-01-11 10:56 ` Will Deacon
2021-01-11 10:56 ` Will Deacon
2021-01-11 17:57 ` Vanshidhar Konda
2021-01-11 17:57 ` Vanshidhar Konda
2021-01-11 18:03 ` Randy Dunlap
2021-01-11 18:03 ` Randy Dunlap
2021-01-11 18:24 ` Vanshi Konda
2021-01-11 18:24 ` Vanshi Konda
2021-01-11 18:25 ` Catalin Marinas
2021-01-11 18:25 ` Catalin Marinas
2021-01-12 5:20 ` Vanshidhar Konda
2021-01-12 5:20 ` Vanshidhar Konda
2021-01-12 14:27 ` Will Deacon
2021-01-12 14:27 ` Will Deacon
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.