From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Mcnamara, John" <john.mcnamara@intel.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH v2] docs: add statistics read frequency to fm10k guide
Date: Mon, 22 Feb 2016 18:40:41 +0100 [thread overview]
Message-ID: <1700761.WB86EvbuoI@xps13> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE20245E3E6@IRSMSX103.ger.corp.intel.com>
2016-02-22 17:18, Mcnamara, John:
> > Known Issues
> > ------------
> >
> > +* **FM10K: Statistics Polling Frequency**
> > +
> > + A section has been added to the NIC guide for fm10k about the maximum
> > + time between reading statistics and 32 bit packet counter overflows.
>
> Hi Thomas,
>
> We should probably call this section "New Known Issues" and then copy them to the legacy "Known Issues" doc after 1 release.
>
> http://dpdk.org/doc/guides/rel_notes/release_2_2.html#known-issues
> http://dpdk.org/doc/guides/rel_notes/known_issues.html
>
> Or any other suggestion?
Yes it is an option.
Or we can simply maintain known issues in one place and remove the
per-release section.
next prev parent reply other threads:[~2016-02-22 17:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 15:42 [PATCH] docs: add statistics read frequency to fm10k guide Harry van Haaren
2016-02-08 16:00 ` Thomas Monjalon
2016-02-08 16:06 ` Van Haaren, Harry
2016-02-09 15:00 ` Mcnamara, John
2016-02-09 15:19 ` [PATCH v2] " Harry van Haaren
2016-02-22 17:13 ` Mcnamara, John
2016-02-22 17:18 ` Mcnamara, John
2016-02-22 17:40 ` Thomas Monjalon [this message]
2016-03-06 22:35 ` Thomas Monjalon
2016-03-08 17:16 ` [PATCH v3] " Harry van Haaren
2016-03-09 17:39 ` Thomas Monjalon
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=1700761.WB86EvbuoI@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.