qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: Mauro Matteo Cascella <mcascell@redhat.com>
Cc: Dmitry Fleytman <dmitry.fleytman@gmail.com>,
	QEMU Developers <qemu-devel@nongnu.org>,
	ziming zhang <ezrakiez@gmail.com>
Subject: Re: [PATCH 1/2] hw/net/net_tx_pkt: add function to check pkt->max_raw_frags
Date: Thu, 30 Jul 2020 13:27:51 +0800	[thread overview]
Message-ID: <3672bcc5-329f-0cc6-a505-e5b21a316a20@redhat.com> (raw)
In-Reply-To: <CAA8xKjXagrLU+DVcO3uVw6D0sJHXQ_rOd0nqEHHNcaMwG6oXRA@mail.gmail.com>


On 2020/7/29 上午12:26, Mauro Matteo Cascella wrote:
> On Tue, Jul 28, 2020 at 6:06 AM Jason Wang <jasowang@redhat.com> wrote:
>>
>> On 2020/7/28 上午1:08, Mauro Matteo Cascella wrote:
>>> This patch introduces a new function in hw/net/net_tx_pkt.{c,h} to check the
>>> current data fragment against the maximum number of data fragments.
>>
>> I wonder whether it's better to do the check in
>> net_tx_pkt_add_raw_fragment() and fail there.
> Given the assertion, I assumed the caller is responsible for the
> check, but moving the check in net_tx_pkt_add_raw_fragment() totally
> makes sense to me.


Want to send a new version for this?


>
>> Btw, I find net_tx_pkt_add_raw_fragment() does not unmap dma when
>> returning to true, is this a bug?
> Isn't it unmapped in net_tx_pkt_reset()?


Probably but see how it was used in e1000e, the net_tx_pkt_reset() is 
only called when eop is set. Is this a bug?

Thanks

>
>> Thanks
>>
>>
>>> Reported-by: Ziming Zhang <ezrakiez@gmail.com>
>>> Signed-off-by: Mauro Matteo Cascella <mcascell@redhat.com>
>>> ---
>>>    hw/net/net_tx_pkt.c | 5 +++++
>>>    hw/net/net_tx_pkt.h | 8 ++++++++
>>>    2 files changed, 13 insertions(+)
>>>
>>> diff --git a/hw/net/net_tx_pkt.c b/hw/net/net_tx_pkt.c
>>> index 9560e4a49e..d035618f2c 100644
>>> --- a/hw/net/net_tx_pkt.c
>>> +++ b/hw/net/net_tx_pkt.c
>>> @@ -400,6 +400,11 @@ bool net_tx_pkt_add_raw_fragment(struct NetTxPkt *pkt, hwaddr pa,
>>>        }
>>>    }
>>>
>>> +bool net_tx_pkt_exceed_max_fragments(struct NetTxPkt *pkt)
>>> +{
>>> +    return pkt->raw_frags >= pkt->max_raw_frags;
>>> +}
>>> +
>>>    bool net_tx_pkt_has_fragments(struct NetTxPkt *pkt)
>>>    {
>>>        return pkt->raw_frags > 0;
>>> diff --git a/hw/net/net_tx_pkt.h b/hw/net/net_tx_pkt.h
>>> index 4ec8bbe9bd..e2ee46ae03 100644
>>> --- a/hw/net/net_tx_pkt.h
>>> +++ b/hw/net/net_tx_pkt.h
>>> @@ -179,6 +179,14 @@ bool net_tx_pkt_send_loopback(struct NetTxPkt *pkt, NetClientState *nc);
>>>     */
>>>    bool net_tx_pkt_parse(struct NetTxPkt *pkt);
>>>
>>> +/**
>>> +* indicates if the current data fragment exceeds max_raw_frags
>>> +*
>>> +* @pkt:            packet
>>> +*
>>> +*/
>>> +bool net_tx_pkt_exceed_max_fragments(struct NetTxPkt *pkt);
>>> +
>>>    /**
>>>    * indicates if there are data fragments held by this packet object.
>>>    *



  reply	other threads:[~2020-07-30  5:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-27 17:08 [PATCH 0/2] assertion failure in net_tx_pkt_add_raw_fragment() in hw/net/net_tx_pkt.c Mauro Matteo Cascella
2020-07-27 17:08 ` [PATCH 1/2] hw/net/net_tx_pkt: add function to check pkt->max_raw_frags Mauro Matteo Cascella
2020-07-28  4:06   ` Jason Wang
2020-07-28 16:26     ` Mauro Matteo Cascella
2020-07-30  5:27       ` Jason Wang [this message]
2020-07-30 17:05         ` Mauro Matteo Cascella
2020-07-31  3:33           ` Jason Wang
2020-07-27 17:08 ` [PATCH 2/2] hw/net: check max_raw_frags in e1000e and vmxnet3 devices Mauro Matteo Cascella
2020-07-27 17:29 ` [PATCH 0/2] assertion failure in net_tx_pkt_add_raw_fragment() in hw/net/net_tx_pkt.c Alexander Bulekov
2020-07-28 16:59   ` Mauro Matteo Cascella
2020-07-29  8:48   ` Dmitry Fleytman

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=3672bcc5-329f-0cc6-a505-e5b21a316a20@redhat.com \
    --to=jasowang@redhat.com \
    --cc=dmitry.fleytman@gmail.com \
    --cc=ezrakiez@gmail.com \
    --cc=mcascell@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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).