From: Jakub Kicinski <kuba@kernel.org>
To: Martin T <m4rtntns@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: Why is NIC driver queue depth driver dependent when it allocates system memory?
Date: Thu, 30 Jan 2020 08:56:29 -0800 [thread overview]
Message-ID: <20200130085629.42c71fdf@cakuba> (raw)
In-Reply-To: <CAJx5YvHH9CoC8ZDz+MwG8RFr3eg2OtDvmU-EaqG76CiAz+W+5Q@mail.gmail.com>
On Thu, 30 Jan 2020 15:02:02 +0200, Martin T wrote:
> Hi,
>
> when I read the source code of for example tg3 driver or e1000e
> driver, then looks like the driver queue is allocated from system
> memory. For example, in e1000_ethtool.c kcalloc() is called to
> allocate GFP_KERNEL memory.
>
> If system memory is allocated, then why are there driver-dependent
> limits? For example, in my workstation the maximum RX/TX queue for the
> NIC using tg3 driver is 511 while maximum RX/TX queue for the NIC
> using e1000e driver is 4096:
Hi Martin,
the idea is that drivers can choose the initial setting which are
optimal for the implementation and the hardware. Whether they actually
are, or whether values chosen 10 years ago for tg3 and e1000e are
reasonable for modern uses of that hardware could perhaps be questioned.
next prev parent reply other threads:[~2020-01-30 16:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-30 13:02 Why is NIC driver queue depth driver dependent when it allocates system memory? Martin T
2020-01-30 16:56 ` Jakub Kicinski [this message]
2020-01-31 14:45 ` Martin T
2020-02-01 19:08 ` Cong Wang
2020-02-01 19:14 ` Michal Kubecek
2020-02-01 19:51 ` Cong Wang
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=20200130085629.42c71fdf@cakuba \
--to=kuba@kernel.org \
--cc=m4rtntns@gmail.com \
--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