From: David Miller <davem@davemloft.net>
To: Raghuram.Kothakota@oracle.com
Cc: sowmini.varadhan@oracle.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next 0/2] sunvnet: Packet processing in non-interrupt context.
Date: Fri, 10 Oct 2014 00:36:28 -0400 (EDT) [thread overview]
Message-ID: <20141010.003628.646817757614430018.davem@davemloft.net> (raw)
In-Reply-To: <EB9A1CD1-6E1D-409C-89CB-95CC9A5AFC1D@oracle.com>
From: Raghuram Kothakota <Raghuram.Kothakota@oracle.com>
Date: Thu, 9 Oct 2014 18:10:24 -0700
> Lock less Tx and Rx implementation is very nice, but requires to the
> code path to single threaded to achieve it.
I would like to know how you believe the Linux LLTX "lockless TX"
facility works.
It's not truly lockless, it just turns off the generic networking TX
path per-queue spinlock and puts the full burdon on the driver. It's
just moving the locking from one place to another, not eliminating it.
next prev parent reply other threads:[~2014-10-10 4:36 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-01 18:56 [PATCH net-next 0/2] sunvnet: Packet processing in non-interrupt context Sowmini Varadhan
2014-10-01 19:10 ` Eric Dumazet
2014-10-01 19:50 ` David Miller
2014-10-01 19:55 ` Sowmini Varadhan
2014-10-01 20:15 ` David Miller
2014-10-01 20:23 ` Sowmini Varadhan
2014-10-01 20:25 ` David Miller
2014-10-02 20:12 ` Sowmini Varadhan
2014-10-02 20:43 ` David Miller
2014-10-03 14:40 ` Sowmini Varadhan
2014-10-03 19:08 ` David Miller
2014-10-06 16:04 ` Sowmini Varadhan
2014-10-06 19:25 ` David Miller
2014-10-06 19:31 ` Sowmini Varadhan
2014-10-06 19:37 ` David Miller
2014-10-10 1:10 ` Raghuram Kothakota
2014-10-10 4:36 ` David Miller [this message]
2014-10-10 4:56 ` Raghuram Kothakota
2014-10-10 5:03 ` David Miller
2014-10-10 5:13 ` Raghuram Kothakota
2014-10-15 14:05 ` sunvnet NAPIfication Sowmini Varadhan
-- strict thread matches above, loose matches on Subject: below --
2014-10-01 20:24 [PATCH net-next 0/2] sunvnet: Packet processing in non-interrupt context 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=20141010.003628.646817757614430018.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Raghuram.Kothakota@oracle.com \
--cc=netdev@vger.kernel.org \
--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).