DPDK patches and discussions
 help / color / mirror / Atom feed
From: Chaoyong He <chaoyong.he@corigine.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	oss-drivers <oss-drivers@corigine.com>,
	Long Wu <Long.Wu@nephogine.com>,
	Nole Zhang <peng.zhang@corigine.com>
Subject: RE: [PATCH v2 2/2] net/bonding: add command to set dedicated queue size
Date: Thu, 19 Dec 2024 05:52:40 +0000	[thread overview]
Message-ID: <SJ0PR13MB55459C6FE25A00FA3F869D899E062@SJ0PR13MB5545.namprd13.prod.outlook.com> (raw)
In-Reply-To: <SJ0PR13MB55451F1DAC105D0521F37FCC9E302@SJ0PR13MB5545.namprd13.prod.outlook.com>

> > On Wed, 4 Dec 2024 06:21:00 +0000
> > Chaoyong He <chaoyong.he@corigine.com> wrote:
> >
> > > > The definition of what a "dedicated queue" is a bit confusing.
> > > > If it is only for LACP packets, it should never need to be very big.
> > > > Only under a mis-configuration and DoS kind of flood should there
> > > > ever be many packets.
> > >
> > > Yes, the dedicated queue is only for LACP packets now and it doesn't
> > > need be
> > set very big.
> > >
> > > But if we use a hardware queue as the "dedicated queue", we must
> > > consider the hardware capability. The minimum queue size of some
> > > NICs may be larger than the hardcode dedicated queue size. In this
> > > case, I think it
> > is better to add an interface to set the dedicated queue size.
> >
> > How about using the existing descriptor queue limits api for that?
> > It is reported by info get
> 
> Using existing descriptor queue limits api is good enough for current
> problem(hardware capability), but I think it is not very flexible.
> Now we use a macro as a default value for dedicated queue size, but we can
> replace the macro with queue limit while still retaining the interface for
> modifying queue size.
> What do you think of this?

A gentle ping ~

  reply	other threads:[~2024-12-19  5:52 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-24  2:03 [PATCH 0/2] add function " Chaoyong He
2024-06-24  2:03 ` [PATCH 1/2] net/bonding: standard the log message Chaoyong He
2024-10-10 18:10   ` Stephen Hemminger
2024-10-11  3:02     ` Chaoyong He
2024-06-24  2:03 ` [PATCH 2/2] net/bonding: add command to set dedicated queue size Chaoyong He
2024-10-10 18:13   ` Stephen Hemminger
2024-10-11  3:00     ` Chaoyong He
2024-10-11  3:24 ` [PATCH v2 0/2] add function " Chaoyong He
2024-10-11  3:24   ` [PATCH v2 1/2] net/bonding: standard the log message Chaoyong He
2024-10-11  5:10     ` Stephen Hemminger
2024-10-29  1:51     ` lihuisong (C)
2024-10-11  3:24   ` [PATCH v2 2/2] net/bonding: add command to set dedicated queue size Chaoyong He
2024-10-17 16:05     ` Thomas Monjalon
2024-10-29  1:49     ` lihuisong (C)
2024-12-03 18:39     ` Stephen Hemminger
2024-12-03 19:57     ` Stephen Hemminger
2024-12-04  6:21       ` Chaoyong He
2024-12-04 16:00         ` Stephen Hemminger
2024-12-05  2:53           ` Chaoyong He
2024-12-19  5:52             ` Chaoyong He [this message]
2024-12-20  5:25     ` Stephen Hemminger

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=SJ0PR13MB55459C6FE25A00FA3F869D899E062@SJ0PR13MB5545.namprd13.prod.outlook.com \
    --to=chaoyong.he@corigine.com \
    --cc=Long.Wu@nephogine.com \
    --cc=dev@dpdk.org \
    --cc=oss-drivers@corigine.com \
    --cc=peng.zhang@corigine.com \
    --cc=stephen@networkplumber.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;
as well as URLs for NNTP newsgroup(s).