From: "Liu, Yong" <yong.liu@intel.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>,
"Bie, Tiwei" <tiwei.bie@intel.com>
Cc: "Wang, Zhihong" <zhihong.wang@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2 7/8] net/virtio: add IN_ORDER Rx/Tx into selection
Date: Thu, 28 Jun 2018 14:11:34 +0000 [thread overview]
Message-ID: <86228AFD5BCD8E4EBFD2B90117B5E81E630CD909@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <83ce85c8-5eee-90d5-bd3a-de0912b4ba92@redhat.com>
> -----Original Message-----
> From: Maxime Coquelin [mailto:maxime.coquelin@redhat.com]
> Sent: Wednesday, June 27, 2018 4:20 PM
> To: Liu, Yong <yong.liu@intel.com>; Bie, Tiwei <tiwei.bie@intel.com>
> Cc: Wang, Zhihong <zhihong.wang@intel.com>; dev@dpdk.org
> Subject: Re: [PATCH v2 7/8] net/virtio: add IN_ORDER Rx/Tx into selection
>
>
>
> On 06/25/2018 05:17 PM, Marvin Liu wrote:
> > After IN_ORDER Rx/Tx paths added, need to update Rx/Tx path selection
> > logic.
> >
> > Rx path select logic: If IN_ORDER is disabled will select normal Rx
> > path. If IN_ORDER is enabled, Rx offload and merge-able are disabled
> > will select simple Rx path. Otherwise will select IN_ORDER Rx path.
> >
> > Tx path select logic: If IN_ORDER is disabled will select normal Tx
> > path. If IN_ORDER is enabled and merge-able is disabled will select
> > simple Tx path. Otherwise will select IN_ORDER Tx path.
> >
> > Signed-off-by: Marvin Liu <yong.liu@intel.com>
> >
> > diff --git a/drivers/net/virtio/virtio_ethdev.c
> b/drivers/net/virtio/virtio_ethdev.c
> > index df50a571a..f48a84a11 100644
> > --- a/drivers/net/virtio/virtio_ethdev.c
> > +++ b/drivers/net/virtio/virtio_ethdev.c
> > @@ -1320,6 +1320,11 @@ set_rxtx_funcs(struct rte_eth_dev *eth_dev)
> > PMD_INIT_LOG(INFO, "virtio: using simple Rx path on port %u",
> > eth_dev->data->port_id);
> > eth_dev->rx_pkt_burst = virtio_recv_pkts_vec;
> > + } else if (hw->use_inorder_rx) {
> > + PMD_INIT_LOG(INFO,
> > + "virtio: using inorder mergeable buffer Rx path on
> port %u",
> > + eth_dev->data->port_id);
> > + eth_dev->rx_pkt_burst = &virtio_recv_mergeable_pkts_inorder;
> > } else if (vtpci_with_feature(hw, VIRTIO_NET_F_MRG_RXBUF)) {
> > PMD_INIT_LOG(INFO,
> > "virtio: using mergeable buffer Rx path on port %u",
> > @@ -1335,6 +1340,10 @@ set_rxtx_funcs(struct rte_eth_dev *eth_dev)
> > PMD_INIT_LOG(INFO, "virtio: using simple Tx path on port %u",
> > eth_dev->data->port_id);
> > eth_dev->tx_pkt_burst = virtio_xmit_pkts_simple;
> > + } else if (hw->use_inorder_tx) {
> > + PMD_INIT_LOG(INFO, "virtio: using inorder Tx path on port %u",
> > + eth_dev->data->port_id);
> > + eth_dev->tx_pkt_burst = virtio_xmit_pkts_inorder;
> > } else {
> > PMD_INIT_LOG(INFO, "virtio: using standard Tx path on port %u",
> > eth_dev->data->port_id);
> > @@ -1871,23 +1880,25 @@ virtio_dev_configure(struct rte_eth_dev *dev)
> >
> > rte_spinlock_init(&hw->state_lock);
> >
> > - hw->use_simple_rx = 1;
> > - hw->use_simple_tx = 1;
> > -
> > #if defined RTE_ARCH_ARM64 || defined RTE_ARCH_ARM
> > if (!rte_cpu_get_flag_enabled(RTE_CPUFLAG_NEON)) {
> > hw->use_simple_rx = 0;
> > hw->use_simple_tx = 0;
> > }
> > #endif
> > - if (vtpci_with_feature(hw, VIRTIO_NET_F_MRG_RXBUF)) {
> > - hw->use_simple_rx = 0;
> > - hw->use_simple_tx = 0;
> > - }
> > + if (vtpci_with_feature(hw, VIRTIO_F_IN_ORDER)) {
> > + if (vtpci_with_feature(hw, VIRTIO_NET_F_MRG_RXBUF)) {
> > + hw->use_inorder_rx = 1;
> > + hw->use_inorder_tx = 1;
> > + } else {
> > + hw->use_simple_rx = 1;
> > + hw->use_simple_tx = 1;
> > + }
> >
> > - if (rx_offloads & (DEV_RX_OFFLOAD_UDP_CKSUM |
> > - DEV_RX_OFFLOAD_TCP_CKSUM))
> > - hw->use_simple_rx = 0;
> > + if (rx_offloads & (DEV_RX_OFFLOAD_UDP_CKSUM |
> > + DEV_RX_OFFLOAD_TCP_CKSUM))
> > + hw->use_inorder_rx = 1;
> Isn't there a problem here if mrg_rxbuf has been negotiated?
>
That's the problem, has changed selection logic in v3. Thanks for review.
> > + }
> >
> > return 0;
> > }
> >
next prev parent reply other threads:[~2018-06-28 14:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-25 15:17 [dpdk-dev] [PATCH v2 0/8] support VIRTIO_F_IN_ORDER feature Marvin Liu
2018-06-25 15:17 ` [dpdk-dev] [PATCH v2 1/8] vhost: announce VIRTIO_F_IN_ORDER support Marvin Liu
2018-06-26 7:54 ` Maxime Coquelin
2018-06-25 15:17 ` [dpdk-dev] [PATCH v2 2/8] net/virtio: add VIRTIO_F_IN_ORDER definition Marvin Liu
2018-06-26 7:58 ` Maxime Coquelin
2018-06-25 15:17 ` [dpdk-dev] [PATCH v2 3/8] net/virtio-user: add mrg_rxbuf and in_order vdev parameters Marvin Liu
2018-06-27 6:53 ` Maxime Coquelin
2018-06-25 15:17 ` [dpdk-dev] [PATCH v2 4/8] net/virtio: free IN_ORDER descriptors before device start Marvin Liu
2018-06-27 6:58 ` Maxime Coquelin
2018-06-25 15:17 ` [dpdk-dev] [PATCH v2 5/8] net/virtio: extract common part for IN_ORDER functions Marvin Liu
2018-06-27 6:59 ` Maxime Coquelin
2018-06-25 15:17 ` [dpdk-dev] [PATCH v2 6/8] net/virtio: support IN_ORDER Rx and Tx Marvin Liu
2018-06-27 8:18 ` Maxime Coquelin
2018-06-27 14:27 ` Liu, Yong
2018-06-27 14:32 ` Maxime Coquelin
2018-06-25 15:17 ` [dpdk-dev] [PATCH v2 7/8] net/virtio: add IN_ORDER Rx/Tx into selection Marvin Liu
2018-06-27 8:19 ` Maxime Coquelin
2018-06-28 14:11 ` Liu, Yong [this message]
2018-06-25 15:17 ` [dpdk-dev] [PATCH v2 8/8] net/virtio: annouce VIRTIO_F_IN_ORDER support Marvin Liu
2018-06-27 8:20 ` Maxime Coquelin
2018-06-26 7:56 ` [dpdk-dev] [PATCH v2 0/8] support VIRTIO_F_IN_ORDER feature Maxime Coquelin
2018-06-26 8:01 ` Liu, Yong
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=86228AFD5BCD8E4EBFD2B90117B5E81E630CD909@SHSMSX103.ccr.corp.intel.com \
--to=yong.liu@intel.com \
--cc=dev@dpdk.org \
--cc=maxime.coquelin@redhat.com \
--cc=tiwei.bie@intel.com \
--cc=zhihong.wang@intel.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;
as well as URLs for NNTP newsgroup(s).