patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>,
	David Marchand <david.marchand@redhat.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Chenbo Xia <chenbox@nvidia.com>,
	Fan Zhang <fanzhang.oss@gmail.com>,
	Jay Zhou <jianjay.zhou@huawei.com>,
	Anoob Joseph <anoobj@marvell.com>,
	Akhil Goyal <gakhil@marvell.com>,
	"stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [EXTERNAL] Re: [v6 1/5] vhost: skip crypto op fetch before vring init
Date: Fri, 28 Feb 2025 13:59:57 +0000	[thread overview]
Message-ID: <CO1PR18MB4714F4177DFF356821A12395CBCC2@CO1PR18MB4714.namprd18.prod.outlook.com> (raw)
In-Reply-To: <4407830e-f739-439e-8962-c1fcd80ade69@redhat.com>

Hi Maxime,

> 
> Before your series arrived, we were wondering if we should not deprecate Vhost
> crypto as it was not really maintained and we had no identified user.
> 
> Since it seems you are going to use it, which is great, would you commit to make
> the necessary changes to make it reliable? If yes, I would agree to take your v8 as
> is for v25.03 if proper rework is done for v25.07, would that work for you?
> 
I have sent v9 to include one additional patch to fix vhost_crypto_process_one_req()
thread safety attribute. Please consider it.

Yes, if any other changes are required, we can assist going forward. We also believe
this software backend needs to be reliable and hence can help test required virtio
functionalities.

Thanks,
Gowrishankar

Regards,
Gowrishankar

> Maxime


  reply	other threads:[~2025-02-28 14:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1740594750.git.gmuthukrishn@marvell.com>
2025-02-26 18:43 ` Gowrishankar Muthukrishnan
2025-02-27  9:15   ` Maxime Coquelin
2025-02-27  9:19     ` Maxime Coquelin
2025-02-27 13:15       ` [EXTERNAL] " Gowrishankar Muthukrishnan
2025-02-27 18:07         ` Gowrishankar Muthukrishnan
2025-02-28  8:48           ` David Marchand
2025-02-28  9:40             ` Maxime Coquelin
2025-02-28 13:59               ` Gowrishankar Muthukrishnan [this message]
2025-02-28 15:16                 ` Maxime Coquelin
2025-02-28 13:53             ` Gowrishankar Muthukrishnan
2025-02-26 18:43 ` [v6 3/5] examples/vhost_crypto: fix user callbacks Gowrishankar Muthukrishnan

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=CO1PR18MB4714F4177DFF356821A12395CBCC2@CO1PR18MB4714.namprd18.prod.outlook.com \
    --to=gmuthukrishn@marvell.com \
    --cc=anoobj@marvell.com \
    --cc=chenbox@nvidia.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=fanzhang.oss@gmail.com \
    --cc=gakhil@marvell.com \
    --cc=jianjay.zhou@huawei.com \
    --cc=maxime.coquelin@redhat.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).