From: "Александр Киселев" <kiselev99@gmail.com>
To: John Ousterhout <ouster@cs.stanford.edu>
Cc: users <users@dpdk.org>
Subject: Re: [dpdk-users] Redirect DPDK log?
Date: Thu, 15 Sep 2016 21:06:59 +0300 [thread overview]
Message-ID: <CAMKNYbzW+9eqN2hjPvRt+GREx_8O3+3YE=3azLH1HUVY2Bdijw@mail.gmail.com> (raw)
In-Reply-To: <CAGXJAmyy87zUK9X69dEw3Qgt99zAhXq4oPr_A24ETfuLcQ4+Qg@mail.gmail.com>
Hi, John.
Take a look at
http://man7.org/linux/man-pages/man3/fopencookie.3.html
2016-09-15 3:52 GMT+03:00 John Ousterhout <ouster@cs.stanford.edu>:
> At first I thought this approach (fmemopen) might work, but now I'm not so
> sure. The problem is that fmemopen doesn't provide any sort of notification
> when it adds data to the buffer.
--
Alexander Kiselev
prev parent reply other threads:[~2016-09-15 18:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-14 21:08 John Ousterhout
2016-09-14 21:24 ` Matthew Hall
2016-09-15 0:52 ` John Ousterhout
2016-09-15 6:49 ` Thomas Monjalon
2016-09-15 18:06 ` Александр Киселев [this message]
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='CAMKNYbzW+9eqN2hjPvRt+GREx_8O3+3YE=3azLH1HUVY2Bdijw@mail.gmail.com' \
--to=kiselev99@gmail.com \
--cc=ouster@cs.stanford.edu \
--cc=users@dpdk.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).