From: Grant Edwards <grante@visi.com>
To: Jonathan Larmour <jlarmour@redhat.com>
Cc: Hugo Tyson <hmt@redhat.com>, ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] DHCP shuts down Ethernet device?
Date: Mon, 23 Apr 2001 13:35:00 -0000 [thread overview]
Message-ID: <20010423153657.A2947@visi.com> (raw)
In-Reply-To: <3AE4822A.24EC454B@redhat.com>
On Mon, Apr 23, 2001 at 08:27:38PM +0100, Jonathan Larmour wrote:
> > It shuts down everything, deliberately.
> >
> > > I think I'm going to have to either comment out the above call,
> > > or make my Ethernet driver's _stop() method into a noop...
> >
> > Either of those would do.
>
> I'm wondering: isn't the problem just that configuring the
> interface down calls the _stop() method? Why not just not do
> that? The common eth driver already just has eth_drv_recv()
> return immediately if the interface is down. Of course it
> depends where any non-TCP/IP stack is plugging in...
In my case, The non-IP stack hooks into the Ethernet driver at
the same level that the TCP/IP stack does. I decided to change
my _stop() method so that it doesn't shut off the interface, it
just sets a flag so that packets normally passed to the TCP/IP
stack are discarded (this should result in the behvior expected
by the TCP/IP stack).
> It probably shouldn't be the default behaviour admittedly,
> otherwise we're just doing a bunch of interrupt processing for
> no reason in the most common case.
Right.
--
Grant Edwards
grante@visi.com
prev parent reply other threads:[~2001-04-23 13:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-23 10:38 Grant Edwards
2001-04-23 11:30 ` Hugo Tyson
2001-04-23 12:27 ` Jonathan Larmour
2001-04-23 13:35 ` Grant Edwards [this message]
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=20010423153657.A2947@visi.com \
--to=grante@visi.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=hmt@redhat.com \
--cc=jlarmour@redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).