All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Dickson <SteveD@redhat.com>
To: "David Härdeman" <david@hardeman.nu>
Cc: Timo Teras <timo.teras@iki.fi>, linux-nfs@vger.kernel.org
Subject: Re: [PATCH v2 0/5] rework access to /proc/net/rpc
Date: Tue, 09 Dec 2014 16:30:52 -0500	[thread overview]
Message-ID: <54876A0C.3090109@RedHat.com> (raw)
In-Reply-To: <20141209202652.GA32738@hardeman.nu>



On 12/09/2014 03:26 PM, David Härdeman wrote:
> On Tue, Dec 09, 2014 at 11:08:39AM -0500, Steve Dickson wrote:
>> On 12/09/2014 09:01 AM, David Härdeman wrote:
>>> On 2014-12-09 09:42, Timo Teras wrote:
>>>> On Tue, 09 Dec 2014 09:16:59 +0100
>>>> David Härdeman <david@hardeman.nu> wrote:
>>>>> 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?
>>>
>>> I agree that it depends on your view. I tend to be very sceptical of arbitrary 
>>> limitations unless they have a very good reason (like measurable and relevant 
>>> performance impact), I doubt that's the case here.
>> Your skeptical-ability of arbitrary limitations has become very clear in 
>> the last few hours... ;-) I guess I'm indifferent about it... From reading
>> your gssd patch set, it is a bit more artful not to use fixed size buffers
>> but again, I'm indifferent... That said... if patches appear removing these
>> fixed buffers they definitely would be considered... 
>>
>>>
>>> It's up to the maintainer though, I just wanted to point it out :)
>> My understanding these patches were needed to make nfs-utils compatible with the musl c-library.
>> That is the case, correct? 
> 
> The fread/fwrite removal seems reasonable, yes. The removal of the
> readline() function though (which could be implemented using normal
> read/malloc/realloc) seems less so.....IMHO.
> 
Patches welcome! 8-)

steved.

  reply	other threads:[~2014-12-09 21:31 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
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 [this message]
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=54876A0C.3090109@RedHat.com \
    --to=steved@redhat.com \
    --cc=david@hardeman.nu \
    --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.