From: "yukuai (C)" <yukuai3@huawei.com>
To: Jens Axboe <axboe@kernel.dk>, <paolo.valente@linaro.org>
Cc: <jack@suse.cz>, <tj@kernel.org>, <linux-block@vger.kernel.org>,
<cgroups@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<yi.zhang@huawei.com>
Subject: Re: [PATCH -next v5 0/3] support concurrent sync io for bfq on a specail occasion
Date: Mon, 23 May 2022 09:10:38 +0800 [thread overview]
Message-ID: <55919e29-1f22-e8aa-f3d2-08c57d9e1c22@huawei.com> (raw)
In-Reply-To: <d5a90a08-1ac6-587a-e900-0436bd45543a@kernel.dk>
在 2022/05/21 20:21, Jens Axboe 写道:
> On 5/21/22 1:22 AM, yukuai (C) wrote:
>> 在 2022/05/14 17:29, yukuai (C) 写道:
>>> 在 2022/05/05 9:00, yukuai (C) 写道:
>>>> Hi, Paolo
>>>>
>>>> Can you take a look at this patchset? It has been quite a long time
>>>> since we spotted this problem...
>>>>
>>>
>>> friendly ping ...
>> friendly ping ...
>
> I can't speak for Paolo, but I've mentioned before that the majority
> of your messages end up in my spam. That's still the case, in fact
> I just marked maybe 10 of them as not spam.
>
> You really need to get this issued sorted out, or you will continue
> to have patches ignore because folks may simply not see them.
>
Hi,
Thanks for your notice.
Is it just me or do you see someone else's messages from *huawei.com
end up in spam? I tried to seek help from our IT support, however, they
didn't find anything unusual...
next prev parent reply other threads:[~2022-05-23 1:10 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-28 12:08 Yu Kuai
2022-04-28 12:08 ` [PATCH -next v5 1/3] block, bfq: record how many queues are busy in bfq_group Yu Kuai
2022-04-28 12:45 ` Jan Kara
2022-04-28 12:08 ` [PATCH -next v5 2/3] block, bfq: refactor the counting of 'num_groups_with_pending_reqs' Yu Kuai
2022-04-28 12:08 ` [PATCH -next v5 3/3] block, bfq: do not idle if only one group is activated Yu Kuai
2022-05-05 1:00 ` [PATCH -next v5 0/3] support concurrent sync io for bfq on a specail occasion yukuai (C)
2022-05-14 9:29 ` yukuai (C)
2022-05-21 7:22 ` yukuai (C)
2022-05-21 12:21 ` Jens Axboe
2022-05-23 1:10 ` yukuai (C) [this message]
2022-05-23 1:24 ` Jens Axboe
2022-05-23 8:18 ` Yu Kuai
2022-05-23 12:36 ` Jens Axboe
2022-05-23 12:58 ` Yu Kuai
2022-05-23 13:29 ` Jens Axboe
2022-05-23 8:59 ` Jan Kara
2022-05-23 12:36 ` Jens Axboe
2022-05-23 15:25 ` Jan Kara
2022-05-24 1:13 ` Yu Kuai
2022-06-01 6:16 ` Jens Axboe
2022-06-01 7:19 ` Yu Kuai
2022-06-07 3:10 ` Yu Kuai
2022-06-07 9:54 ` Jan Kara
2022-06-07 11:51 ` Yu Kuai
2022-06-07 13:06 ` Yu Kuai
2022-06-07 20:30 ` Jan Kara
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=55919e29-1f22-e8aa-f3d2-08c57d9e1c22@huawei.com \
--to=yukuai3@huawei.com \
--cc=axboe@kernel.dk \
--cc=cgroups@vger.kernel.org \
--cc=jack@suse.cz \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paolo.valente@linaro.org \
--cc=tj@kernel.org \
--cc=yi.zhang@huawei.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
all inboxes | Powered by JetHome®