asomers d4f614fd9c Remove artificial restriction on lio_listio's operation count
In r322258 I made p1003_1b.aio_listio_max a tunable. However, further
investigation shows that there was never any good reason for that limit to
exist in the first place. It's used in two completely different ways:

* To size a UMA zone, which globally limits the number of concurrent
  aio_suspend calls.

* To artifically limit the number of operations in a single lio_listio call.
  There doesn't seem to be any memory allocation associated with this limit.

This change does two things:

* Properly names aio_suspend's UMA zone, and sizes it based on a new constant.

* Eliminates the artifical restriction on lio_listio. Instead, lio_listio
  calls will now be limited by the more generous max_aio_queue_per_proc. The
  old p1003_1b.aio_listio_max is now an alias for
  vfs.aio.max_aio_queue_per_proc, so sysconf(3) will still work with
  _SC_AIO_LISTIO_MAX.

Reported by:	bde
Reviewed by:	jhb
MFC after:	3 weeks
Sponsored by:	Spectra Logic Corp
Differential Revision:	https://reviews.freebsd.org/D12120
2017-10-23 23:12:01 +00:00
..
2017-10-12 15:48:37 +00:00
2017-05-23 09:29:05 +00:00
2016-11-08 23:59:41 +00:00
2017-05-18 18:24:11 +00:00
2017-08-15 02:21:02 +00:00
2017-02-12 09:49:44 +00:00
2017-01-25 20:22:32 +00:00
2017-05-23 16:59:24 +00:00
2017-02-14 13:54:05 +00:00
2017-03-19 00:51:12 +00:00
2017-08-07 14:09:57 +00:00
2016-11-08 23:59:41 +00:00
2017-10-22 13:42:56 +00:00
2017-02-07 16:01:07 +00:00
2017-07-12 07:30:14 +00:00
2017-05-16 23:31:52 +00:00
2017-06-17 00:58:19 +00:00
2017-06-17 00:58:19 +00:00
2017-05-23 09:29:05 +00:00
2017-05-23 09:29:05 +00:00
2017-06-08 21:30:34 +00:00
2017-06-15 04:49:12 +00:00
2017-10-16 21:46:11 +00:00
2017-09-14 18:05:54 +00:00
2017-10-06 09:02:36 +00:00