From: Paul Chavent <paul.chavent@fnac.net>
To: "Ricardo Tubío" <rtpardavila@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: Single socket with TX_RING and RX_RING
Date: Mon, 20 May 2013 22:54:31 +0200 [thread overview]
Message-ID: <519A8D87.6080409@fnac.net> (raw)
In-Reply-To: <loom.20130516T125157-378@post.gmane.org>
On 05/16/2013 01:01 PM, Ricardo Tubío wrote:
> Phil Sutter <phil <at> nwl.cc> writes:
>
>> So you do not call init_ring() twice as one may imply when reading your
>> first mail? Please provide a complete code sample.
>>
>
> Yes, I call it twice. The problem is that if I call it twice with the same
> socket_fd, the second time I call it I get the EBUSY error from kernel. I
> have to use two different sockets (two different socket_fd's, therefore) in
> order to workaround this issue.
>
> The code I use for calling "init_ring" is the one below. If in function
> "init_rings", instead of using two different sockets (rx_socket_fd and
> tx_socket_fd), I use a single socket, I get the EBUSY error from kernel.
>
> Hope this clarifies, Cardo.
Hi.
As stated before, you should call mmap only once.
Paul.
next prev parent reply other threads:[~2013-05-20 20:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-15 12:53 Single socket with TX_RING and RX_RING Ricardo Tubío
2013-05-15 13:20 ` 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 [this message]
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=519A8D87.6080409@fnac.net \
--to=paul.chavent@fnac.net \
--cc=netdev@vger.kernel.org \
--cc=rtpardavila@gmail.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).