From: Zhu Yanjun <zyjzyj2000@gmail.com>
To: "Håkon Bugge" <haakon.bugge@oracle.com>,
linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, rds-devel@oss.oracle.com
Cc: Jason Gunthorpe <jgg@ziepe.ca>, Leon Romanovsky <leon@kernel.org>,
Saeed Mahameed <saeedm@nvidia.com>,
Tariq Toukan <tariqt@nvidia.com>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Tejun Heo <tj@kernel.org>, Lai Jiangshan <jiangshanlai@gmail.com>,
Allison Henderson <allison.henderson@oracle.com>,
Manjunath Patil <manjunath.b.patil@oracle.com>,
Mark Zhang <markzhang@nvidia.com>,
Chuck Lever <chuck.lever@oracle.com>,
Shiraz Saleem <shiraz.saleem@intel.com>,
Yang Li <yang.lee@linux.alibaba.com>
Subject: Re: [PATCH 0/6] rds: rdma: Add ability to force GFP_NOIO
Date: Tue, 14 May 2024 14:02:22 +0200 [thread overview]
Message-ID: <54d14e4e-63e7-4bce-866f-0e2f2c801232@gmail.com> (raw)
In-Reply-To: <38a5ccc6-d0bc-41e0-99de-fe7902b1951f@linux.dev>
On 14.05.24 10:53, Zhu Yanjun wrote:
> On 13.05.24 14:53, Håkon Bugge wrote:
>> This series enables RDS and the RDMA stack to be used as a block I/O
>> device. This to support a filesystem on top of a raw block device
>
> This is to support a filesystem ... ?
Sorry. my bad. I mean, normally rds is used to act as a communication
protocol between Oracle databases. Now in this patch series, it seems
that rds acts as a communication protocol to support a filesystem. So I
am curious which filesystem that rds is supporting?
Thanks a lot.
Zhu Yanjun
>
>> which uses RDS and the RDMA stack as the network transport layer.
>>
>> Under intense memory pressure, we get memory reclaims. Assume the
>> filesystem reclaims memory, goes to the raw block device, which calls
>> into RDS, which calls the RDMA stack. Now, if regular GFP_KERNEL
>> allocations in RDS or the RDMA stack require reclaims to be fulfilled,
>> we end up in a circular dependency.
>>
>> We break this circular dependency by:
>>
>> 1. Force all allocations in RDS and the relevant RDMA stack to use
>> GFP_NOIO, by means of a parenthetic use of
>> memalloc_noio_{save,restore} on all relevant entry points.
>>
>> 2. Make sure work-queues inherits current->flags
>> wrt. PF_MEMALLOC_{NOIO,NOFS}, such that work executed on the
>> work-queue inherits the same flag(s).
>>
>> Håkon Bugge (6):
>> workqueue: Inherit NOIO and NOFS alloc flags
>> rds: Brute force GFP_NOIO
>> RDMA/cma: Brute force GFP_NOIO
>> RDMA/cm: Brute force GFP_NOIO
>> RDMA/mlx5: Brute force GFP_NOIO
>> net/mlx5: Brute force GFP_NOIO
>>
>> drivers/infiniband/core/cm.c | 15 ++++-
>> drivers/infiniband/core/cma.c | 20 ++++++-
>> drivers/infiniband/hw/mlx5/main.c | 22 +++++--
>> .../net/ethernet/mellanox/mlx5/core/main.c | 14 ++++-
>> include/linux/workqueue.h | 2 +
>> kernel/workqueue.c | 17 ++++++
>> net/rds/af_rds.c | 60 ++++++++++++++++++-
>> 7 files changed, 138 insertions(+), 12 deletions(-)
>>
>> --
>> 2.39.3
>>
>
--
Best
next prev parent reply other threads:[~2024-05-14 12:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-13 12:53 [PATCH 0/6] rds: rdma: Add ability to force GFP_NOIO Håkon Bugge
2024-05-13 12:53 ` [PATCH 1/6] workqueue: Inherit NOIO and NOFS alloc flags Håkon Bugge
2024-05-13 16:48 ` Tejun Heo
2024-05-14 13:48 ` Haakon Bugge
2024-05-14 16:49 ` Tejun Heo
2024-05-15 14:11 ` Haakon Bugge
2024-05-13 12:53 ` [PATCH 2/6] rds: Brute force GFP_NOIO Håkon Bugge
2024-05-13 18:04 ` kernel test robot
2024-05-13 18:14 ` Simon Horman
2024-05-14 13:31 ` Haakon Bugge
2024-05-13 12:53 ` [PATCH 3/6] RDMA/cma: " Håkon Bugge
2024-05-13 12:53 ` [PATCH 4/6] RDMA/cm: " Håkon Bugge
2024-05-13 12:53 ` [PATCH 5/6] RDMA/mlx5: " Håkon Bugge
2024-05-13 12:53 ` [PATCH 6/6] net/mlx5: " Håkon Bugge
2024-05-13 23:03 ` [PATCH 0/6] rds: rdma: Add ability to " Jason Gunthorpe
2024-05-14 18:19 ` Haakon Bugge
2024-05-17 17:30 ` Jason Gunthorpe
2024-05-14 8:53 ` Zhu Yanjun
2024-05-14 12:02 ` Zhu Yanjun [this message]
2024-05-14 18:32 ` Haakon Bugge
2024-05-15 10:25 ` Zhu Yanjun
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=54d14e4e-63e7-4bce-866f-0e2f2c801232@gmail.com \
--to=zyjzyj2000@gmail.com \
--cc=allison.henderson@oracle.com \
--cc=chuck.lever@oracle.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=haakon.bugge@oracle.com \
--cc=jgg@ziepe.ca \
--cc=jiangshanlai@gmail.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=manjunath.b.patil@oracle.com \
--cc=markzhang@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rds-devel@oss.oracle.com \
--cc=saeedm@nvidia.com \
--cc=shiraz.saleem@intel.com \
--cc=tariqt@nvidia.com \
--cc=tj@kernel.org \
--cc=yang.lee@linux.alibaba.com \
/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).