From: David Miller <davem@davemloft.net>
To: David.Laight@ACULAB.COM
Cc: willemb@google.com, john.fastabend@gmail.com,
dborkman@redhat.com, fw@strlen.de, gerlitz.or@gmail.com,
hannes@stressinduktion.org, netdev@vger.kernel.org,
john.ronciak@intel.com, amirv@mellanox.com,
eric.dumazet@gmail.com, danny.zhou@intel.com
Subject: Re: [net-next PATCH v1 1/3] net: sched: af_packet support for direct ring access
Date: Tue, 07 Oct 2014 11:43:41 -0400 (EDT) [thread overview]
Message-ID: <20141007.114341.1417644866461362364.davem@davemloft.net> (raw)
In-Reply-To: <063D6719AE5E284EB5DD2968C1650D6D174C5C35@AcuExch.aculab.com>
From: David Laight <David.Laight@ACULAB.COM>
Date: Tue, 7 Oct 2014 09:27:03 +0000
> That is (probably) the only scheme that stops the application
> accessing random parts of physical memory.
I don't know where this claim keeps coming from, it's false.
The application has to attach memory to the ring, and then the
ring can only refer to that memory for the duration of the
session.
There is no way that the user can program the address field of the
descriptors to point at arbitrary physical memory locations.
There is protection and control.
next prev parent reply other threads:[~2014-10-07 15:43 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-06 0:06 [net-next PATCH v1 1/3] net: sched: af_packet support for direct ring access John Fastabend
2014-10-06 0:07 ` [net-next PATCH v1 2/3] net: sched: add direct ring acces via af_packet to ixgbe John Fastabend
2014-10-06 0:07 ` [net-next PATCH v1 3/3] net: packet: Document PACKET_DEV_QPAIR_SPLIT and friends John Fastabend
2014-10-06 0:29 ` [net-next PATCH v1 1/3] net: sched: af_packet support for direct ring access Florian Westphal
2014-10-06 1:09 ` David Miller
2014-10-06 1:18 ` John Fastabend
2014-10-06 1:12 ` John Fastabend
2014-10-06 9:49 ` Daniel Borkmann
2014-10-06 15:01 ` John Fastabend
2014-10-06 16:35 ` Jesper Dangaard Brouer
2014-10-06 17:03 ` Hannes Frederic Sowa
2014-10-06 20:37 ` John Fastabend
2014-10-06 23:26 ` Hannes Frederic Sowa
2014-10-07 18:59 ` Neil Horman
2014-10-08 17:20 ` John Fastabend
2014-10-09 13:36 ` [PATCH] af_packet: Add Doorbell transmit mode to AF_PACKET sockets Neil Horman
2014-10-09 15:01 ` John Fastabend
2014-10-09 16:05 ` Neil Horman
2014-10-06 16:55 ` [net-next PATCH v1 1/3] net: sched: af_packet support for direct ring access Stephen Hemminger
2014-10-06 20:42 ` John Fastabend
2014-10-06 21:42 ` David Miller
2014-10-07 4:25 ` John Fastabend
2014-10-07 4:24 ` Willem de Bruijn
2014-10-07 9:27 ` David Laight
2014-10-07 15:43 ` David Miller [this message]
2014-10-07 15:59 ` David Laight
2014-10-07 16:08 ` David Miller
2014-10-07 15:21 ` Zhou, Danny
2014-10-07 15:46 ` Willem de Bruijn
2014-10-07 15:55 ` John Fastabend
2014-10-07 16:06 ` Zhou, Danny
2014-10-07 16:05 ` David Miller
2014-10-10 3:49 ` Zhou, Danny
-- strict thread matches above, loose matches on Subject: below --
2014-10-07 16:33 Alexei Starovoitov
2014-10-07 16:46 ` Zhou, Danny
2014-10-07 17:01 ` 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=20141007.114341.1417644866461362364.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=David.Laight@ACULAB.COM \
--cc=amirv@mellanox.com \
--cc=danny.zhou@intel.com \
--cc=dborkman@redhat.com \
--cc=eric.dumazet@gmail.com \
--cc=fw@strlen.de \
--cc=gerlitz.or@gmail.com \
--cc=hannes@stressinduktion.org \
--cc=john.fastabend@gmail.com \
--cc=john.ronciak@intel.com \
--cc=netdev@vger.kernel.org \
--cc=willemb@google.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).