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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Tue, 28 Jun 2011 18:04:48 -0700
From:	Ram Pai <linuxram@...ibm.com>
To:	Jesse Barnes <jbarnes@...tuousgeek.org>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org,
	yinghai@...nel.org
Subject: Re: [git pull] PCI fixes

On Tue, Jun 28, 2011 at 10:02:27AM -0700, Jesse Barnes wrote:
> On Fri, 24 Jun 2011 15:56:42 -0700
> Linus Torvalds <torvalds@...ux-foundation.org> wrote:
> 
> > 
> > 
> > 
> > Jesse Barnes <jbarnes@...tuousgeek.org> wrote:
> > >
> > >How about a boot param?  We've done similar things for _CRS, and it
> > >might give Yinghai and Ram some more flexibility in improving our
> > >dynamic resource allocation before enabling it again (if ever).
> > 
> > I'm OK with that, but then I'd suggest against the currently not yet merged series that doesn't seem to work anyway...
> > 
> > IOW, just a simple patch that disables the resource re-allocation, and enables it with some command line option.
> 
> Ram or Yinghai, want to come up with something?  (And
> note: pci=bridge_realloc or something would be a lot more descriptive
> than pci=try=2!)
Jesse,

	Will have something your way soon.

RP
--
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