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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070517174952.GB30571@kvack.org>
Date:	Thu, 17 May 2007 13:49:52 -0400
From:	Benjamin LaHaise <bcrl@...ck.org>
To:	James Bottomley <James.Bottomley@...elEye.com>
Cc:	Satyam Sharma <satyam.sharma@...il.com>,
	Matthew Wilcox <matthew@....cx>,
	Simon Arlott <simon@...e.lp0.eu>,
	Dave Jones <davej@...hat.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-scsi@...r.kernel.org, kernel-packagers@...r.kernel.org,
	"Robert P. J. Day" <rpjday@...dspring.com>
Subject: Re: sysfs makes scaling suck Re: Asynchronous scsi scanning

On Thu, May 17, 2007 at 01:45:24PM -0400, James Bottomley wrote:
> But also, the sysfs with over 4,000 (and higher) devices was
> specifically checked by OSDL (actually as part of the CGL testing) some
> of the Manoj changes (for unpinning entries etc) were needed to get it
> to function, but as of now, I believe an enterprise scaling test works
> reasonably well for it ... there certainly wasn't any evidence of it
> dying horribly in the tests.

i386 exhausts lowmem very quickly.  SCSI is in a bit better shape than 
network devices as the multiplier is only around 4 compared to 16 for network 
devices.

My point stands, though.  Forcing every new feature to go in via sysfs is 
not the right thing to do.  Some people don't/can't use it, please remember 
them.

		-ben
-- 
"Time is of no importance, Mr. President, only life is important."
Don't Email: <zyntrop@...ck.org>.
-
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ