From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] igb: Update to 5.3.2.2
Date: Sun, 16 Aug 2015 09:25:41 +0200 [thread overview]
Message-ID: <55D03AF5.1040101@ipfire.org> (raw)
In-Reply-To: <24cf9f37c5d7f189ae5831e1674b1677@mail01.ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1554 bytes --]
Hi,
On 16.08.2015 07:54, Arne Fitzenreiter wrote:
> Is the MultiQueue mode working with this version?
Being rather naive, I just saw that this version was relatively old, had
some "computing time" left on my devel, so I thought: "Why not...?" ;-)
> Currently we not use the igb lfs because the older Version from
> backports works with MultiQueue.
I didn't know that and actually can't test this driver on my system. I
just thought it could be updated.
An excerpt from README - perhaps always the same - leads me to the
assumption that Multiqueue mode perhaps can be enabled (?):
***SNIP***
Multiqueue
----------
In this mode, a separate MSI-X vector is allocated for each queue and
one for "other" interrupts such as link status change and errors. All
interrupts are throttled via interrupt moderation. Interrupt moderation
must be used to avoid interrupt storms while the driver is processing
one interrupt. The moderation value should be at least as large as the
expected time for the driver to process an interrupt. Multiqueue is off
by default.
REQUIREMENTS: MSI-X support is required for Multiqueue. If MSI-X is not
found, the system will fallback to MSI or to Legacy interrupts. This
driver supports multiqueue in kernel versions 2.6.24 and newer. This
driver supports receive multiqueue on all kernels that support MSI-X.
NOTES:
- Do not use MSI-X with the 2.6.19 or 2.6.20 kernels.
- On some kernels a reboot is required to switch between single queue
mode and multiqueue mode or vice-versa.
***SNAP***
Regards
Matthias
next prev parent reply other threads:[~2015-08-16 7:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-15 16:46 Matthias Fischer
2015-08-16 5:54 ` Arne Fitzenreiter
2015-08-16 7:25 ` Matthias Fischer [this message]
2015-08-16 7:32 ` Matthias Fischer
2015-08-17 21:24 ` Michael Tremer
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=55D03AF5.1040101@ipfire.org \
--to=matthias.fischer@ipfire.org \
--cc=development@lists.ipfire.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