From: "Joonwoo Park" <joonwpark81@gmail.com>
To: "David Miller" <davem@davemloft.net>
Cc: auke-jan.h.kok@intel.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, jesse.brandeburg@intel.com,
jgarzik@pobox.com, shemminger@linux-foundation.org
Subject: Re: [PATCH 1/7] : e1000 Fix possible causing oops of net_rx_action
Date: Fri, 14 Dec 2007 11:41:26 +0900 [thread overview]
Message-ID: <b25c3fa70712131841k6c06949evd247c9a2eabd9360@mail.gmail.com> (raw)
In-Reply-To: <20071213.053354.82143565.davem@davemloft.net>
2007/12/13, David Miller <davem@davemloft.net>:
> From: "Joonwoo Park" <joonwpark81@gmail.com>
> Date: Thu, 13 Dec 2007 19:18:56 +0900
>
> > Just blowing netif_running up is not best solution I think, it makes
> > ifconfig down hang at least for e1000.
>
> It hangs because the packet receive rate is so high that NAPI
> poll never exits.
Certainly I'm aware it
>
> I think we need a cheap solution to something so obscure and
> almost not worth explicitly even coding for. Really, if you
> setup silly situations like that, you get what you asked for.
>
I can agree that we need good solution for that.
BUT I don't think I didn't setup *silly* situation. my customers who
are reporting this problem, running firewall on linux which is
forwarding packets with high rate.
I don't want to say 'don't ifconfig down, don't reboot, don't
shutdown' it would introduce problem on your such *sily* sitution'.
In addition, my laptop is just connected to another *linux* machine
which is generating 300mbps 64byte udp packets infinitely.
Joonwoo
next prev parent reply other threads:[~2007-12-14 2:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-13 10:18 [PATCH 1/7] : e1000 Fix possible causing oops of net_rx_action Joonwoo Park
2007-12-13 13:33 ` David Miller
2007-12-14 2:41 ` Joonwoo Park [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-12-12 4:01 Joonwoo Park
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=b25c3fa70712131841k6c06949evd247c9a2eabd9360@mail.gmail.com \
--to=joonwpark81@gmail.com \
--cc=auke-jan.h.kok@intel.com \
--cc=davem@davemloft.net \
--cc=jesse.brandeburg@intel.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.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