From: Ram <vshrirama@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: linux-arm-kernel@lists.arm.linux.org.uk
Subject: Network drivers - porting to 2.6 issues
Date: Thu, 15 Jun 2006 17:52:09 +0530 [thread overview]
Message-ID: <8bf247760606150522w6e66bbcfs8951dff00db8277a@mail.gmail.com> (raw)
Hi,
I have ported a wlan driver from 2.4 to 2.6.
I am referring to the porting article in lwn.net.
The driver works fine for sometime. after which data transfer
becomes very slow.
i have telnet to a remote machine. i do ls -Rl /
data transfer is ok to start with, then it becomes very slow.
also whatever i type on the shell prompt appears after a while.
This happens - sometimes it is faster and then slow. this goes on in a cycle.
Is there any difference between a 2.4 and 2.6 kernel network stack?.
I have changed registeration, changing task queues to work queues
and stuff like that.
am not sure if the network stack api's and thier meanings have changed.
is there anything i should watch out for?.
sometimes i do get : NETDEV WATCHDOG: eth1: transmit timed out
What does this mean?.
is there anything more i should watch out for?.
Regards,
sriram
next reply other threads:[~2006-06-15 12:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-15 12:22 Ram [this message]
2006-06-15 16:29 ` Lee Revell
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=8bf247760606150522w6e66bbcfs8951dff00db8277a@mail.gmail.com \
--to=vshrirama@gmail.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--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
all inboxes | Powered by JetHome®