Re: [LEDE-DEV] Adding new targets/subtargets

> On Jan 2, 2017, at 1:38 PM, Alberto Bursi wrote: > > > > On 01/02/2017 07:36 PM, Philip Prindeville wrote: >> >> >> Right, this is why I’m trying to create a new target (or subtarget) called >> “xeon” which is optimized for Xeon targets and leverages the on-chip

Re: [LEDE-DEV] Adding new targets/subtargets

> On Jan 2, 2017, at 1:05 PM, Stefan Lippers-Hollmann wrote: > > Hi > > On 2017-01-02, Philip Prindeville wrote: >>> On Jan 2, 2017, at 10:01 AM, Jo-Philipp Wich wrote: >>> >>> Hi, >>> The x86/64/config-default is missing the following switches:

Re: [LEDE-DEV] Adding new targets/subtargets

On 2017-01-03 00:41, Philip Prindeville wrote: > And I’d like to do that. > > (a) we’d need to decide what benchmarks are meaningful… are the openssl > encryption benchmarks sufficient? I think it's a good start. However, please make sure you have the same encryption acceleration drivers enabled

Re: [LEDE-DEV] Adding new targets/subtargets

> On Jan 2, 2017, at 3:06 PM, Felix Fietkau wrote: > > On 2017-01-02 19:36, Philip Prindeville wrote: >> Right, this is why I’m trying to create a new target (or subtarget) >> called “xeon” which is optimized for Xeon targets and leverages the >> on-chip crypto-accelerators. >>

Re: [LEDE-DEV] Adding new targets/subtargets

On 01/02/2017 07:36 PM, Philip Prindeville wrote: > > > Right, this is why I’m trying to create a new target (or subtarget) called > “xeon” which is optimized for Xeon targets and leverages the on-chip > crypto-accelerators. > > We’ve come a long way since the Athalon-64 (k8) in 2004. > >

Re: [LEDE-DEV] Adding new targets/subtargets

Hi On 2017-01-02, Philip Prindeville wrote: > > On Jan 2, 2017, at 10:01 AM, Jo-Philipp Wich wrote: > > > > Hi, > > > >> The x86/64/config-default is missing the following switches: > >> > >> CONFIG_MCORE2=y [...] > Right, this is why I’m trying to create a new target (or

Re: [LEDE-DEV] Adding new targets/subtargets

> On Jan 2, 2017, at 10:08 AM, Jo-Philipp Wich wrote: > >> Why not instead just add a profile attribute like: >> >> BUILDBOT_BUILD_ME:=no > > Because we want to have complete coverage. Experience has shown that > untested subtargets quickly become stale and broken. > > ~ Jo

Re: [LEDE-DEV] Adding new targets/subtargets

Hi, > If this is going to be the road we travel down (I'm bikeshedding here) > wouldn't a BUILDBOT_INTERVAL:=daily/3d/7d/14d make more sense? it wouldn't as buildbot activity is distributed randomly and the master currently lacks suitable scheduling logic to implement such behavior. Besides

Re: [LEDE-DEV] Adding new targets/subtargets

Hi, > Pruning useful subtargets to solve a buildbot resource shortage seems > like taking a sledgehammer to kill a fly. Saving resources was only one of the considerations to cut back the amount of sub targets. The introduction of per-device/per-profile rootfs support in LEDE allowed us to

Re: [LEDE-DEV] Adding new targets/subtargets

Hi, > The x86/64/config-default is missing the following switches: > > CONFIG_MCORE2=y That would break support for older x86_64 iirc. > CONFIG_MDIO=y > CONFIG_X86_USE_PPRO_CHECKSUM=y Those can probably go into x86/64 directly, at least I see no reason why not. > [...] > ARCH_SUFFIX is taken

Re: [LEDE-DEV] Adding new targets/subtargets

> On Jan 1, 2017, at 8:34 AM, Weedy wrote: > > On 31 December 2016 at 20:23, Philip Prindeville > wrote: >> >> >> Pruning useful subtargets to solve a buildbot resource shortage seems like >> taking a sledgehammer to kill a fly. >>

Re: [LEDE-DEV] Adding new targets/subtargets

On 31 December 2016 at 20:23, Philip Prindeville wrote: > >> On Dec 31, 2016, at 9:32 AM, Yousong Zhou wrote: >> >> On 31 December 2016 at 06:13, Philip Prindeville >> wrote: >>> >>> I noticed that in

Re: [LEDE-DEV] Adding new targets/subtargets

> On Dec 31, 2016, at 9:32 AM, Yousong Zhou wrote: > > On 31 December 2016 at 06:13, Philip Prindeville > wrote: >> >>> On Dec 29, 2016, at 7:46 PM, Yousong Zhou wrote: >>> >>> On 30 December 2016 at 03:29,

Re: [LEDE-DEV] Adding new targets/subtargets

On 31 December 2016 at 06:13, Philip Prindeville wrote: > >> On Dec 29, 2016, at 7:46 PM, Yousong Zhou wrote: >> >> On 30 December 2016 at 03:29, Philip Prindeville >> wrote: >>> On Dec 28, 2016, at

Re: [LEDE-DEV] Adding new targets/subtargets

> On Dec 29, 2016, at 7:46 PM, Yousong Zhou wrote: > > On 30 December 2016 at 03:29, Philip Prindeville > wrote: >> On Dec 28, 2016, at 7:57 PM, Yousong Zhou wrote: >> >> The x86/64/config-default is missing

Re: [LEDE-DEV] Adding new targets/subtargets

On 30 December 2016 at 03:29, Philip Prindeville wrote: > On Dec 28, 2016, at 7:57 PM, Yousong Zhou wrote: >> >> On 29 December 2016 at 10:04, Philip Prindeville >> wrote: >>> I wanted to add a new

Re: [LEDE-DEV] Adding new targets/subtargets

On Dec 28, 2016, at 7:57 PM, Yousong Zhou wrote: > > On 29 December 2016 at 10:04, Philip Prindeville > wrote: >> I wanted to add a new target for x86, or possibly several. >> >> I have an immediate need for an optimized build to run

Re: [LEDE-DEV] Adding new targets/subtargets

On 29 December 2016 at 10:04, Philip Prindeville wrote: > I wanted to add a new target for x86, or possibly several. > > I have an immediate need for an optimized build to run on Xeon-based 1U > servers for a project that I’m working on. My work in progress