From: Neil Brown <neilb@suse.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Olaf Kirch <okir@suse.de>, linux-nfs@vger.kernel.org
Subject: Re: [PATCH/RFC] sunrpc/cache: make cache flushing more reliable.
Date: Fri, 16 Oct 2015 08:57:23 +1100 [thread overview]
Message-ID: <874mhrx0ak.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <20151015135039.GB18976@fieldses.org>
[-- Attachment #1: Type: text/plain, Size: 995 bytes --]
"J. Bruce Fields" <bfields@fieldses.org> writes:
>>
>> I'll resend it people are otherwise happy.
>
> I'm otherwise happy! Looks like a reasonable approach.
>
> (The one thing I wonder is whether it would be clearer to outright fail
> writes that attempt to create already-expired cache entries.
>
> But I think that's an unimportant corner case really. And if there are
> existing cases where that's happening then perhaps it's less disruptive
> just to let them expire a second later rathern than to introduce a new
> error.)
I hadn't thought about. There is often a good case for failing a
meaningless value rather than silently doing something different.
Were I creating a new interface, I would probably do that.
But revising an old interface that doesn't currently return an error...
I agree with you that it is likely less disruptive to not introduce a
new error. Thanks for asking the question.
I'll post the proper patch separately.
Thanks,
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
next prev parent reply other threads:[~2015-10-15 21:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-15 6:31 [PATCH/RFC] sunrpc/cache: make cache flushing more reliable Neil Brown
2015-10-15 6:39 ` Neil Brown
2015-10-15 13:50 ` J. Bruce Fields
2015-10-15 21:57 ` Neil Brown [this message]
2015-10-15 21:59 ` [PATCH v2] " Neil Brown
2015-10-22 19:14 ` J. Bruce Fields
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=874mhrx0ak.fsf@notabene.neil.brown.name \
--to=neilb@suse.com \
--cc=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=okir@suse.de \
/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