[ 
https://issues.apache.org/jira/browse/TS-4806?focusedWorklogId=28090&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-28090
 ]

ASF GitHub Bot logged work on TS-4806:
--------------------------------------

                Author: ASF GitHub Bot
            Created on: 05/Sep/16 00:38
            Start Date: 05/Sep/16 00:38
    Worklog Time Spent: 10m 
      Work Description: Github user PSUdaemon commented on a diff in the pull 
request:

    https://github.com/apache/trafficserver/pull/956#discussion_r77461718
  
    --- Diff: iocore/eventsystem/UnixEventProcessor.cc ---
    @@ -152,6 +155,59 @@ EventProcessor::start(int n_event_threads, size_t 
stacksize)
     #else
           Debug("iocore_thread", "EThread: %d %s: %d", i, obj_name, 
obj->logical_index);
     #endif // HWLOC_API_VERSION
    +    }
    +#endif // TS_USE_HWLOC
    +
    +    snprintf(thr_name, MAX_THREAD_NAME_LENGTH, "[ET_NET %d]", i);
    +#if TS_USE_HWLOC
    +    if (obj_count > 0) {
    --- End diff --
    
    It can be, and it's basically an error case from HWLOC in that it couldn't 
figure out your topology. If you pass a `NULL`stack it just allocates the way 
it did before, which is to leave it up to the OS.


Issue Time Tracking
-------------------

    Worklog Id:     (was: 28090)
    Time Spent: 2h 50m  (was: 2h 40m)

> Fix up event processor thread stacks
> ------------------------------------
>
>                 Key: TS-4806
>                 URL: https://issues.apache.org/jira/browse/TS-4806
>             Project: Traffic Server
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Phil Sorber
>            Assignee: Phil Sorber
>             Fix For: 7.0.0
>
>          Time Spent: 2h 50m
>  Remaining Estimate: 0h
>
> Fix event processor to create stacks on the appropriate numa node and with 
> the appropriate page size. Also, stop using the main thread as ET_NET 0 since 
> we can't control any of these aspects of it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to