All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: prodyut hazarika <prodyuth@gmail.com>
Cc: Victor Gallardo <vgallardo@amcc.com>, Feng Kan <fkan@amcc.com>,
	netdev@vger.kernel.org, lada.podivin@gmail.com,
	Loc Ho <lho@amcc.com>,
	bhutchings@solarflare.com, Prodyut Hazarika <phazarika@amcc.com>,
	linuxppc-dev@lists.ozlabs.org, davem@davemloft.net
Subject: Re: [PATCH 1/2] ibm_newemac: Add Support for MAL Interrupt Coalescing
Date: Tue, 22 Sep 2009 10:39:03 +1000	[thread overview]
Message-ID: <1253579943.7103.194.camel@pasglop> (raw)
In-Reply-To: <49c0ff980909211728s2d39e356p6900d047c6918826@mail.gmail.com>

On Mon, 2009-09-21 at 17:28 -0700, prodyut hazarika wrote:
> > BTW. If you guys are ever going to do another change to MAL, please
> > please plase, add the -one- major missing feature that's causing all
> the
> > pain and complication in the current design: Add a per-channel
> interrupt
> > masking option.
> >
> > The lack of ability to mask the interrupt per MAL channel is what
> forces
> > us to create that fake netdev structure in order to share the napi
> > device instance between all the EMACs in the system. This is very
> > inefficient too. We would be able to make things run a lot smoother
> if
> > we could just have a napi instance per EMAC, but for that, we need
> > per-channel interrupt masking.
> >
> 
> I will add a patch for the above as soon as I am done incorporating
> your comments on the MAL coalescing support.
> 
Well... the above is a HW limitation :-) IE. I was suggesting you fix
the HW, but in the case where you already did and the current MAL in
your SoC can indeed mask the interrupt per-channel, then that's great
and we should definitely look into having the driver go back to a more
standard NAPI model on MALs that have that capability.

Cheers,
Ben.

  reply	other threads:[~2009-09-22  0:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-21 22:47 [PATCH 1/2] ibm_newemac: Add Support for MAL Interrupt Coalescing Prodyut Hazarika
2009-09-21 23:41 ` Benjamin Herrenschmidt
2009-09-21 23:41   ` Benjamin Herrenschmidt
2009-09-21 23:49   ` Prodyut Hazarika
2009-09-22  0:07     ` Benjamin Herrenschmidt
2009-09-22  0:05   ` Prodyut Hazarika
2009-09-22  0:05     ` Prodyut Hazarika
2009-09-22  0:12     ` Benjamin Herrenschmidt
2009-09-22  0:28       ` prodyut hazarika
2009-09-22  0:39         ` Benjamin Herrenschmidt [this message]
2009-09-22  0:53           ` Prodyut Hazarika
2009-09-22  0:53             ` Prodyut Hazarika
2009-09-22  1:09             ` Benjamin Herrenschmidt

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=1253579943.7103.194.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=bhutchings@solarflare.com \
    --cc=davem@davemloft.net \
    --cc=fkan@amcc.com \
    --cc=lada.podivin@gmail.com \
    --cc=lho@amcc.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=netdev@vger.kernel.org \
    --cc=phazarika@amcc.com \
    --cc=prodyuth@gmail.com \
    --cc=vgallardo@amcc.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.