Displaying 4 results from an estimated 4 matches for "hree".
Did you mean:
free
2009 Mar 23
0
[LLVMdev] X86InstrFormats.td Question
On Mar 23, 2009, at 12:57 PM, David A. Greene wrote:
> I'm looking at the instruction formats and I can't grok the
> comments. For
> example:
>
> // SSSE3 Instruction Templates:
> //
> // SS38I - SSSE3 instructions with T8 prefix.
> // SS3AI - SSSE3 instructions with TA prefix.
> //
>
> Where are these prefix names coming from? I can't find any
2012 Jun 26
0
[rfc] virtio-spec: introduce VIRTIO_NET_F_MULTIQUEUE
...93017
+VIRTIO_NET_F_MULTIQUEUE (22) Device has multiple tx/rx queues.
+\change_unchanged
+
\end_layout
\end_deeper
@@ -4039,11 +4112,22 @@ configuration
\begin_inset space ~
\end_inset
-layout Two configuration fields are currently defined.
+layout T
+\change_inserted 2090695081 1340693345
+hree
+\change_deleted 2090695081 1340693344
+wo
+\change_unchanged
+ configuration fields are currently defined.
The mac address field always exists (though is only valid if VIRTIO_NET_F_MAC
is set), and the status field only exists if VIRTIO_NET_F_STATUS is set.
Two read-only bits are currently d...
2012 Jun 26
0
[rfc] virtio-spec: introduce VIRTIO_NET_F_MULTIQUEUE
...93017
+VIRTIO_NET_F_MULTIQUEUE (22) Device has multiple tx/rx queues.
+\change_unchanged
+
\end_layout
\end_deeper
@@ -4039,11 +4112,22 @@ configuration
\begin_inset space ~
\end_inset
-layout Two configuration fields are currently defined.
+layout T
+\change_inserted 2090695081 1340693345
+hree
+\change_deleted 2090695081 1340693344
+wo
+\change_unchanged
+ configuration fields are currently defined.
The mac address field always exists (though is only valid if VIRTIO_NET_F_MAC
is set), and the status field only exists if VIRTIO_NET_F_STATUS is set.
Two read-only bits are currently d...
2009 Mar 23
2
[LLVMdev] X86InstrFormats.td Question
I'm looking at the instruction formats and I can't grok the comments. For
example:
// SSSE3 Instruction Templates:
//
// SS38I - SSSE3 instructions with T8 prefix.
// SS3AI - SSSE3 instructions with TA prefix.
//
Where are these prefix names coming from? I can't find any mention of them in
the Intel literature.
Also, there's this curious table:
// Prefix byte classes