About CPU cores numbering an processor affinity

2013-08-23 Thread Dmitry Sivachenko 
Hello!

I am using FreeBSD-9-STABLE on the following hardware:

FreeBSD/SMP: Multiprocessor System Detected: 24 CPUs
FreeBSD/SMP: 2 package(s) x 6 core(s) x 2 SMT threads

So I have 2 physical CPUs with 6 core each.

# cpuset -g
pid -1 mask: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 
19, 20, 21, 22, 23


So each of 24 cores are numbered 0..23.

1) In what particular order are these cores numbered?  Can I assume that 0..11 
correspond to 1st physical CPU and 12..23 to second?  How SMT threads are 
numbered within each core?

2) This machine has Intel network adapter (em driver).  I want to pin network 
interrupt thread and proxy software to the same processor so they share at 
least L2 or L3 cache.  How can I do this?  From the one hand, I see the 
following processes:

   11 root -92- 0K   720K WAIT   19 146:38  0.00% intr{irq260: 
em1:rx 0}
   11 root -92- 0K   720K WAIT   19  15:11  0.00% intr{irq261: 
em1:tx 0}

From the other hand, the following processes seems to be unrelated to network 
but they share same PID:
   11 root -60- 0K   720K WAIT1 131:20  0.00% intr{swi4: 
clock}
   11 root -88- 0K   720K WAIT   17  40:03  0.00% intr{irq263: 
ahci0}
   11 root -72- 0K   720K WAIT   22  17:35  0.00% intr{swi1: 
netisr 0}
   11 root -88- 0K   720K WAIT3   3:08  0.00% intr{irq256: 
mfi0}

Should I use -x option of cpuset for that purpose (to bind irq 260 and 261 in 
my example)?

Thanks in advance!

___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org

Re: weekly periodic security status

2013-08-23 Thread Darren Pilgrim 
Thank you for this, but if I may make one suggestion: don't combine all 
the security report settings--keep both daily_* and weekly_*.  This 
makes possible running some security tasks on a daily basis and others 
on a weekly basis.  For example, daily pkg/portaudit checks, but weekly 
filesystem scans.

___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org

mpx on laptop produces pointer but does not show usb mouse

2013-08-23 Thread Super Bisquit 
Says right there.

http://alec.mooo.com/mpx.html
Followed the instructions in the link.
Second part will have more info.

Thanks much and apologies.
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org

Re: weekly periodic security status

2013-08-23 Thread Royce Williams 
On Fri, Aug 23, 2013 at 10:44 AM, Darren Pilgrim 
list_free...@bluerosetech.com wrote:

 Thank you for this, but if I may make one suggestion: don't combine all
 the security report settings--keep both daily_* and weekly_*.  This makes
 possible running some security tasks on a daily basis and others on a
 weekly basis.  For example, daily pkg/portaudit checks, but weekly
 filesystem scans.


Agreed.  I welcome and would use the weekly option at this level of
granularity, but would like to retain daily for many checks, and so would
not use weekly if was an all-or-nothing option.

Royce
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org