From: David Miller <davem@davemloft.net>
To: sowmini.varadhan@oracle.com
Cc: raghuram.kothakota@oracle.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/2] sunvnet: Reduce LDC message overhead.
Date: Thu, 04 Sep 2014 22:37:24 -0700 (PDT) [thread overview]
Message-ID: <20140904.223724.206826043871814498.davem@davemloft.net> (raw)
In-Reply-To: <20140902161936.GA31516@oracle.com>
From: Sowmini Varadhan <sowmini.varadhan@oracle.com>
Date: Tue, 2 Sep 2014 12:19:36 -0400
> This patchset has an updated version of the v1 changes to reduce the
> overhead from LDC messages.
Let's hold on these changes until the memory barrier issues brought up
by David is resolved.
next prev parent reply other threads:[~2014-09-05 5:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-02 16:19 [PATCH net-next v2 0/2] sunvnet: Reduce LDC message overhead Sowmini Varadhan
2014-09-05 5:37 ` David Miller [this message]
2014-09-08 14:38 ` Sowmini Varadhan
2014-09-08 14:43 ` David L Stevens
2014-09-10 14:04 ` Sowmini Varadhan
2014-09-10 22:25 ` David Miller
2014-09-10 22:37 ` Sowmini Varadhan
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=20140904.223724.206826043871814498.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=raghuram.kothakota@oracle.com \
--cc=sowmini.varadhan@oracle.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 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).