From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Hall Subject: Re: [PKTGEN] fixing weird termio issues that complicate debugging Date: Wed, 20 Jan 2016 19:53:24 -0800 Message-ID: <56A05634.1050008@mhcomputing.net> References: <569F2A07.9000606@mhcomputing.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable To: "Wiles, Keith" , "dev@dpdk.org" Return-path: Received: from mail.mhcomputing.net (master.mhcomputing.net [74.208.228.170]) by dpdk.org (Postfix) with ESMTP id E6A128E87 for ; Thu, 21 Jan 2016 04:53:25 +0100 (CET) In-Reply-To: List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On 1/20/16 8:26 AM, Wiles, Keith wrote: > One problem is a number of people wanted to steal the code and use in a= paid application, so the copyright is some what a requirement. As you ma= y know I do a lot of debugging on Pktgen and I feel they are a nuisance. = I can try to see if we can clean up these messages, but do not hold your = breath on getting them to be removed. Understood, I am just providing some usability feedback from the=20 community. Any cleanup, however partial it may be for other reasons,=20 will personally aid me in simplicity of debugging and using the pktgen=20 to find performance improvements in other community applications and=20 DPDK itself, which is my true end goal here. In particular I need it for=20 all the changes I posted at various points for librte_lpm so I can test=20 all this stuff to make sure it really works. > IMO most of the information from DPDK is not very useful as why do I ne= ed to see every lcore line, plus a lot of more useless information. Most = of the information could be reduced a couple of lines or only report issu= es not just a bunch of useless information. DPDK's messages might not be helpful for you, but in my case, the=20 temporary hostile modifications I made based on the writeup sent=20 previously, in order to make these messages visible again, is what=20 allowed me to find and fix the root causes of my inactive port issues,=20 because I have been working with DPDK's messages since 2011 and am very=20 familiar with what they mean inside DPDK itself, so they were the only=20 UI of Pktgen familiar to me at all compared to the rest which is custom=20 stuff I didn't use before. > The screen init should be scrolling the information off the screen to p= reserve that info, unless it was changed by mistake. I found a lot of info is being overwritten or lost due to the complex=20 sequence of all these calls. This is what led to my email of questions=20 for you. > Please use tab stop of 4 instead of 8. IMO tab stop of 8 is so 1970=E2=80= =99s and we should not need tab stop of 8 as any system today will work. = :-) OK. But do note that this convention is different from every other=20 project I've coded on before. Sincerely, Matthew.