> -----Original Message----- > From: Greg KH [mailto:gregkh@xxxxxxxxxxxxxxxxxxx] > Sent: Friday, March 7, 2014 12:19 PM > To: KY Srinivasan > Cc: linux-kernel@xxxxxxxxxxxxxxx; devel@xxxxxxxxxxxxxxxxxxxxxx; > olaf@xxxxxxxxx; apw@xxxxxxxxxxxxx; jasowang@xxxxxxxxxx > Subject: Re: [PATCH 1/1] Drivers: hv: vmbus: Include the limit on the number > of pfns we can handle > > On Thu, Mar 06, 2014 at 11:15:08PM -0800, K. Y. Srinivasan wrote: > > Increase the maximum number of pfns we can handle is a single vmbus > packet. > > Is that a correct sentance? I will fix the typo in the sentence. > > > > > > Signed-off-by: K. Y. Srinivasan <kys@xxxxxxxxxxxxx> > > --- > > include/linux/hyperv.h | 2 +- > > 1 files changed, 1 insertions(+), 1 deletions(-) > > > > diff --git a/include/linux/hyperv.h b/include/linux/hyperv.h index > > 330ec44..ab7359f 100644 > > --- a/include/linux/hyperv.h > > +++ b/include/linux/hyperv.h > > @@ -37,7 +37,7 @@ > > #include <linux/mod_devicetable.h> > > > > > > -#define MAX_PAGE_BUFFER_COUNT 19 > > +#define MAX_PAGE_BUFFER_COUNT 32 > > What is the problem if this number isn't changed? On the networking side we may send frames that require more than 19 PFN entries. Number 32 is imposed by some limitations by the vmbus data structures. For some reason MAX_PAGE_BUFFER_COUNT was set to a lower value and I want to bump this up to what vmbus can support. > > Again, I'm going to have to ask you, what kernel is this for? > > Please remember this when sending patches that look like they might be > fixing a bug, you don't want me to guess, as my "guess" usually is "delete the > patch". Sorry Greg; this is not a bug fix and can go into the *next kernel. I will resend this patch after fixing the changelog comment. Regards, K. Y > > greg k-h _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
