public inbox for gwml@vger.gnuweeb.org
 help / color / mirror / Atom feed
From: Alviro Iskandar Setiawan <alviro.iskandar@gnuweeb.org>
To: Ahmad Gani <reyuki@gnuweeb.org>
Cc: Ammar Faizi <ammarfaizi2@gnuweeb.org>,
	"GNU/Weeb Mailing List" <gwml@vger.gnuweeb.org>
Subject: Re: [PATCH gwproxy v4 4/6] dnslookup: Initial work for implementation of C-ares-like getaddrinfo function
Date: Wed, 6 Aug 2025 18:20:10 +0700	[thread overview]
Message-ID: <CAOG64qNGUiw2WnxXOQFYAFt89mTVbTyGYXpdvphvf3eRDsseyg@mail.gmail.com> (raw)
In-Reply-To: <CAOG64qMnayX=Oi=qYQJZcu7++s_DjvJOdVXg078HEXHHYU-tCQ@mail.gmail.com>

On Wed, Aug 6, 2025 at 6:09 PM Alviro Iskandar Setiawan wrote:
> On Wed, Aug 6, 2025 at 10:57 AM Ahmad Gani wrote:
> > Introducing glibc's getaddrinfo replacement, the DNS protocol
> > implementation is limited to standard query (OPCODE_QUERY) as for now,
> > but may extended later as necessary.
>
> Thinking about this further, I think this design is wrong. The DNS
> library is expected to only handle bytes processing, leaving the
> networking stack to the caller.
>
> Think, how is it going to be integrated with io_uring?
>
> We should let the caller perform the recv and send. This library
> doesn't need to care about the networking stack at all. Make it the
> caller's responsibility to feed the library with bytes from the
> network.

Please take a look at src/gwproxy/socks5.c

That's a perfect example of socks5 bytes processing without
networking. Purely bytes parsing.

That way you can use io_uring, epoll, or whatever shiny features, even
statically allocated fake bytes work.

-- Viro

  reply	other threads:[~2025-08-06 11:20 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-06  3:57 [PATCH gwproxy v4 0/6] Initial work for DNS lookup implementation Ahmad Gani
2025-08-06  3:57 ` [PATCH gwproxy v4 1/6] dnslookup: Split common functionality and struct into net.h and net.c Ahmad Gani
2025-08-06  6:18   ` Alviro Iskandar Setiawan
2025-08-06  3:57 ` [PATCH gwproxy v4 2/6] dnslookup: Add a new parameter default_port Ahmad Gani
2025-08-06  6:20   ` Alviro Iskandar Setiawan
2025-08-06  3:57 ` [PATCH gwproxy v4 3/6] dnslookup: Allow only port string number Ahmad Gani
2025-08-06  3:57 ` [PATCH gwproxy v4 4/6] dnslookup: Initial work for implementation of C-ares-like getaddrinfo function Ahmad Gani
2025-08-06  6:40   ` Alviro Iskandar Setiawan
2025-08-06  6:51     ` Alviro Iskandar Setiawan
2025-08-06  8:43       ` Ahmad Gani
2025-08-06  8:40     ` Ahmad Gani
2025-08-06 11:09   ` Alviro Iskandar Setiawan
2025-08-06 11:20     ` Alviro Iskandar Setiawan [this message]
2025-08-06 11:39       ` Ammar Faizi
2025-08-06 12:30         ` Ahmad Gani
2025-08-06 20:54           ` Ammar Faizi
2025-08-06 12:30       ` Ahmad Gani
2025-08-06 21:33         ` Ammar Faizi
2025-08-14  4:54           ` Ahmad Gani
2025-08-06  3:57 ` [PATCH gwproxy v4 5/6] dnsparser: Transaction id creation is delegated to caller Ahmad Gani
2025-08-06  6:28   ` Alviro Iskandar Setiawan
2025-08-06 10:20     ` Ahmad Gani
2025-08-06 10:51       ` Alviro Iskandar Setiawan
2025-08-06 12:29         ` Ahmad Gani
2025-08-06  3:57 ` [PATCH gwproxy v4 6/6] dnslookup: Make gw_ares_getaddrinfo asynchronous Ahmad Gani
2025-08-06  6:22   ` Alviro Iskandar Setiawan
2025-08-06  8:42     ` Ahmad Gani
2025-08-06  7:03 ` [PATCH gwproxy v4 0/6] Initial work for DNS lookup implementation Ammar Faizi
2025-08-06  7:08 ` Ammar Faizi
2025-08-06  8:37   ` Ahmad Gani
2025-08-06  8:58     ` Ammar Faizi
2025-08-06  9:47       ` Ammar Faizi
2025-08-06 20:50         ` Ammar Faizi
2025-08-06 22:14     ` Ammar Faizi
2025-08-06  7:08 ` (subset) " Ammar Faizi

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=CAOG64qNGUiw2WnxXOQFYAFt89mTVbTyGYXpdvphvf3eRDsseyg@mail.gmail.com \
    --to=alviro.iskandar@gnuweeb.org \
    --cc=ammarfaizi2@gnuweeb.org \
    --cc=gwml@vger.gnuweeb.org \
    --cc=reyuki@gnuweeb.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