From: David Miller <davem@davemloft.net>
To: Raghu.Vatsavayi@cavium.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next V3 0/9] liquidio CN23XX VF support
Date: Mon, 31 Oct 2016 08:53:56 -0400 (EDT) [thread overview]
Message-ID: <20161031.085356.305731038030662065.davem@davemloft.net> (raw)
In-Reply-To: <DM3PR07MB21386FE887D71590E16ED59B81AE0@DM3PR07MB2138.namprd07.prod.outlook.com>
From: "Vatsavayi, Raghu" <Raghu.Vatsavayi@cavium.com>
Date: Mon, 31 Oct 2016 07:21:27 +0000
> So please confirm if you want us to remove these two parameters
> num_queues_per_{p,v}f. Then I can remove these module parameters and
> resubmit the patches.
Yes.
We cannot allow drivers to keep adding unique ways to configure these
things.
There has to be a generic, consistent, mechanism the user can use
to control these parameters. Rather than a per-driver unique one.
prev parent reply other threads:[~2016-10-31 12:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-26 0:57 [PATCH net-next V3 0/9] liquidio CN23XX VF support Raghu Vatsavayi
2016-10-26 0:57 ` [PATCH net-next V3 1/9] liquidio CN23XX: HW config for " Raghu Vatsavayi
2016-10-26 0:57 ` [PATCH net-next V3 2/9] liquidio CN23XX: sysfs VF config support Raghu Vatsavayi
2016-10-26 0:57 ` [PATCH net-next V3 3/9] liquidio CN23XX: Mailbox support Raghu Vatsavayi
2016-10-26 0:57 ` [PATCH net-next V3 4/9] liquidio CN23XX: mailbox interrupt processing Raghu Vatsavayi
2016-10-26 0:57 ` [PATCH net-next V3 5/9] liquidio CN23XX: VF related operations Raghu Vatsavayi
2016-10-26 0:57 ` [PATCH net-next V3 6/9] liquidio CN23XX: device states Raghu Vatsavayi
2016-10-26 0:57 ` [PATCH net-next V3 7/9] liquidio CN23XX: code cleanup Raghu Vatsavayi
2016-10-26 0:57 ` [PATCH net-next V3 8/9] liquidio CN23XX: copyrights changes and alignment Raghu Vatsavayi
2016-10-26 0:57 ` [PATCH net-next V3 9/9] liquidio CN23XX: fix for new check patch errors Raghu Vatsavayi
2016-10-29 18:31 ` [PATCH net-next V3 0/9] liquidio CN23XX VF support David Miller
2016-10-31 7:21 ` Vatsavayi, Raghu
2016-10-31 12:53 ` David Miller [this message]
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=20161031.085356.305731038030662065.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Raghu.Vatsavayi@cavium.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;
as well as URLs for NNTP newsgroup(s).