From: "Michael S. Tsirkin" <mst@redhat.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: Heng Qi <hengqi@linux.alibaba.com>,
virtio-comment@lists.oasis-open.org,
virtio-dev@lists.oasis-open.org, Parav Pandit <parav@nvidia.com>,
Jason Wang <jasowang@redhat.com>,
Yuri Benditovich <yuri.benditovich@daynix.com>,
Xuan Zhuo <xuanzhuo@linux.alibaba.com>
Subject: [virtio-dev] Re: [PATCH v21] virtio-net: support inner header hash
Date: Wed, 12 Jul 2023 08:25:33 -0400 [thread overview]
Message-ID: <20230712082508-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <87pm4xjp4t.fsf@redhat.com>
On Wed, Jul 12, 2023 at 02:22:26PM +0200, Cornelia Huck wrote:
> On Mon, Jul 03 2023, Heng Qi <hengqi@linux.alibaba.com> wrote:
>
> (...)
>
> > +\paragraph{Inner Header Hash}
> > +\label{sec:Device Types / Network Device / Device Operation / Processing of Incoming Packets / Inner Header Hash}
> > +
> > +If VIRTIO_NET_F_HASH_TUNNEL has been negotiated, the driver can send the command
> > +VIRTIO_NET_CTRL_HASH_TUNNEL_SET to configure the calculation of the inner header hash.
> > +
> > +struct virtnet_hash_tunnel {
> > + le32 enabled_tunnel_types;
> > +};
> > +
> > +#define VIRTIO_NET_CTRL_HASH_TUNNEL 7
> > + #define VIRTIO_NET_CTRL_HASH_TUNNEL_SET 0
>
> This needs to be wrapped in \begin{lstlisting}..\end{lstlisting}, can do
> so when applying.
>
> (...)
>
> > +Encapsulation types applicable for inner header hash:
> > +\begin{lstlisting}
> > +#define VIRTIO_NET_HASH_TUNNEL_TYPE_GRE_2784 (1 << 0) /* \hyperref[intro:gre_rfc2784]{[GRE_rfc2784]} */
> > +#define VIRTIO_NET_HASH_TUNNEL_TYPE_GRE_2890 (1 << 1) /* \hyperref[intro:gre_rfc2890]{[GRE_rfc2890]} */
> > +#define VIRTIO_NET_HASH_TUNNEL_TYPE_GRE_7676 (1 << 2) /* \hyperref[intro:gre_rfc7676]{[GRE_rfc7676]} */
> > +#define VIRTIO_NET_HASH_TUNNEL_TYPE_GRE_UDP (1 << 3) /* \hyperref[intro:gre_in_udp_rfc8086]{[GRE-in-UDP]} */
> > +#define VIRTIO_NET_HASH_TUNNEL_TYPE_VXLAN (1 << 4) /* \hyperref[intro:vxlan]{[VXLAN]} */
> > +#define VIRTIO_NET_HASH_TUNNEL_TYPE_VXLAN_GPE (1 << 5) /* \hyperref[intro:vxlan_gpe]{[VXLAN-GPE]} */
> > +#define VIRTIO_NET_HASH_TUNNEL_TYPE_GENEVE (1 << 6) /* \hyperref[intro:geneve]{[GENEVE]} */
> > +#define VIRTIO_NET_HASH_TUNNEL_TYPE_IPIP (1 << 7) /* \hyperref[intro:ipip]{[IPIP]} */
> > +#define VIRTIO_NET_HASH_TUNNEL_TYPE_NVGRE (1 << 8) /* \hyperref[intro:nvgre]{[NVGRE]} */
> > +\end{lstlisting}
>
> I'm afraid this one doesn't come out quite as intended, we'll end up
> with verbatim "\hyperref" text instead of a link. Anyone have a good
> idea on how to fix that?
>
> I'd prefer to push this now with the first issue addressed and to do an
> (editorial) patch on top to deal with the second issue (unless someone
> can come up with a really trivial fix for it, then I can apply that
> straightaway.)
Someone suggested using escapechar:
https://tex.stackexchange.com/questions/314903/inline-links-in-code-listings
Didn't try.
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next prev parent reply other threads:[~2023-07-12 12:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 15:27 [virtio-dev] [PATCH v21] virtio-net: support inner header hash Heng Qi
2023-07-03 15:47 ` [virtio-dev] " Michael S. Tsirkin
2023-07-04 6:56 ` Cornelia Huck
2023-07-12 12:22 ` Cornelia Huck
2023-07-12 12:25 ` Michael S. Tsirkin [this message]
2023-07-12 12:42 ` Cornelia Huck
2023-07-12 12:59 ` [virtio-dev] Re: [virtio-comment] " Heng Qi
2023-07-12 13:25 ` Cornelia Huck
2023-07-12 14:54 ` Heng Qi
2023-07-12 15:23 ` [virtio-dev] Re: [virtio-comment] " Cornelia Huck
2023-07-12 16:52 ` [virtio-dev] " Parav Pandit
2023-07-12 22:28 ` Parav Pandit
2023-07-12 22:31 ` [virtio-dev] " Michael S. Tsirkin
2023-07-12 22:35 ` [virtio-dev] " Parav Pandit
2023-07-13 6:40 ` [virtio-dev] " Heng Qi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230712082508-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=cohuck@redhat.com \
--cc=hengqi@linux.alibaba.com \
--cc=jasowang@redhat.com \
--cc=parav@nvidia.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio-dev@lists.oasis-open.org \
--cc=xuanzhuo@linux.alibaba.com \
--cc=yuri.benditovich@daynix.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox