From: Ganesh Venkatesan <ganesh.venkatesan@gmail.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: "Venkatesan, Ganesh" <ganesh.venkatesan@intel.com>,
Andrew Morton <akpm@osdl.org>, Jian Jun He <hejianj@cn.ibm.com>,
anton@samba.org, rende@cn.ibm.com, "Brandeburg,
Jesse" <jesse.brandeburg@intel.com>,
jgarzik@pobox.com, wangjs@cn.ibm.com, "Ronciak,
John" <john.ronciak@intel.com>,
cdlwangl@cn.ibm.com, linuxppc64-dev@lists.linuxppc.org.sgi.com,
netdev@oss.sgi.com
Subject: Re: Fw: [Bugme-new] [Bug 4628] New: Test server hang while running rhr (network) test on RHEL4 with kernel 2.6.12-rc1-mm4
Date: Thu, 26 May 2005 16:08:17 -0700 [thread overview]
Message-ID: <5fc59ff30505261608541b74fb@mail.gmail.com> (raw)
In-Reply-To: <20050526213421.GA8077@gondor.apana.org.au>
Herbert:
I do not get it. Bear with my ignorance.
e100_tx_timeout does not call e100_down.
It is called from e100_tx_timeout_task which is invoked as a result of
schedule_work. Are you saying that it would still not have the right
context to call netif_disable_poll()?
thanks,
ganesh.
On 5/26/05, Herbert Xu <herbert@gondor.apana.org.au> wrote:
> On Thu, May 26, 2005 at 01:41:53PM -0700, Venkatesan, Ganesh wrote:
> >
> > I already responded to this analysis before. In any case, here it is:
> >
> > Later versions of e100 (3.4.8 for instance) includes a call to
> > netif_poll_disable in e100_down. This is supposed to wait and when it
>
> As I said last time, this is broken since the code path in question
> starts from tx_timeout which is called in softirq context. You'll
> need to schedule a work struct at least.
>
> Cheers,
> --
> Visit Openswan at http://www.openswan.org/
> Email: Herbert Xu ~{PmV>HI~} <herbert@gondor.apana.org.au>
> Home Page: http://gondor.apana.org.au/~herbert/
> PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
>
next prev parent reply other threads:[~2005-05-26 23:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-26 20:41 Fw: [Bugme-new] [Bug 4628] New: Test server hang while running rhr (network) test on RHEL4 with kernel 2.6.12-rc1-mm4 Venkatesan, Ganesh
2005-05-26 21:34 ` Herbert Xu
2005-05-26 23:08 ` Ganesh Venkatesan [this message]
2005-05-27 0:11 ` Herbert Xu
2005-05-27 0:20 ` Herbert Xu
-- strict thread matches above, loose matches on Subject: below --
2005-05-27 0:28 Venkatesan, Ganesh
2005-05-27 1:26 ` Herbert Xu
2005-05-27 1:44 ` Andrew Morton
2005-05-26 13:00 Venkatesan, Ganesh
2005-05-26 16:09 ` Jian Jun He
2005-05-26 20:31 ` Andrew Morton
2005-05-27 6:18 ` Jian Jun He
2005-05-27 8:21 ` Andrew Morton
2005-05-27 10:12 ` Jian Jun He
2005-05-16 9:59 Andrew Morton
2005-05-16 10:41 ` Jian Jun He
2005-05-16 11:00 ` Herbert Xu
2005-05-16 17:43 ` Ganesh Venkatesan
2005-05-16 21:29 ` Herbert Xu
2005-05-16 21:58 ` Jeff Garzik
[not found] ` <OFB1F7DBFD.6A6514AD-ON48257004.0038A154-48257004.0038E08A@cn.ibm.com>
2005-05-26 7:38 ` Andrew Morton
2005-05-26 7:53 ` Jeff Garzik
2005-05-24 18:36 ` Ganesh Venkatesan
2005-05-25 3:21 ` Jian Jun He
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=5fc59ff30505261608541b74fb@mail.gmail.com \
--to=ganesh.venkatesan@gmail.com \
--cc=akpm@osdl.org \
--cc=anton@samba.org \
--cc=cdlwangl@cn.ibm.com \
--cc=ganesh.venkatesan@intel.com \
--cc=hejianj@cn.ibm.com \
--cc=herbert@gondor.apana.org.au \
--cc=jesse.brandeburg@intel.com \
--cc=jgarzik@pobox.com \
--cc=john.ronciak@intel.com \
--cc=linuxppc64-dev@lists.linuxppc.org.sgi.com \
--cc=netdev@oss.sgi.com \
--cc=rende@cn.ibm.com \
--cc=wangjs@cn.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.