netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dick Hollenbeck <dick@softplc.com>
To: figo zhang <figo1802@gmail.com>
Cc: Yegor Yefremov <yegorslists@googlemail.com>,
	netdev@vger.kernel.org, zealcook@gmail.com
Subject: Re: KS8695: possible NAPI issue
Date: Tue, 02 Mar 2010 23:01:29 -0600	[thread overview]
Message-ID: <4B8DED29.9000605@softplc.com> (raw)
In-Reply-To: <c6ed1ac51003021746n2b246591g880b584550ec5e84@mail.gmail.com>

figo zhang wrote:
> 2010/3/2 Dick Hollenbeck <dick@softplc.com>:
>   
>> Yegor Yefremov wrote:
>>     
>>> I'm using 2.6.33 kernel and I noticed such a strange behavior:
>>>
>>> after system start I transfer one file via netcat from my development
>>> host, after this transfer the network is not functioning i.e. no pings
>>> possible etc.
>>>
>>> To narrow down the problem I checked out this commit
>>>
>>> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=451f14439847db302e5104c44458b2dbb4b1829d.
>>> Till here the network driver is functioning as intended, but after
>>> NAPI introduction I have this issue. With latest git-pull of "Linus'
>>> kernel tree" I can't even ping right after the systems start.
>>>
>>> Any Ideas? What am I missing?
>>>
>>>       
>> No idea, although I am using the same ARM chip, my kernel is at 2.6.30.5,
>> and except for this occasional loss of connection I get, the ethernet driver
>> seems to work better than what you are reporting.
>>     
>
> from linux-2.6.32, this ethernet  driver have add NAPI support, would
> you like to
> try using this version?
>   

Seems like a lot of work for me, given that my 2.6.30.5 kernel is mostly 
working.   Yegor is having the problems on the newer kernels, newer than 
mine.  Sounds like a warning flag to me, not an incentive.

What is NAPI and why do I care?

Dick



  reply	other threads:[~2010-03-03  5:01 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 [this message]
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
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=4B8DED29.9000605@softplc.com \
    --to=dick@softplc.com \
    --cc=figo1802@gmail.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).