From: Ron Mercer <ron.mercer@qlogic.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, ron.mercer@qlogic.com
Subject: [net-next PATCH 0/3] qlge: Change RSS ring to MSIx vector mapping.
Date: Wed, 19 Aug 2009 16:53:08 -0700 [thread overview]
Message-ID: <1250725991-7155-1-git-send-email-ron.mercer@qlogic.com> (raw)
Hello Dave and All,
Attached is a respin of the changes posted earlier this week.
The new RX buffer changes were removed from this series
and will be address them in a separate series when these changes
are accepted.
Changes are as follows:
1) Move TX completion processing from a worker thread to
the send path. This reduces overhead and causes better
locality for freeing TX resources. It also prevents
the TX completion rings from using MSIx vectors hence
allowing them all to be used for RSS rings.
2) Change RSS ring to MSIx vector mapping. Some platforms
are stingy with vectors. This change causes all vectors
to be used for RSS rings. Previously there was a dedicated
ring/vector for handling broadcast/multicast and
various events from the chip and firmware. This 'default'
functionality is now performed by the zeroth RSS ring before
waking NAPI for normal RX processing.
This is a big patch but is mostly deletions.
3) Remove worker threads and ISR that were rendered unused
by #2 above. They were left in the code for patch #2
to make it more readable.
Regards,
Ron Mercer
next reply other threads:[~2009-08-19 23:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-19 23:53 Ron Mercer [this message]
2009-08-19 23:53 ` [net-next PATCH 1/3] qlge: Move TX completion processing to send path Ron Mercer
2009-08-20 9:18 ` David Miller
2009-08-21 17:23 ` Ron Mercer
2009-08-21 20:25 ` David Miller
2009-08-19 23:53 ` [net-next PATCH 2/3] qlge: Change RSS ring to MSIx vector mapping Ron Mercer
2009-08-19 23:53 ` [net-next PATCH 3/3] qlge: Remove unused workers and irq handler Ron Mercer
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=1250725991-7155-1-git-send-email-ron.mercer@qlogic.com \
--to=ron.mercer@qlogic.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.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