From: "Freddy" <freddy@asix.com.tw>
To: "'Daniel J Blueman'" <daniel@quora.org>
Cc: "'Linux Kernel'" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH, resubmit] ax88179_178a: ASIX AX88179_178A USB 3.0/2.0 to gigabit ethernet adapter driver
Date: Wed, 4 Dec 2013 20:48:24 +0800 [thread overview]
Message-ID: <002901cef0ef$1f4a0e00$5dde2a00$@asix.com.tw> (raw)
In-Reply-To: <CAMVG2suXHz2ZhikrTa0j3gFc+_c7rdu0qFrXD3sve9JwfyzFAQ@mail.gmail.com>
-----Original Message-----
From: Daniel J Blueman [mailto:daniel@quora.org]
Sent: Sunday, February 03, 2013 10:22 PM
To: Freddy Xin
Cc: Linux Kernel
Subject: Re: [PATCH, resubmit] ax88179_178a: ASIX AX88179_178A USB 3.0/2.0
to gigabit ethernet adapter driver
> Hi Freddy,
> Michael, could you give me more information about how do you test this
driver?
> I have tried to reproduce the issue by using "ifconfig ethX mtu 1500", but
I didn't confront the same issue.
> Thank you in advance for your help.
> I found the same by just starting with 'ifconfig eth0 1500' and testing as
high as 4000; pinging another host with a large payload of size mtu-40
starts failing; after ~30s, I see the transmit time out trace [1].
> Of course, a default MTU size of 1500 is essential to avoid fragmentation
issues, so should be fixed too. Jumbo frames support is essential these days
too.
Hi Daniel,
The default MTU size will be change to 1500 and the HW jumbo frame function
will be enabled in the next submission of the driver.
Thanks for your help.
Freddy
next prev parent reply other threads:[~2013-02-04 12:48 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-03 14:21 [PATCH, resubmit] ax88179_178a: ASIX AX88179_178A USB 3.0/2.0 to gigabit ethernet adapter driver Daniel J Blueman
2013-12-04 12:48 ` Freddy [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-03-02 10:41 [PATCH " Freddy Xin
2013-03-03 6:44 ` David Miller
2013-02-27 12:01 Freddy Xin
2013-03-01 21:15 ` David Miller
2013-02-07 13:39 [PATCH, " Freddy Xin
2013-02-07 20:02 ` Ben Hutchings
2013-02-07 20:05 ` David Miller
2013-02-08 3:41 ` Freddy
2013-02-08 10:23 ` David Laight
2013-02-08 19:23 ` David Miller
2013-02-07 4:36 Freddy Xin
2013-02-07 5:45 ` Stephen Hemminger
2013-02-07 6:45 ` Freddy
2013-02-07 5:46 ` Stephen Hemminger
2013-02-07 6:50 ` Freddy
2013-01-23 2:32 Freddy Xin
2013-01-23 4:15 ` David Miller
2013-01-26 23:13 ` Michael Leun
2013-01-28 9:07 ` Bjørn Mork
2013-01-28 13:36 ` Freddy
2013-01-28 14:24 ` Bjørn Mork
2013-01-28 16:42 ` Michael Leun
2013-01-17 9:32 Freddy Xin
2013-01-18 19:23 ` David Miller
2013-01-18 20:29 ` Alan Stern
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='002901cef0ef$1f4a0e00$5dde2a00$@asix.com.tw' \
--to=freddy@asix.com.tw \
--cc=daniel@quora.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 NNTP newsgroup(s).