On Tue, Jul 24, 2012 at 10:08:13PM +0100, David Chisnall wrote:
> On 23 Jul 2012, at 20:53, David Chisnall wrote:
>
> > On 23 Jul 2012, at 20:18, Konstantin Belousov wrote:
> >
> >> Longer description is that pc_curthread is offset 0 if %gs-based.
> >> The dereferenced pointer point to the struct
Interesting, lem is all the non-pcie hardware, and if you see better
performance
out of the LEGACY path then I'm OK with changing the default.
Jack
On Tue, Jul 24, 2012 at 1:20 PM, Luigi Rizzo wrote:
> if_lem.c ("lem", one of the e1000 drivers) has 2 possible interrupt modes:
> EM_LEGACY_IRQ u
On 23 Jul 2012, at 20:53, David Chisnall wrote:
> On 23 Jul 2012, at 20:18, Konstantin Belousov wrote:
>
>> Longer description is that pc_curthread is offset 0 if %gs-based.
>> The dereferenced pointer point to the struct thread, which contains
>> td_proc pointer at offset 8. Instead, clang seems
if_lem.c ("lem", one of the e1000 drivers) has 2 possible interrupt modes:
EM_LEGACY_IRQ uses the standard dispatch mechanism, whereas
FAST_INTR has a custom handler that signals a taskqueue to do the job.
I have no idea which actual hardware uses it (all of my Intel 1G
cards use either "em" or "i
TB --- 2012-07-24 18:30:00 - tinderbox 2.9 running on freebsd-current.sentex.ca
TB --- 2012-07-24 18:30:00 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2012-
On Mon, Jul 23, 2012 at 12:45:14AM -0700, Julian Elischer wrote:
> On 7/22/12 9:11 PM, Warner Losh wrote:
> >On Jul 22, 2012, at 9:12 PM, Alexander Kabaev wrote:
> >
> >>On Sun, 22 Jul 2012 20:22:33 -0600
> >>Scott Long wrote:
> >>
> >>>On Jul 20, 2012, at 8:04 PM, Julian Elischer wrote:
> >>>
> >
