Is there any way to map the qla2xxx_x_dpc or lpfc_worker_x threads back to specific adapters?

Solution Verified - Updated -

Issue

  • Is there any way to map the qla2xxx_x_dpc or lpfc_worker_x threads back to specific adapters or are all threads shared among all adapters.

System with 8 lpfc ports

drwxr-xr-x 3 root root 0 Jul 22 01:08 host2
drwxr-xr-x 3 root root 0 Jul 22 01:08 host3
drwxr-xr-x 3 root root 0 Jul 22 01:08 host4
drwxr-xr-x 3 root root 0 Jul 22 01:08 host5
drwxr-xr-x 3 root root 0 Jul 22 01:08 host6
drwxr-xr-x 3 root root 0 Jul 22 01:08 host7
drwxr-xr-x 3 root root 0 Jul 22 01:08 host8
drwxr-xr-x 3 root root 0 Jul 22 01:08 host9

$ ps -ef |grep lpfc
root      2541  1161  0 Jul21 ?        00:00:00 [lpfc_worker_0]
root      2546  1161  0 Jul21 ?        00:00:00 [lpfc_worker_1]
root      2551  1161  0 Jul21 ?        00:00:00 [lpfc_worker_2]
root      2556  1161  0 Jul21 ?        00:00:00 [lpfc_worker_3]
root      2561  1161  0 Jul21 ?        00:00:00 [lpfc_worker_4]
root      2566  1161  0 Jul21 ?        00:00:00 [lpfc_worker_5]
root      2571  1161  0 Jul21 ?        00:00:00 [lpfc_worker_6]
root      2576  1161  0 Jul21 ?        00:00:00 [lpfc_worker_7]

would thread 1 map to host2? Looking at specific NUMA placement and bindings of kernel threads to specific CPUs. Would like to taskset the kernel threads to the same socket that is handling the interrupts for the card.

Environment

  • Red Hat Enterprise Linux (RHEL) 6.5

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content