From: Naruto Nguyen <narutonguyen2018@gmail.com>
To: kernel derkeiler <linux-kernel@vger.kernel.org>,
kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: Small MSS in vmxnet3
Date: Mon, 25 Sep 2023 20:57:11 +1000 [thread overview]
Message-ID: <CANpxKHEDD+fjQiH=DrHPWTm6CMkT78Tcbk2sVfPydO9+M2-FQA@mail.gmail.com> (raw)
In-Reply-To: <CANpxKHHzre03bFfW_UpJy1W40oFa6Q6x688WrCXKtNeqkeVk7Q@mail.gmail.com>
Hello,
could you please let me know any ideas?
Thank you,
Kind regards,
Bao
On Sat, 23 Sept 2023 at 12:12, Naruto Nguyen <narutonguyen2018@gmail.com> wrote:
>
> Hello everyone,
>
> Recently I found that packets sent from vmxnet3 driver on guest have
> MSS value set to very small size, some 10 bytes, some 25 bytes MSS.
> The vmxnet3 NIC enables TSO. Could you let me know any possible reason
> that the packets are fragmented with very small MSS.and is it normal?.
> Any way to avoid this small MSS or it's just normal.
>
> In addition, when enabling debug for vmxnet3, in function
> vmxnet3_tq_xmit, it has a printout
>
> netdev_dbg(adapter->netdev,
> "txd[%u]: SOP 0x%Lx 0x%x 0x%x\n",
> (u32)(ctx.sop_txd -
> tq->tx_ring.base), le64_to_cpu(gdesc->txd.addr),
> le32_to_cpu(gdesc->dword[2]), le32_to_cpu(gdesc->dword[3]));
>
> could you suggest an easier way to extract the MSS value from this output?
>
> Thanks,
> Kind regards, Naruto
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
prev parent reply other threads:[~2023-09-25 10:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-23 2:12 Small MSS in vmxnet3 Naruto Nguyen
2023-09-25 10:57 ` Naruto Nguyen [this message]
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='CANpxKHEDD+fjQiH=DrHPWTm6CMkT78Tcbk2sVfPydO9+M2-FQA@mail.gmail.com' \
--to=narutonguyen2018@gmail.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=linux-kernel@vger.kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).