* Re: [2.4.20] e1000 as module gives unresolved symbol _mmx_memcpy [rescued]
@ 2003-01-10 18:38 Alan Cox
0 siblings, 0 replies; only message in thread
From: Alan Cox @ 2003-01-10 18:38 UTC (permalink / raw)
To: 1042211459.2706.9.camel; +Cc: Linux Kernel Mailing List
> a) a kernel build for a VIA C3 doesn't use MMX, userspace programs can
> still use it
Basically true. It might be instructive to do more benching on this with
the C3 and MMX especially if the new cores add full prefetch stuff
> b) Both kernel and userspace can't use MMX any more
MMX is designed to need no OS support. SSE/SSE2 do need OS helpers but
not MMX.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2003-01-10 18:39 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-01-10 18:38 [2.4.20] e1000 as module gives unresolved symbol _mmx_memcpy [rescued] Alan Cox
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.