All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.18 orinoco.c __orinoco_ev_rx question
Date: Wed, 29 May 2002 13:28:22 +1000	[thread overview]
Message-ID: <20020529032822.GA16537@zax> (raw)
In-Reply-To: <20020528160135.D24097@bigmac.e-technik.uni-dortmund.de>

On Tue, May 28, 2002 at 04:01:35PM +0200, Wolfgang Wegner wrote:
> Hi all,
> 
> after sorting out my sk_buff problem [turned out to be problems with
> pcmcia-cs-3.1.33's own include files, which throw away some of the kernel's
> config options, thus affecting struct sk_buff declaration] i am now
> investigating some things in orinoco.c of 2.4.18, which seems almost
> identical to the one from pcmcia-cs
> 
> My concern is, if it is really necessary to do the whole rx work in the
> interrupt handler, or a bottom half could be used here?
> I ask because like this, the interrupt is set for about 800us in a
> whole-frame (MTU) receive, which IMHO is not really desirable. I have to
> admit i still did not really understand the use of FIDs, so i am not sure,
> but couldn't this be taken out of the interrupt handler itself?

No it doesn't have to be done in the interrupt handler, it could be
done in a bottom half.  However essentially every other network driver
does all the Rx work (up to netif_rx()) in the hard irq, so I'm
disinclined to do it otherwise.

> (Of course, i can simply implement and try it, but as i am absolutely
> not aware about the use of FIDs, i do not want to risk introducing any
> nice subtle bugs...)



-- 
David Gibson			| For every complex problem there is a
david@gibson.dropbear.id.au	| solution which is simple, neat and
				| wrong.  -- H.L. Mencken
http://www.ozlabs.org/people/dgibson

  reply	other threads:[~2002-05-29  3:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-28 14:01 2.4.18 orinoco.c __orinoco_ev_rx question Wolfgang Wegner
2002-05-29  3:28 ` David Gibson [this message]
2002-05-29  7:06   ` Wolfgang Wegner
2002-06-03  6:24     ` David Gibson

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=20020529032822.GA16537@zax \
    --to=david@gibson.dropbear.id.au \
    --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 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.