Linux NFS development
 help / color / mirror / Atom feed
From: Timo Teras <timo.teras@iki.fi>
To: "David Härdeman" <david@hardeman.nu>
Cc: linux-nfs@vger.kernel.org, SteveD@redhat.com
Subject: Re: [PATCH v2 0/5] rework access to /proc/net/rpc
Date: Tue, 9 Dec 2014 10:42:36 +0200	[thread overview]
Message-ID: <20141209104236.2204671c@vostro> (raw)
In-Reply-To: <399e974867e03c052fedfa8e8fd688ca@hardeman.nu>

On Tue, 09 Dec 2014 09:16:59 +0100
David Härdeman <david@hardeman.nu> wrote:

> it seems that the "rework access to /proc/net/rpc" patchset removed 
> dynamic buffers in favour of static, fixed size, buffers. That seems 
> like a step backwards to me?

Depends a bit on your view. On read() side, readline() like
functionality is removed yes. Though, my understanding is so that this
is not needed with the kernel API. Maybe someone can correct me if I'm
wrong. The removal simplifies memory management, overall code size. As
probably has a positive impact on speed too (probably not too big, but
this communication is used all overall, so it might be useful).

On write() side the old code was completely wrong. It did several
assumptions on how FILE buffering works, most of them being incorrect
in general, but also glibc. It only worked because no large messages
have been sent to kernel.

> At least the readline() function could be implemented using
> read/write (instead of fread/fwrite) and a dynamic buffer...no?

It's extra complexity. I'd rather not add it unless it's required. My
understanding about the communication mechanism with kernel is that
it's not required. Why have code that would never be used?

Thanks,
Timo

  reply	other threads:[~2014-12-09  8:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-09  8:16 [PATCH v2 0/5] rework access to /proc/net/rpc David Härdeman
2014-12-09  8:42 ` Timo Teras [this message]
2014-12-09 14:01   ` David Härdeman
2014-12-09 16:08     ` Steve Dickson
2014-12-09 20:26       ` David Härdeman
2014-12-09 21:30         ` Steve Dickson
2014-12-10  6:09           ` Timo Teras
2014-12-10 14:13             ` David Härdeman
  -- strict thread matches above, loose matches on Subject: below --
2014-10-02 13:41 Timo Teräs
2014-12-07 15:30 ` Steve Dickson

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=20141209104236.2204671c@vostro \
    --to=timo.teras@iki.fi \
    --cc=SteveD@redhat.com \
    --cc=david@hardeman.nu \
    --cc=linux-nfs@vger.kernel.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