In addition to what vcTheGuru said, here are some other things to consider.

Using an alternate delimiter for your regex would make it easier on the eye, and would avoid LTS (Leaning Toothpick Syndrome). Instead of "/", you could use "{}", for example: 

    m{  Input queue: 0/75/(.*)/39 \(size/max/drops/flushes\); Total ou
+tput drops: (.*)}

[download]

Also consider making portions of the regex independent of whitespace. You could start the regex with m{\s+Input

The $1 alone looks a little suspicous. If the regex matches, then $1 should be set, so checking it again seems redundant. Did you really mean if (($1 != 0) || ($2 != 0))

If your captures should always be integers, it might be better to use (\d+) instead of (.*).

In reply to Re: RegEx & Approach Question by toolic
in thread RegEx & Approach Question by ewhitt

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.