From: "Ricardo Tubío" <rtpardavila@gmail.com>
To: netdev@vger.kernel.org
Subject: Single socket with TX_RING and RX_RING
Date: Wed, 15 May 2013 12:53:55 +0000 (UTC) [thread overview]
Message-ID: <loom.20130515T144941-798@post.gmane.org> (raw)
Once I tell kernel to export the TX_RING through setsockopt() (see code
below) I always get an error (EBUSY) if i try to tell kernel to export the
RX_RING with the same socket descriptor. Therefore, I have to open an
additional socket for the RX_RING and I require of two sockets when I though
that I would only require of one socket for both TX and RX using mmap()ed
memory.
Do I need both sockets or am I doing something wrong?
Code:
/* init_ring; type = {PACKET_TX_RING, PACKET_RX_RING} */
void *init_ring(const int socket_fd, const int type)
{
void *ring = NULL;
int ring_access_flags = PROT_READ | PROT_WRITE;
tpacket_req_t *p = init_tpacket_req(FRAMES_PER_RING);
int ring_len = ( p->tp_block_size ) * ( p->tp_block_nr );
if ( setsockopt(socket_fd, SOL_PACKET, type,
p, LEN__TPACKET_REQ) < 0 )
{
log_sys_error("Setting socket options for this ring");
}
// 2) open ring
if ( ( ring = mmap(NULL, ring_len, ring_access_flags, MAP_SHARED,
socket_fd, 0) ) == NULL )
{
log_sys_error("mmap()ing error");
}
return(ring);
}
next reply other threads:[~2013-05-15 13:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-15 12:53 Ricardo Tubío [this message]
2013-05-15 13:20 ` Single socket with TX_RING and RX_RING Daniel Borkmann
2013-05-15 13:32 ` Ricardo Tubío
2013-05-15 14:47 ` Daniel Borkmann
2013-05-15 14:52 ` Daniel Borkmann
2013-05-15 14:58 ` Ricardo Tubío
2013-05-15 15:04 ` Daniel Borkmann
2013-05-20 20:50 ` Paul Chavent
2013-05-15 22:44 ` Phil Sutter
2013-05-16 9:18 ` Ricardo Tubío
2013-05-16 10:45 ` Phil Sutter
2013-05-16 11:01 ` Ricardo Tubío
2013-05-16 11:14 ` Daniel Borkmann
2013-05-16 11:52 ` Phil Sutter
2013-05-20 20:54 ` Paul Chavent
2013-05-22 19:36 ` Ricardo Tubío
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=loom.20130515T144941-798@post.gmane.org \
--to=rtpardavila@gmail.com \
--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).