DPDK patches and discussions
 help / color / mirror / Atom feed
From: "WanRenyong" <wanry@yunsilicon.com>
To: "fengchengwen" <fengchengwen@huawei.com>,
	 "Stephen Hemminger" <stephen@networkplumber.org>
Cc: <dev@dpdk.org>, <ferruh.yigit@amd.com>, <thomas@monjalon.net>
Subject: Re: [PATCH v2 05/19] net/xsc: add ioctl command interface
Date: Fri, 13 Sep 2024 10:55:08 +0800	[thread overview]
Message-ID: <a449904c-80cf-4ba3-8b07-a5d5606ba777@yunsilicon.com> (raw)
In-Reply-To: <7c5d74b1-2d69-4595-b966-4044b6f7c698@huawei.com>

On 2024/9/12 17:18, fengchengwen wrote:
> On 2024/9/12 16:19, WanRenyong wrote:
>> On 2024/9/12 13:50, Stephen Hemminger wrote:
>>> On Thu, 12 Sep 2024 12:14:08 +0800
>>> "WanRenyong" <wanry@yunsilicon.com> wrote:
>>>
>>>>>    
>>>>>> +};
>>>>>> +
>>>>> Does this device driver depend on some upstr
>>>> Yes, it depends on linux kernel driver of the device.
>>>>
>>>> Hello, Stephen,
>>>>
>>>> Thanks for your review,  please see above.
>>> What is the driver? I don't see in the current kernel.org tree.
>>>
>>>
>>> My concern is that if the driver is not upstream, it is probably not
>>> going to pass the review of kernel developers. This means security and
>>> API changes would be required.
>>>
>>> Ioctl's are considered the worst API to the kernel and unlikely
>>> to be accepted.
>> Hello, Stephen,
>>
>> Thank you for reply.Our kernel driver is being prepared to open source.
>>
>> Our PMD is going to coexist with kernel driver to support flow
>> bifurcation feature.
> It seemed uacce bus could handle this, so that you could use several queues on DPDK, and
> steer flows to these queues by bifurcation feature.
>
>> Ioctl API is used for interaction between PMD and kernel driver. As you
>> said, ioctl is
>>
>> the worst API, should I consider using read and write instead?
> It seemed the ioctl couldn't handle VF located in VM, and interact 
> with PF driver which run in host kernel.
>> If not, could you please give me some advice?
> If your NIC support firmware, could consider use firmware as mid-man between DPDK and kernel.
>
>>
Hello, fengchenwen,

Thanks for your reply.
Sorry for not describing it clearly. We know how to implement the 
bifurcation functionality. The main issue is that ioctl is used 
forcommunication with the kernel driver by PMD, but ioctl is not 
considered a good API, we need to find a better approach. Implemented 
via firmware might be a good idea, but it's complex, we can think about 
it in the further.Recently shoud I consider using read and write 
instead?  Is there any advise?

-- 
Thanks,
WanRenyong

  reply	other threads:[~2024-09-13  2:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-11  2:07 WanRenyong
2024-09-11  3:48 ` Stephen Hemminger
2024-09-12  4:07   ` WanRenyong
2024-09-11  3:49 ` Stephen Hemminger
2024-09-12  4:07   ` WanRenyong
2024-09-11  3:50 ` Stephen Hemminger
2024-09-12  4:14   ` WanRenyong
2024-09-12  5:50     ` Stephen Hemminger
2024-09-12  8:19       ` WanRenyong
2024-09-12  9:18         ` fengchengwen
2024-09-13  2:55           ` WanRenyong [this message]
2024-09-14  2:54             ` Stephen Hemminger
2024-09-14  6:33               ` fengchengwen

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=a449904c-80cf-4ba3-8b07-a5d5606ba777@yunsilicon.com \
    --to=wanry@yunsilicon.com \
    --cc=dev@dpdk.org \
    --cc=fengchengwen@huawei.com \
    --cc=ferruh.yigit@amd.com \
    --cc=stephen@networkplumber.org \
    --cc=thomas@monjalon.net \
    /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).