| 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: <1171914227.29415.4.camel@localhost.localdomain> Date: Mon, 19 Feb 2007 11:43:46 -0800 From: Matthew Helsley <matthltc@...ibm.com> To: balbir@...ibm.com Cc: Paul Menage <menage@...gle.com>, Andrew Morton <akpm@...ux-foundation.org>, linux-kernel@...r.kernel.org, vatsa@...ibm.com, ckrm-tech@...ts.sourceforge.net, xemul@...ru, linux-mm@...ck.org, svaidy@...ux.vnet.ibm.com, devel@...nvz.org Subject: Re: [RFC][PATCH][1/4] RSS controller setup On Mon, 2007-02-19 at 16:43 +0530, Balbir Singh wrote: > Paul Menage wrote: > > On 2/19/07, Andrew Morton <akpm@...ux-foundation.org> wrote: <snip> > > Hmm, I don't appear to have documented this yet, but I think a good > > naming scheme for container files is <subsystem>.<whatever> - i.e. > > these should be memctlr.usage and memctlr.limit. The existing > > grandfathered Cpusets names violate this, but I'm not sure there's a > > lot we can do about that. > > > > Why <subsystem>.<whatever>, dots are harder to parse using regular > expressions and sound DOS'ish. I'd prefer "_" to separate the > subsystem and whatever :-) "_" is useful for names with "spaces". Names like mem_controller. "." seems reasonable despite its regex nastyness. Alternatively there's always ":". <snip> Cheers, -Matt Helsley - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists