Project

General

Profile

Actions

Bug #5881

closed

taskq.c: maxall vs. maxalloc in comments

Added by Marcel Telka over 6 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Low
Assignee:
Category:
kernel
Start date:
2015-04-30
Due date:
% Done:

100%

Estimated time:
Difficulty:
Bite-size
Tags:
needs-triage
Gerrit CR:

Description

Here in usr/src/uts/common/os/taskq.c the 'maxall' should be changed to 'maxalloc' to avoid confusion:

81 * taskq_t *taskq_create(name, nthreads, pri, minalloc, maxall, flags);

...

131 *    maxall, flags);

...

136 * taskq_t *taskq_create_proc(name, nthreads, pri, minalloc, maxall, proc,

...

143 * taskq_t *taskq_create_sysdc(name, nthreads, minalloc, maxall, proc,
Actions #1

Updated by Marcel Telka over 6 years ago

  • Subject changed from taskq.c: maxall vs maxalloc in comments to taskq.c: maxall vs. maxalloc in comments
Actions #2

Updated by Sergio Aguayo over 6 years ago

  • Status changed from New to Pending RTI
  • Assignee set to Sergio Aguayo
Actions #3

Updated by Electric Monk over 6 years ago

  • Status changed from Pending RTI to Closed
  • % Done changed from 0 to 100

git commit a676a7c97415355daa312ec065acc852a3286e00

commit  a676a7c97415355daa312ec065acc852a3286e00
Author: Sergio Aguayo <sergioag@qmailhosting.net>
Date:   2015-06-01T14:39:43.000Z

    5881 taskq.c: maxall vs. maxalloc in comments
    Reviewed by: Robert Mustacchi <rm@joyent.com>
    Reviewed by: Garrett D'Amore <garrett@damore.org>
    Approved by: Dan McDonald <danmcd@omniti.com>

Actions

Also available in: Atom PDF