All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David Härdeman" <david@hardeman.nu>
To: linux-nfs@vger.kernel.org
Cc: SteveD@redhat.com, timo.teras@iki.fi
Subject: Re: [PATCH v2 0/5] rework access to /proc/net/rpc
Date: Tue, 09 Dec 2014 09:16:59 +0100	[thread overview]
Message-ID: <399e974867e03c052fedfa8e8fd688ca@hardeman.nu> (raw)

Hi,

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?

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

//David


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

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-09  8:16 David Härdeman [this message]
2014-12-09  8:42 ` [PATCH v2 0/5] rework access to /proc/net/rpc Timo Teras
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=399e974867e03c052fedfa8e8fd688ca@hardeman.nu \
    --to=david@hardeman.nu \
    --cc=SteveD@redhat.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=timo.teras@iki.fi \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.