DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Tom Jones" <thj@freebsd.org>
To: "Bruce Richardson" <bruce.richardson@intel.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH] freebsd: Add support for multiple dpdk instances on FreeBSD
Date: Fri, 03 May 2024 14:12:58 +0100	[thread overview]
Message-ID: <005a46b7-e86e-4530-80e8-955bc0cb5411@app.fastmail.com> (raw)
In-Reply-To: <ZjTgrbHoxN-7awzw@bricha3-mobl1.ger.corp.intel.com>

Hi Bruce,

thanks for letting me know

I'm not tied to anything particularly. This change isn't compatible with the previous API, but I'm not against making it so if that is really the best thing to do. As is, the dpdk changes and the contigmem changes need to come together because the API changes for getting the physical addresses.

It is just the sysctl paths that differ. I'm not sure what the compatibility needs to be for DPDK, for all of my usage I have built the kernel module with the package - making API changes easy.

I'm happy to follow which ever path you think is best.

Sorry for the patch confusion, I'll try to keep the sequence obvious going forward.

Tom

On Fri, May 3, 2024, at 14:03, Bruce Richardson wrote:
> On Fri, May 03, 2024 at 09:46:15AM +0000, Tom Jones wrote:
>> Add support to the contigmem module on FreeBSD for multiple concurrent
>> files, this enables running multiple dpdk instances with the nic_uio
>> driver.
>> 
>> Add relevant parts in dpdk to support this.
>> 
>> Signed-off-by: Tom Jones <thj@freebsd.org> ---
>
> Thanks for these patches, I hope to review and test them soon.  From an
> initial quick scan through, I think the changes may be easier reviewed if
> split up into more than one patch. For example, could the changes to move
> the "SYSCTL_INT" declarations from being in global to local scope be
> separated out into one patch? Also, if the kernel module changes are
> backward compatible, they could be in a separate patch to the userspace 
> changes to take advantage of the kernel module enhancements.
>
> Is such a split possible or are all the changes tightly tied together?
>
> /Bruce
>
> PS: For sending new versions of this patch, or as a patchset, please add a
> version number so we can track what version is the latest one in patchwork
> and on the mailing list. [Use -v<N> flag to git format-patch] Thanks.

-- 
- Tom

  reply	other threads:[~2024-05-03 13:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-02 13:55 Tom Jones
2024-05-03  9:46 ` Tom Jones
2024-05-03 13:03   ` Bruce Richardson
2024-05-03 13:12     ` Tom Jones [this message]
2024-05-03 13:24       ` Bruce Richardson
2024-05-03 16:25   ` Bruce Richardson
2024-05-03 16:48   ` Bruce Richardson
2024-05-03 16:52     ` Bruce Richardson
2024-05-06 15:34       ` Tom Jones

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=005a46b7-e86e-4530-80e8-955bc0cb5411@app.fastmail.com \
    --to=thj@freebsd.org \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.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).