From: chetan loke <loke.chetan@gmail.com>
To: John Fastabend <john.fastabend@gmail.com>
Cc: Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
Jesper Dangaard Brouer <brouer@redhat.com>,
bjorn.topel@gmail.com, jasowang@redhat.com, ast@fb.com,
alexander.duyck@gmail.com, john.r.fastabend@intel.com,
Network Development <netdev@vger.kernel.org>
Subject: Re: [RFC PATCH 1/2] af_packet: direct dma for packet ineterface
Date: Mon, 6 Mar 2017 13:28:02 -0800 [thread overview]
Message-ID: <CAAsGZS7HF3cvJ5e45tGHRJhU3xJHnSb4jJV8JEG_eKCcV8hEoQ@mail.gmail.com> (raw)
In-Reply-To: <58916D84.7090706@gmail.com>
On Tue, Jan 31, 2017 at 9:09 PM, John Fastabend
<john.fastabend@gmail.com> wrote:
>> If I understand correctly, the difficulty lies in v3 requiring that the
>> timer "close" the block when the timer expires. That may not be worth
>> implementing, indeed.
>>
>
> Yep that is where I just gave up and decided it wasn't worth it.
>
Without a support for timeout, when a user-space app has to do its own
book-keeping or lets say - shutdown for maintenance/upgrade, then how
can they(app) unblock from this operation? Because if the link is idle
then the DMA may never happen because there are no frames on the wire.
So is there a way to handle this?
Chetan
next prev parent reply other threads:[~2017-03-06 21:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-27 21:33 [RFC PATCH 0/2] rx zero copy interface for af_packet John Fastabend
2017-01-27 21:33 ` [RFC PATCH 1/2] af_packet: direct dma for packet ineterface John Fastabend
2017-01-30 18:16 ` Jesper Dangaard Brouer
2017-01-30 21:51 ` John Fastabend
2017-01-31 1:31 ` Willem de Bruijn
2017-02-01 5:09 ` John Fastabend
2017-03-06 21:28 ` chetan loke [this message]
2017-01-31 12:20 ` Jesper Dangaard Brouer
2017-02-01 5:01 ` John Fastabend
2017-02-04 3:10 ` Jason Wang
2017-01-27 21:34 ` [RFC PATCH 2/2] ixgbe: add af_packet direct copy support John Fastabend
2017-01-31 2:53 ` Alexei Starovoitov
2017-02-01 4:58 ` John Fastabend
2017-01-30 22:02 ` [RFC PATCH 0/2] rx zero copy interface for af_packet David Miller
2017-01-31 16:30 ` Sowmini Varadhan
2017-02-01 4:23 ` John Fastabend
2017-01-31 19:39 ` tndave
2017-02-01 5:09 ` John Fastabend
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=CAAsGZS7HF3cvJ5e45tGHRJhU3xJHnSb4jJV8JEG_eKCcV8hEoQ@mail.gmail.com \
--to=loke.chetan@gmail.com \
--cc=alexander.duyck@gmail.com \
--cc=ast@fb.com \
--cc=bjorn.topel@gmail.com \
--cc=brouer@redhat.com \
--cc=jasowang@redhat.com \
--cc=john.fastabend@gmail.com \
--cc=john.r.fastabend@intel.com \
--cc=netdev@vger.kernel.org \
--cc=willemdebruijn.kernel@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).