From: Sowmini Varadhan <sowmini.varadhan@oracle.com>
To: Raghuram Kothakota <Raghuram.Kothakota@oracle.com>
Cc: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: [PATCH net-next 3/3] sunvnet: Schedule maybe_tx_wakeup as a tasklet from ldc_rx path
Date: Wed, 13 Aug 2014 06:51:37 -0400 [thread overview]
Message-ID: <20140813105137.GB16865@oracle.com> (raw)
In-Reply-To: <163B73C6-95EF-4398-B399-ECD5B95F5EC8@oracle.com>
On (08/12/14 21:26), Raghuram Kothakota wrote:
>
> We do not consider a peer which couldn't process LDC messages
> as an offender but just a peer in a broken state. A peer could get
So I was using "offender" in the same way that one typically
talks about sending ICMP errors for "offending IP packets"
(nothing pesonal :-)). I dont want to quibble over terminology here.
> From what I read the ldc_disconect() code, it seems like it is reconfiguring
> the queues, so I assume a reset event would re-enable the communication
> fine, but I don't know for sure without testing this specific condition.
No such events were generated by the code when I tested it.
I'll send a consolidated reply to the rest of that very long thread
in a bit.
--Sowmini
next prev parent reply other threads:[~2014-08-13 10:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-12 14:35 [PATCH net-next 3/3] sunvnet: Schedule maybe_tx_wakeup as a tasklet from ldc_rx path Sowmini Varadhan
2014-08-12 22:13 ` David Miller
2014-08-13 1:58 ` Sowmini Varadhan
2014-08-13 4:25 ` David Miller
2014-08-13 11:20 ` Sowmini Varadhan
2014-08-13 23:29 ` David Miller
2014-08-13 4:26 ` Raghuram Kothakota
2014-08-13 4:31 ` David Miller
2014-08-13 5:14 ` Raghuram Kothakota
2014-08-13 5:29 ` David Miller
2014-08-13 5:44 ` Raghuram Kothakota
2014-08-13 6:11 ` David Miller
2014-08-13 6:37 ` Raghuram Kothakota
2014-08-13 10:51 ` Sowmini Varadhan [this message]
2014-08-13 21:59 ` Raghuram Kothakota
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=20140813105137.GB16865@oracle.com \
--to=sowmini.varadhan@oracle.com \
--cc=Raghuram.Kothakota@oracle.com \
--cc=davem@davemloft.net \
--cc=netdev@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).