From: Eli Cohen <eli-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
To: Or Gerlitz <ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Cc: Eli Cohen <eli-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>,
Bart Van Assche <bvanassche-HInyCGIudOg@public.gmane.org>,
Chris Moore <Chris.Moore-laKkSmNT4hbQT0dZR+AlfA@public.gmane.org>,
"linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"Nicholas A. Bellinger"
<nab-IzHhD5pYlfBP7FQvKIMDCQ@public.gmane.org>
Subject: Re: Can someone help me understand the reason for this code in ib_isert.c?
Date: Tue, 28 Oct 2014 12:55:08 +0200 [thread overview]
Message-ID: <20141028105508.GC742@mtldesk30> (raw)
In-Reply-To: <544F6A8E.9000400-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
On Tue, Oct 28, 2014 at 12:06:06PM +0200, Or Gerlitz wrote:
> >we already have reported max_sge value. Maybe what we need is another
> >field, "guarnateed_num_sge" so applicatios providing this value can be
> >sure it would succeed (or there is some other problem). Then they can
> >either use this value or iterate from max_sge down to
> >guarnateed_num_sge to find the highest possible value.
> >
> Eli, can we be a bit more restrictive and report something which
> would work?
I don't think this is the right approach because it would cause
applications to ask for values lower than they could succeed and the
spec does not require it.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2014-10-28 10:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-20 15:29 Can someone help me understand the reason for this code in ib_isert.c? Chris Moore
[not found] ` <462EF229174FDB4D92ACE4656EA5610051E2EEF9-DWYeeINJQrxExQ8dmkPuX0M9+F4ksjoh@public.gmane.org>
2014-10-20 21:13 ` Or Gerlitz
[not found] ` <CAJ3xEMjmmt1guJO8rF6ChnTq-ZQbt9dpb_hwsNQCR65C79waRQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-10-22 5:06 ` Nicholas A. Bellinger
[not found] ` <1413954397.30983.33.camel-XoQW25Eq2zviZyQQd+hFbcojREIfoBdhmpATvIKMPHk@public.gmane.org>
2014-10-22 9:02 ` Or Gerlitz
2014-10-22 21:50 ` Nicholas A. Bellinger
2014-10-29 18:05 ` Chris Moore
[not found] ` <462EF229174FDB4D92ACE4656EA5610051E396BE-DWYeeINJQrxExQ8dmkPuX0M9+F4ksjoh@public.gmane.org>
2014-10-30 8:24 ` Sagi Grimberg
2014-10-30 15:06 ` Chris Moore
2014-10-22 11:39 ` Sagi Grimberg
2014-10-23 7:43 ` Eli Cohen
2014-10-26 12:57 ` Bart Van Assche
[not found] ` <544CEFBD.2090405-HInyCGIudOg@public.gmane.org>
2014-10-26 14:08 ` Eli Cohen
2014-10-28 10:06 ` Or Gerlitz
[not found] ` <544F6A8E.9000400-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2014-10-28 10:55 ` Eli Cohen [this message]
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=20141028105508.GC742@mtldesk30 \
--to=eli-ldsdmyg8hgv8yrgs2mwiifqbs+8scbdb@public.gmane.org \
--cc=Chris.Moore-laKkSmNT4hbQT0dZR+AlfA@public.gmane.org \
--cc=bvanassche-HInyCGIudOg@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=nab-IzHhD5pYlfBP7FQvKIMDCQ@public.gmane.org \
--cc=ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.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