From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Ye Xiaolong <xiaolong.ye@intel.com>
Cc: dev@dpdk.org, ybrustin@cisco.com, tiwei.bie@intel.com,
jfreimann@redhat.com, david.marchand@redhat.com, stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v3 4/4] net/virtio: remove useless pointers checks
Date: Thu, 6 Jun 2019 09:31:39 +0200 [thread overview]
Message-ID: <0fd1b580-b1cf-4005-b4fc-69e1f2ef1700@redhat.com> (raw)
In-Reply-To: <20190606071537.GA14480@intel.com>
On 6/6/19 9:15 AM, Ye Xiaolong wrote:
> On 06/05, Maxime Coquelin wrote:
>> This patch removes uses checks on 'prev' pointer, as it
>
> s/uses/useless/
Thanks, will fix while applying.
Maxime
>> is always set before with a valid value.
>>
>> Reviewed-by: David Marchand <david.marchand@redhat.com>
>> Signed-off-by: Maxime Coquelin <maxime.coquelin@redhat.com>
>> ---
>> drivers/net/virtio/virtio_rxtx.c | 15 ++++-----------
>> 1 file changed, 4 insertions(+), 11 deletions(-)
>>
>> diff --git a/drivers/net/virtio/virtio_rxtx.c b/drivers/net/virtio/virtio_rxtx.c
>> index 358cc86627..ca40ba9c5d 100644
>> --- a/drivers/net/virtio/virtio_rxtx.c
>> +++ b/drivers/net/virtio/virtio_rxtx.c
>> @@ -1517,9 +1517,7 @@ virtio_recv_pkts_inorder(void *rx_queue,
>>
>> rx_pkts[nb_rx]->pkt_len += (uint32_t)(len[i]);
>>
>> - if (prev)
>> - prev->next = rxm;
>> -
>> + prev->next = rxm;
>> prev = rxm;
>> seg_res -= 1;
>> }
>> @@ -1701,9 +1699,7 @@ virtio_recv_mergeable_pkts(void *rx_queue,
>>
>> rx_pkts[nb_rx]->pkt_len += (uint32_t)(len[i]);
>>
>> - if (prev)
>> - prev->next = rxm;
>> -
>> + prev->next = rxm;
>> prev = rxm;
>> seg_res -= 1;
>> }
>> @@ -1876,9 +1872,7 @@ virtio_recv_mergeable_pkts_packed(void *rx_queue,
>>
>> rx_pkts[nb_rx]->pkt_len += (uint32_t)(len[i]);
>>
>> - if (prev)
>> - prev->next = rxm;
>> -
>> + prev->next = rxm;
>> prev = rxm;
>> seg_res -= 1;
>> }
>> @@ -1921,8 +1915,7 @@ virtio_recv_mergeable_pkts_packed(void *rx_queue,
>> } else {
>> PMD_RX_LOG(ERR,
>> "No enough segments for packet.");
>> - if (prev)
>> - virtio_discard_rxbuf(vq, prev);
>> + virtio_discard_rxbuf(vq, prev);
>> rxvq->stats.errors++;
>> break;
>> }
>> --
>> 2.21.0
>>
next prev parent reply other threads:[~2019-06-06 7:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 10:00 [dpdk-dev] [PATCH v3 0/4] et/virtio: Fix packet segmentation bug Maxime Coquelin
2019-06-05 10:00 ` [dpdk-dev] [PATCH v3 1/4] net/virtio: fix segmented packet issue in in-order Rx path Maxime Coquelin
2019-06-05 10:00 ` [dpdk-dev] [PATCH v3 2/4] net/virtio: fix segmented packet issue in mergeable " Maxime Coquelin
2019-06-05 10:00 ` [dpdk-dev] [PATCH v3 3/4] net/virtio: fix segment data len in mergeable packed " Maxime Coquelin
2019-06-05 11:16 ` Jens Freimann
2019-06-05 11:34 ` Maxime Coquelin
2019-06-05 10:00 ` [dpdk-dev] [PATCH v3 4/4] net/virtio: remove useless pointers checks Maxime Coquelin
2019-06-06 7:15 ` Ye Xiaolong
2019-06-06 7:31 ` Maxime Coquelin [this message]
2019-06-05 13:25 ` [dpdk-dev] [PATCH v3 0/4] et/virtio: Fix packet segmentation bug Tiwei Bie
2019-06-06 9:31 ` Maxime Coquelin
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=0fd1b580-b1cf-4005-b4fc-69e1f2ef1700@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=jfreimann@redhat.com \
--cc=stable@dpdk.org \
--cc=tiwei.bie@intel.com \
--cc=xiaolong.ye@intel.com \
--cc=ybrustin@cisco.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).