From: Sowmini Varadhan <sowmini.varadhan@oracle.com>
To: davem@davemloft.net, bob.picco@oracle.com,
dwight.engen@oracle.com, raghuram.kothakota@oracle.com
Cc: netdev@vger.kernel.org, sparclinux@vger.kernel.org
Subject: Re: [PATCHv3 RFC net-next 0/4] sunvnet: NAPIfy sunvnet
Date: Wed, 22 Oct 2014 14:57:57 -0400 [thread overview]
Message-ID: <20141022185757.GA8134@oracle.com> (raw)
In-Reply-To: <20141015164234.GA11840@oracle.com>
Please hold off on this patch-set for the moment.
I just discovered a subtle bug that can be triggered when multiple
ldc events (e.g., UP and DATA_READY) are passed up from
ldc_rx -> send_events in one shot- we need to treat the vnet_port's
(new field) rx_event as a bit mask, and need to unroll send_events()
into vnet_event_napi.
the result of this bug is that inter-vnet handshake can sometimes
fail incorrectly causing things to needlessly go thorugh the
switchport. I'm working on the fix for this, I'll send out
PATCHv5 for this series shortly.
Apologies for the confusion.
--Sowmini
next prev parent reply other threads:[~2014-10-22 18:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-15 16:42 [PATCHv3 RFC net-next 0/4] sunvnet: NAPIfy sunvnet Sowmini Varadhan
2014-10-22 18:57 ` Sowmini Varadhan [this message]
2014-10-22 19:39 ` David Miller
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=20141022185757.GA8134@oracle.com \
--to=sowmini.varadhan@oracle.com \
--cc=bob.picco@oracle.com \
--cc=davem@davemloft.net \
--cc=dwight.engen@oracle.com \
--cc=netdev@vger.kernel.org \
--cc=raghuram.kothakota@oracle.com \
--cc=sparclinux@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 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 NNTP newsgroup(s).