From: figo zhang <figo1802@gmail.com>
To: Yegor Yefremov <yegorslists@googlemail.com>
Cc: Dick Hollenbeck <dick@softplc.com>,
netdev@vger.kernel.org, zealcook@gmail.com
Subject: Re: KS8695: possible NAPI issue
Date: Tue, 9 Mar 2010 09:50:29 +0800 [thread overview]
Message-ID: <c6ed1ac51003081750v19f9d5fuf07ad0cc2478005d@mail.gmail.com> (raw)
In-Reply-To: <f69abfc31003080611xde6fe26v150dd1fa90b82928@mail.gmail.com>
2010/3/8 Yegor Yefremov <yegorslists@googlemail.com>:
> This is ping afterwards:
>
> debian:~# ping -c 1 192.168.1.38
>
> PING 192.168.1.38 (192.168.1.38) 56(84) bytes of data.
>
>
> tx ram addr = c371c202 , data len = 62
>
> dst:00:18:f3:fe:84:84 src:00:04:d9:80:94:cd type: 0x0800
=> the print info is not clear, it had better just keep "print_mem()",
and remove other printk.
>
> 0xc371c20e : 45 00
>
> 0xc371c212 : 00 54 00 00 40 00 40 01 b6 f0 c0 a8 01 42 c0 a8
>
> 0xc371c222 : 01 26 08 00 65 51 1a 07 00 01 92 00 95 4b 5f 57
>
> 0xc371c232 : 07 00 08 09 0a 0b 0c 0d 0e 0f 10 11 12 13 14 15
>
> 0xc371c242 : 16 17 18 19 1a 1b 1c 1d 1e 1f 20 21 22 23 24 25
>
> 0xc371c252 : 26 27 28 29 2a 2b 2c 2d 2e 2f 30 31 32 33 34 35
>
> 0xc371c262 : 36 37
>
>
>
> tx ram addr = c371c202 , data len = 2a
>
> dst:00:18:f3:fe:84:84 src:00:04:d9:80:94:cd type: 0x0806
>
> 0xc371c20e : 00 01
>
> 0xc371c212 : 08 00 06 04 00 01 00 04 d9 80 94 cd c0 a8 01 42
=> it is a send arp packet, "c0 a8 01 42" is your curr ip addr
192.168.1.66, tell the other side it's ip addr.
>
> 0xc371c222 : 00 00 00 00 00 00 c0 a8 01 26
>
>
>
> rx ram addr = c35d2020 , data len = 3c
>
> dst:00:04:d9:80:94:cd src:00:18:f3:fe:84:84 type: 0x0806
>
> 0xc35d202c : 00 01
>
> 0xc35d2030 : 08 00 06 04 00 02 00 18 f3 fe 84 84 c0 a8 01 26
=> it is a reply arp packet, "c0 a8 01 26" (192.168.1.38 ) is other
side ip addr. so the arp
request is finished.
>
> 0xc35d2040 : 00 04 d9 80 94 cd c0 a8 01 42 00 00 00 00 00 00
>
> 0xc35d2050 : 00 00 00 00 00 00 00 00 00 00 00 00
>
=> so , it should still send "IMCP" packet, you using "ping -c 1", it
send one IMCP packet , and wait for reply. at this point, it have not
send packet?
next prev parent reply other threads:[~2010-03-09 1:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-02 12:04 KS8695: possible NAPI issue Yegor Yefremov
2010-03-02 14:09 ` Dick Hollenbeck
2010-03-03 1:46 ` figo zhang
2010-03-03 5:01 ` Dick Hollenbeck
2010-03-03 8:28 ` Yegor Yefremov
2010-03-04 10:10 ` Yegor Yefremov
2010-03-05 6:54 ` figo zhang
2010-03-05 10:06 ` Yegor Yefremov
2010-03-05 13:52 ` Figo.zhang
2010-03-05 15:03 ` Yegor Yefremov
2010-03-05 14:07 ` Figo.zhang
2010-03-05 15:00 ` Yegor Yefremov
2010-03-05 16:22 ` Stephen Hemminger
2010-03-06 2:40 ` Figo.zhang
2010-03-08 9:04 ` figo zhang
2010-03-08 14:10 ` Yegor Yefremov
2010-03-08 14:11 ` Yegor Yefremov
2010-03-09 1:50 ` figo zhang [this message]
2010-03-15 9:19 ` Yegor Yefremov
2010-08-04 14:40 ` Yegor Yefremov
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=c6ed1ac51003081750v19f9d5fuf07ad0cc2478005d@mail.gmail.com \
--to=figo1802@gmail.com \
--cc=dick@softplc.com \
--cc=netdev@vger.kernel.org \
--cc=yegorslists@googlemail.com \
--cc=zealcook@gmail.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).