Re: [PATCH 4 of 53] ipath - cap number of PDs that can be allocated

 > Put an arbitrary cap on the maximum number of PDs that can be allocated
 > for a device.  This is arbitrary because the number we support
 > is constrained only by system memory and what kmalloc can give us.
 > Nevertheless, if we don't have a limit, some third-party  OpenIB stress
 > tests fail.  The limit can be changed on the fly using a module parameter.

Would it make more sense to fix the stress test?

 - R.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Follow-Ups:
- Re: [PATCH 4 of 53] ipath - cap number of PDs that can be allocated
  - From: "Bryan O'Sullivan" <[email protected]>

References:
- [PATCH 4 of 53] ipath - cap number of PDs that can be allocated
  - From: "Bryan O'Sullivan" <[email protected]>

Prev by Date: Re: mcelog ?
Next by Date: Re: Assorted bugs in the PIIX drivers
Previous by thread: [PATCH 4 of 53] ipath - cap number of PDs that can be allocated
Next by thread: Re: [PATCH 4 of 53] ipath - cap number of PDs that can be allocated
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]