ALT Linux Team development discussions
 help / color / mirror / Atom feed
From: "Alexey V. Vissarionov" <gremlin@altlinux.org>
To: ALT Linux Team development discussions <devel@lists.altlinux.org>
Subject: Re: [devel] Версия драйвера для карт Intel
Date: Fri, 7 Jun 2019 09:14:55 +0300
Message-ID: <20190607061455.GF26157@altlinux.org> (raw)
In-Reply-To: <2d60693d-929d-07b4-90c4-f9326634b69b@basealt.ru>

On 2019-06-06 20:25:47 +0300, Anton Farygin wrote:
 >>> Т.е. - переход на mainline модули внутри ядра равносилен их
 >>> выпиливанию - пользоваться ими нельзя и они ломают обратную
 >>> совместимость.
 >> нет, почему же. При выпиленных модулях ты теряешь доступ к
 >> серверу, а при невыпеленных -- сохраняешь и можешь поставить
 >> другие драйверы. На мой взгляд, это довольно существенная
 >> разница.
 > Нет, т.к. старые модули работают таким образом, что любое
 > нормальное использование этих железок лишает тебя доступа
 > к серверу.

Вот только хрена с два ты объяснишь это коллегам: у них даже
такого опыта администрирования нет.

 > Там с vlan'ами проблема (по крайней мере у меня была).

Исправили. Ну, то есть, все в порядке как минимум со свежими
ядрами (хотя там надо было что-то включить при сборке) и

08:00.0 Ethernet controller [0200]: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection [8086:10fb] (rev 01)
        Subsystem: QLogic, Corp. Device [1fc1:00a1]
        Flags: bus master, fast devsel, latency 0, IRQ 16
        Memory at f2da0000 (64-bit, prefetchable) [size=128K]
        I/O ports at c880 [size=32]
        Memory at f2dd8000 (64-bit, prefetchable) [size=16K]
        Capabilities: [40] Power Management version 3
        Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+
        Capabilities: [70] MSI-X: Enable+ Count=64 Masked-
        Capabilities: [a0] Express Endpoint, MSI 00
        Capabilities: [e0] Vital Product Data
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [140] Device Serial Number 00-00-00-ff-ff-00-00-00
        Capabilities: [150] Alternative Routing-ID Interpretation (ARI)
        Capabilities: [160] Single Root I/O Virtualization (SR-IOV)
        Kernel driver in use: ixgbe

08:00.1 Ethernet controller [0200]: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection [8086:10fb] (rev 01)
        Subsystem: QLogic, Corp. Device [1fc1:00a1]
        Flags: bus master, fast devsel, latency 0, IRQ 17
        Memory at f2de0000 (64-bit, prefetchable) [size=128K]
        I/O ports at cc00 [size=32]
        Memory at f2ddc000 (64-bit, prefetchable) [size=16K]
        Capabilities: [40] Power Management version 3
        Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+
        Capabilities: [70] MSI-X: Enable+ Count=64 Masked-
        Capabilities: [a0] Express Endpoint, MSI 00
        Capabilities: [e0] Vital Product Data
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [140] Device Serial Number 00-00-00-ff-ff-00-00-00
        Capabilities: [150] Alternative Routing-ID Interpretation (ARI)
        Capabilities: [160] Single Root I/O Virtualization (SR-IOV)
        Kernel driver in use: ixgbe

(вообще оно у меня на 6 портов, но для примера хватит и этих двух).


-- 
Alexey V. Vissarionov
gremlin ПРИ altlinux ТЧК org; +vii-cmiii-ccxxix-lxxix-xlii
GPG: 0D92F19E1C0DC36E27F61A29CD17E2B43D879005 @ hkp://keys.gnupg.net


  reply	other threads:[~2019-06-07  6:14 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-04 10:30 ` Alexei Takaseev
2019-06-04 12:45   ` Sergey Afonin
2019-06-04 13:47     ` Anton Farygin
2019-06-05  2:56       ` Alexei Takaseev
2019-06-05  4:42         ` Anton Farygin
2019-06-05  4:44           ` Alexey V. Vissarionov
2019-06-05  4:45             ` Anton Farygin
2019-06-05  7:24               ` Anton Gorlov
2019-06-05  7:30                 ` Anton Farygin
2019-06-05  7:39                 ` Anton Gorlov
2019-06-05  7:43                   ` Anton Farygin
2019-06-05  7:46                     ` Anton Gorlov
2019-06-05  7:56                       ` Anton Farygin
2019-06-05  7:59                         ` Anton Gorlov
2019-06-05  8:00                           ` Anton Farygin
2019-06-05  8:06                             ` Anton Gorlov
2019-06-05  8:32       ` Anton V. Boyarshinov
2019-06-05  9:13         ` Anton Farygin
2019-06-06 10:01           ` Anton V. Boyarshinov
2019-06-06 10:50             ` Anton Farygin
2019-06-06 11:06               ` Dmitry V. Levin
2019-06-06 11:21                 ` Alexey V. Vissarionov
2019-06-06 11:34                 ` Anton Farygin
2019-06-06 11:53                   ` Dmitry V. Levin
2019-06-06 13:30                     ` Anton Farygin
2019-06-06 13:49                       ` Sergey V Turchin
2019-06-06 14:41                       ` Anton V. Boyarshinov
2019-06-06 14:44                         ` Anton Farygin
2019-06-06 14:43                       ` Anton V. Boyarshinov
2019-06-06 14:46                         ` Anton Farygin
2019-06-06 16:03                           ` Anton V. Boyarshinov
2019-06-06 17:25                             ` Anton Farygin
2019-06-07  6:14                               ` Alexey V. Vissarionov [this message]
2019-06-07  6:28                                 ` Anton Farygin
2019-06-07  6:50                                   ` Alexey V. Vissarionov
2019-06-07  7:58                                     ` Anton Farygin
2019-06-07  7:54                           ` Sergey Afonin
2019-06-07  8:06                             ` Dmitry V. Levin
2019-06-06 16:24                       ` Dmitry V. Levin
2019-06-06 17:38                         ` Anton Farygin
2019-06-06 17:51                           ` Dmitry V. Levin
2019-06-06 18:19                             ` Anton Farygin
2019-06-06 20:51                         ` Vitaly Chikunov
2019-06-07  4:41                           ` Anton Farygin
2019-06-07  6:20                           ` Alexey V. Vissarionov
2019-06-06 11:58                   ` Sergey V Turchin

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=20190607061455.GF26157@altlinux.org \
    --to=gremlin@altlinux.org \
    --cc=devel@lists.altlinux.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

ALT Linux Team development discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://lore.altlinux.org/devel/0 devel/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 devel devel/ http://lore.altlinux.org/devel \
		devel@altlinux.org devel@altlinux.ru devel@lists.altlinux.org devel@lists.altlinux.ru devel@linux.iplabs.ru mandrake-russian@linuxteam.iplabs.ru sisyphus@linuxteam.iplabs.ru
	public-inbox-index devel

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://lore.altlinux.org/org.altlinux.lists.devel


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git