public inbox for [email protected]
 help / color / mirror / Atom feed
From: Ammar Faizi <[email protected]>
To: Jens Axboe <[email protected]>
Cc: Praveen Kumar <[email protected]>, [email protected]
Subject: Re: io-uring
Date: Sun, 24 Oct 2021 10:22:03 +0700	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>


On Sat, 23 Oct 2021 09:02:24 -0600, Jens Axboe wrote:
>On 10/23/21 2:08 AM, Praveen Kumar wrote:
>> Hello,
>> 
>> I am Praveen and have worked on couple of projects in my professional
>> experience, that includes File system driver and TCP stack
>> development. I came across fs/io_uring.c and was interested to know
>> more in-depth about the same and the use-cases, this solves. In
>> similar regards, I read https://kernel.dk/io_uring.pdf and going
>> through liburing. I'm interested to add value to this project.
>> 
>> I didn't find any webpage or TODO items, which I can start looking
>> upon. Please guide me and let me know if there are any small items to
>> start with. Also, is there any irc channel or email group apart from
>> [email protected], where I can post my queries(design specific
>> or others).
>
>Great that you are interested! It's quite a fast moving project, but
>still plenty of things to tackle and improve. All discussion happens on
>the io-uring mailing list, we don't have a more realtime communication
>channel. Might make sense to setup a slack channel or something... But
>for now I'd encourage you to just participate on the mailing list, and
>question there are a good way to do it too.
>

Hello,

We have several unresolved issues on liburing GitHub repo. Maybe they
can be the TODO list?

Most of them are kernel side issue, so they need to be resolved from
io_uring.

Link: https://github.com/axboe/liburing/issues

I would love to contribute too. But my experience in kernel space
programming is not yet ready for that. I can test the patches. I
can also integrate the feature with liburing, create regression test,
and some userspace stuff work.

Recently, I nudged this one:
  https://github.com/axboe/liburing/issues/397

The work is to add recvfrom() and sendto() operation. You can CC me if
you're willing to pick up this work. I can do the liburing part and
create the test.

-- 
Ammar Faizi

  reply	other threads:[~2021-10-24  3:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-23  8:08 io-uring Praveen Kumar
2021-10-23 15:02 ` io-uring Jens Axboe
2021-10-24  3:22   ` Ammar Faizi [this message]
2021-10-25  9:22     ` io-uring Praveen Kumar

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