lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <28432.1423551917@famine> Date: Mon, 09 Feb 2015 23:05:17 -0800 From: Jay Vosburgh <jay.vosburgh@...onical.com> To: Mahesh Bandewar <maheshb@...gle.com> cc: Andy Gospodarek <gospo@...ulusnetworks.com>, Andy Gospodarek <andy@...yhouse.net>, Veaceslav Falico <vfalico@...il.com>, Nikolay Aleksandrov <nikolay@...hat.com>, David Miller <davem@...emloft.net>, netdev <netdev@...r.kernel.org>, Eric Dumazet <edumazet@...gle.com> Subject: Re: [PATCH next 4/6] bonding: Allow userspace to set system_priority Mahesh Bandewar <maheshb@...gle.com> wrote: [...] >Actually I was thinking of making ad_actor_sysprio instead of making >ad_user_port_key (feels like having more underscores makes it >unnecessary longer). That way all three look similar. So > > ad_actor_sysprio > ad_actor_system > ad_user_portkey > >All carry the same theme of meaning. Otherwise we could do something like - > > ad_actor_sys_prio > ad_actor_sys_mac > ad_user_port_key > >Which one seems more logical / reasonable? FWIW, I would go with ad_actor_sys_prio, ad_actor_system and ad_user_port_key. The first two then mimic the terms from the standard, and the "user" one is part of the Actor_Admin_Port_Key from the standard, so it follows the same sort of naming. -J --- -Jay Vosburgh, jay.vosburgh@...onical.com -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists