public inbox for [email protected]
 help / color / mirror / Atom feed
From: Jens Axboe <[email protected]>
To: Stefano Garzarella <[email protected]>
Cc: [email protected], [email protected]
Subject: Re: [PATCH liburing 0/1] test: add epoll test case
Date: Mon, 27 Jan 2020 11:07:41 -0700	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <20200127180028.f7s5xhhizii3dsnr@steredhat>

On 1/27/20 11:00 AM, Stefano Garzarella wrote:
> On Mon, Jan 27, 2020 at 09:26:41AM -0700, Jens Axboe wrote:
>> On 1/27/20 9:17 AM, Stefano Garzarella wrote:
>>> Hi Jens,
>>> I wrote the test case for epoll.
>>>
>>> Since it fails also without sqpoll (Linux 5.4.13-201.fc31.x86_64),
>>> can you take a look to understand if the test is wrong?
>>>
>>> Tomorrow I'll travel, but on Wednesday I'll try this test with the patch
>>> that I sent and also with the upstream kernel.
>>
>> I'll take a look, but your patches are coming through garbled and don't
>> apply.
> 
> Weird, I'm using git-publish as usual. I tried to download the patch
> received from the ML, and I tried to reapply and it seams to work here.
> 
> Which kind of issue do you have? (just to fix my setup)

First I grabbed it from email, and I get the usual =3D (instead of =)
and =20 instead of a space. Longer lines also broken up, with an = at
the end.

Then I grabbed it from the lore io-uring archive, but it was the exact
same thing.

> Anyway I pushed my tree here:
>     https://github.com/stefano-garzarella/liburing.git epoll

As per other email, I think you're having some coordination issues
with the reaping and submitting side being separated. If the reaper
isn't keeping up, you'll get the -EBUSY problem I saw. I'm assuming
that's the failure case you are also seeing, you didn't actually
mention how it fails for you?

-- 
Jens Axboe


  reply	other threads:[~2020-01-27 18:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-27 16:17 [PATCH liburing 0/1] test: add epoll test case Stefano Garzarella
2020-01-27 16:17 ` [PATCH liburing 1/1] " Stefano Garzarella
2020-01-27 16:32   ` Jens Axboe
2020-01-27 18:25     ` Stefano Garzarella
2020-01-27 18:46       ` Jens Axboe
2020-01-27 18:50         ` Stefano Garzarella
2020-01-28 13:06         ` Stefano Garzarella
2020-01-27 16:26 ` [PATCH liburing 0/1] " Jens Axboe
2020-01-27 18:00   ` Stefano Garzarella
2020-01-27 18:07     ` Jens Axboe [this message]
2020-01-27 18:28       ` Stefano Garzarella

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 \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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