From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Wiles, Keith" <keith.wiles@intel.com>,
Adrien Mazarguil <adrien.mazarguil@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 1/2] net/tap: remove redundant syscall on Tx
Date: Tue, 14 Mar 2017 17:04:16 +0000 [thread overview]
Message-ID: <6ddb1576-5272-87a0-1883-3deeb62b7fe2@intel.com> (raw)
In-Reply-To: <BA5B46C0-CB25-4102-B062-046D08C1BA7A@intel.com>
On 3/14/2017 1:52 PM, Wiles, Keith wrote:
>
>> On Mar 14, 2017, at 8:51 PM, Adrien Mazarguil <adrien.mazarguil@6wind.com> wrote:
>>
>> Polling the Tx queue file descriptor before writing to it is not mandatory
>> since it is configured as non-blocking.
>>
>> Signed-off-by: Adrien Mazarguil <adrien.mazarguil@6wind.com>
>> Acked-by: Pascal Mazon <pascal.mazon@6wind.com>
>
> Acked-by: Keith Wiles <keith.wiles@intel.com>
Series applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2017-03-14 17:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-14 12:51 Adrien Mazarguil
2017-03-14 12:51 ` [dpdk-dev] [PATCH 2/2] net/tap: add Rx trigger Adrien Mazarguil
2017-03-14 13:57 ` Wiles, Keith
2017-03-14 13:52 ` [dpdk-dev] [PATCH 1/2] net/tap: remove redundant syscall on Tx Wiles, Keith
2017-03-14 17:04 ` Ferruh Yigit [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=6ddb1576-5272-87a0-1883-3deeb62b7fe2@intel.com \
--to=ferruh.yigit@intel.com \
--cc=adrien.mazarguil@6wind.com \
--cc=dev@dpdk.org \
--cc=keith.wiles@intel.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).