All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Kumar Sanghvi <kumaras@chelsio.com>
Cc: Hariprasad Shenai <hariprasad@chelsio.com>,
	netdev@vger.kernel.org, davem@davemloft.net, leedom@chelsio.com,
	anish@chelsio.com, nirranjan@chelsio.com, praveenm@chelsio.com
Subject: Re: [PATCH net-next] cxgb4: Add low latency socket busy_poll support
Date: Tue, 03 Feb 2015 23:50:50 -0800	[thread overview]
Message-ID: <1423036250.907.101.camel@edumazet-glaptop2.roam.corp.google.com> (raw)
In-Reply-To: <20150204062137.GD30631@kumar-pc.asicdesigners.com>

On Wed, 2015-02-04 at 12:21 +0600, Kumar Sanghvi wrote:
> On Tuesday, February 02/03/15, 2015 at 21:58:29 -0800, Eric Dumazet wrote:
> > On Tue, 2015-02-03 at 10:50 +0530, Hariprasad Shenai wrote:
> > 
> > > @@ -1978,9 +2016,13 @@ static int napi_rx_handler(struct napi_struct *napi, int budget)
> > >  {
> > >  	unsigned int params;
> > >  	struct sge_rspq *q = container_of(napi, struct sge_rspq, napi);
> > > -	int work_done = process_responses(q, budget);
> > > +	int work_done = 0;
> > >  	u32 val;
> > >  
> > > +	if (!cxgb_poll_lock_napi(q))
> > > +		return work_done;
> > > +
> > 
> > 
> > This is very suspicious. Please take a look at commits
> > 
> > 24e579c8898aa641 ("bnx2x: fix napi poll return value for repoll") 
> > f104fedc0da126ab ("enic: fix rx napi poll return value")
> > 
> > for context.
> 
> Thanks Eric for pointing on this.
> So, this probably needs change after commit d75b1ade567ffab ("net: less interrupt masking in NAPI"), or
> is there something else that is missed ?

Right, you probably need to return budget here, not 0 (work_done == 0 at
this stage)

      reply	other threads:[~2015-02-04  7:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-03  5:20 [PATCH net-next] cxgb4: Add low latency socket busy_poll support Hariprasad Shenai
2015-02-03 16:45 ` Rick Jones
2015-02-04  6:24   ` Kumar Sanghvi
2015-02-04  5:58 ` Eric Dumazet
2015-02-04  6:21   ` Kumar Sanghvi
2015-02-04  7:50     ` Eric Dumazet [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=1423036250.907.101.camel@edumazet-glaptop2.roam.corp.google.com \
    --to=eric.dumazet@gmail.com \
    --cc=anish@chelsio.com \
    --cc=davem@davemloft.net \
    --cc=hariprasad@chelsio.com \
    --cc=kumaras@chelsio.com \
    --cc=leedom@chelsio.com \
    --cc=netdev@vger.kernel.org \
    --cc=nirranjan@chelsio.com \
    --cc=praveenm@chelsio.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.