DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Pravin M Bathija <pravin.bathija@dell.com>
Cc: pravin.m.bathija.dev@gmail.com, boris.glimcher@dell.com,
	stable@dpdk.org,  dev@dpdk.org
Subject: Re: [PATCH 0/3] PATCH 25.03.0: vhost_user: configure memory slots
Date: Mon, 11 Aug 2025 15:21:45 +0200	[thread overview]
Message-ID: <2263105.NgBsaNRSFp@thomas> (raw)
In-Reply-To: <20250808051305.2386231-1-pravin.bathija@dell.com>

Welcome in DPDK community,

Thank you for contributing.
Please check this quick guide about our tools and process:
	https://core.dpdk.org/contribute/

There is a link to register to the dev mailing list
so your future patches and replies won't be moderated.
Note that you can disable receiving all list mails after registration
if it is too much for your box.

More comments below.

08/08/2025 07:13, Pravin M Bathija:
> add protocol feature support add and removal of memory
> regions/slots dynamically.
> this patch set has been tested with multiple instances of fio
> connected via libblkio to spdk target backed unix domain socket.
> please apply this this patch-set to dpdk mainline as well as
> version 25.03.0.

We didn't plan to maintain a branch for 25.03.
Do you think we should?
The next LTS branch will be 25.11.


> Pravin M Bathija (3):
>   mailmap: add user

This patch can be squashed with the next one,
but it is a detail which can be handled by the maintainer.

>   vhost_user: configure memory slots
>   vhost_user: support for memory regions




       reply	other threads:[~2025-08-11 13:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250808051305.2386231-1-pravin.bathija@dell.com>
2025-08-11 13:21 ` Thomas Monjalon [this message]
2025-08-12  2:43   ` Bathija, Pravin

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=2263105.NgBsaNRSFp@thomas \
    --to=thomas@monjalon.net \
    --cc=boris.glimcher@dell.com \
    --cc=dev@dpdk.org \
    --cc=pravin.bathija@dell.com \
    --cc=pravin.m.bathija.dev@gmail.com \
    --cc=stable@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).